Re: Regression: 2.6.22-rcX: hda: lost interrupt

[David Chinner <dgc@sgi.com>]

On Fri, Jun 29, 2007 at 10:27:05AM -0400, Jeff Garzik wrote:
> David Chinner wrote:
> >Folks,
> >
> >After updating an x86_64 machine from 2.6.21 to 2.6.22-rc6 and
> >fighting off the where-the-fuck-did-my-serial-console-go blues
> >(legacy_serial.force), I finally discovered why the damn thing
> >wasn't booting - the machine was sitting there in a loop outputting
> >"hda: lost interrupt" over and over again during hardware
> >discovery (hda = dvd drive).
> >
> >It doesn't happen on every boot - more boots hung than failed,
> >though, while I was trying to work out where my serial port
> >went and get some work done.
> >
> >Since I've had the console operative, the boot hangs are
> >basically like:
> >
> >ESB2: IDE controller at PCI slot 0000:00:1f.1
> >ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 20 (level, low) -> IRQ20
> >ESB2: chipset revision 9
> >ESB2: not 100% native mode: will probe irqs later
> >    ide0: DM-DMA at 0x50a0-0x50a7, BIOS settings: hda:DMA, hdb:pio
> >    ide1: DM-DMA at 0x50a8-0x50af, BIOS settings: hda:pio, hdb:pio
> >Probing IDE interface ide0...
> >hda: probing with STATUS(0xa0) instead of ALTSTATUS(0x58)
> >hda: <some ctrl char>, ATAPI UNKNOWN (type 31) drive
> >hdb: probing with STATUS(0xb0) instead of ALTSTATUS(0x00)
> >hdb: probing with STATUS(0xa1) instead of ALTSTATUS(0x51)
> >hdb: <some ctrl char>, ATAPI UNKNOWN (type 31) drive
> >hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete 
> >DataRequest }
> >hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
> >hda: set_drive_speed_status: error=0x04 { AbortedCommand }
> >ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> >hda: lost interrupt
> >hda: lost interrupt
> >hda: lost interrupt
> >hda: lost interrupt
> >hda: lost interrupt
> >hda: lost interrupt
> >hda: lost interrupt
> >hda: lost interrupt
> >hda: lost interrupt
> >hda: lost interrupt
> >hda: lost interrupt
> 
> What is the behavior under libata?
> 
> If you see timeouts/etc. there too, it might be an interrupt routing or 
> hardware problem.

Sorry to take so long to get back to this, Jeff.

I think the problem is on my side. It looks like a dodgy initrd
was causing the problems - a statically built kernel detects
the DVD drive without any issues so there may not be a problem
here at all. I'll continue trying to track down why the initrd
was not being built properly...

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group