dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 30575] New: Hard Lockup with r300g
Date: Sat,  2 Oct 2010 16:24:09 -0700 (PDT)	[thread overview]
Message-ID: <bug-30575-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Hard Lockup with r300g
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: hicham.haouari@gmail.com


Created an attachment (id=39127)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=39127)
glxinfo

I am having a hard lockup with r300g when playing Penumbra Black Plague game (
a free demo is available via http://www.penumbragame.com/demo.php ), or when
playing flash content with lightspark.

Card   : ATI Mobility Radeon X700 PCIE ( RV410 )
Kernel : 2.6.35.6-37.fc14.i686
driver : xf86-video-ati-6.13.2
mesa   : d6e2b707baecb7655cd09d64080fc944cc5704a6 , built with Fedora spec file
glxinfo: (attached)

I am sorry for filing this bug with this few information, but the hard lockup
left me out of options.

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

             reply	other threads:[~2010-10-02 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-02 23:24 bugzilla-daemon [this message]
2010-10-02 23:32 ` [Bug 30575] Hard Lockup with r300g bugzilla-daemon
2010-10-02 23:58 ` bugzilla-daemon
2010-10-20 18:29 ` bugzilla-daemon
2010-11-21 10:59 ` 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=bug-30575-502@http.bugs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox