public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc4-mm1 doesn't boot
Date: 11 Aug 2004 18:22:09 -0400	[thread overview]
Message-ID: <1092262929.7765.132.camel@dhcppc4> (raw)
In-Reply-To: <20040811215105.GK26174@fs.tum.de>

Does the system have any BIOS settings to enable/disable the floppy?
Is the floppy physically present on the system?

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

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.

-Len

On Wed, 2004-08-11 at 17:51, Adrian Bunk wrote:
> On Wed, Aug 11, 2004 at 05:32:00PM -0400, 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?
> 
> Yes, this is my 2.6.8-rc3-mm1 /proc/interrupts :
> 
> <--  snip  -->
> 
>            CPU0       
>   0:   17615908          XT-PIC  timer
>   1:      22333          XT-PIC  i8042
>   2:          0          XT-PIC  cascade
>   6:      94751          XT-PIC  eth0
>   8:          4          XT-PIC  rtc
>   9:          0          XT-PIC  acpi
>  10:       5119          XT-PIC  ehci_hcd
>  11:    1329292          XT-PIC  Ensoniq AudioPCI, radeon@PCI:1:0:0
>  12:     118130          XT-PIC  i8042
>  14:      44614          XT-PIC  ide0
>  15:         24          XT-PIC  ide1
> NMI:          0 
> ERR:          8
> 
> <--  snip  -->
> 
> 
> > -Len
> 
> cu
> Adrian
> 
> -- 
> 
>        "Is there not promise of rain?" Ling Tan asked suddenly out
>         of the darkness. There had been need of rain for many days.
>        "Only a promise," Lao Er said.
>                                        Pearl S. Buck - Dragon Seed
> 


  reply	other threads:[~2004-08-11 22:23 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 [this message]
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=1092262929.7765.132.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