linux-kernel - Re: kernel lockups with 2.6.36

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] [day] [month] [year] [list]

Message-Id: <201011170039.54869.thomas@fjellstrom.ca>
Date:	Wed, 17 Nov 2010 00:39:54 -0700
From:	Thomas Fjellstrom <thomas@...llstrom.ca>
To:	Linux Kernel List <linux-kernel@...r.kernel.org>
Subject: Re: kernel lockups with 2.6.36

On November 14, 2010, you wrote:
> Today I experienced something odd, several kernel threads locked up in
> several different subsystems. It caused X to lock up, and not draw
> anything, access to nfs died, and trying to unmount, remount readonly, or
> do much other than ssh and copy files with scp (which may or may not have
> been in cache, might have been) locked up.
> 
> I'm using a vanila 2.6.36.
> 
> It looks to me like fscache/cachefiles may have started the problem, but I
> can't be sure, and I'm not entirely sure why that would cause i915 to lock
> up as well. I've disabled cachefiles for now, thinking that might make it
> go away. (its locked up twice today)
> 
> here's the entire dmesg:
[snip]

Does anyone know whats going on here? Is it just a fscache bug? Or something a 
little more insidious (since it seemed to cause a drm/intel_gfx lockup as 
well?)

-- 
Thomas Fjellstrom
thomas@...llstrom.ca
--
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/