From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Stoyan Gaydarov <stoyboyker@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: ata error
Date: Fri, 25 Jul 2008 19:56:18 +0100 [thread overview]
Message-ID: <20080725195618.5f09c3bf@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <6d291e080807251147n14b0f0d1g4c8ad1d4759c702b@mail.gmail.com>
> > [ 1078.735322] ata3.00: configured for UDMA/133
> > [ 1078.735336] ata3: EH complete
> > [ 1078.766066] sd 2:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
We timed out, reset the drive and it came back.
> > [ 1078.766442] sd 2:0:0:0: [sda] Write Protect is off
> > [ 1078.766448] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
> > [ 1078.766957] sd 2:0:0:0: [sda] Write cache: enabled, read cache:
> > enabled, doesn't support DPO or FUA
> > [ 1107.310768] [drm] Loading R300 Microcode
I notice there is a drm Loading R300 Microcode logged just before each
drive failure. That seems very suspicious to me. Does it ever occur if
you are not in X ?
next prev parent reply other threads:[~2008-07-25 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 18:43 ata error Stoyan Gaydarov
2008-07-25 18:47 ` Stoyan Gaydarov
2008-07-25 18:56 ` Alan Cox [this message]
2008-07-25 19:26 ` Stoyan Gaydarov
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=20080725195618.5f09c3bf@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=stoyboyker@gmail.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