From: "Torsten Kaiser" <just.for.lkml@googlemail.com>
To: "Tejun Heo" <htejun@gmail.com>, "Jeff Garzik" <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: sata_sil24 broken since 2.6.23-rc4-mm1
Date: Wed, 26 Sep 2007 22:26:43 +0200 [thread overview]
Message-ID: <64bb37e0709261326h4890a07fx60c7d6772e4e63c4@mail.gmail.com> (raw)
As reported in the "2.6.23-rc4-mm1"-thread and the "What's in
linux-2.6-block.git for 2.6.24"-thread I'm having trouble that
sometimes on bootup one drive from the SiI-3132 throws errors and
becomes inaccesible.
The latest kernel I have seen this error was 2.6.23-rc7-mm1.
>From 7 boots 2 times the following happend:
Sep 25 07:42:11 treogen [ 33.810000] md1: bitmap initialized from
disk: read 10/10 pages, set 0 bits
Sep 25 07:42:11 treogen [ 33.810000] created bitmap (145 pages) for device md1
Sep 25 07:42:11 treogen [ 63.910000] ata1.00: exception Emask 0x0
SAct 0x1 SErr 0x0 action 0x6 frozen
Sep 25 07:42:11 treogen [ 63.910000] ata1.00: cmd
61/08:00:09:d6:42/00:00:25:00:00/40 tag 0 cdb 0x0 data 4096 out
Sep 25 07:42:11 treogen [ 63.910000] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 25 07:42:11 treogen [ 63.910000] ata1.00: status: {DRDY }
Sep 25 07:42:11 treogen [ 63.910000] ata1: hard resetting link
Sep 25 07:42:11 treogen [ 66.210000] ata1: softreset failed (port not ready)
Sep 25 07:42:11 treogen [ 66.210000] ata1: reset failed (errno=-5),
retrying in 8 secs
Sep 25 07:42:11 treogen [ 73.910000] ata1: hard resetting link
Sep 25 07:42:11 treogen [ 76.210000] ata1: softreset failed (port not ready)
Sep 25 07:42:11 treogen [ 76.210000] ata1: reset failed (errno=-5),
retrying in 8 secs
Sep 25 07:42:11 treogen [ 83.910000] ata1: hard resetting link
Sep 25 07:42:11 treogen [ 86.210000] ata1: softreset failed (port not ready)
Sep 25 07:42:11 treogen [ 86.210000] ata1: reset failed (errno=-5),
retrying in 33 secs
Sep 25 07:42:11 treogen [ 118.910000] ata1: limiting SATA link speed
to 1.5 Gbps
Sep 25 07:42:11 treogen [ 118.910000] ata1: hard resetting link
Sep 25 07:42:11 treogen [ 121.210000] ata1: softreset failed (port not ready)
Sep 25 07:42:11 treogen [ 121.210000] ata1: reset failed, giving up
Sep 25 07:42:11 treogen [ 121.210000] ata1.00: disabled
Sep 25 07:42:11 treogen [ 121.210000] ata1: EH complete
Sep 25 07:42:11 treogen [ 121.210000] sd 0:0:0:0: [sda] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Sep 25 07:42:11 treogen [ 121.210000] end_request: I/O error, dev
sda, sector 625137161
Sep 25 07:42:11 treogen [ 121.210000] md: super_written gets
error=-5, uptodate=0
Sep 25 07:42:11 treogen [ 121.210000] raid5: Disk failure on sda2,
disabling device. Operation continuing on 2 devices
Comparing the driver/ata directory from rc3-mm1 and rc4-mm1 the
following change looked the most suspicions to me:
http://git.kernel.org/?p=linux/kernel/git/jgarzik/libata-dev.git;a=blobdiff;f=drivers/ata/sata_sil24.c;h=3dcb223117be9739ee04d70b6bfc776a4b839a3f;hp=e0cd31aa8002350add53ba6ff07493e503275244;hb=020bc1bd8d369a77bd9379cd9763ac0057651753;hpb=8d4bdf8087e682df98bdb856f6ad451bf6d597e7
That after rc4-mm1 the sata_sil24.c did not change anymore also
matches the occurrence of the error.
To confirm my theorie I exchanged the sata_sil24.c from rc8-mm1 with
the version from rc3-mm1.
I was able to boot the resulting kernel successfully 5 times, without
the error happening again.
Torsten
next reply other threads:[~2007-09-26 20:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 20:26 Torsten Kaiser [this message]
2007-09-27 4:54 ` Tejun Heo
2007-09-27 4:57 ` Tejun Heo
2007-09-27 6:14 ` Torsten Kaiser
2007-09-27 6:24 ` Jeff Garzik
2007-09-27 17:34 ` Torsten Kaiser
2007-09-27 20:22 ` Tejun Heo
2007-09-28 5:36 ` Torsten Kaiser
2007-09-30 6:00 ` Torsten Kaiser
2007-09-30 14:34 ` Tejun Heo
2007-09-30 16:19 ` Torsten Kaiser
2007-09-30 17:39 ` Tejun Heo
2007-09-30 18:39 ` Torsten Kaiser
2007-10-01 18:00 ` Torsten Kaiser
2007-10-03 15:21 ` Torsten Kaiser
2007-10-03 15:55 ` Torsten Kaiser
2007-10-03 16:38 ` Matt Mackall
2007-10-03 17:36 ` Torsten Kaiser
2007-10-03 17:51 ` Matt Mackall
2007-10-03 18:06 ` Torsten Kaiser
2007-10-04 5:32 ` Torsten Kaiser
2007-10-04 17:05 ` Matt Mackall
2007-10-05 6:06 ` Torsten Kaiser
2007-10-07 8:44 ` Torsten Kaiser
2007-10-07 14:39 ` Torsten Kaiser
2007-10-11 3:25 ` Tejun Heo
2007-10-11 5:54 ` Torsten Kaiser
2007-10-11 6:26 ` Tejun Heo
2007-10-11 17:51 ` Torsten Kaiser
2007-10-11 8:26 ` Jens Axboe
2007-10-11 8:36 ` Tejun Heo
2007-10-11 10:28 ` Jens Axboe
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=64bb37e0709261326h4890a07fx60c7d6772e4e63c4@mail.gmail.com \
--to=just.for.lkml@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--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
all inboxes | Powered by JetHome®