mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Alexander Huemer <alexander.huemer@sbg.ac.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.{30,31} x86_64 ahci problem - irq 23: nobody cared
Date: Thu, 24 Sep 2009 12:38:54 -0700	[thread overview]
Message-ID: <4ABBCACE.90506@caviumnetworks.com> (raw)
In-Reply-To: <4ABBC54E.6090209@sbg.ac.at>

Alexander Huemer wrote:
> David Daney wrote:
>> 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 
>> Right here is the problem  ->         ^^^^^^^^
>>
>> Haven't you read all the threads about the evil of C++.  This is just
>> one more example of the why we shouldn't be using it. :-)
>>
>> David Daney
>>
[...]
> thanks for your quick answer, david.
> so, this isn't a kernel issue at all ?
> imho a user process shouldn't be able to cause such a situation.
> what can i do against that phenomenon ?
> 

Just for avoidance of doubt, it was an attempt at a joke.

You are of course correct.  It looks like a real bug.  User-space 
shouldn't matter.

David Daney

  reply	other threads:[~2009-09-24 19:39 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 18:21 Alexander Huemer
2009-09-24 18:31 ` David Daney
2009-09-24 19:15   ` Alexander Huemer
2009-09-24 19:38     ` David Daney [this message]
2009-09-24 19:24 ` Frans Pop
2009-09-24 19:30   ` 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=4ABBCACE.90506@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=alexander.huemer@sbg.ac.at \
    --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

Powered by JetHome