From: Ian Pilcher <i.pilcher@comcast.net>
To: acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: More info on VP6 panics
Date: Sat, 17 Jan 2004 00:50:53 -0600 [thread overview]
Message-ID: <4008DB4D.8090407@comcast.net> (raw)
Background: I get a kernel panic when I boot 2.4.2{2,3,4} with ACPI on
my dual-processor Abit VP6. Compiling the kernel with CONFIG_DEBUG_SLAB
turned on allows it to boot, as does booting with "idle=poll".
I do not believe that the panic occurs anywhere in the ACPI code. From
what I can tell, the transition to ACPI mode causes the idle thread on
the other processor to panic.
I believe that I have identified the line of code that triggers the
panic. It is the actual transition to ACPI mode at
drivers/acpi/hardware/hwacpi.c, line 143. If I insert an infinite loop
before the call to acpi_os_write_port, the boot process simply hangs.
If I move the loop below the call to acpi_os_write_port, I get the same
old panic message.
How can I debug this further?
Thanks!
--
========================================================================
Ian Pilcher i.pilcher@comcast.net
========================================================================
reply other threads:[~2004-01-17 6:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4008DB4D.8090407@comcast.net \
--to=i.pilcher@comcast.net \
--cc=acpi-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox