linux-kernel - Re: X server hung, kernel said "task blocked for >120 secs" (2.6.30)

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: <1246496595.16527.3.camel@gaiman.anholt.net>
Date:	Wed, 01 Jul 2009 18:03:15 -0700
From:	Eric Anholt <eric@...olt.net>
To:	Sanjoy Mahajan <sanjoy@....EDU>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, dri-devel@...ts.sourceforge.net
Subject: Re: X server hung, kernel said "task blocked for >120 secs"
 (2.6.30)

On Wed, 2009-07-01 at 12:48 -0400, Sanjoy Mahajan wrote:
> [Have been away for 10 days and just saw the message]
> 
> > I assume this is a regression?  Since 2.6.29?
> 
> I never saw it before using 2.6.30 and haven't been able to reproduce
> it even running 2.6.30.  
> 
> So it could be a regression.  Or it could be a recurring problem (I had
> a few X lockups with earlier kernels) now exposed by a blocked-task
> timer (the "INFO: task events/0:9 blocked for more than 120 seconds"
> message) -- if that notification code is new in 2.6.30?

This message appears when the GPU is hung but somebody is still trying
to use it.  The problem is that the GPU is hung, not the presence of the
message (so you can't use the message to indicate any particular bug,
and the bug is almost always in userland).

-- 
Eric Anholt
eric@...olt.net                         eric.anholt@...el.com



Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)