From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36086] New: [wine] Segfault r300_resource_copy_region with some wine apps and RADEON_HYPERZ
Date: Fri, 8 Apr 2011 12:15:28 -0700 (PDT) [thread overview]
Message-ID: <bug-36086-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=36086
Summary: [wine] Segfault r300_resource_copy_region with some
wine apps and RADEON_HYPERZ
Product: Mesa
Version: git
Platform: Other
URL: http://www.daionet.gr.jp/~masa/rthdribl/
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: sa@whiz.se
Created an attachment (id=45430)
--> (https://bugs.freedesktop.org/attachment.cgi?id=45430)
backtrace
Some wine apps, like the rthdribl demo, but also some games, causes a segfault
in 300_resource_copy_region when hyperz is enabled.
Backtrace is attached.
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: RV570
-- Model: Asus EAX1950Pro 256MB
-- Display connector: DVI
-- xf86-video-ati: 6.14.1
-- xserver: 1.9.4.901 (1.9.5 RC 1)
-- mesa: 1329d9433496618ad02bb9a91eccecd9736fdf54
-- drm: 2.4.24
-- kernel: 2.6.38
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-04-08 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 19:15 bugzilla-daemon [this message]
2011-04-08 21:18 ` [Bug 36086] [wine] Segfault r300_resource_copy_region with some wine apps and RADEON_HYPERZ 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-36086-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