[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <454CDE6E.5000507@rtr.ca>
Date: Sat, 04 Nov 2006 13:39:42 -0500
From: Mark Lord <lkml@....ca>
To: Alberto Alonso <alberto@...ys.net>
Cc: linux-kernel@...r.kernel.org
Subject: Re: qstor driver -> irq 193: nobody cared
Alberto Alonso wrote:
> I have a Pacific Digital qstor card on irq 193. I am using kernel
> 2.6.17.13 SMP
>
> The error happens every now and then. I have not been able to
> figure out any triggers and I can not reproduce it on demand. Today
> it happened 3 times within a 40 minutes period.
>
> All disks connected to the card are disabled and I can't do anything
> other than a reboot to get them back.
>
> It is reported as follows:
>
> irq 193: nobody cared (try booting with the "irqpoll" option)
> <c013e19a> __report_bad_irq+0x2a/0xa0 <c013d970> handle_IRQ_event
> +0x30/0x70
> <c013e2b0> note_interrupt+0x80/0xf0 <c013da8c> __do_IRQ+0xdc/0xf0
> <c0105799> do_IRQ+0x19/0x30 <c010391a> common_interrupt+0x1a/0x20
> <c0100d91> default_idle+0x41/0x70 <c0100e60> cpu_idle+0x80/0x90
> <c046699d> start_kernel+0x18d/0x1d0 <c0466330> unknown_bootoption
> +0x0/0x1d0
> handlers:
> [<c0301300>] (qs_intr+0x0/0x220)
> Disabling IRQ #193
What other devices are routed to that same interrupt line?
The sata_qstor driver is very rigorous in acknowledging *only* it's own
interrupts, to prevent other devices sharing the same IRQ from losing theirs.
Mmm.. We could apply a bit of fuzzy tolerance for the odd glitch.
Try this patch (attached) and report back.
Thanks.
View attachment "qstor_spurious.patch" of type "text/x-patch" (834 bytes)
Powered by blists - more mailing lists