linux-kernel - Re: SSD + sata

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]

Date:	Mon, 31 May 2010 22:59:44 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Dave Airlie <airlied@...il.com>
CC:	LKML <linux-kernel@...r.kernel.org>, Jeff Garzik <jeff@...zik.org>,
	Chris Mason <chris.mason@...cle.com>
Subject: Re: SSD + sata_nv + btrfs oops

On 05/31/2010 09:04 PM, Dave Airlie wrote:
> Hi guys,
>
> I've been running an Intel SSD (the KS one) on my Dell XPS710 desktop
> machine, with btrfs on it.
>
> I'm not sure the btrfs oops isn't due to the disk/controller doing
> something bad (almost guaranteed).
>
> Attached the dmesg + config, using 2.6.34 + only drm patches.
>
> Jeff I'd be interested in knowing what is happening to the disk before
> btrfs oops.

ata2: EH in SWNCQ mode,QC:qc_active 0x7FFFFE03 sactive 0x7FFFFE03
ata2: SWNCQ:qc_active 0xFE00 defer_bits 0x7FFF0003 last_issue_tag 0xf
   dhfis 0x7E00 dmafis 0x200 sdbfis 0x0
ata2: ATA_REG 0x40 ERR_REG 0x0
ata2: tag : dhfis dmafis sdbfis sacitve
ata2: tag 0x9: 1 1 0 1
ata2: tag 0xa: 1 0 0 1
ata2: tag 0xb: 1 0 0 1
ata2: tag 0xc: 1 0 0 1
ata2: tag 0xd: 1 0 0 1
ata2: tag 0xe: 1 0 0 1
ata2: tag 0xf: 0 0 0 1
ata2.00: exception Emask 0x0 SAct 0x7ffffe03 SErr 0x1800000 action 0x6 
frozen
ata2: SError: { LinkSeq TrStaTrns }

Last line is probably the most informative, SATA link sequence error and 
transport state transition error. That's probably something bad 
happening at the low level between the controller and drive. Is this 
happening repeatedly?
--
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/