From: Jos Hulzink <josh@stack.nl>
To: Matthew Harrell
<mharrell-dated-1049658915.d5a407@bittwiddlers.com>,
Matthew Harrell <lists-sender-14a37a@bittwiddlers.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: chris@wirex.com, andrew.grover@intel.com
Subject: Re: [Bug 529] New: ACPI under 2.5.50+ (approx) locks system hard during bootup
Date: Wed, 2 Apr 2003 01:07:58 +0200 [thread overview]
Message-ID: <200304020107.58676.josh@stack.nl> (raw)
In-Reply-To: <20030401195514.GA29214@bittwiddlers.com>
On Tuesday 01 April 2003 21:55, Matthew Harrell wrote:
> I've tried every kernel I could get to build up through 2.5.66 and nothing
> changed. Same behavior every time
>
> Also, I can get them all to boot into single user mode. I'm going to check
> if the hang is caused by the loading of the alsa modules (which run on the
> same interrupt) or something else.
The only way I can boot recent 2.5 kernels is to make sure my BIOS does
nothing that even smells like ACPI. The only response I got so far on the
lkml is "disable acpi support" and "disable apic support". The only
conclusion I can make is that the ACPI support in 2.5 is buggy enough to
prevent 2.5 to emerge into 2.6 for a long time from now, and unfortunately
nobody seems to care. I detected big IRQ / ACPI / APIC trouble since about
2.5.44 - 2.5.53, and nothing has changed since.
NFI, I just don't understand that a core problem that prevents me from booting
2.5 kernels, is noticed by so few others that it is able to remain unfixed
for so long.
Jos
next prev parent reply other threads:[~2003-04-01 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 19:20 Martin J. Bligh
2003-04-01 19:47 ` Chris Wright
2003-04-01 19:55 ` Matthew Harrell
2003-04-01 23:07 ` Jos Hulzink [this message]
2003-04-01 23:20 ` Matthew Harrell
2003-04-02 6:47 ` Jos Hulzink
2003-04-02 7:22 ` Zwane Mwaikambo
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=200304020107.58676.josh@stack.nl \
--to=josh@stack.nl \
--cc=andrew.grover@intel.com \
--cc=chris@wirex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists-sender-14a37a@bittwiddlers.com \
--cc=mharrell-dated-1049658915.d5a407@bittwiddlers.com \
/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
all inboxes | Powered by JetHome®