public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: 12 Aug 2004 18:43:00 -0400	[thread overview]
Message-ID: <1092350580.7765.190.camel@dhcppc4> (raw)
In-Reply-To: <200408121550.15892.bjorn.helgaas@hp.com>

On Thu, 2004-08-12 at 17:50, Bjorn Helgaas wrote:
> 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
> 
> floppy_init() requests IRQ6, but then frees it before returning.  It
> looks like the driver only holds onto it while the device is actually
> open, which explains why it doesn't usually show up in
> /proc/interrupts.

ah, the mysterious floppy.c -- explained;-)

> Len later wrote:
> > I assert it is a BIOS bug for the BIOS to set LNKD to
> > IRQ6 if there is a floppy present and enabled; but fair
> > game if there is no floppy.  Though perhaps floppy.c
> > doesn't understand that.
> 
> Adrian has the floppies disabled in the BIOS, so maybe it's
> legit to use IRQ6 for the NIC PCI interrupt.  But floppy.c
> doesn't check for anything like that as far as I can see.
> 
> The fact that floppy.c seems to be able to poke the controller
> and get an interrupt back (with "pci=routeirq") suggests to me
> that the floppy controller responds even when disabled in the
> BIOS, and that it actually expects IRQ6 to be level-triggered,
> but the BIOS is leaving it configured as edge-triggered.

I expect that the the bug is that floppy.c, like other motherboard
devices, should take advantage of ACPI for device resource
enumeration.  This is one of the gaps I described at OLS,
and it is embodied in this bug report:
http://bugzilla.kernel.org/show_bug.cgi?id=2733

My expectation is that if the SETUP option is changed to
enable the floppy (the controller is probably burried inside
an LPC super-io or south bridge, even if there is no physical
drive in the box) Then we should see

ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 *6 7 10 11 12 14 15)
turn into

ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12 14 15)

with the * moving off of 6 (11 in this example) showing that
the BIOS selected a different active IRQ for this link.

Or even
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 *11 12 14 15)

Where IRQ6 is not in the possible-list, which would prevent
Linux from setting the device to that IRQ even if we wanted to.
(and again, the '*' on some other IRQ, 11 in this example)

Adrian, if you enable your not-present floppy in the BIOS,
what does Linux do?

thanks,
-Len



  reply	other threads:[~2004-08-12 22:46 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 ` 2.6.8-rc4-mm1 doesn't boot Len Brown
2004-08-11 21:37   ` 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 [this message]
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=1092350580.7765.190.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