From: Matthew Harrell <lists-sender-14a37a@bittwiddlers.com>
To: Jos Hulzink <josh@stack.nl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 529] New: ACPI under 2.5.50+ (approx) locks system hard during bootup
Date: Tue, 01 Apr 2003 18:20:43 -0500 [thread overview]
Message-ID: <20030401232043.GA10066@bittwiddlers.com> (raw)
In-Reply-To: <200304020107.58676.josh@stack.nl>
I sympathize since I've been feeling the same way. When I mentioned it to
Andrew in response to another ACPI problem I saw posted he recommended I
send it via bugzilla to see if more people will pay attention then.
But, in the ACPI team's defense, I also have about three other computers with
ACPI that do work fine and I've seen a number of other people on the ACPI list
without problems. In my case it's annoying since it's my laptop which has
the problem and that's the only one that I really care about when it comes to
ACPI.
I suggest you read through my initial email and see if you find anything
unusually different in your setup. I'm not positive since I'm new to bugzilla
but if you do have anything different that you notice then go to
bugzilla.kernel.org under bug 529 and add on to the bug report. Sounds like
the more info the better for this bug
: 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.
--
Matthew Harrell The perversity of the universe
Bit Twiddlers, Inc. tends to a maximum.
mharrell@bittwiddlers.com
next prev parent reply other threads:[~2003-04-01 23:11 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
2003-04-01 23:20 ` Matthew Harrell [this message]
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=20030401232043.GA10066@bittwiddlers.com \
--to=lists-sender-14a37a@bittwiddlers.com \
--cc=josh@stack.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mharrell-dated-1049671247.27e955@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®