From: Len Brown <len.brown@intel.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.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: 11 Aug 2004 17:32:00 -0400 [thread overview]
Message-ID: <1092259920.5021.117.camel@dhcppc4> (raw)
In-Reply-To: <566B962EB122634D86E6EE29E83DD808182C2B33@hdsmsx403.hd.intel.com>
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?
-Len
On Wed, 2004-08-11 at 16:33, Bjorn Helgaas wrote:
> On Tuesday 10 August 2004 5:56 pm, Adrian Bunk wrote:
> > On Tue, Aug 10, 2004 at 04:46:57PM -0600, Bjorn Helgaas wrote:
> > > On Tuesday 10 August 2004 11:32 am, Adrian Bunk wrote:
> > > > On Tue, Aug 10, 2004 at 09:59:18AM -0600, Bjorn Helgaas wrote:
> > > > > On Tuesday 10 August 2004 9:09 am, Adrian Bunk wrote:
> > > > > > 2.6.8-rc3-mm1 boots fine on my computer.
> > > > > > 2.6.8-rc4-mm1 doesn't boot.
> > > > > > 2.6.8-rc4-mm1 with pci=routeirq boots.
> > >
> > It happens before the
> > floppy0: no floppy controllers found
> > line.
> >
> > Could there be a problem because the floppy driver doesn't find
> > anything (there's currently no floppy drive in my computer)?
>
> Not only is your machine floppy drive-less, but the driver thinks you
> don't even have a floppy *controller*, which I assume is separate
> from the actual drive.
>
> What mainboard do you have? Does it boot without "pci=routeirq"
> if you turn CONFIG_BLK_DEV_FD off?
>
> The code in the floppy_init() -> user_reset_fdc() -> WAIT() ->
> wait_til_done() -> reset_fdc() path looks pretty scary if there
> really is no controller out there. I'd feel much better if
> we at least tried to use ACPI to figure out whether we have
> a controller before we try to talk to it.
>
> All that aside, I still don't see how the pci=routeirq change
> would affect the floppy driver. It does request_irq(6, ...),
> and it is interesting that you have this:
>
> ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 6
> ACPI: PCI interrupt 0000:00:04.0[A] -> GSI 6 (level, low) -> IRQ 6
>
> which is for your NIC. But the floppy controller isn't a PCI
> device, so the LNKD enable shouldn't matter to it.
>
> Let's see... you're using the PIC model. Maybe the floppy driver
> depends on the ACPI_IRQ_MODEL_PIC stuff in acpi_register_gsi()?
> Can you post the contents of /proc/interrupts with the floppy
> driver and "pci=routeirq"? It seems weird to have the floppy
> and the NIC share an IRQ, but it looks like that's what should
> be happening.
>
> Bjorn
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next parent reply other threads:[~2004-08-11 21:33 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 [this message]
2004-08-11 21:37 ` 2.6.8-rc4-mm1 doesn't boot Bjorn Helgaas
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=1092259920.5021.117.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=bunk@fs.tum.de \
--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