On Sat, Dec 6, 2014 at 7:45 PM, Andrew Wade <andrew.j.wade@xxxxxxxxx> wrote: > I've had repeated lockups as well; I can trigger them by attempting to > copy files off of a damaged DVD. > > I saw the btrfs_assert_delayed_root_empty warning as well, but not > during the lockup; instead I saw it on a boot after a lockup. > > During the lockup I sometimes get a different message: > > Dec 6 19:41:11 pluto kernel: [347280.104032] INFO: task init:1228 > blocked for more than 120 seconds. > Dec 6 19:41:11 pluto kernel: [347280.104038] Tainted: G > E 3.18.0-rc7-ajw #78 > Dec 6 19:41:11 pluto kernel: [347280.104039] "echo 0 > > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > Dec 6 19:41:11 pluto kernel: [347280.104041] init D > ffff88011fc13640 0 1228 1215 0x00000000 Typically a dev will want to see the result of sysrq+w to show details on the blocked tasks. I suggest reproducing the conditions, then issue sysrq+w, then recapture dmesg. And also you might look at your own previous post in the archives and see if it formats legibly because the result I've got in gmail (above) is wrapping poorly and makes it hard to read. If you can't figure that out, then it's easier to just file a bug at bugzilla.kernel.org, and attach the dmesg output as a text file, then cite the bug URL in this thread. https://www.kernel.org/doc/Documentation/sysrq.txt -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
