From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Len Brown <len.brown@intel.com>
Cc: Adrian Bunk <bunk@fs.tum.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc4-mm1 doesn't boot
Date: Wed, 11 Aug 2004 15:37:42 -0600 [thread overview]
Message-ID: <200408111537.42598.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <1092259920.5021.117.camel@dhcppc4>
On Wednesday 11 August 2004 3:32 pm, Len Brown wrote:
> I've never understood this floppy IRQ6 business.
> Apparently it requests IRQ6, but doesn't show up in /proc/interrupts
>
> In any case, dropping a PCI interrupt on IRQ6 would surely break it
> b/c that would set that IRQ6 to level trigger.
>
> Before this change, did LNKD get set to something other than IRQ6?
I don't think so. Adrian originally posted[1] a 2.6.8-rc3-mm1 boot log
(this was before the change):
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 *6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 6
ACPI: PCI interrupt 0000:00:04.0[A] -> GSI 6 (level, low) -> IRQ 6
[1]: http://groups.google.com/groups?dq=&hl=en&lr=&ie=UTF-8&c2coff=1&th=cfe35677cfe8e54b
next prev parent reply other threads:[~2004-08-11 21:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <566B962EB122634D86E6EE29E83DD808182C2B33@hdsmsx403.hd.intel.com>
2004-08-11 21:32 ` Len Brown
2004-08-11 21:37 ` Bjorn Helgaas [this message]
2004-08-11 21:51 ` Adrian Bunk
2004-08-11 22:22 ` Len Brown
2004-08-11 23:15 ` Adrian Bunk
2004-08-12 21:50 ` Bjorn Helgaas
2004-08-12 22:43 ` Len Brown
2004-08-13 0:23 ` Adrian Bunk
2004-08-13 21:15 ` Bjorn Helgaas
2004-08-13 23:55 ` Adrian Bunk
2004-08-14 2:22 ` Len Brown
2004-08-17 23:11 ` Adrian Bunk
2004-08-17 23:48 ` Len Brown
2004-08-10 7:21 2.6.8-rc4-mm1 Andrew Morton
2004-08-10 15:09 ` 2.6.8-rc4-mm1 doesn't boot Adrian Bunk
2004-08-10 15:59 ` Bjorn Helgaas
2004-08-10 17:32 ` Adrian Bunk
2004-08-10 22:46 ` Bjorn Helgaas
2004-08-10 23:56 ` Adrian Bunk
2004-08-11 20:33 ` Bjorn Helgaas
2004-08-11 23:23 ` Adrian Bunk
2004-08-11 9:56 ` Alan Cox
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=200408111537.42598.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--cc=len.brown@intel.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®