From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
airlied@redhat.com, intel-gfx@lists.freedesktop.org
Subject: Re: Regressions in resume on intel graphics
Date: Fri, 19 Nov 2010 13:03:29 -0800 [thread overview]
Message-ID: <20101119130329.675ebf0b@jbarnes-desktop> (raw)
In-Reply-To: <AANLkTik4Bj2_D_oz8jWxzKSKz16S=Yv6884iHA072bJe@mail.gmail.com>
On Fri, 12 Nov 2010 10:17:07 +0100
Zdenek Kabelac <zdenek.kabelac@gmail.com> wrote:
> 2010/11/12 Zdenek Kabelac <zdenek.kabelac@gmail.com>:
> > Hi
> >
> > I've noticed that after resume with 2.6.36 kernel I need to switch
> > between console and back to Xorg to get usable Xsession again.
> > (my hw - T61, gma965, 4GB)
> >
> > I've played bisect game - and this is the first broken kernel:
> >
> > ---
> > commit 8fd4bd22350784d5b2fe9274f6790ba353976415
> > Author: Jesse Barnes <jbarnes@virtuousgeek.org>
> > Date: Wed Jun 23 12:56:12 2010 -0700
> >
> > vt/console: try harder to print output when panicing
> > ---
>
> I've been able to boot and test with 2.6.37-rc1-00170-gf6614b7
> - and this problem seems to be fixed in this version (vt.c file seems
> to be gone?).
This is really weird; there was one issue Dave tracked down related to
lockdep and the new oops code, but I think it's been fixed. And it
should manifest as something other than a GPU hang...
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-11-19 21:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 0:31 Regressions in resume on intel graphics Zdenek Kabelac
2010-11-12 9:17 ` Zdenek Kabelac
2010-11-19 21:03 ` Jesse Barnes [this message]
2010-11-19 21:35 ` Zdenek Kabelac
2010-11-19 22:05 ` Dave Airlie
2010-11-19 23:05 ` Zdenek Kabelac
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=20101119130329.675ebf0b@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zdenek.kabelac@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox