linux-kernel - Re: USB misbehavior causes system hang

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <20070301133857.GA4068@pool-71-161-135-187.spfdma.east.verizon.net>
Date:	Thu, 01 Mar 2007 08:39:07 -0500
From:	Eric Buddington <ebuddington@...izon.net>
To:	Pete Zaitcev <zaitcev@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: USB misbehavior causes system hang

On Tue, Feb 27, 2007 at 01:49:40PM -0800, Pete Zaitcev wrote:
> However, the main issue here is the OOM with all the dirty data.
> We saw that before. For some weird reason, ext3 is especially good
> at producing the immense amounts of write-out. Are you on ext3 or
> VFAT on that drive?

Reiser4.

> Please try to find the CPU traces by hitting SysRq-w, SysRq-p. CPU
> is looping under a lock somewhere and eventually it cases the watchdog
> to trigger. It may be a USB issue, maybe a VM issue. I can't tell
> until we get stack traces.

I can log the dmesg's via netconsole, but I'm often not at the
computer to use SysRq. I've just discovered /proc/sysrq-trigger, which
I can maybe use from a script that watches dmesg. I'll report back if
I can catch the dumps.

-Eric



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/