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 44405] New: Spring RTS crashes using r600g (5670, Redwood), kernel rejects relocations
Date: Tue, 03 Jan 2012 00:23:45 +0000	[thread overview]
Message-ID: <bug-44405-502@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 44405
           Summary: Spring RTS crashes using r600g (5670, Redwood), kernel
                    rejects relocations
    Classification: Unclassified
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: marbacz@gmail.com


Created attachment 55060
  --> https://bugs.freedesktop.org/attachment.cgi?id=55060
gdb bt full

I'm using Mesa from git(77058335), r600g on Redwood [Radeon HD 5670], kernel
3.1.5. Spring crashes on startup, with following trace(full trace attached)

#7  0x00007fd1b9f858d5 in pipe_surface_reference (ptr=0x7fd1ae5a1a58,
surf=<optimized out>)
    at ../../src/gallium/auxiliary/util/u_inlines.h:112
#8  st_renderbuffer_delete (rb=0x7fd1ae5a19b0) at state_tracker/st_cb_fbo.c:181
#9  0x00007fd1b9f59c30 in _mesa_reference_renderbuffer_ (ptr=0x7fd1ae596998,
rb=0x0)
    at main/renderbuffer.c:186
#10 0x00007fd1b9f30b1e in _mesa_reference_renderbuffer (rb=0x0,
ptr=0x7fd1ae596998)
    at main/renderbuffer.h:62
#11 _mesa_free_framebuffer_data (fb=0x7fd1ae596740) at main/framebuffer.c:216
#12 0x00007fd1b9f30bfe in _mesa_destroy_framebuffer (fb=0x7fd1ae596740)
    at main/framebuffer.c:193
#13 0x00007fd1b9f30cb3 in _mesa_reference_framebuffer_ (ptr=0x7fff6a0c34a8,
fb=0x0)
    at main/framebuffer.c:253
#14 0x00007fd1b9f2c304 in _mesa_reference_framebuffer (fb=0x0,
ptr=0x7fff6a0c34a8)
    at main/framebuffer.h:62
#15 _mesa_DeleteFramebuffersEXT (n=1, framebuffers=<optimized out>) at
main/fbobject.c:1832

and with lots of similar messages in dmesg:

[14960.505619] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed
0x136
[14960.505622] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
[14960.524494] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed
0x136
[14960.524497] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
[14960.758968] unknown[16452]: segfault at 0 ip 0000000000a84204 sp
00007fff3e6ac280 error 4 in spring[400000+d4a000]

attached full trace and glxinfo. Let me know if you need more info.

-- 
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:[~2012-01-03  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03  0:23 bugzilla-daemon [this message]
2012-01-03  0:24 ` [Bug 44405] Spring RTS crashes using r600g (5670, Redwood), kernel rejects relocations bugzilla-daemon
2012-01-03 18:48 ` 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-44405-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