linux-kernel - Re: System lockup with 2.6.38-rc4+

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: <87fwrqxzcw.fsf@gmail.com>
Date:	Mon, 14 Feb 2011 13:09:03 -0500
From:	Ben Gamari <bgamari.foss@...il.com>
To:	chris2553@...glemail.com, LKML <linux-kernel@...r.kernel.org>
Cc:	Chris Wilson <chris@...is-wilson.co.uk>
Subject: Re: System lockup with 2.6.38-rc4+

On Mon, 14 Feb 2011 17:31:29 +0000, Chris Clayton <chris2553@...glemail.com> wrote:
> Hi,
> 
> I'm not subscribed, so please cc me on any reply.
> 
> I've just had a complete system lock up with a kernel that I pulled, built and 
> installed yesterday morning. IT was locked hard and I had to power off and on 
> to get it back.
>
It looks like the GPU barfed. If you SSH'd in to the machine you'd find
that everything but the display and resources held by the hung X server
would be fine. Were you doing anything particular in your X session when
this happened? There's a good chance this isn't actually a kernel bug
but instead is a DRI client doing something dumb.

Cheers, 

- Ben

P.S. The bzipped kernel image generally won't help in diagnosing the
problem. The most important thing to include in a bug report is the
kernel version and the dmesg output from the failure if available. Folks
will ask later if more is necessary.
--
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/