mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Sanjoy Mahajan <sanjoy@MIT.EDU>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: X server hung, kernel said "task blocked for >120 secs" (2.6.30)
Date: Wed, 01 Jul 2009 18:03:15 -0700	[thread overview]
Message-ID: <1246496595.16527.3.camel@gaiman.anholt.net> (raw)
In-Reply-To: <E1MM2yf-0002dX-Lg@approx.mit.edu>

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

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@anholt.net                         eric.anholt@intel.com



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-07-02  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15  1:46 Sanjoy Mahajan
2009-06-22 22:31 ` Andrew Morton
2009-07-01 16:48   ` Sanjoy Mahajan
2009-07-02  1:03     ` Eric Anholt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1246496595.16527.3.camel@gaiman.anholt.net \
    --to=eric@anholt.net \
    --cc=akpm@linux-foundation.org \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sanjoy@MIT.EDU \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®