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 for Android: free password hash cracker in your pocket

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

Message-Id: <E1MM2yf-0002dX-Lg@approx.mit.edu>
Date:	Wed, 01 Jul 2009 12:48:09 -0400
From:	Sanjoy Mahajan <sanjoy@....EDU>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	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)

[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?

-Sanjoy

`Until lions have their historians, tales of the hunt shall always
 glorify the hunters.'  --African Proverb
--
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/