From: Dominik Brodowski <devel-JhLEnvuH02M@public.gmane.org>
To: Aaron Gaudio
<prothonotar-2LEdZMXKCZJeeLb3ft/vUmD2FQJk+8+b@public.gmane.org>
Cc: Linux ACPI Devel Mailing List
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Failure w/ latest ACPI patch...
Date: Tue, 30 Jul 2002 16:54:33 +0200 [thread overview]
Message-ID: <20020730165433.A1445@brodo.de> (raw)
In-Reply-To: <20020729210341.B11837-2LEdZMXKCZJeeLb3ft/vUmD2FQJk+8+b@public.gmane.org>; from prothonotar-2LEdZMXKCZJeeLb3ft/vUmD2FQJk+8+b@public.gmane.org on Mon, Jul 29, 2002 at 09:03:41PM -0400
Hi,
Intersting problem you're reporting here:
On Mon, Jul 29, 2002 at 09:03:41PM -0400, Aaron Gaudio wrote:
> I notice that in the acpi-patched version, there is some (possibly
> BIOS?) message before the actual dmesg output gets printed
Even before "uncompressing kernel...." ???
, and
> for at least one of those devices for which an IRQ is not found, it
> says it will use IRQ 255.
That's BAD. IRQ 255 does not exist on any known laptop, I dare to say.
> Unfortunately, because the boot sequence does not complete, I don't
> have the output of dmesg available for the failed boot (I can always
> attach one for the RH-based kernel, if anyone would like to see that).
Could you pass pci=noacpi to the ACPI kernel, and try if it boots, please?
Dominik
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
next prev parent reply other threads:[~2002-07-30 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 1:03 Failure w/ latest ACPI patch Aaron Gaudio
[not found] ` <20020729210341.B11837-2LEdZMXKCZJeeLb3ft/vUmD2FQJk+8+b@public.gmane.org>
2002-07-30 14:54 ` Dominik Brodowski [this message]
[not found] ` <20020730165433.A1445-JhLEnvuH02M@public.gmane.org>
2002-07-31 2:14 ` Aaron Gaudio
2002-07-31 3:15 ` Sérgio Monteiro Basto
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=20020730165433.A1445@brodo.de \
--to=devel-jhlenvuh02m@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=prothonotar-2LEdZMXKCZJeeLb3ft/vUmD2FQJk+8+b@public.gmane.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