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 35254] New: Radeon TTM Crash With E-350 Fusion
Date: Sat, 12 Mar 2011 09:31:07 -0800 (PST)	[thread overview]
Message-ID: <bug-35254-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Radeon TTM Crash With E-350 Fusion
           Product: DRI
           Version: XOrg CVS
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: Michael@phoronix.com


Created an attachment (id=44397)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=44397)
dmesg 1

Dave & co: Another Fusion problem on my E35M1-M PRO setup... With Git of all
major components as of few days plus the kernel with the Fusion fix talked
about a few days ago, Warsow and Padman at least are crashing on load, 100%
reproducible so far for me (OpenArena though runs fine, haven't tested anything
else yet). Two example dmesg outputs attached, plus one with drm.debug=15.

-- 
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:[~2011-03-12 17:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 17:31 bugzilla-daemon [this message]
2011-03-12 17:31 ` [Bug 35254] Radeon TTM Crash With E-350 Fusion bugzilla-daemon
2011-03-13  8:19 ` bugzilla-daemon
2011-03-13 10:14 ` bugzilla-daemon
2011-03-14  0:03 ` bugzilla-daemon
2011-03-14  0:03 ` bugzilla-daemon
2011-03-15 16:43 ` bugzilla-daemon
2011-05-05 16:27 ` bugzilla-daemon
2011-06-12 12:24 ` bugzilla-daemon
2011-06-12 14:13 ` 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-35254-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