From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arne Jansen Subject: Re: 3.2-rc4: scrubbing locks up the kernel, then hung tasks on boot Date: Tue, 24 Jan 2012 11:29:26 +0100 Message-ID: <4F1E8806.5080504@gmx.net> References: <201112171833.34720.Martin@lichtvoll.de> <201201211149.53403.Martin@lichtvoll.de> <4F1E79AB.10206@gmx.net> (sfid-20120124_103332_350492_DEB3AE00) <201201241116.11489.Martin@lichtvoll.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: linux-btrfs@vger.kernel.org To: Martin Steigerwald Return-path: In-Reply-To: <201201241116.11489.Martin@lichtvoll.de> List-ID: On 24.01.2012 11:16, Martin Steigerwald wrote: > Am Dienstag, 24. Januar 2012 schrieb Arne Jansen: >> On 21.01.2012 11:49, Martin Steigerwald wrote: >>> Am Dienstag, 20. Dezember 2011 schrieb Martin Steigerwald: >>> >>> When I do btrfs scrub start / the machine locks immediately up hard. >> >> Can you please give me the output of sysrq-w when the machine is locked >> up? > > What would be the easiest way to do that? > > The machine is locked up, means, no mouse, no keyboard, no ping - as far > as I remember I tested a ping, but I can verify -, no nothing. Hm, I always use a (hardware) serial console, but I think on default loglevel the sysrq-output goes to dmesg only, so you have to adjust the loglevel also. Normally I have a ssh into the box running with a tail -f /var/log/messages. This locks up very seldom. Have you tried some sysrq combinations? It might work, even when the keyboard looks locked up in all other respects. > > Serial console with USB serial adapter? > > Thanks,