linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	linux-ide@vger.kernel.org, apiszcz@solarrain.com
Subject: Re: Kernel 2.6.23.9 / P35 Chipset + WD 750GB Drives (reset port)
Date: Mon, 10 Dec 2007 17:23:39 +0900	[thread overview]
Message-ID: <475CF78B.3040404@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712020409280.30169@p34.internal.lan>

Justin Piszcz wrote:
> The badblocks did not do anything; however, when I built a software raid
> 5 and the performed a dd:
> 
> /usr/bin/time dd if=/dev/zero of=fill_disk bs=1M
> 
> [42332.936615] ata5.00: exception Emask 0x2 SAct 0x7000 SErr 0x0 action
> 0x2 frozen
> [42332.936706] ata5.00: spurious completions during NCQ issue=0x0
> SAct=0x7000 FIS=004040a1:00000800
> 
> Next test, I will turn off NCQ and try to make the problem re-occur.
> If anyone else has any thoughts here..?
> I ran long smart tests on all 3 disks, they all ran successfully.
> 
> Perhaps these drives need to be NCQ BLACKLISTED with the P35 chipset?

That was me being stupid.  Patches for both upstream and -stable
branches are posted.  These will go away.

Thanks.

-- 
tejun

  reply	other threads:[~2007-12-10  8:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-01 11:26 Kernel 2.6.23.9 / P35 Chipset + WD 750GB Drives (reset port) Justin Piszcz
2007-12-01 12:13 ` Jan Engelhardt
2007-12-01 12:23   ` Justin Piszcz
     [not found]     ` <20071201174733.646a5c35@absurd>
     [not found]       ` <Pine.LNX.4.64.0712011155110.6257@p34.internal.lan>
2007-12-02  9:11         ` Justin Piszcz
2007-12-10  8:23           ` Tejun Heo [this message]
2007-12-01 18:44   ` Bill Davidsen
2007-12-10  8:14     ` Tejun Heo
2007-12-13 22:27       ` Bill Davidsen
2007-12-06 22:00 ` Andrew Morton
2007-12-06 22:38   ` Justin Piszcz
2007-12-06 23:05     ` Andrew Morton
     [not found] <fa.hhS4g1h0uppt8Xx/ZZfNNQfAv1Q@ifi.uio.no>
2007-12-01 20:08 ` Robert Hancock
     [not found] ` <fa.YIWyRfjQw18aIH2fKaze37Gwuzo@ifi.uio.no>
     [not found]   ` <fa.ib4H8TQ3raADIWdsEBy+eSL/1RU@ifi.uio.no>
     [not found]     ` <fa.S4u1AwoYnqrSuegcUaP78D3SFXQ@ifi.uio.no>
     [not found]       ` <fa.H1nTe/xQV/oyEMTHAkOjqgqu7jY@ifi.uio.no>
     [not found]         ` <fa.YpQ6xCPOijQOCKsLJr1SDINFURI@ifi.uio.no>
2007-12-05  1:26           ` Robert Hancock

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=475CF78B.3040404@gmail.com \
    --to=htejun@gmail.com \
    --cc=apiszcz@solarrain.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).