From: Alan <alan@lxorguk.ukuu.org.uk>
To: rbrito@ime.usp.br, rbrito@gmail.com
Cc: rbrito@ime.usp.br, akpm@osdl.org, linux-kernel@vger.kernel.org,
rbrito@gmail.com
Subject: Re: The return of the dreaded "nobody cared" message with a Promise Card
Date: Wed, 29 Nov 2006 11:03:36 +0000 [thread overview]
Message-ID: <20061129110336.22e2ca18@localhost.localdomain> (raw)
In-Reply-To: <20061129060130.GA2913@ime.usp.br>
On Wed, 29 Nov 2006 04:01:30 -0200
Rogério Brito <rbrito@ime.usp.br> wrote:
>> The problem is that whenever I plug the Quantum drive, I get stack
> traces like this one (with a bit of context, so that you can get sense of
> what I am talking about):
Ok IRQ routing problem on what seems to be an external IRQ.
> ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
> PCI: setting IRQ 10 as level-triggered
> ACPI: PCI Interrupt 0000:00:11.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
Do your working kernels also have ACPI enabled and what do they say here ?
> I am willing to do a git bisect to see which may be a problematic patch
> or not, but the "irq 10: nobody cared (try booting with the "irqpoll"
> option)" is one that I reported to Andrew quite some time ago (I thought
> that it had gone away), and it didn't manifest itself until I had to
> reuse this extra drive, since I am doing a work that is producing a lot
> of data.
Ok I have a guess here - what does 2.6.19-rc6-mm2 do ? I've been working
on fixing up the VIA IRQ routing bugs as it happens. full dmesg of the
work/fail cases and an lspci -vxxx would be useful so I can see how the
hardware thinks it is configured.
next prev parent reply other threads:[~2006-11-29 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 6:01 The return of the dreaded "nobody cared" message with a Promise Card Rogério Brito
2006-11-29 11:03 ` Alan [this message]
2006-12-03 1:49 ` Rogério Brito
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=20061129110336.22e2ca18@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rbrito@gmail.com \
--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