From: Jochen Heuer <jogi-kernel@planetzork.ping.de>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Bug or HW? ata1: command timeout, stat 0x50 host_stat 0x4
Date: Wed, 28 Jun 2006 10:09:12 +0200 [thread overview]
Message-ID: <20060628080912.GA18463@planetzork.ping.de> (raw)
In-Reply-To: <44A222CB.1080300@gmail.com>
Hi Tejun,
> >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.
ok, I will try to get this disc replaced after some testing ...
> >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?
Patch is installed and system is running:
libata version 1.30 loaded.
sata_via 0000:00:0f.0: version 1.2
ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 18
sata_via 0000:00:0f.0: routed to hard irq line 10
ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xB802 bmdma 0xA800 irq 18
ata2: SATA max UDMA/133 cmd 0xB400 ctl 0xB002 bmdma 0xA808 irq 18
scsi0 : sata_via
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/133
scsi1 : sata_via
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata2.00: configured for UDMA/133
Vendor: ATA Model: SAMSUNG SP2504C Rev: VT10
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: ST3200822AS Rev: 3.01
Type: Direct-Access ANSI SCSI revision: 05
I will monitor this for a some time. And thanks for the quick response!
Jochen
--
Well, yeah ... I suppose there's no point in getting greedy, is there?
<< Calvin & Hobbes >>
next prev parent reply other threads:[~2006-06-28 8:14 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
2006-06-28 8:09 ` Jochen Heuer [this message]
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=20060628080912.GA18463@planetzork.ping.de \
--to=jogi-kernel@planetzork.ping.de \
--cc=htejun@gmail.com \
--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).