From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Diego Calleja <diegocg@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pata_serverworks oopses in latest -git
Date: Tue, 26 Sep 2006 11:56:29 -0400 [thread overview]
Message-ID: <45194DAD.6060904@garzik.org> (raw)
In-Reply-To: <1159275010.11049.215.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
Alan Cox wrote:
> Ar Maw, 2006-09-26 am 14:00 +0200, ysgrifennodd Diego Calleja:
>> When trying to test the new libata PATA drivers in the latest -git tree, I
>> got this when udev tried to load the module:
>
> Yes something seems to be very ill in the -git tree but I'm not sure
> what has changed in the libata core to trigger all this at the moment.
One thing I notice in pata_serverworks.c is the lack of an ->irq_clear()
hook, which is called unconditionally in ata_device_add(). It's a bit
strange that it wasn't caught before, since ->irq_clear() has been
called unconditionally for a great many kernel releases.
Diego, does the attached patch help?
Jeff
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 697 bytes --]
diff --git a/drivers/ata/pata_serverworks.c b/drivers/ata/pata_serverworks.c
index af45611..9c1719c 100644
--- a/drivers/ata/pata_serverworks.c
+++ b/drivers/ata/pata_serverworks.c
@@ -356,6 +356,8 @@ static struct ata_port_operations server
.data_xfer = ata_pio_data_xfer,
.irq_handler = ata_interrupt,
+ .irq_clear = ata_bmdma_irq_clear,
+
.port_start = ata_port_start,
.port_stop = ata_port_stop,
.host_stop = ata_host_stop
@@ -389,6 +391,8 @@ static struct ata_port_operations server
.data_xfer = ata_pio_data_xfer,
.irq_handler = ata_interrupt,
+ .irq_clear = ata_bmdma_irq_clear,
+
.port_start = ata_port_start,
.port_stop = ata_port_stop,
.host_stop = ata_host_stop
next prev parent reply other threads:[~2006-09-26 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 12:00 pata_serverworks oopses in latest -git Diego Calleja
2006-09-26 12:50 ` Alan Cox
2006-09-26 15:56 ` Jeff Garzik [this message]
2006-09-26 19:29 ` Diego Calleja
2006-09-26 19:43 ` Jeff Garzik
2006-09-26 20:02 ` Alan Cox
2006-09-26 20:38 ` Diego Calleja
2006-09-26 21:24 ` Alan Cox
2006-09-26 21:25 ` Jeff Garzik
2006-09-26 22:21 ` Diego Calleja
2006-09-26 23:06 ` Alan Cox
2006-09-26 22:58 ` Diego Calleja
2006-09-26 23:27 ` Diego Calleja
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=45194DAD.6060904@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=diegocg@gmail.com \
--cc=linux-kernel@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 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.