From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: ACPI Developers <acpi-devel@lists.sourceforge.net>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.7 - ACPI still broken
Date: Wed, 16 Jun 2004 21:15:05 -0700 [thread overview]
Message-ID: <40D11AC9.3060009@backtobasicsmgmt.com> (raw)
In-Reply-To: <1087407777.2959.12.camel@forum-beta.geizhals.at>
Thomas Zehetbauer wrote:
> As posted on 2004-06-07 ACPI support seems to be broken for Intel
> D865PERL board since at least 2.6.7-rc2.
>
> When booting with the standard flags (nmi_watchdog=1 root=/dev/md0
> video=matroxfb:vesa:0x1bb) the kernel locks up with different error
> messages immediately after "ACPI: Subsystem revision 20040326". Adding
> "acpi=off" to the command line makes everything work again.
I have the same problem, using a D865GBF, which is nearly the same
board. BIOS is the most current version; booting with acpi=off allows
the boot to proceed and function normally. I've tried rebuilding without
"kernel IRQ balancing" and "register parameters" (which were my two most
recent config changes), but no improvement.
parent reply other threads:[~2004-06-17 4:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1087407777.2959.12.camel@forum-beta.geizhals.at>]
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=40D11AC9.3060009@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--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