public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Boot <bootc@bootc.net>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: New libata PATA patch for 2.6.16-rc1
Date: Tue, 14 Mar 2006 19:54:58 +0000	[thread overview]
Message-ID: <44171F92.8030702@bootc.net> (raw)
In-Reply-To: <200603141048.39785.s0348365@sms.ed.ac.uk>

Alistair John Strachan wrote:
> On Tuesday 14 March 2006 01:24, Alan Cox wrote:
>> On Llu, 2006-03-13 at 17:13 +0000, Alistair John Strachan wrote:
>>> However, I just tried the same driver on my desktop PC (4xSATA HDs,
>>> 1xPATA) and I get the following periodically (when the PATA device is NOT
>>> being used):
>> Can you try the vanilla rc6 kernel to check, and if it does it then let
>> Jeff Garzik known ASAP - especially if rc4 was ok.
>>
>>> ata1: irq trap
> 
> No such error without your patch on this machine. I've got a RAID5 spanning 
> four SATA drives on a dual core Athlon 64, and it'll happily do 185MB/s 
> to /dev/null with the command:
> 
> for FILE in *; do dd if="$FILE" of=/dev/null bs=1M; done
> 
> 300,000 interrupts later, still no messages. Anything I can do to isolate this 
> further?
> 

I'd like to second this. On -rc5-ide{1,2} I didn't have any trouble, but now on 
-rc6-ide1 I keep getting the messages on all 4 of my SATA drives (2 on sata_via, 
2 on sata_sil). I haven't tried with vanilla -rc6 but let me know if that can help.

HTH,
Chris

-- 
Chris Boot
bootc@bootc.net
http://www.bootc.net/

  reply	other threads:[~2006-03-14 19:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13 15:07 New libata PATA patch for 2.6.16-rc1 Alan Cox
2006-03-13 16:39 ` Alistair John Strachan
2006-03-13 17:13   ` Alistair John Strachan
2006-03-14  1:24     ` Alan Cox
2006-03-14 10:48       ` Alistair John Strachan
2006-03-14 19:54         ` Chris Boot [this message]
2006-03-17 14:57         ` Alan Cox
2006-03-18 16:14           ` Chris Boot
2006-03-13 20:28 ` Matthieu CASTET
2006-03-13 20:41   ` Matthieu CASTET
2006-03-13 20:39 ` Kevin Radloff
2006-03-13 22:31 ` Prakash Punnoor
2006-03-15 10:54   ` Prakash Punnoor
2006-03-15 11:29     ` Ed Sweetman
2006-03-15 14:02       ` Prakash Punnoor
2006-03-14  0:39 ` Chris Boot
2006-03-14  1:23   ` Alan Cox
     [not found] <20060313195722.6ADBF1401F@rhn.tartu-labor>
2006-03-13 20:08 ` Meelis Roos
2006-03-14  1:21   ` Alan Cox
2006-03-14  7:31     ` Meelis Roos
2006-03-14  7:36     ` Meelis Roos

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=44171F92.8030702@bootc.net \
    --to=bootc@bootc.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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