All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 48305] New: llpp gets segfault in r600g_dri.so
Date: Wed, 04 Apr 2012 17:33:58 +0000	[thread overview]
Message-ID: <bug-48305-502@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 48305
           Summary: llpp gets segfault in r600g_dri.so
    Classification: Unclassified
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: myxolmyxmyx@yopmail.com


Loading any pdf with llpp produces segfault. 
Message in dmesg:
[115638.669260] llpp[15916] general protection ip:b64f6d84 sp:bfe416dc error:0
in r600g_dri.so[b62d3000+a72000]

mupdf that is used by llpp works flawlessly on r600g. And llpp works on fglrx.
I'm using Radeon 2600 PRO AGPx4.

-- 
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-04-04 17:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 17:33 bugzilla-daemon [this message]
2012-04-04 13:40 ` [Bug 48305] llpp gets segfault in r600g_dri.so bugzilla-daemon
2012-04-04 18:06 ` bugzilla-daemon
2012-04-04 20:42 ` bugzilla-daemon
2012-04-04 20:45 ` bugzilla-daemon
2012-04-05  6:48 ` bugzilla-daemon
2012-04-05 12:54 ` bugzilla-daemon
2012-04-06  0:49 ` bugzilla-daemon
2012-04-06 11:11 ` bugzilla-daemon
2012-04-07 14:28 ` bugzilla-daemon
2019-09-18 18: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-48305-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 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.