From: Jeff Garzik <jeff@garzik.org>
To: David Chinner <dgc@sgi.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Regression: 2.6.22-rcX: hda: lost interrupt
Date: Fri, 29 Jun 2007 10:27:05 -0400 [thread overview]
Message-ID: <468516B9.1080300@garzik.org> (raw)
In-Reply-To: <20070629124248.GJ989688@sgi.com>
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.
Jeff
next prev parent reply other threads:[~2007-06-29 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 12:42 Regression: 2.6.22-rcX: hda: lost interrupt David Chinner
2007-06-29 14:27 ` Jeff Garzik [this message]
2007-07-04 10:20 ` David Chinner
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=468516B9.1080300@garzik.org \
--to=jeff@garzik.org \
--cc=dgc@sgi.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