All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "Rogério Brito" <rbrito@ime.usp.br>
Cc: Brian Kuschak <bkuschak@yahoo.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] Re: 2.6.11-rc4 libata-core (irq 30: nobody cared!)
Date: Sat, 26 Feb 2005 15:19:42 -0500	[thread overview]
Message-ID: <4220D9DE.10904@pobox.com> (raw)
In-Reply-To: <20050226193255.GA6256@ime.usp.br>

Rogério Brito wrote:
> On Feb 23 2005, Jeff Garzik wrote:
> 
>>Does this patch do anything useful?
>>	Jeff
> 
> (...)
> 
> The patch you posted seems to only affect people using SATA, right?
> 
> BTW, just for clarity I'm seeing the message in a PATA environment (on
> i386) and Brian is seeing his problem with a SATA device on ppc.

"irq XX: nobody cared" is a screaming interrupt situation, which could 
have 1001 causes.

Normally it's something that "pci=biosirq" or "acpi=off" will fix, but 
on occasion the driver itself is what needs fixing.

	Jeff




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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24  1:58 2.6.11-rc4 libata-core (irq 30: nobody cared!) Brian Kuschak
2005-02-24  2:01 ` Brian Kuschak
2005-02-24  2:34 ` [PATCH] " Jeff Garzik
2005-02-24  2:36   ` Jeff Garzik
2005-02-24  2:58   ` Brian Kuschak
2005-02-26 19:32   ` Rogério Brito
2005-02-26 20:19     ` Jeff Garzik [this message]
2005-02-26 23:18       ` Rogério Brito
2005-02-28 16:10       ` Mark Lord
2005-03-02  7:18         ` [PATCH 0/3] Fix 3ware irq handling Jeff Garzik
2005-03-02  7:20           ` [PATCH 1/3] Fix 3ware irq handling: correct IRQ_HANDLED Jeff Garzik
2005-03-02  7:21           ` [PATCH 2/3] Fix 3ware irq handling: remove bogus test Jeff Garzik
2005-03-02  7:22           ` [PATCH 3/3] Fix 3ware irq handling: update irq handler indentation Jeff Garzik
2005-03-02  7:31             ` Jeff Garzik

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=4220D9DE.10904@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=bkuschak@yahoo.com \
    --cc=linux-ide@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.