From: Andrew Lutomirski <luto@mit.edu>
To: intel-gfx@lists.freedesktop.org
Subject: [2.6.39 regression] hard lock when GNOME starts
Date: Fri, 13 May 2011 01:38:02 -0400
Message-ID: <BANLkTi=HDaOeoz7zQ82oog1yTw2zGF18Yw@mail.gmail.com> (raw)
Hi-
Something in the range ^8aa7500 40c7f2112ce18fa5eb ^b04d0a90908c
causes by Q67 Sandy Bridge box to lock hard about one second after I
start GNOME. It locks so hard that the reset button doesn't work and
netconsole doesn't say anything.
I'm about to have trouble finishing the bisection because I've had
trouble running revisions that are older than 2.6.38 and the next bit
of bisection has merge conflicts if I merge in 2.6.38. I can power
through it, but maybe one of you will recognize the bug from the fact
that there aren't that many revisions in there and there can't be many
ways to make the reset button stop working.
--Andy
next reply index
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 5:38 Andrew Lutomirski [this message]
2011-05-13 16:07 ` Andrew Lutomirski
2011-05-13 16:14 ` [PATCH] drm/i915: Revert i915.semaphore=1 default from 47ae63e0 Andy Lutomirski
2011-05-15 23:09 ` Keith Packard
2011-05-19 19:56 ` Keith Packard
2011-05-19 20:50 ` Andrew Lutomirski
2011-05-24 17:10 ` Andrew Lutomirski
2011-05-24 17:46 ` Keith Packard
2011-05-24 20:05 ` Ivan Bulatovic
2011-06-07 7:12 ` Eric Anholt
2011-06-10 14:06 ` Andrew Lutomirski
2011-08-22 16:53 ` Jesse Barnes
2011-08-31 18:24 ` Ben Widawsky
2011-08-31 18:30 ` Andrew Lutomirski
2011-08-31 19:07 ` Keith Packard
2011-08-31 19:37 ` Andrew Lutomirski
2011-09-26 17:59 ` [PATCH] drm/i915: kicking rings considered harmful Daniel Vetter
2011-09-26 19:07 ` Andrew Lutomirski
2011-09-27 9:57 ` Daniel Vetter
2011-09-27 5:22 ` Ben Widawsky
2011-09-27 10:03 ` Daniel Vetter
2011-09-27 16:46 ` Ben Widawsky
2011-09-27 17:31 ` Chris Wilson
2011-09-27 18:03 ` Daniel Vetter
2011-09-27 19:38 ` Ben Widawsky
2011-09-27 21:54 ` Chris Wilson
2011-09-28 1:34 ` Ben Widawsky
2011-09-28 8:47 ` Chris Wilson
2011-09-28 8:53 ` Daniel Vetter
2011-10-03 20:21 ` Andrew Lutomirski
2011-10-03 21:02 ` Daniel Vetter
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='BANLkTi=HDaOeoz7zQ82oog1yTw2zGF18Yw@mail.gmail.com' \
--to=luto@mit.edu \
--cc=intel-gfx@lists.freedesktop.org \
/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
Intel-GFX Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/intel-gfx/0 intel-gfx/git/0.git
git clone --mirror https://lore.kernel.org/intel-gfx/1 intel-gfx/git/1.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 intel-gfx intel-gfx/ https://lore.kernel.org/intel-gfx \
intel-gfx@lists.freedesktop.org
public-inbox-index intel-gfx
Example config snippet for mirrors
Newsgroup available over NNTP:
nntp://nntp.lore.kernel.org/org.freedesktop.lists.intel-gfx
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git