linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Nigel Kukard <nkukard@lbsd.net>
Cc: linux-kernel@vger.kernel.org,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: SATA problems
Date: Thu, 14 Jun 2007 13:33:22 -0400	[thread overview]
Message-ID: <46717BE2.3000703@garzik.org> (raw)
In-Reply-To: <467173C4.1050500@lbsd.net>

Nigel Kukard wrote:
>>> I'm stumped trying to track down the below intermittent problem.....
>>>
>>> I've confirmed this problem on 2.6.19, 2.6.20 and 2.6.21.

>>> Jun 14 07:55:52 nigel-m2v kernel: ata2.00: exception Emask 0x0 SAct 0x0
>>> SErr 0x0 action 0x2 frozen
>>> Jun 14 07:55:52 nigel-m2v kernel: ata2.00: cmd
>>> ca/00:18:87:e7:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 12288 out
>>> Jun 14 07:55:52 nigel-m2v kernel:          res
>>> 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
>>> Jun 14 07:55:52 nigel-m2v kernel: ata2: soft resetting port
>>> Jun 14 07:55:52 nigel-m2v kernel: ATA: abnormal status 0x7F on port
>>> 0x0001c807
>>> Jun 14 07:55:52 nigel-m2v kernel: ATA: abnormal status 0x7F on port
>>> 0x0001c807
>>> Jun 14 07:56:22 nigel-m2v kernel: ata2.00: qc timeout (cmd 0xef)
>>> Jun 14 07:56:22 nigel-m2v kernel: ata2.00: failed to set xfermode
>>> (err_mask=0x4)

>> Try 2.6.22-rc4-gitX...

> Is there a patch in particular I can maybe apply? I see you made a
> couple of commits ... my problem is this is also happening on one of my
> production boxes which has a few other patches applied, I'm a bit scared
> of conflicts ... I don't really want to break anything by upgrading the
> kernel.

The two most relevant git commits:

commit 51b94d2a5a90d4800e74d7348bcde098a28f4fb3
Author: Tejun Heo <htejun@gmail.com>
Date:   Fri Jun 8 13:46:55 2007 -0700

     sata_promise: use TF interface for polling NODATA commands

commit 464cf177df7727efcc5506322fc5d0c8b896f545
Author: Tejun Heo <htejun@gmail.com>
Date:   Sun May 27 15:10:40 2007 +0200

     libata: always use polling SETXFER

If you have a git tree local to you, "git-diff-tree -p $COMMIT" will 
extract a patch, otherwise click "raw" after surfing to 
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=$COMMIT

Regards,

	Jeff



       reply	other threads:[~2007-06-14 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8vX5T-4hg-5@gated-at.bofh.it>
     [not found] ` <8w0n1-15u-27@gated-at.bofh.it>
     [not found]   ` <467173C4.1050500@lbsd.net>
2007-06-14 17:33     ` Jeff Garzik [this message]
2007-06-18  8:05       ` SATA problems Nigel Kukard
     [not found] <4671366B.7090702@lbsd.net>
     [not found] ` <46716B1D.1070902@garzik.org>
     [not found]   ` <20070614182854.GC1223@redhat.com>
     [not found]     ` <20070618200703.GB13344@redhat.com>
     [not found]       ` <46776223.3050402@lbsd.net>
     [not found]         ` <46D68CC2.3030206@lbsd.net>
2007-09-10  9:02           ` Andrew Morton
2007-09-13  8:55             ` Tejun Heo

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=46717BE2.3000703@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nkukard@lbsd.net \
    /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).