linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Rusty Conover <rconover@infogears.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Resets on sil3124 & sil3726 PMP
Date: Wed, 15 Aug 2007 15:10:05 +0900	[thread overview]
Message-ID: <46C298BD.1070600@gmail.com> (raw)
In-Reply-To: <36D83AB0-1848-4240-B8FC-D634D9E90B31@infogears.com>

Hello, Rusty.

Rusty Conover wrote:
> I'm having some trouble with my e-SATA ports being reset.  I'm testing
> 2.6.22.1 with the 20070808 patch tarball on a nortec ds-1220 flashed to
> Silicon Image bios version 6.4.09 (the latest).
> 
> I'm testing with 6 500gig SATA drives shown as:
> 
> WD5000AAKS-22TMA0, 12.01C01, max UDMA/133
> 
> The error I'm getting is:
> 
> ata3.04: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x2 frozen
> ata3.04: cmd 61/00:08:3f:c9:00/04:00:00:00:00/40 tag 1 cdb 0x0 data
> 524288 out
>          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.01: hard resetting link
> ata3.01: SATA link down (SStatus 0 SControl 300)
> ata3.02: hard resetting link
> ata3.02: SATA link down (SStatus 0 SControl 300)
> ata3.03: hard resetting link
> ata3.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.04: hard resetting link
> ata3.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.05: hard resetting link
> ata3.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata3.00: configured for UDMA/100
> ata3.03: configured for UDMA/100
> ata3.04: configured for UDMA/100
> ata3: EH complete
> 
> This is happening under moderate load, but it does appear to recover and
> have all of the drives come back.  I'd be happy to provide a full dmesg
> log if desired.
> 
> If you have any ideas how I can work around this or what's causing the
> problem it would be greatly appreciated.

* Please post kernel log including boot messages and errors.

* Please post the result of 'hdparm -I /dev/sdX' where sdX is the
offending device.

* Are the errors localized to ata3.04 or are other drives affected too?

* If you keep the machine running, libata will fall back to 1.5Gbps
after several such errors.  Do the errors go away after falling back to
1.5Gbps?

Thanks.

-- 
tejun

  reply	other threads:[~2007-08-15  6:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14 23:39 Resets on sil3124 & sil3726 PMP Rusty Conover
2007-08-15  6:10 ` Tejun Heo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-15 13:58 Rusty Conover
2007-08-17 18:06 ` Tejun Heo
2007-08-20 19:56   ` Rusty Conover
2007-08-21  2:42     ` Rusty Conover
2007-08-22  3:03       ` Tejun Heo
2007-08-22  5:00         ` Rusty Conover
2007-08-22  5:43           ` Tejun Heo
2007-08-22  6:11             ` Rusty Conover
2007-08-22  6:39               ` Tejun Heo
2007-08-22  6:56                 ` Rusty Conover
2007-08-22  7:02                   ` Tejun Heo
2007-08-22  7:49                     ` Rusty Conover
2007-08-25  2:19                       ` Tejun Heo
2007-08-26 16:37                         ` Rusty Conover
2007-08-27  1:18                           ` Tejun Heo
2007-08-27  4:55 Richard Scobie
2007-08-27  7:11 ` Petr Vandrovec
2007-09-03  8:59   ` Tejun Heo
2007-09-03  9:57     ` Petr Vandrovec
2007-09-03 12:50       ` Tejun Heo
2007-09-04  1:38         ` Petr Vandrovec
2007-09-05 12:08           ` Petr Vandrovec
2007-09-05 21:30             ` Robin H. Johnson
2007-09-06  9:52               ` Petr Vandrovec
2007-09-06 18:02                 ` Tejun Heo
2007-09-06 17:59             ` Tejun Heo
2007-08-27  8:08 Richard Scobie
2007-08-27 22:49 ` Robin H. Johnson
2007-09-03 19:39 Richard Scobie
2007-09-03 20:34 ` Robin H. Johnson
2007-09-03 21:21   ` Richard Scobie

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=46C298BD.1070600@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=rconover@infogears.com \
    /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).