On Sun, Dec 7, 2014 at 2:20 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > On Sat, Dec 6, 2014 at 7:45 PM, Andrew Wade <andrew.j.wade@xxxxxxxxx> wrote: >> ... > > 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 > Thanks Chris. I found an exiting bug for my issue and attached a log with sysrq+w https://bugzilla.kernel.org/show_bug.cgi?id=82251 thanks, Andrew -- 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
