From: Jody Bruchon <jody@nctritech.com>
To: linux-kernel@vger.kernel.org
Subject: ACPI+Inspiron 1545 = crash at xrstor_state()
Date: Fri, 12 Nov 2010 19:06:37 -0500 [thread overview]
Message-ID: <4CDDD68D.4050506@nctritech.com> (raw)
I previously reported a boot hang on an Inspiron 1545 laptop which is
cured by disabling CONFIG_ACPI. I didn't know about the "earlyprintk"
boot option, and upon using it, I was able to see the actual crash.
Hopefully the following information will help. Note that I have turned
off SMP and APIC/LAPIC support, but the bug persists even with these
disabled (I noticed a lot of APIC/IO-APIC code that is eliminated in
early boot if they're disabled.)
The crash was in function xsave_init with EIP at xstate_enable_boot_cpu
(the last normal message output before this was "Initializing CPU#0").
To narrow this down further, I edited xsave.c to be full of printk()
messages for each called function. The last printk message indicates
that the function in xsave.c which crashes out is:
xrstor_state(init_xstate_buf, -1);
The result is a general protection fault. xrstor_state is just a tiny
piece of asm code, and at this point I've reached the extent of my
current capabilities, so I don't know where to go from here. I can
manually type out chunks of the crash info on request. I'm clueless as
to how the inclusion of ACPI causes this.
Please CC my email if you respond since I don't subscribe to LKML.
Thanks in advance.
Jody Bruchon
next reply other threads:[~2010-11-13 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 0:06 Jody Bruchon [this message]
2010-11-14 12:17 ` ACPI+Inspiron 1545 = crash at xrstor_state() Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CDDD68D.4050506@nctritech.com \
--to=jody@nctritech.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.