On Mon, Feb 11, 2013 at 4:05 PM, Josef Bacik <jbacik@xxxxxxxxxxxx> wrote: > On Fri, Feb 08, 2013 at 04:12:17PM -0700, Florian Hofmann wrote: >> I ran it as root. The first times there was no output whatsoever. This >> time triggering gave the SysRq : Show Blocked State line. Strange >> > > Well that's weird, it looks like you don't have any blocked tasks, so either > sysrq+w is screwing up or you are getting stuck in something CPU intensive. Try > doing sysrq+w next time it happens again and also run top and see if something > is using up 100% of the CPU. If it's something chewing up CPU then I'll tell > you how to figure out what's going on. Thanks, > I noticed you have the FS mounted with compress flag (compress=lzo). Could it be that your CPU is bottle-necking the process? > Josef > -- > 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 -- Caution: breathing may be hazardous to your health. #include <stdio.h> int main(){printf("%s","\x4c\x65\x6f\x6e\x69\x64\x61\x73");} -- 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
