From: Thomas Gleixner <tglx@linutronix.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
netdev@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.6.21-rc3-git4 ata1.00: qc timeout (cmd 0xef) (crashdump kernel)
Date: Mon, 12 Mar 2007 17:47:44 +0100 [thread overview]
Message-ID: <1173718065.13341.96.camel@localhost.localdomain> (raw)
In-Reply-To: <45F581B9.9020005@gmail.com>
On Tue, 2007-03-13 at 01:37 +0900, Tejun Heo wrote:
> Michal Piotrowski wrote:
> > Calling initcall 0xc19154d8: piix_ide_init+0x0/0xbb()
> > Calling initcall 0xc19155b6: generic_ide_init+0x0/0x16()
> > Calling initcall 0xc191572e: ide_init+0x0/0x81()
> > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> > ICH5: IDE controller at PCI slot 0000:00:1f.1
> > irq 5: nobody cared (try booting with the "irqpoll" option)
> > [<c1604556>] show_trace_log_lvl+0x1a/0x2f
> > [<c1604c2c>] show_trace+0x12/0x14
> > [<c1604cde>] dump_stack+0x16/0x18
> > [<c164341c>] __report_bad_irq+0x39/0x79
> > [<c16435eb>] note_interrupt+0x18f/0x1c8
> > [<c1643ec6>] handle_level_irq+0x95/0xcb
> > [<c1605dd8>] do_IRQ+0xb4/0xe0
> > =======================
> > handlers:
> > [<c174f55e>] (skge_intr+0x0/0x3ff)
> > Disabling IRQ #5
> > ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
> > ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
> > ICH5: chipset revision 2
> > ICH5: not 100% native mode: will probe irqs later
> > ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:DMA
> > ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:DMA
> >
> > Is this an IDE or skge bug?
>
> It seems skge's. skge is screaming and kernel shuts down IRQ 5.
> ata_piix is unfortunately sharing the IRQ, so its IRQ doesn't get
> serviced and commands time out.
I doubt that. On my box the interrupt is solely used by ata_piix.
tglx
next prev parent reply other threads:[~2007-03-12 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6bffcb0e0703090857r14eda34bj92f3fd1d0008edb8@mail.gmail.com>
[not found] ` <45F51218.9030907@gmail.com>
2007-03-12 16:31 ` 2.6.21-rc3-git4 ata1.00: qc timeout (cmd 0xef) (crashdump kernel) Michal Piotrowski
2007-03-12 16:37 ` Tejun Heo
2007-03-12 16:47 ` Thomas Gleixner [this message]
2007-03-12 16:47 ` Tejun Heo
2007-03-12 17:36 ` Michal Piotrowski
2007-03-12 16:46 ` Thomas Gleixner
2007-03-12 16:56 ` Tejun Heo
2007-03-12 18:50 ` Stephen Hemminger
2007-03-12 19:03 ` Tejun Heo
2007-03-12 19:30 ` Stephen Hemminger
2007-03-12 19:40 ` Tejun Heo
2007-03-13 18:26 ` Michal Piotrowski
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=1173718065.13341.96.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).