From: alex=lists-linux-kernel@yuriev.com
To: linux-kernel@vger.kernel.org
Subject: SATA errors/messages after upgrade to 2.6.20.7
Date: Sun, 22 Apr 2007 23:56:22 -0400 [thread overview]
Message-ID: <20070423035622.GB10106@s2.yuriev.com> (raw)
It is a Samsung HD501LJ SATA drive connected to 631xESB/632xESB controller.
Reading and writing every block of the drive does not generate any other
errors/failures. This is observed in 2.6.20.7 like a clockwork on any
badblocks -v run or rebuild of a MD raid1 array onto the disk.
It, however, was not observed on 2.6.18 in 182 badblocks -v runs followed by
rebuild of MD raid1 array.
Any idea what it might be?
Apr 23 14:45:34 stdsrv-x86-64bit kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Apr 23 14:45:34 stdsrv-x86-64bit kernel: ata4.00: (irq_stat 0x40000008)
Apr 23 14:45:34 stdsrv-x86-64bit kernel: ata4.00: cmd 60/80:00:14:16:c4/00:00:05:00:00/40 tag 0 cdb 0x0 data 65536 in
Apr 23 14:45:34 stdsrv-x86-64bit kernel: res 51/40:00:40:16:c4/6f:00:05:00:00/40 Emask 0x9 (media error)
Apr 23 14:45:34 stdsrv-x86-64bit kernel: ata4.00: configured for UDMA/133
Apr 23 14:45:34 stdsrv-x86-64bit kernel: ata4: EH complete
Apr 23 14:45:37 stdsrv-x86-64bit kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Apr 23 14:45:37 stdsrv-x86-64bit kernel: ata4.00: (irq_stat 0x40000008)
Apr 23 14:45:37 stdsrv-x86-64bit kernel: ata4.00: cmd 60/80:00:14:16:c4/00:00:05:00:00/40 tag 0 cdb 0x0 data 65536 in
Apr 23 14:45:37 stdsrv-x86-64bit kernel: res 51/40:00:40:16:c4/6f:00:05:00:00/40 Emask 0x9 (media error)
Apr 23 14:45:37 stdsrv-x86-64bit kernel: ata4.00: configured for UDMA/133
Apr 23 14:45:37 stdsrv-x86-64bit kernel: ata4: EH complete
Apr 23 14:45:40 stdsrv-x86-64bit kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Apr 23 14:45:49 stdsrv-x86-64bit kernel: ata4.00: (irq_stat 0x40000008)
Apr 23 14:45:49 stdsrv-x86-64bit kernel: ata4.00: cmd 60/80:00:14:16:c4/00:00:05:00:00/40 tag 0 cdb 0x0 data 65536 in
Apr 23 14:45:49 stdsrv-x86-64bit kernel: res 51/40:00:40:16:c4/6f:00:05:00:00/40 Emask 0x9 (media error)
Apr 23 14:45:49 stdsrv-x86-64bit kernel: ata4.00: configured for UDMA/133
Apr 23 14:45:50 stdsrv-x86-64bit kernel: ata4: EH complete
Apr 23 14:45:50 stdsrv-x86-64bit kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Apr 23 14:45:50 stdsrv-x86-64bit kernel: ata4.00: (irq_stat 0x40000008)
Apr 23 14:45:50 stdsrv-x86-64bit kernel: ata4.00: cmd 60/80:00:14:16:c4/00:00:05:00:00/40 tag 0 cdb 0x0 data 65536 in
Apr 23 14:45:51 stdsrv-x86-64bit kernel: res 51/40:00:40:16:c4/6f:00:05:00:00/40 Emask 0x9 (media error)
Apr 23 14:45:51 stdsrv-x86-64bit kernel: ata4.00: configured for UDMA/133
Apr 23 14:45:51 stdsrv-x86-64bit kernel: ata4: EH complete
Apr 23 14:45:51 stdsrv-x86-64bit kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Apr 23 14:45:52 stdsrv-x86-64bit kernel: ata4.00: (irq_stat 0x40000008)
Apr 23 14:45:52 stdsrv-x86-64bit kernel: ata4.00: cmd 60/80:00:14:16:c4/00:00:05:00:00/40 tag 0 cdb 0x0 data 65536 in
Apr 23 14:45:52 stdsrv-x86-64bit kernel: res 51/40:00:40:16:c4/6f:00:05:00:00/40 Emask 0x9 (media error)
Apr 23 14:45:52 stdsrv-x86-64bit kernel: ata4.00: configured for UDMA/133
Apr 23 14:45:52 stdsrv-x86-64bit kernel: ata4: EH complete
Apr 23 14:45:52 stdsrv-x86-64bit kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Apr 23 14:45:53 stdsrv-x86-64bit kernel: ata4.00: (irq_stat 0x40000008)
Apr 23 14:45:53 stdsrv-x86-64bit kernel: ata4.00: cmd 60/80:00:14:16:c4/00:00:05:00:00/40 tag 0 cdb 0x0 data 65536 in
Apr 23 14:45:53 stdsrv-x86-64bit kernel: res 51/40:00:40:16:c4/6f:00:05:00:00/40 Emask 0x9 (media error)
Apr 23 14:45:54 stdsrv-x86-64bit kernel: ata4.00: configured for UDMA/133
Apr 23 14:45:54 stdsrv-x86-64bit kernel: ata4: EH complete
Apr 23 14:45:54 stdsrv-x86-64bit kernel: SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB)
Apr 23 14:45:54 stdsrv-x86-64bit kernel: sdd: Write Protect is off
Apr 23 14:45:54 stdsrv-x86-64bit kernel: SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 23 14:45:54 stdsrv-x86-64bit kernel: SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB)
Apr 23 14:45:55 stdsrv-x86-64bit kernel: sdd: Write Protect is off
Apr 23 14:45:55 stdsrv-x86-64bit kernel: SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
next reply other threads:[~2007-04-23 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 3:56 alex=lists-linux-kernel [this message]
2007-04-23 5:29 ` Jeff Garzik
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=20070423035622.GB10106@s2.yuriev.com \
--to=alex=lists-linux-kernel@yuriev.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
all inboxes | Powered by JetHome®