From: Tejun Heo <htejun@gmail.com>
To: Jochen Heuer <jogi-kernel@planetzork.ping.de>
Cc: linux-ide@vger.kernel.org
Subject: Re: Bug or HW? ata1: command timeout, stat 0x50 host_stat 0x4
Date: Wed, 28 Jun 2006 15:33:47 +0900 [thread overview]
Message-ID: <44A222CB.1080300@gmail.com> (raw)
In-Reply-To: <20060627184320.GA16782@planetzork.ping.de>
Jochen Heuer wrote:
> Hi everyone!
>
> I have some severe problems on my Athlon X2 system. The problem is that the
> system sometimes hangs (during plain web browsing). If I wait long enough the
> system comes to a complete halt so that not even sysrq does work. The system
> has to be reset and then everything is fine again for some time.
>
> Today I was quick enough to switch from X11 to console and check sysrq output.
> After enabling logging (sysrq+6) I got the following messages on console:
>
> ata1: command 0xca timeout, stat 0x50 host_stat 0x4
> ata1: status=0x50 { DriveReady SeekComplete }
> ata1: command 0xea timeout, stat 0x50 host_stat 0x0
> ata1: status=0x50 { DriveReady SeekComplete }
The original error is probably a hardware problem.
> Then the system was frozen again and only reset did help. Log files don't
> contain any infos which makes sense since ata1 is the disk with the OS and
> where metalog should save log files ...
>
> Some infos to my system:
>
> Asus A8V with Athlon X2 3800 and 2GB memory
> current kernel 2.6.17 with SMP compiled
>
> I had hoped 2.6.17 would fix this since I seem to remember some fixes for
> libata with similar error messages. But at least on my system it did not.
Can you apply the following patch and see what happens?
http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17-20060625-1.tar.bz2
--
tejun
next prev parent reply other threads:[~2006-06-28 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 18:43 Bug or HW? ata1: command timeout, stat 0x50 host_stat 0x4 Jochen Heuer
2006-06-28 6:33 ` Tejun Heo [this message]
2006-06-28 8:09 ` Jochen Heuer
2006-07-02 0:07 ` Jochen Heuer
2006-07-04 15:31 ` Mark Lord
2006-07-04 22:24 ` Jochen Heuer
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=44A222CB.1080300@gmail.com \
--to=htejun@gmail.com \
--cc=jogi-kernel@planetzork.ping.de \
--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).