From: Frans Pop <elendil@planet.nl>
To: Alexander Huemer <alexander.huemer@sbg.ac.at>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: 2.6.{30,31} x86_64 ahci problem - irq 23: nobody cared
Date: Thu, 24 Sep 2009 21:24:40 +0200 [thread overview]
Message-ID: <200909242124.42187.elendil@planet.nl> (raw)
In-Reply-To: <4ABBB8C2.2080901@sbg.ac.at>
Adding linux-ide to CC.
Alexander Huemer wrote:
> the problem appears under heavy system load and slows down the system to
> unusable speed.
> kernels before .30 were not affected.
> irqpoll does not change behavior.
>
> error message from .31:
> [157152.418524] irq 23: nobody cared (try booting with the "irqpoll" option)
> [157152.418530] Pid: 1359, comm: cc1plus Tainted: G W 2.6.31-gentoo-blackbit #2
> [157152.418532] Call Trace:
> [157152.418534] <IRQ> [<ffffffff81066e3f>] ? __report_bad_irq+0x30/0x7d
> [157152.418544] [<ffffffff81066f93>] ? note_interrupt+0x107/0x170
> [157152.418547] [<ffffffff81067580>] ? handle_fasteoi_irq+0x8a/0xaa
> [157152.418551] [<ffffffff8100d1cf>] ? handle_irq+0x17/0x1d
> [157152.418554] [<ffffffff8100c84b>] ? do_IRQ+0x54/0xb2
> [157152.418558] [<ffffffff8100b6d3>] ? ret_from_intr+0x0/0xa
> [157152.418559] <EOI>
> [157152.418560] handlers:
> [157152.418562] [<ffffffff813d2a6f>] (ahci_interrupt+0x0/0x426)
> [157152.418566] Disabling IRQ #23
>
> bios of the machine is up to date,
> i tried all related bios settings, no change.
>
> kernel config for .31 http://xx.vu/~ahuemer/config_ahuemer_20090923.gz
> lspci -vxxx http://xx.vu/~ahuemer/lspci_ahuemer_20090923
> lsusb -v http://xx.vu/~ahuemer/lsusb_ahuemer_20090923
> /proc/interrupts http://xx.vu/~ahuemer/proc_interrupts_ahuemer_20090923
> thread in gentoo forums http://forums.gentoo.org/viewtopic-t-780725-start-0.html
>
> please tell me what additional info is needed.
A full dmesg (or kernel log) starting from a clean boot up to the error
could be useful.
If no others reply and the issue can be reproduced reliably, running a
git bisect between v2.6.29 and v2.6.30 to trace the cause of the regression
could be an option.
Cheers,
FJP
next parent reply other threads:[~2009-09-24 19:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ABBB8C2.2080901@sbg.ac.at>
2009-09-24 19:24 ` Frans Pop [this message]
2009-09-24 19:30 ` 2.6.{30,31} x86_64 ahci problem - irq 23: nobody cared Alexander Huemer
2009-09-24 19:40 ` Frans Pop
2009-09-24 19:43 ` Alexander Huemer
2009-09-25 0:02 ` Alexander Huemer
2009-09-25 11:28 ` Alexander Huemer
2009-09-25 12:24 ` Frans Pop
2009-09-25 12:27 ` Alexander Huemer
2009-09-25 12:48 ` Frans Pop
2009-10-08 12:00 ` Alexander Huemer
2009-10-09 21:30 ` Alexander Huemer
2009-10-10 13:13 ` Frans Pop
2009-10-11 20:57 ` Alexander Huemer
2009-10-12 7:49 ` Tejun Heo
2009-10-12 9:48 ` Frans Pop
2009-10-12 9:52 ` Tejun Heo
2009-10-12 9:55 ` Alexander Huemer
2009-10-12 10:07 ` Tejun Heo
2009-10-12 10:11 ` Alexander Huemer
2009-10-12 15:03 ` Alexander Huemer
2009-10-12 17:28 ` Robert Hancock
2009-10-13 2:17 ` Tejun Heo
2009-10-13 6:49 ` Alexander Huemer
2009-10-13 12:35 ` Tejun Heo
2009-10-14 11:45 ` Jean Delvare
2009-10-21 8:38 ` Jean Delvare
2009-10-21 10:01 ` Alexander Huemer
2009-10-21 11:28 ` Jean Delvare
2009-10-26 15:01 ` Alexander Huemer
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=200909242124.42187.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=alexander.huemer@sbg.ac.at \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).