linux-kernel - Re: Seagate disk freeze for 30 seconds then comes back (RecovComm 10B8B)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:  <4980FDE6.7080406@shaw.ca>
Date:	Wed, 28 Jan 2009 18:52:54 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	linux-kernel@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject:  Re: Seagate disk freeze for 30 seconds then comes back (RecovComm
   10B8B)

Catalin(ux) M. BOIE wrote:
> Hello!
> 
> I have a ST9160821AS drive, firmware 3.BHE, and I experience some seldom 
> problems with it. It is in a HP 6715s HP laptop, kernel 2.6.27.5.
> 
> The error message is:
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x80002 action 0x6 frozen
> ata1: SError: { RecovComm 10B8B }
> ata1.00: cmd ca/00:f8:11:b8:38/00:00:00:00:00/ec tag 0 dma 126976 out
> res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata1.00: status: { DRDY }
> ata1: hard resetting link
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
> ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
> ata1.00: configured for UDMA/100
> ata1: EH complete
> sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
> support DPO or FUA
> 
> When it happens, the system freezes for around 30 seconds.
> 
> Seagate told me that there is no firmware update for this drive.
> 
> Please, let me know if it is a software issue.

Quite unlikely, it looks like something caused the communications with 
the drive to be dropped. It's likely either a drive, cabling/connection 
or power problem (the latter two seem unlikely in a laptop though, 
unless the drive isn't connected all the way or something..)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/