From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 30802] exception & eSATA hard link resets
Date: Thu, 10 Mar 2011 02:23:42 GMT [thread overview]
Message-ID: <201103100223.p2A2NgW7017422@demeter2.kernel.org> (raw)
In-Reply-To: <bug-30802-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=30802
Robert Hancock <hancockrwd@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hancockrwd@gmail.com
--- Comment #3 from Robert Hancock <hancockrwd@gmail.com> 2011-03-10 02:23:40 ---
So you're getting stuff like:
[20698.759685] ata6: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe
frozen
[20698.759691] ata6: irq_stat 0x00400040, connection status changed
[20698.759697] ata6: SError: { PHYRdyChg CommWake DevExch }
[20698.759706] ata6: hard resetting link
Your controller's reporting a bunch of link state change events occurring. My
first inclination is to suspect a problem with the eSATA cable or drive
enclosure. A lot of these seem to be rather flaky as far as power and/or the
solidity of the cable connections.
Does it recover if you disconnect/power off and reconnect the drive?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-03-10 2:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 13:53 [Bug 30802] New: exception & eSATA hard link resets bugzilla-daemon
2011-03-09 13:55 ` [Bug 30802] " bugzilla-daemon
2011-03-09 13:58 ` bugzilla-daemon
2011-03-10 2:23 ` bugzilla-daemon [this message]
2011-03-10 8:51 ` bugzilla-daemon
2011-03-10 10:21 ` bugzilla-daemon
2011-03-10 10:40 ` bugzilla-daemon
2011-03-10 19:40 ` bugzilla-daemon
2012-07-02 13:40 ` bugzilla-daemon
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=201103100223.p2A2NgW7017422@demeter2.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.