From: Johannes Deisenhofer <joe@bndlg.de>
To: Justin Cormack <justin@street-vision.com>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Undecoded Interrupt with SiL3112 IDE?
Date: Sun, 04 Apr 2004 14:12:03 +0000 [thread overview]
Message-ID: <407017B3.7000705@bndlg.de> (raw)
In-Reply-To: <1080928106.30729.140.camel@lotte.street-vision.com>
Justin Cormack wrote:
> siimage driver has buggy interrupt handling - have seen similar
> behaviour. It appears to be unmaintained. Recommend using libata
> instead.
>
I tried libata from 2.6.5-rc3. Previous versions are considered broken by the
author, especially for error handling.
However, I had far worse problems:
Apr 3 10:18:10 urmel kernel: <3>ata1: DMA timeout, stat 0x0
Apr 3 10:18:10 urmel kernel: ATA: abnormal status 0x58 on port 0xF8854087
Apr 3 10:18:10 urmel kernel: scsi0: ERROR on channel 0, id 0, lun 0, CDB:
Read (10) 00 00 07 65 3f 00 00 c8 00
Apr 3 10:18:10 urmel kernel: Current sda: sense key Medium Error
Apr 3 10:18:10 urmel kernel: Additional sense: Unrecovered read error - auto
reallocate failed
Apr 3 10:18:10 urmel kernel: end_request: I/O error, dev sda, sector 484671
Apr 3 10:18:10 urmel kernel: ATA: abnormal status 0x58 on port 0xF8854087
Apr 3 10:18:10 urmel last message repeated 2 times
Apr 3 10:19:47 urmel PAM_pwdb[3086]: (login) session opened for user root by
(uid=0)
This probably was a hardware problem. A new SATA cable seems to have fixed it.
Can't explain the 'medium error'.
SMART status of the drive is ok. No bad sectors according to SMART, none
reallocated.
Jo
prev parent reply other threads:[~2004-04-04 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 17:29 Undecoded Interrupt with SiL3112 IDE? Johannes Deisenhofer
2004-04-02 17:48 ` Justin Cormack
2004-04-04 14:12 ` Johannes Deisenhofer [this message]
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=407017B3.7000705@bndlg.de \
--to=joe@bndlg.de \
--cc=justin@street-vision.com \
--cc=linux-kernel@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