FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 12-15-2011, 04:44 AM
Ben Hutchings
 
Default Bug#625922: SATA devices get reset without real hardware failure

Summary of the bug so far:

Messages #5, #63 from Natalia Portillo <claunia@claunia.com>:

package version: Ubuntu 2.6.38-8.?? (Debian did not use version 2.6.38-8)
Debian 2.6.32-38 ("all squeeze kernels up to two weeks away")
(Gentoo 2.6.32 does not have the problem)
drive(s): Seagate ST2000DL003-9VT166
controller(s): Intel ICH9 (AHCI mode) (and JMicron JMB36?)
kernel log:
[255352.928063] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[255352.928071] ata4.00: failed command: FLUSH CACHE EXT
[255352.928080] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[255352.928082] res 40/00:01:09:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[255352.928087] ata4.00: status: { DRDY }
[255352.928096] ata4: hard resetting link
[255362.932028] ata4: softreset failed (1st FIS failed)
[255362.932036] ata4: hard resetting link
[255372.932018] ata4: softreset failed (1st FIS failed)
[255372.932026] ata4: hard resetting link
[255407.932029] ata4: softreset failed (1st FIS failed)
[255407.932038] ata4: limiting SATA link speed to 1.5 Gbps
[255407.932042] ata4: hard resetting link
[255413.120028] ata4: softreset failed (device not ready)
[255413.120035] ata4: reset failed, giving up
[255413.120040] ata4.00: disabled
[255413.120060] ata4: EH complete

Messages #18, #33 from Paul Faure <paul@faure.ca>:

package version: Ubuntu 2.6.38-8.42
drive(s): Seagate ST2000DL003, ST2000DL003-9VT1
(but no problem with ST32000644NS)
controller(s): Intel ICH9 (legacy mode)
kernel log:
[247972.000120] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[247972.000132] ata3.00: failed command: FLUSH CACHE EXT
[247972.000146] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[247972.000148] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[247972.000155] ata3.00: status: { DRDY }
[247972.000169] ata3: hard resetting link
[247977.550053] ata3: link is slow to respond, please be patient (ready=0)
[247982.050113] ata3: SRST failed (errno=-16)
[247982.050138] ata3: hard resetting link
[247987.600068] ata3: link is slow to respond, please be patient (ready=0)
[247992.100087] ata3: SRST failed (errno=-16)
[247992.100109] ata3: hard resetting link
[247997.650040] ata3: link is slow to respond, please be patient (ready=0)
[248027.110050] ata3: SRST failed (errno=-16)
[248027.110066] ata3: limiting SATA link speed to 1.5 Gbps
[248027.110075] ata3: hard resetting link
[248032.120042] ata3: SRST failed (errno=-16)
[248032.120053] ata3: reset failed, giving up
[248032.120060] ata3.00: disabled
[248032.120069] ata3.00: device reported invalid CHS sector 0
[248032.120094] ata3: EH complete

Message #23 from Christian Robottom Reis <kiko@canonical.com>:

package version: Ubuntu 2.6.35-28
drive(s): Seagate ST2000DL003-9VT166
controller(s): ?
kernel log: not provided

Messages #38, #43 from Juhani Karlsson <juhani.karlsson@lrdlnx.iki.fi>:

Seems to be a different problem.

Message #48 from Javier Ortega Conde (Malkavian) <malkavian666@gmail.com>:

A bunch of different problems.

Message #70 from Alessio Treglia <alessio@debian.org>:

package version: Debian 3.1.1-1
drive(s): TOSHIBA MK5055GSXN
controller(s): ? (AHCI)
kernel log:
[ 6838.837215] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 6838.837222] ata2.00: failed command: FLUSH CACHE EXT
[ 6838.837230] ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 6838.837231] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 6838.837241] ata2.00: status: { DRDY }
[ 6838.837254] ata2: hard resetting link
[ 6844.199464] ata2: link is slow to respond, please be patient (ready=0)
[ 6848.846062] ata2: COMRESET failed (errno=-16)
[ 6848.846075] ata2: hard resetting link
[ 6854.208316] ata2: link is slow to respond, please be patient (ready=0)
[ 6858.854933] ata2: COMRESET failed (errno=-16)
[ 6858.854943] ata2: hard resetting link
[ 6864.213249] ata2: link is slow to respond, please be patient (ready=0)
[ 6875.073958] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 6875.117586] ata2.00: configured for UDMA/100
[ 6875.117598] ata2.00: retrying FLUSH 0xea Emask 0x4
[ 6875.129847] ata2.00: device eported invalid CHS sector 0
[ 6875.129864] ata2: EH complete

--
Ben Hutchings
Computers are not intelligent. They only think they are.
 
Old 01-26-2012, 09:58 AM
Alessio Treglia
 
Default Bug#625922: SATA devices get reset without real hardware failure

Hi all,

seems unreproducible to me with linux-2.6 3.1.8-2 currently available
in testing.

Regards,

--
Alessio Treglia * * * * *| www.alessiotreglia.com
Debian Developer * * * * | alessio@debian.org
Ubuntu Core Developer * *| quadrispro@ubuntu.com
0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAMHuwozR12Y6EwtHUOcGLyqGZf6gLfd9rzjF-Fw1Vi_ek7=ZaA@mail.gmail.com">http://lists.debian.org/CAMHuwozR12Y6EwtHUOcGLyqGZf6gLfd9rzjF-Fw1Vi_ek7=ZaA@mail.gmail.com
 
Old 05-16-2012, 06:49 AM
Francois Gouget
 
Default Bug#625922: SATA devices get reset without real hardware failure

This is mostly a mee too to report that I have had this issue at least
three times in the past 4 months (more or less), and every time with the
one ST2000DL003-9VT166 drive in my computer (out of four). I'm also
running with the CC32 firmware (apparently there's nothing more recent)
but the Linux kernel is newer:

Linux version 3.2.0-2-amd64 (Debian 3.2.15-1)
(debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) )
#1 SMP Sun Apr 15 16:47:38 UTC 2012

Other details that may be relevant:
* It's part of a software RAID1 device (which causes it to drop out
obviously).
* I did a long test with SeaTools and it passed.

Here's how it started last night:

May 16 01:42:29 amboise kernel: [713845.984035] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
May 16 01:42:29 amboise kernel: [713845.984040] ata5.00: failed command: FLUSH CACHE EXT
May 16 01:42:29 amboise kernel: [713845.984046] ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
May 16 01:42:29 amboise kernel: [713845.984047] res 40/00:02:00:08:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
May 16 01:42:29 amboise kernel: [713845.984051] ata5.00: status: { DRDY }
May 16 01:42:29 amboise kernel: [713845.984060] ata5.00: hard resetting link
May 16 01:42:29 amboise kernel: [713846.304016] ata5.01: hard resetting link
May 16 01:42:34 amboise kernel: [713851.820015] ata5.00: link is slow to respond, please be patient (ready=0)
May 16 01:42:39 amboise kernel: [713856.020035] ata5.00: SRST failed (errno=-16)
May 16 01:42:39 amboise kernel: [713856.020045] ata5.00: hard resetting link
May 16 01:42:39 amboise kernel: [713856.340022] ata5.01: hard resetting link
May 16 01:42:44 amboise kernel: [713861.856014] ata5.00: link is slow to respond, please be patient (ready=0)
May 16 01:42:49 amboise kernel: [713866.056013] ata5.00: SRST failed (errno=-16)
May 16 01:42:49 amboise kernel: [713866.056022] ata5.00: hard resetting link
May 16 01:42:49 amboise kernel: [713866.376014] ata5.01: hard resetting link
May 16 01:42:54 amboise kernel: [713871.892010] ata5.00: link is slow to respond, please be patient (ready=0)
May 16 01:43:24 amboise kernel: [713901.068011] ata5.00: SRST failed (errno=-16)
May 16 01:43:24 amboise kernel: [713901.068019] ata5.00: limiting SATA link speed to 1.5 Gbps
May 16 01:43:24 amboise kernel: [713901.068023] ata5.01: limiting SATA link speed to 1.5 Gbps
May 16 01:43:24 amboise kernel: [713901.068028] ata5.00: hard resetting link
May 16 01:43:24 amboise kernel: [713901.388013] ata5.01: hard resetting link
May 16 01:43:29 amboise kernel: [713906.120012] ata5.00: SRST failed (errno=-16)
May 16 01:43:29 amboise kernel: [713906.130577] ata5.00: reset failed, giving up
May 16 01:43:29 amboise kernel: [713906.130580] ata5.00: disabled
May 16 01:43:29 amboise kernel: [713906.130585] ata5.01: disabled
May 16 01:43:29 amboise kernel: [713906.130589] ata5.00: device reported invalid CHS sector 0
May 16 01:43:29 amboise kernel: [713906.130598] ata5: EH complete
May 16 01:43:29 amboise kernel: [713906.130670] sd 4:0:0:0: [sdb] Unhandled error code
May 16 01:43:29 amboise kernel: [713906.130677] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 16 01:43:29 amboise kernel: [713906.130691] sd 4:0:0:0: [sdb] CDB: Write(10): 2a 00 17 00 6f 80 00 00 08 00
May 16 01:43:29 amboise kernel: [713906.130713] end_request: I/O error, dev sdb, sector 385904512


--
Francois Gouget <fgouget@free.fr> http://fgouget.free.fr/
In theory, theory and practice are the same, but in practice they're different.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: alpine.DEB.2.02.1205160840120.27276@amboise.dolphi n">http://lists.debian.org/alpine.DEB.2.02.1205160840120.27276@amboise.dolphi n
 

Thread Tools




All times are GMT. The time now is 12:23 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org