From: Torsten Kaiser <just.for.lkml@googlemail.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org
Subject: Re: MSI broken in libata?
Date: Tue, 19 Jan 2010 08:00:43 +0100 [thread overview]
Message-ID: <64bb37e1001182300u13f41817hf1a3d18ffdc75847@mail.gmail.com> (raw)
In-Reply-To: <4B55130D.8070503@gmail.com>
On Tue, Jan 19, 2010 at 3:03 AM, Robert Hancock <hancockrwd@gmail.com> wrote:
> On 01/18/2010 02:51 PM, Torsten Kaiser wrote:
>> Should I try to put some printks in arch/x86/kernel/apic/io_apic.c
>> __assign_irq_vector() or is there a better way to look at the irq
>> vectors?
>
> Might not be a bad idea.
OK, I will try it later today.
> Something definitely seems to be banging on vector
> 165. Any references to 165 in dmesg prior to that? I wonder where that is
> coming from..
No, grepping for 165 only shows some timestamps and some output from
the serial driver, because that's a 16550A.
I hope adding these debugs will help, maybe something suspicious
reserved 164 or 166...
Torsten
next prev parent reply other threads:[~2010-01-19 7:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 9:22 MSI broken in libata? Torsten Kaiser
2010-01-09 9:11 ` Tejun Heo
2010-01-10 4:33 ` Torsten Kaiser
2010-01-11 1:15 ` Tejun Heo
2010-01-11 1:39 ` Robert Hancock
2010-01-11 2:17 ` Tejun Heo
2010-01-16 21:58 ` Torsten Kaiser
2010-01-17 19:22 ` Robert Hancock
2010-01-17 21:11 ` Torsten Kaiser
2010-01-18 20:51 ` Torsten Kaiser
2010-01-19 2:03 ` Robert Hancock
2010-01-19 7:00 ` Torsten Kaiser [this message]
2010-01-19 20:20 ` Torsten Kaiser
2010-01-20 3:00 ` Robert Hancock
2010-01-20 6:48 ` Torsten Kaiser
2010-01-22 0:53 ` Robert Hancock
2010-01-11 6:44 ` Torsten Kaiser
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=64bb37e1001182300u13f41817hf1a3d18ffdc75847@mail.gmail.com \
--to=just.for.lkml@googlemail.com \
--cc=hancockrwd@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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).