From: Chris Wright <chrisw@osdl.org>
To: Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: Jeff Garzik <jgarzik@pobox.com>,
lkml <linux-kernel@vger.kernel.org>,
acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Re: [PATCH] Next round of ACPI IRQ fixes (VIA ACPI fixed)
Date: Wed, 10 Sep 2003 18:36:55 -0700 [thread overview]
Message-ID: <20030910183655.H9800@osdlab.pdx.osdl.net> (raw)
In-Reply-To: <200309061332.39489.adq_dvb@lidskialf.net>; from adq_dvb@lidskialf.net on Sat, Sep 06, 2003 at 01:32:39PM +0100
* Andrew de Quincey (adq_dvb@lidskialf.net) wrote:
> On Saturday 06 September 2003 03:03, Chris Wright wrote:
> > You'll find dmesg and interrupts from pci=noacpi, acpi=off, disassembled
> > dsdt and dmidecode. Don't have the failed boot dmesg yet. I ported
> > netconsole to my eth driver, but it's not yet working.
>
> Cool, ta.. I'll have a look, but I'll probably need the failed dmesg to make
> any real progress.
Sorry, for the delay. I captured console output from failed (normal
acpi) boot. I also re-ran on 2.6.0-test5 and captured those outputs.
The test3-bk3 is actually test3-bk2+acpi_>15_irq.patch which is the
patch that began the breakage for me.
http://developer.osdl.org/chrisw/acpi/2.6.0-test3-bk3/
http://developer.osdl.org/chrisw/acpi/2.6.0-test5/
Each have dmesg and interrupts from pci=noacpi and acpi=off, dmesg with
acpi enabled, disassembled dsdt, and dmidecode.
Let me know if you need any more info.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2003-09-11 1:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 18:58 Andrew de Quincey
2003-09-05 21:35 ` Jeff Garzik
2003-09-05 23:16 ` [ACPI] " Andrew de Quincey
2003-09-05 22:28 ` Jeff Garzik
2003-09-05 22:28 ` Andrew Morton
2003-09-05 22:56 ` Randy.Dunlap
2003-09-06 0:15 ` [PATCH] 2.4.23-pre3 ACPI fixes series (1/3) Andrew de Quincey
2003-09-10 11:45 ` Bernhard Rosenkraenzer
2003-09-10 21:27 ` Andrew de Quincey
2003-09-10 15:31 ` Daniel Egger
2003-09-06 0:15 ` [PATCH] 2.4.23-pre3 ACPI fixes series (2/3) Andrew de Quincey
2003-09-06 0:15 ` [PATCH] 2.4.23-pre3 ACPI fixes series (3/3) Andrew de Quincey
2003-09-06 0:57 ` [PATCH] 2.6.0-test4 ACPI fixes series (1/4) Andrew de Quincey
2003-09-06 0:57 ` [PATCH] 2.6.0-test4 ACPI fixes series (2/4) Andrew de Quincey
2003-09-06 0:57 ` [PATCH] 2.6.0-test4 ACPI fixes series (3/4) Andrew de Quincey
2003-09-06 0:57 ` [PATCH] 2.6.0-test4 ACPI fixes series (4/4) Andrew de Quincey
2003-09-06 1:22 ` Jeff Garzik
2003-09-06 12:27 ` [ACPI] " Andrew de Quincey
2003-09-06 13:45 ` Andi Kleen
2003-09-08 19:46 ` Mikael Pettersson
2003-09-06 15:47 ` [ACPI] " Alan Cox
2003-09-07 14:54 ` Andrew de Quincey
2003-09-07 17:59 ` Alan Cox
2003-09-07 20:19 ` Andrew de Quincey
2003-09-06 0:02 ` [ACPI] Re: [PATCH] Next round of ACPI IRQ fixes (VIA ACPI fixed) Chris Wright
2003-09-06 1:21 ` Andrew de Quincey
2003-09-06 0:30 ` Jeff Garzik
2003-09-06 2:03 ` Chris Wright
2003-09-06 12:32 ` Andrew de Quincey
2003-09-11 1:36 ` Chris Wright [this message]
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=20030910183655.H9800@osdlab.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=adq_dvb@lidskialf.net \
--cc=jgarzik@pobox.com \
--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
all inboxes | Powered by JetHome®