All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28474] [r300g] lugaru/etc locks up laptop
Date: Fri, 11 Jun 2010 14:33:41 -0700 (PDT)	[thread overview]
Message-ID: <20100611213341.9C7F51300EB@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-28474-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=28474

Tormod Volden <bugzi09.fdo.tormod@xoxy.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[gallium] lugaru/etc locks  |[r300g] lugaru/etc locks up
                   |up laptop                   |laptop

--- Comment #4 from Tormod Volden <bugzi09.fdo.tormod@xoxy.net> 2010-06-11 14:33:41 PDT ---
I have no idea any longer. My install log does not match my memory, and I guess
that means EBRAIN. It seems I never used 20100523 (fa552261) but in fact
upgraded straight from 20100429 (f7cf8b46) to 20100528 (f4bcd0ca). So now I
checked out f7cf8b46 from git but it also locked up.

>From timestamps I can see that I installed lugaru 20100528 and then did the
mesa upgrade to f4bcd0ca some hours later. At the time I installed lugaru (and
did not see any crash) I had just installed 2.6.34-996.201005261005 (drm-next
from mainline kernel PPA). Hours before I had installed 2.6.34-999.201005231006
(linus tree). So I must have been running one of those kernels.

Both these kernels hang when I try them now with mesa 20100523 fa552261
(installed), and also with 20100429 f7cf8b46 (git checkout, using
LD_LIBRARY_PATH and LIBGL_DRIVERS_PATH).

So maybe I was just lucky when I tried lugaro out the first times. I think I
played with it more than 10 minutes. The way I reproduce the hang now is simply
by choosing Tutorial and then do nothing. Just let the rabbit stand there and
jump by itself. After 10-30 seconds the machine locks up. The sound goes into a
stuttering (sub-second) loop and I have to power off with the power button.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-06-11 21:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 21:04 [Bug 28474] New: lugaru/etc locks up laptop bugzilla-daemon
2010-06-09 23:37 ` [Bug 28474] " bugzilla-daemon
2010-06-10 22:38 ` [Bug 28474] [gallium] " bugzilla-daemon
2010-06-10 22:43 ` bugzilla-daemon
2010-06-11 21:33 ` bugzilla-daemon [this message]
2010-06-11 22:09 ` [Bug 28474] [r300g] " bugzilla-daemon
2010-06-26 23:20 ` bugzilla-daemon
2010-06-27  8:55 ` bugzilla-daemon
2010-06-27 10:02 ` bugzilla-daemon
2010-07-29  7:23 ` bugzilla-daemon
2010-07-29  7:24 ` bugzilla-daemon
2010-08-04 15:43 ` bugzilla-daemon
2010-08-11 21:35 ` bugzilla-daemon
2010-08-15  6:33 ` bugzilla-daemon
2010-08-19 14:07 ` bugzilla-daemon
2010-08-19 17:55 ` bugzilla-daemon
2010-08-20 14:48 ` bugzilla-daemon
2010-08-26 21:57 ` bugzilla-daemon
2010-08-28  4:21 ` bugzilla-daemon

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=20100611213341.9C7F51300EB@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@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
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.