All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Zhenyu Wang <zhenyu.z.wang@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Woodhouse <David.Woodhouse@intel.com>,
	David Airlie <airlied@linux.ie>,
	Andrew Morton <akpm@linux-foundation.org>,
	Eric Anholt <eric@anholt.net>
Subject: Xorg hangs on >= ~2.6.31 with Intel i915 driver
Date: Tue, 05 Jan 2010 11:02:48 -0800	[thread overview]
Message-ID: <1262718168.7057.29.camel@nimitz> (raw)

I've been seeing hangs when X starts up with newer kernels.  I sometimes
get a cursor on the screen, sometimes not.  I can move the cursor when I
can see it, but I can't switch to a text console.  Sysrq works.

I bisected down to this commit:

commit 176616814d700f19914d8509d9f65dec51a6ebf7
Author: Zhenyu Wang <zhenyu.z.wang@intel.com>
Date:   Mon Jul 27 12:59:57 2009 +0100

http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=176616814d700f19914d8509d9f65dec51a6ebf7

However, backing that commit out of current mainline
(v2.6.33-rc2-302-gc5974b8) doesn't seem to do any good.  It didn't back
out cleanly so I did it by hand and could have easily made a mistake in
the process.

Doing this:

	http://sr71.net/~dave/linux/xhangs/fix-config.patch

to the config worked around the issue in current mainline, although I'm
not quite sure why.

Some additional debug information is here:

	http://sr71.net/~dave/linux/xhangs/

including X logs and dmesg from a bunch of boots. 

-- Dave


             reply	other threads:[~2010-01-05 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 19:02 Dave Hansen [this message]
2010-01-05 19:18 ` Xorg hangs on >= ~2.6.31 with Intel i915 driver David Woodhouse

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=1262718168.7057.29.camel@nimitz \
    --to=dave@linux.vnet.ibm.com \
    --cc=David.Woodhouse@intel.com \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=eric@anholt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhenyu.z.wang@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.