* btrfs oops on dodgy SSD
@ 2010-10-06 1:07 Dave Airlie
2010-10-06 15:15 ` Chris Mason
0 siblings, 1 reply; 3+ messages in thread
From: Dave Airlie @ 2010-10-06 1:07 UTC (permalink / raw)
To: Chris Mason, LKML
[-- Attachment #1: Type: text/plain, Size: 7057 bytes --]
I have an SSD which I use for scratch builds and stuff, it seems to be
broken or just dislike my NV sata controller.
Was just running Linus tree and got the attached oops when doing a
kernel build on it this morning.
oops didn't come out in logs, though there were some disk reset and a
hung task detect.
Might help btrfs robustness maybe if we could avoid the panic ;-)
Dave.
this:
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: EH in SWNCQ
mode,QC:qc_active 0x3FE sactive 0x3FE
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: SWNCQ:qc_active 0xFE
defer_bits 0x300 last_issue_tag 0x7
Oct 6 10:11:57 clockmaker-el6 kernel: dhfis 0x7E dmafis 0x2 sdbfis 0x0
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: ATA_REG 0x41 ERR_REG 0x84
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: tag : dhfis dmafis sdbfis sacitve
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: tag 0x1: 1 1 0 1
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: tag 0x2: 1 0 0 1
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: tag 0x3: 1 0 0 1
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: tag 0x4: 1 0 0 1
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: tag 0x5: 1 0 0 1
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: tag 0x6: 1 0 0 1
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: tag 0x7: 0 0 0 1
Oct 6 10:11:57 clockmaker-el6 kernel: ata2.00: exception Emask 0x1
SAct 0x3fe SErr 0x3800000 action 0x6 frozen
Oct 6 10:11:57 clockmaker-el6 kernel: ata2.00: Ata error. fis:0x21
Oct 6 10:11:57 clockmaker-el6 kernel: ata2: SError: { LinkSeq
TrStaTrns UnrecFIS }
Oct 6 10:11:57 clockmaker-el6 kernel: ata2.00: failed command: READ
FPDMA QUEUED
Oct 6 10:11:57 clockmaker-el6 kernel: ata2.00: cmd
60/08:08:4f:6c:26/00:00:02:00:00/40 tag 1 ncq 4096 in
Oct 6 10:11:57 clockmaker-el6 kernel: res
41/84:38:b7:6c:26/84:00:02:00:00/40 Emask 0x10 (ATA bus error)
Oct 6 10:11:57 clockmaker-el6 kernel: ata2.00: status: { DRDY ERR }
then later
6 10:47:20 clockmaker-el6 kernel: ata2: SRST failed (errno=-16)
Oct 6 10:47:20 clockmaker-el6 kernel: ata2: reset failed, giving up
Oct 6 10:47:20 clockmaker-el6 kernel: ata2: exception Emask 0x10 SAct
0x0 SErr 0x1950000 action 0xe frozen t2
Oct 6 10:47:20 clockmaker-el6 kernel: ata2: SError: { PHYRdyChg
CommWake Dispar LinkSeq TrStaTrns }
Oct 6 10:47:20 clockmaker-el6 kernel: ata2: hard resetting link
Oct 6 10:47:26 clockmaker-el6 kernel: ata2: link is slow to respond,
please be patient (ready=0)
Oct 6 10:47:30 clockmaker-el6 kernel: ata2: SRST failed (errno=-16)
Oct 6 10:47:30 clockmaker-el6 kernel: ata2: hard resetting link
Oct 6 10:47:36 clockmaker-el6 kernel: ata2: link is slow to respond,
please be patient (ready=0)
Oct 6 10:47:40 clockmaker-el6 kernel: ata2: SRST failed (errno=-16)
Oct 6 10:47:40 clockmaker-el6 kernel: ata2: hard resetting link
Oct 6 10:47:46 clockmaker-el6 kernel: ata2: link is slow to respond,
please be patient (ready=0)
Oct 6 10:48:15 clockmaker-el6 kernel: ata2: SRST failed (errno=-16)
Oct 6 10:48:15 clockmaker-el6 kernel: ata2: limiting SATA link speed
to 1.5 Gbps
Oct 6 10:48:15 clockmaker-el6 kernel: ata2: hard resetting link
Oct 6 10:48:20 clockmaker-el6 kernel: ata2: SRST failed (errno=-16)
Oct 6 10:48:20 clockmaker-el6 kernel: ata2: reset failed, giving up
Oct 6 10:48:20 clockmaker-el6 kernel: ata2: exception Emask 0x10 SAct
0x0 SErr 0x1950000 action 0xe frozen t1
Oct 6 10:48:20 clockmaker-el6 kernel: ata2: SError: { PHYRdyChg
CommWake Dispar LinkSeq TrStaTrns }
Oct 6 10:48:20 clockmaker-el6 kernel: ata2: hard resetting link
Oct 6 10:48:21 clockmaker-el6 kernel: INFO: task btrfs-transacti:1036
blocked for more than 120 seconds.
Oct 6 10:48:21 clockmaker-el6 kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 6 10:48:21 clockmaker-el6 kernel: btrfs-transac D c2804c40 0
1036 2 0x00000008
Oct 6 10:48:21 clockmaker-el6 kernel: f3a21a90 00000046 00000001
c2804c40 00000002 f3acfb34 f3acfb30 00000000
Oct 6 10:48:21 clockmaker-el6 kernel: 00000000 f0163e40 00000237
c0ac0060 f26cab71 00000237 c0ac0060 f3a21d38
Oct 6 10:48:21 clockmaker-el6 kernel: c0ac0060 c0abbb34 c0ac0060
f3a21d38 f3994000 00000400 0020a899 f3a21a90
Oct 6 10:48:21 clockmaker-el6 kernel: Call Trace:
Oct 6 10:48:21 clockmaker-el6 kernel: [<c080bab9>] ? io_schedule+0x59/0xa0
Oct 6 10:48:21 clockmaker-el6 kernel: [<c04d5a0c>] ? sync_page+0x2c/0x40
Oct 6 10:48:21 clockmaker-el6 kernel: [<c080c1a5>] ? __wait_on_bit+0x45/0x70
Oct 6 10:48:21 clockmaker-el6 kernel: [<c04d59e0>] ? sync_page+0x0/0x40
Oct 6 10:48:21 clockmaker-el6 kernel: [<c04d5c26>] ? wait_on_page_bit+0x96/0xb0
Oct 6 10:48:21 clockmaker-el6 kernel: [<c0470d50>] ? wake_bit_function+0x0/0x60
Oct 6 10:48:21 clockmaker-el6 kernel: [<fae25d49>] ?
read_extent_buffer_pages+0x3c9/0x420 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadfbca6>] ?
btree_read_extent_buffer_pages+0x56/0xc0 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadf8f70>] ?
btree_get_extent+0x0/0x200 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadfbd99>] ?
read_tree_block+0x49/0x60 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadde7d5>] ?
read_block_for_search+0x105/0x390 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadfdaa6>] ?
btrfs_buffer_uptodate+0x46/0x70 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<c0436c2a>] ?
kmap_atomic_prot+0x11a/0x150
Oct 6 10:48:21 clockmaker-el6 kernel: [<c0436ac7>] ? kunmap_atomic+0x67/0x80
Oct 6 10:48:21 clockmaker-el6 kernel: [<fade524f>] ?
btrfs_search_slot+0x21f/0x6a0 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadefb7d>] ?
lookup_inline_extent_backref+0x13d/0x590 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fae20087>] ?
set_extent_dirty+0x47/0x60 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadf07ef>] ?
__btrfs_free_extent+0x11f/0x950 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadf39e4>] ?
run_clustered_refs+0x584/0x970 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fae0add0>] ?
btrfs_get_extent+0x0/0xb00 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<c04e7cd4>] ? do_writepages+0x14/0x30
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadf3e77>] ?
btrfs_run_delayed_refs+0xa7/0x1d0 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fae1da80>] ?
btrfs_run_ordered_operations+0x1b0/0x1d0 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadfee75>] ?
btrfs_commit_transaction+0x65/0x650 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<c080c4b1>] ? mutex_lock+0x11/0x40
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadff7ed>] ?
start_transaction+0x18d/0x210 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<c0470d10>] ?
autoremove_wake_function+0x0/0x40
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadf9dbf>] ?
transaction_kthread+0x21f/0x230 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<c043d7b0>] ? complete+0x40/0x60
Oct 6 10:48:21 clockmaker-el6 kernel: [<fadf9ba0>] ?
transaction_kthread+0x0/0x230 [btrfs]
Oct 6 10:48:21 clockmaker-el6 kernel: [<c0470ad4>] ? kthread+0x74/0x80
Oct 6 10:48:21 clockmaker-el6 kernel: [<c0470a60>] ? kthread+0x0/0x80
Oct 6 10:48:21 clockmaker-el6 kernel: [<c040a647>] ?
kernel_thread_helper+0x7/0x10
[-- Attachment #2: photo.jpg --]
[-- Type: image/jpeg, Size: 240499 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: btrfs oops on dodgy SSD
2010-10-06 1:07 btrfs oops on dodgy SSD Dave Airlie
@ 2010-10-06 15:15 ` Chris Mason
2010-10-07 1:39 ` Li Zefan
0 siblings, 1 reply; 3+ messages in thread
From: Chris Mason @ 2010-10-06 15:15 UTC (permalink / raw)
To: Dave Airlie; +Cc: LKML
On Wed, Oct 06, 2010 at 11:07:10AM +1000, Dave Airlie wrote:
> I have an SSD which I use for scratch builds and stuff, it seems to be
> broken or just dislike my NV sata controller.
>
> Was just running Linus tree and got the attached oops when doing a
> kernel build on it this morning.
>
> oops didn't come out in logs, though there were some disk reset and a
> hung task detect.
>
> Might help btrfs robustness maybe if we could avoid the panic ;-)
Ouch, the oops was in the code printing a corrupted btree block. I
should be able to easily trigger this at home...
-chris
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: btrfs oops on dodgy SSD
2010-10-06 15:15 ` Chris Mason
@ 2010-10-07 1:39 ` Li Zefan
0 siblings, 0 replies; 3+ messages in thread
From: Li Zefan @ 2010-10-07 1:39 UTC (permalink / raw)
To: Chris Mason, Dave Airlie, LKML
Chris Mason wrote:
> On Wed, Oct 06, 2010 at 11:07:10AM +1000, Dave Airlie wrote:
>> I have an SSD which I use for scratch builds and stuff, it seems to be
>> broken or just dislike my NV sata controller.
>>
>> Was just running Linus tree and got the attached oops when doing a
>> kernel build on it this morning.
>>
>> oops didn't come out in logs, though there were some disk reset and a
>> hung task detect.
>>
>> Might help btrfs robustness maybe if we could avoid the panic ;-)
>
> Ouch, the oops was in the code printing a corrupted btree block. I
> should be able to easily trigger this at home...
>
This reminded me that weeks ago I found a bug in tree-printing code,
though unrelated to this oops.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-10-07 1:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-06 1:07 btrfs oops on dodgy SSD Dave Airlie
2010-10-06 15:15 ` Chris Mason
2010-10-07 1:39 ` Li Zefan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox