Re: 2.6.{30,31} x86_64 ahci problem - irq 23: nobody cared

From: Alexander Huemer
Date: Fri Sep 25 2009 - 08:27:44 EST


Frans Pop wrote:
On Friday 25 September 2009, Alexander Huemer wrote:
Alexander Huemer wrote:
Frans Pop wrote:
On Thursday 24 September 2009, Frans Pop wrote:
error message from .31:
[157152.418524] irq 23: nobody cared
Looking at the changes in drivers/ata/ahci.c, it might be worth to
try if reverting the following commit fixes the issue:

commit a5bfc4714b3f01365aef89a92673f2ceb1ccf246
Author: Tejun Heo <tj@xxxxxxxxxx>
Date: Fri Jan 23 11:31:39 2009 +0900

ahci: drop intx manipulation on msi enable
i reproduced the issue.

[ 3486.747729] Pid: 9573, comm: jc1 Tainted: G W 2.6.31-gentoo-blackbit #2
[ 3486.747731] Call Trace:
[ 3486.747733] <IRQ> [<ffffffff81066e3f>] ? __report_bad_irq+0x30/0x7d
[ 3486.747743] [<ffffffff81066f93>] ? note_interrupt+0x107/0x170
[ 3486.747746] [<ffffffff81067580>] ? handle_fasteoi_irq+0x8a/0xaa
[ 3486.747750] [<ffffffff8100d1cf>] ? handle_irq+0x17/0x1d
[ 3486.747752] [<ffffffff8100c84b>] ? do_IRQ+0x54/0xb2
[ 3486.747756] [<ffffffff8100b6d3>] ? ret_from_intr+0x0/0xa
[ 3486.747758] <EOI>
[ 3486.747759] handlers:
[ 3486.747761] [<ffffffff813d2a6f>] (ahci_interrupt+0x0/0x426)
[ 3486.747765] Disabling IRQ #23

i will report back after a compile run of gcc-4.3.4 with a kernel
without the commit you suggested.
4 compilation runs of gcc-4.3.4 finished without the issue re-appearing.
it seems like you guessed right, Frans.

Great. Glad to hear it worked out.

i also found this:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commi
t;h=31b239ad1ba7225435e13f5afc47e48eb674c0cc i'll report on bugzilla.

So with the revert already in mainline for .32, the only thing left is for
that to get included in stable updates for .30 and .31.

Cheers,
FJP
please see the last comment in [1].
can i do anything else to help ?

thanks again
-alex

[1] http://bugzilla.kernel.org/show_bug.cgi?id=14124
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/