From: Tejun Heo <tj@kernel.org>
To: Gavin Cameron <gavin@gavsworld.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: libata problems
Date: Fri, 01 Aug 2008 17:48:45 +0900 [thread overview]
Message-ID: <4892CDED.6080302@kernel.org> (raw)
In-Reply-To: <4880BDCD.4030104@gavsworld.net>
Hello, Gavin.
Gavin Cameron wrote:
> I was hunting for a solution to my problem in the "known issues" section
> of the Wiki - my problem being fully described here:
> http://forums.fedoraforum.org/forum/showthread.php?t=192186
>
> Would you be able to shed any light on this problem? Do you require any
> other information from me?
>
It's usually best to describe in the mail again as people (I :-) tend
not to follow link to other forums. So, ATAPI PIO is timing out. I
thought we had most of these problems ironed out by now. Can you please
try 2.6.26 and post full kernel boot log and if it too fails the error
messages?
> Anyway, as a side issue, I read the first problem about frequent head
> unloads and noticed it as another problem I have. So, as requested,
> attached are the outputs of "dmidecode" and "hdparm"
>
> This is definitelly happening on my PC called "picard" and occasionally
> happens on "kirk" and I'm not sure which drive(s) in "picard" so I've
> attached both.
I don't think it would happen on a custom made PC. Can you please post
the result of "smartctl -a"?
--
tejun
next prev parent reply other threads:[~2008-08-01 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 15:59 libata problems Gavin Cameron
2008-08-01 8:48 ` Tejun Heo [this message]
[not found] ` <4898BD4F.90709@gavsworld.net>
[not found] ` <4898F11D.1080902@kernel.org>
[not found] ` <4899EE03.3060204@gavsworld.net>
2008-08-13 9:33 ` Tejun Heo
2008-08-18 22:03 ` Gavin Cameron
[not found] ` <495F5AB3.1090800@gavsworld.net>
2009-01-14 5:05 ` Tejun Heo
2009-01-16 16:30 ` Gavin Cameron
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=4892CDED.6080302@kernel.org \
--to=tj@kernel.org \
--cc=gavin@gavsworld.net \
--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;
as well as URLs for NNTP newsgroup(s).