public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias-Christian Ott <matthias.christian@tiscali.de>
To: "Rogério Brito" <rbrito@ime.usp.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11rc4: irq 5, nobody cared
Date: Sun, 20 Feb 2005 18:19:14 +0100	[thread overview]
Message-ID: <4218C692.9040106@tiscali.de> (raw)
In-Reply-To: <20050220164010.GA17806@ime.usp.br>

Rogério Brito wrote:

>On Feb 20 2005, Folkert van Heusden wrote:
>  
>
>>My linux laptop says:
>>irq 5: nobody cared!
>>    
>>
>(...)
>  
>
>>Does anyone care? :-)
>>    
>>
>
>Well, I'm getting similar stack traces with my system and those are sure
>scary, but it seems that my e-mails to the list are simply ignored,
>unfortunately.
>
>I am willing to test any patch and configuration (let's call me a "guinea
>pig"), but I don't know what I should do. I have, OTOH, reported my problem
>many times in the past few days. :-(
>
>I will retry sending my message to the list once again, with the details
>(in my case, the message I get is "irq 10: nobody cared!" and it is
>regarding my primary HD on my secondary Promise PDC20265 controller).
>
>
>Thanks for any help, Rogério.
>
>P.S.: I have already bought an 80-pin cable just for this drive in the hope
>that the message would go away, but it didn't.
>  
>
Report it to http://bugzilla.kernel.org/. Maybe you'll get help there. 
But "bugs" are _very_ hardware specific, so just a few people will have 
a similar problem and most of this people are just "normal" users -- not 
Linux Kernel developers. The developer (people who are familiar with the 
kernel code and who are maybe able to fix this problem) aren't able to 
reproduce this error and test code to get it working. So they're maybe 
(without knowing anything about the hardware (maybe it's broken 
hardware?)) not able to say something specific about the hardware -- 
they can just guess.
You see it's very difficult to fix such irq problems because some 
factors can cause such an error.
Maybe contacting specific malinglists (e.g. for "broken" pci cards the 
pci mailinglist, etc.), maintainers or developers would be more 
efficient (cc the lkml) and solve your problem (faster), because this 
people are specialists are this type of hardware (e.g. pci).

What hardware is connect through irq 5?

Matthias-Christian Ott

  reply	other threads:[~2005-02-20 17:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-20 15:56 2.6.11rc4: irq 5, nobody cared Folkert van Heusden
2005-02-20 16:40 ` Rogério Brito
2005-02-20 17:19   ` Matthias-Christian Ott [this message]
2005-02-20 18:05     ` Rogério Brito
2005-02-20 20:00       ` Matthias-Christian Ott
2005-02-21 18:43       ` Bartlomiej Zolnierkiewicz
2005-02-21 18:50         ` Jeff Garzik
2005-02-21 19:42           ` Wichert Akkerman
2005-02-21 20:32             ` Jeff Garzik
2005-02-21 21:48               ` Wichert Akkerman
2005-02-23 21:41             ` Bill Davidsen
2005-02-21 19:02         ` Rogério Brito
2005-02-23 21:19   ` Bill Davidsen
2005-02-24 16:44     ` Folkert van Heusden
2005-02-24 21:37       ` Bill Davidsen
2005-02-20 16:43 ` Arjan van de Ven

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=4218C692.9040106@tiscali.de \
    --to=matthias.christian@tiscali.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rbrito@ime.usp.br \
    /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