Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: linux-ide@vger.kernel.org
Subject: Re: Kernel problem or faulty drive?
Date: Mon, 22 Nov 2010 14:07:55 +0000	[thread overview]
Message-ID: <20101122140755.3b02abe6@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <201011221134.oAMBYAaO016345@mercury.physics.adelaide.edu.au>

> At various times the drive seems to get into a state whereby it has repeated
> trouble communicating with the kernel.  The drive clicks once, there's some
> seek activity by the drive and the following set of messages (along with
> variations) are written to the log:
> 
>   ata3: exception Emask 0x50 SAct 0x0 SErr 0x4010800 action 0xe frozen
>   ata3: irq_stat 0x00400040, connection status changed
>   ata3: SError: { HostInt PHYRdyChg DevExch }

It reported the drive being hot plugged.

>   ata3: hard resetting link
>   ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
>   ata3.00: configured for UDMA/33

And a slightly odd choice of speed.

> This can occur a dozen or more times before the drive settles down, or it
> may occur only once.  All this is while Linux is not accessing the drive and
> none of its partitions are mounted.

Check the cables their connections and check your power is sufficient, a
drive dropping off the bus is a classic symptom of insufficient power on
the supply line it is using (with some PSUs moving to a different
'strand' of cable from the PSU box may be enough.

  parent reply	other threads:[~2010-11-22 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 11:34 Kernel problem or faulty drive? Jonathan Woithe
2010-11-22 12:12 ` gene heskett
2010-11-22 14:07 ` Alan Cox [this message]
2010-11-30  7:56   ` Jonathan Woithe

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=20101122140755.3b02abe6@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jwoithe@physics.adelaide.edu.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox