From: Erik Rull <erik.rull@rdsoftware.de>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: IRQ 15 not assigned, but still unable to use it - in MSDOS it works
Date: Sat, 19 Jun 2010 13:25:01 +0200 [thread overview]
Message-ID: <4C1CA90D.9010800@rdsoftware.de> (raw)
In-Reply-To: <4C1AE1A2.405@gmail.com>
Robert Hancock wrote:
> On 06/16/2010 05:30 AM, Erik Rull wrote:
>>
>> I need some ideas where to continue my search - I think that it is
>> somewhere in the libata that blocks this interrupt. /proc/interrupts
>> shows up no interrupt neither that #15 is used.
>
> If no driver attaches to the device and nothing is reported in
> /proc/interrupts then nothing should be blocking the interrupt
> driver-wise. I suspect the problem might be elsewhere, like the IRQ
> routing or something..
Hm interesting. Is there a way to debug/see the IRQ routing somehow or
somewhere? I've found another possiblity of watching incoming interrupts
via /proc/stats but there is also nothing happening (The number that
belongs to IRQ15 remains on 0).
Best regards,
Erik
prev parent reply other threads:[~2010-06-19 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 11:30 IRQ 15 not assigned, but still unable to use it - in MSDOS it works Erik Rull
2010-06-18 3:01 ` Robert Hancock
2010-06-19 11:25 ` Erik Rull [this message]
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=4C1CA90D.9010800@rdsoftware.de \
--to=erik.rull@rdsoftware.de \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@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