LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
	"Neil Schemenauer" <nas@arctrix.com>,
	david@unsolicited.net
Subject: Re: sata_nv - ADMA issues with 2.6.20
Date: Sun, 11 Feb 2007 17:04:55 -0600	[thread overview]
Message-ID: <45CFA117.3030508@shaw.ca> (raw)
In-Reply-To: <fa.skzjVxsBWVzk9Yzhsb2UIA1VDGY@ifi.uio.no>

Björn Steinbrink wrote:
> If the look like this, you might want to try a few patches that are in
> -mm.
> 
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata1.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 out
>          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata1: soft resetting port
> 
> We thought that Robert had fixed these with some changes that went into
> -rc6. But they reappeared a few days later, the -mm patches seem to have
>  finally cured it.
> 
> The original patches are here:
> 
> http://www2.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc6/2.6.20-rc6-mm3/broken-out/sata_nv-cleanup-adma-error-handling-v2.patch
> http://www2.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc6/2.6.20-rc6-mm3/broken-out/sata_nv-cleanup-adma-error-handling-v2-cleanup.patch
> http://www2.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc6/2.6.20-rc6-mm3/broken-out/sata_nv-use-adma-for-nodata-commands.patch
> 
> As they had a few rejects against 2.6.20-rc7, I'm attaching my fixed all-in-one version of these patches, I guess it should apply to 2.6.20 just fine.

This isn't quite the same as that problem we were seeing, these are an 
actual NCQ read/write that is timing out and not a cache flush command. 
Nevertheless it wouldn't hurt for people having this problem to test out 
the latest and greatest sata_nv patches. In particular there was one 
that I resurrected from the debugging of that problem, "sata_nv: wait 
for response on entering/leaving ADMA mode" which though it didn't end 
up fixing it, seemed like a good thing to be doing anyway, and which 
potentially might have some effect on this problem here.

All the patches I have for sata_nv are in Linus' git tree, that is 
probably a simpler way to test them than -mm right now - applying the 
2.6.20-git6 patch on top of 2.6.20 should do it.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-02-11 23:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.4+EfmBKJuhLBKrzZ9Tr6IwbmP9o@ifi.uio.no>
     [not found] ` <fa.k0ZDYzgHEXJHC2/UddL2J4jq/kE@ifi.uio.no>
     [not found]   ` <fa.W/MKSda79+AG31HO6bl30nzW79o@ifi.uio.no>
     [not found]     ` <fa.skzjVxsBWVzk9Yzhsb2UIA1VDGY@ifi.uio.no>
2007-02-11 23:04       ` Robert Hancock [this message]
     [not found] <fa.uoZWqSFxPjjB7zobQOwk/2zqG5A@ifi.uio.no>
2007-02-10  1:33 ` Robert Hancock
2007-02-10  9:34   ` David R
2007-02-11 19:55   ` Neil Schemenauer
2007-02-11 22:23     ` Björn Steinbrink
2007-02-09 21:11 David R

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=45CFA117.3030508@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=B.Steinbrink@gmx.de \
    --cc=david@unsolicited.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nas@arctrix.com \
    --subject='Re: sata_nv - ADMA issues with 2.6.20' \
    /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

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).