public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Kevin Radloff <radsaq@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Updated libata PATA patch
Date: Wed, 10 May 2006 15:09:05 +0100	[thread overview]
Message-ID: <1147270145.17886.42.camel@localhost.localdomain> (raw)
In-Reply-To: <3b0ffc1f0605091848med1f37ua83c283a922ea682@mail.gmail.com>

On Maw, 2006-05-09 at 21:48 -0400, Kevin Radloff wrote:
> ata3: PATA max PIO0 cmd 0x3100 ctl 0x310E bmdma 0x0 irq 11
> setup_irq: irq handler mismatch

Ok so we got an interrupt this time and then when we asked for it got
told "no". That still shouldn't crash but there are some lurking
problems when ata_device_add fails.

More interesting is how it can occur.

We asked for an IRQ that was "exclusive". We got given IRQ 11 which was
shared. A look at the pcmcia code suggests the new drivers/pcmcia code
is broken here: It may fall back to using an interrupt line that is
shared even when told not to.

What occurs if you change

	ae.irq_flags = 0;

to 

	ae.irq_flags = SA_SHIRQ ?

Alan


  reply	other threads:[~2006-05-10 13:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 17:44 Updated libata PATA patch Alan Cox
2006-05-10  1:48 ` Kevin Radloff
2006-05-10 14:09   ` Alan Cox [this message]
2006-05-10 16:05     ` Kevin Radloff
2006-05-10 16:39       ` Alan Cox
2006-05-10 16:39         ` Kevin Radloff
2006-05-15 22:08           ` Alan Cox
2006-05-15 23:13             ` Alan Cox
2006-05-12  2:34     ` John Stoffel
2006-05-15  2:46       ` John Stoffel
2006-05-11 19:06 ` Matthieu CASTET
2006-05-12 23:04 ` Guennadi Liakhovetski

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=1147270145.17886.42.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=radsaq@gmail.com \
    /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