From: Robert Hancock <hancockrwd@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: SSD + sata_nv + btrfs oops
Date: Mon, 31 May 2010 22:59:44 -0600 [thread overview]
Message-ID: <4C0493C0.7000703@gmail.com> (raw)
In-Reply-To: <AANLkTilqsIdlzZgUf7TMLHYKqHDZoVkcs42vcG8wXKEr@mail.gmail.com>
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?
next prev parent reply other threads:[~2010-06-01 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 3:04 SSD + sata_nv + btrfs oops Dave Airlie
2010-06-01 4:59 ` Robert Hancock [this message]
2010-06-01 5:02 ` Dave Airlie
2010-06-01 5:06 ` Robert Hancock
2010-06-01 5:36 ` Jeff Garzik
2010-06-01 11:23 ` Chris Mason
2010-06-08 19:24 ` Maciej Rutecki
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=4C0493C0.7000703@gmail.com \
--to=hancockrwd@gmail.com \
--cc=airlied@gmail.com \
--cc=chris.mason@oracle.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