All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: Ben Gamari <bgamari.foss@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: System lockup with 2.6.38-rc4+
Date: Mon, 14 Feb 2011 19:21:14 +0000	[thread overview]
Message-ID: <201102141921.14406.chris2553@googlemail.com> (raw)
In-Reply-To: <87fwrqxzcw.fsf@gmail.com>

On Monday 14 February 2011, Ben Gamari wrote:
> On Mon, 14 Feb 2011 17:31:29 +0000, Chris Clayton <chris2553@googlemail.com> 
wrote:
> > Hi,
> >
> > I'm not subscribed, so please cc me on any reply.
> >
> > I've just had a complete system lock up with a kernel that I pulled,
> > built and installed yesterday morning. IT was locked hard and I had to
> > power off and on to get it back.
>
> It looks like the GPU barfed. If you SSH'd in to the machine you'd find
> that everything but the display and resources held by the hung X server
> would be fine. Were you doing anything particular in your X session when
> this happened? There's a good chance this isn't actually a kernel bug
> but instead is a DRI client doing something dumb.
>

I was panning around a google map in firefox. Other than that, I had no other 
applications running. I've just done the same thing in 2.6.37 for 10 minutes 
with no problems - 2.6.38-rc4+  In fact, I don't recall having this sort of 
problem in any previous kernel.

> Cheers,
>
> - Ben
>
> P.S. The bzipped kernel image generally won't help in diagnosing the
> problem. The most important thing to include in a bug report is the
> kernel version and the dmesg output from the failure if available. Folks
> will ask later if more is necessary.

Note kernel and Xorg logs, plural - i.e. the logs from the /var/log/kernel 
and /var/Xorg.log. The kernel version is in the subject.

Thanks,

Chris

-- 
The more I see, the more I know. The more I know, the less I understand. 
Changing Man - Paul Weller

      reply	other threads:[~2011-02-14 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 17:31 System lockup with 2.6.38-rc4+ Chris Clayton
2011-02-14 18:09 ` Ben Gamari
2011-02-14 19:21   ` Chris Clayton [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=201102141921.14406.chris2553@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=bgamari.foss@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=linux-kernel@vger.kernel.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
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.