https://bugs.freedesktop.org/show_bug.cgi?id=29953
Summary: [r300g] Heroes of Newerth: texture problems
Product: Mesa
Version: git
Platform: Other
URL: http://www.heroesofnewerth.com/download.php
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: sa(a)whiz.se
Created an attachment (id=38370)
--> (https://bugs.freedesktop.org/attachment.cgi?id=38370)
Screenshot
The game Heroes of Newerth is showing problems when texture compression
(through libtxc_dxtn) is used: most of the menu becomes totally black.
Removing libtxc_dxtn.so, or launching the game with
MESA_EXTENSION_OVERRIDE="-GL_EXT_texture_compression_s3tc -GL_S3_s3tc" makes it
work again. (Though the S2 Games logo that should be visible before the menu
loads is still not there with S3TC disabled)
Neither llvmpipe or softpipe seems to be affected by this problem.
I have tried git from a few months back, and the result is the same, so I don't
think this is a regression.
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: RV570
-- Model: Asus EAX1950Pro 256MB
-- Display connector: DVI
-- xf86-video-ati: fd686668289258ffaf6b81057545e50612aac6a8
-- xserver: 1.9.0
-- mesa: dd5ef33e3c2ac7886ca71344e41201d0be2062c0
-- drm: b61e81a191d3a5c269c5f7c40199aebc9ebc034c
-- kernel: 2.6.35
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=30166
Summary: [wine] Shader issues in rthdribl 1.2
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(a)lists.freedesktop.org
ReportedBy: sa(a)whiz.se
Created an attachment (id=38671)
--> (https://bugs.freedesktop.org/attachment.cgi?id=38671)
Screenshot comparing llvmpipe and r300g
The DirectX9 demo "rthdribl" isn't rendering correctly with r300g.
This is partly a regression from the glsl2 merge, but probably not a problem in
the GLSL compiler since llvmpipe seems to handle the demo. Rendering wasn't
100% prior to the glsl2 merge either.
The "glare" filter causes the screen to be drawn mostly white, so be sure to
turn it off:
Options → Glare → Glare Type → Disable
Version 1.2 of the demo can be downloaded here:
http://www.daionet.gr.jp/~masa/rthdribl/
You'll also need mfc42.dll:
http://www.dlldump.com/download-dll-files_new.php/dllfiles/M/mfc42.dll/6.0.…
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: RV570
-- Model: Asus EAX1950Pro 256MB
-- Display connector: DVI
-- xf86-video-ati: e9928fe036e9382fd7bc353f3f05531445f08977
-- xserver: 1.8.99.904 (1.9.0 RC 5)
-- mesa: 6f839eb631511925505093be4d0509ac14f5675b
-- drm: 23287f05cf2443ddf9e028e29beb5bd30979c6cf
-- kernel: 2.6.35.4
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=33389
Summary: Amesia (closed source game) segfaults
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: r0ugh_l(a)yahoo.de
When trying to run Amnesia (http://www.amnesiagame.com/#demo) on my system it
gives me this output:
[1] 619 segmentation fault ./Amnesia.bin64
It runs fine until the loading screen and then crashes.
Steps to reproduce:
Run Amnesia with r600 driver
Additional information:
It doesn't crash if I'm using the llvm-pipe driver. I've tested it at the
lowest possible graphics settings.
Backtrace:
#0 0x000000000082ab08 in hpl::iParticleEmitter::GetMaterial() ()
#1 0x0000000000805de2 in
hpl::iRenderer::RenderObjectZAndAddToRenderList(hpl::iRenderable*) ()
#2 0x0000000000805e59 in
hpl::iRenderer::RenderObjectZAndAddToRenderListStaticCallback(hpl::iRenderer*,
hpl::iRenderable*) ()
#3 0x0000000000807d8f in
hpl::iRenderer::RenderAndAddNodeObjects(hpl::iRenderableContainerNode*, bool
(*)(hpl::iRenderer*, hpl::iRenderable*), unsigned int) ()
#4 0x000000000080808a in
hpl::iRenderer::CheckForVisibleObjectsAddToListAndRenderZ(hpl::cVisibleRCNodeTracker*,
unsigned int, unsigned int, bool, bool (*)(hpl::iRenderer*, hpl::iRenderable*))
()
#5 0x00000000007e4841 in hpl::cRendererDeferred::RenderObjects() ()
#6 0x0000000000809334 in hpl::iRenderer::Render(float, hpl::cFrustum*,
hpl::cWorld*, hpl::cRenderSettings*, hpl::cRenderTarget*, bool,
std::list<hpl::iRendererCallback*, std::allocator<hpl::iRendererCallback*> >*)
()
#7 0x000000000082496d in hpl::cScene::Render(float, unsigned int) ()
#8 0x0000000000925423 in hpl::cEngine::Run() ()
#9 0x0000000000689890 in hplMain(std::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&) ()
#10 0x000000000090ff29 in main ()
Version Information:
mesa: git 835c4ea1053730c8eea98337c9da1b14fcff6b5e
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV770
OpenGL version string: 2.1 Mesa 7.11-devel
OpenGL shading language version string: 1.20
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=29942
Summary: oops at drivers/gpu/drm/ttm/ttm_bo.c:272
Product: Drivers
Version: 2.5
Kernel Version: 2.6.38-rc6-wl-00360-gcf65005
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: rossi.f(a)inwind.it
Regression: No
Created an attachment (id=49232)
--> (https://bugzilla.kernel.org/attachment.cgi?id=49232)
snapshot of kernel OOPS
Kernel OOPS, attached a snapshot. Bug not reproducible, the kernel version is
2.6.38-rc6-wl-00360-gcf65005, latest wireless-testing.git
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=30901
Summary: Heroes of Newerth won't start when mesa is compiled
with --enable-gallium-llvm
Product: Mesa
Version: git
Platform: x86 (IA32)
URL: http://dl.heroesofnewerth.com/HoNClient-1.0.14.sh
OS/Version: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: drakkk(a)centrum.cz
I usually configure mesa like this: "--enable-debug --enable-gallium-radeon
--with-dri-drivers= --with-state-trackers=dri,glx", with this HoN starts and
runs fine with r300g driver. However I was trying llvmpipe with some other apps
and I noticed, when I add "--enable-gallium-llvm", HoN won't start with "K2 -
Fatal Error: ARB_vertex_buffer_object not available."
This is quite strange because glxinfo is identical and shows
GL_ARB_vertex_buffer_object in both cases (and OpenGL vendor string: X.Org R300
Project, OpenGL renderer string: Gallium 0.4 on RV530, so its not like I was
using some other driver). I'm quite sure I didn't messed up anything I even
asked at #radeon if I'm doing something wrong. LIBGL_DRIVERS_PATH and
LD_LIBRARY_PATH are both pointing to right mesa directories and I did git clean
-fdx between builds.
So far I wasn't able to reproduce this with any other app.
This is with Fedora 14 i686, kernel 2.6.35.6-39.fc14, mesa from git, RV530.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=28876
Summary: [radeon HD4250] Frequent lockups while screen locked
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: ydirson(a)altern.org
Created an attachment (id=36664)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36664)
Xorg log file, with nearly 30k lines of repeated messages stripped
Direct symptoms:
- display left unattended with xscreensaver in simple blank mode
- DPMS disabled (checked both with xset and xscreensaver-demo)
- when coming back to my keyboard the monitor does not get a video signal
- I can still login remotely through ssh and reboot the machine properly
Hardware is an Asus "M4A88TD-V EVO/USB3" motherboard, featuring radeon HD4250
(RS780). OS is uptodate Debian/testing.
syslog contains lines like the following. In this case, although I was not
here, it may be that someone tried to use the box. In the 2 other occurences I
have traces for, it I may even have been myself, but I did not dig at that
time.
However, although the Xorg.0.log error lines are not timestamped, the file
timestamp itself matches the box' reboot. Since there are ~15000 occurences of
the error, X may have been experiencing them since the error reported by the
drm module. I can try to get more detailed facts next time (unless
unnecessary, just tell).
Jun 30 10:17:01 home /USR/SBIN/CRON[27295]: (root) CMD ( cd / && run-parts
--report /etc/cron.hourly)
Jun 30 10:18:10 home kernel: [130052.418150] executing set pll
Jun 30 10:18:10 home kernel: [130052.424023] executing set crtc timing
Jun 30 10:18:10 home kernel: [130052.424072] [drm] TMDS-11: set mode 1920x1200
1b
Jun 30 10:18:10 home acpid: client 2095[0:0] has disconnected
Jun 30 10:18:10 home acpid: client connected from 27304[0:0]
Jun 30 10:18:10 home acpid: 1 client rule loaded
Jun 30 10:18:13 home kernel: [130055.829085] [drm:radeon_ib_get] *ERROR*
radeon: IB(0:0x0000000010101000:668)
Jun 30 10:18:13 home kernel: [130055.829088] [drm:radeon_ib_get] *ERROR*
radeon: GPU lockup detected, fail to get a IB
Jun 30 10:18:13 home kernel: [130055.829090] [drm:radeon_cs_ioctl] *ERROR*
Failed to get ib !
[...]
Jun 30 10:18:42 home kernel: [130084.275900] [drm:radeon_ib_get] *ERROR*
radeon: IB(0:0x0000000010101000:668)
Jun 30 10:18:42 home kernel: [130084.275906] [drm:radeon_ib_get] *ERROR*
radeon: GPU lockup detected, fail to get a IB
Jun 30 10:18:42 home kernel: [130084.275912] [drm:radeon_cs_ioctl] *ERROR*
Failed to get ib !
Jun 30 11:17:01 home /USR/SBIN/CRON[27329]: (root) CMD ( cd / && run-parts
--report /etc/cron.hourly)
In older occurences (do not recall the precise set of events, although the
"wishing to unlock screen" event has always been the only way to see the
problem), the 3 error lines occur on a longer timespan, some in sync with the
clock (??):
Jun 27 19:17:01 home /USR/SBIN/CRON[26082]: (root) CMD ( cd / && run-parts
--report /etc/cron.hourly)
Jun 27 19:18:09 home kernel: [21853.241075] executing set pll
Jun 27 19:18:09 home kernel: [21853.248025] executing set crtc timing
Jun 27 19:18:09 home kernel: [21853.248076] [drm] TMDS-11: set mode 1920x1200
1b
Jun 27 19:18:12 home kernel: [21856.334252] [drm:radeon_ib_get] *ERROR* radeon:
IB(0:0x0000000010101000:668)
Jun 27 19:18:12 home kernel: [21856.334261] [drm:radeon_ib_get] *ERROR* radeon:
GPU lockup detected, fail to get a IB
Jun 27 19:18:12 home kernel: [21856.334269] [drm:radeon_cs_ioctl] *ERROR*
Failed to get ib !
[...]
Jun 27 19:18:32 home kernel: [21876.279726] [drm:radeon_ib_get] *ERROR* radeon:
IB(0:0x0000000010101000:668)
Jun 27 19:18:32 home kernel: [21876.279733] [drm:radeon_ib_get] *ERROR* radeon:
GPU lockup detected, fail to get a IB
Jun 27 19:18:32 home kernel: [21876.279739] [drm:radeon_cs_ioctl] *ERROR*
Failed to get ib !
Jun 27 19:19:00 home kernel: [21904.282670] [drm:radeon_ib_get] *ERROR* radeon:
IB(0:0x0000000010101000:668)
Jun 27 19:19:00 home kernel: [21904.282678] [drm:radeon_ib_get] *ERROR* radeon:
GPU lockup detected, fail to get a IB
Jun 27 19:19:00 home kernel: [21904.282685] [drm:radeon_cs_ioctl] *ERROR*
Failed to get ib !
Jun 27 19:20:00 home kernel: [21964.322037] [drm:radeon_ib_get] *ERROR* radeon:
IB(0:0x0000000010101000:668)
Jun 27 19:20:00 home kernel: [21964.322045] [drm:radeon_ib_get] *ERROR* radeon:
GPU lockup detected, fail to get a IB
Jun 27 19:20:00 home kernel: [21964.322052] [drm:radeon_cs_ioctl] *ERROR*
Failed to get ib !
Jun 27 19:21:00 home kernel: [22024.321528] [drm:radeon_ib_get] *ERROR* radeon:
IB(0:0x0000000010101000:668)
Jun 27 19:21:00 home kernel: [22024.321537] [drm:radeon_ib_get] *ERROR* radeon:
GPU lockup detected, fail to get a IB
Jun 27 19:21:00 home kernel: [22024.321544] [drm:radeon_cs_ioctl] *ERROR*
Failed to get ib !
Jun 27 19:22:00 home kernel: [22084.321217] [drm:radeon_ib_get] *ERROR* radeon:
IB(0:0x0000000010101000:668)
Jun 27 19:22:00 home kernel: [22084.321225] [drm:radeon_ib_get] *ERROR* radeon:
GPU lockup detected, fail to get a IB
Jun 27 19:22:00 home kernel: [22084.321232] [drm:radeon_cs_ioctl] *ERROR*
Failed to get ib !
Jun 27 19:23:00 home kernel: [22144.367818] [drm:radeon_ib_get] *ERROR* radeon:
IB(0:0x0000000010101000:668)
Jun 27 19:23:00 home kernel: [22144.367827] [drm:radeon_ib_get] *ERROR* radeon:
GPU lockup detected, fail to get a IB
Jun 27 19:23:00 home kernel: [22144.367833] [drm:radeon_cs_ioctl] *ERROR*
Failed to get ib !
Jun 27 19:24:00 home kernel: [22204.414007] [drm:radeon_ib_get] *ERROR* radeon:
IB(0:0x0000000010101000:668)
Jun 27 19:24:00 home kernel: [22204.414015] [drm:radeon_ib_get] *ERROR* radeon:
GPU lockup detected, fail to get a IB
Jun 27 19:24:00 home kernel: [22204.414022] [drm:radeon_cs_ioctl] *ERROR*
Failed to get ib !
Jun 27 19:24:12 home kernel: [22216.304962] [drm:radeon_ib_get] *ERROR* radeon:
IB(0:0x0000000010101000:668)
Jun 27 19:24:12 home kernel: [22216.304970] [drm:radeon_ib_get] *ERROR* radeon:
GPU lockup detected, fail to get a IB
Jun 27 19:24:12 home kernel: [22216.304977] [drm:radeon_cs_ioctl] *ERROR*
Failed to get ib !
Xorg.0.log repeated messages are:
(EE) RADEON(0): Timeout trying to update memory controller settings !
(EE) RADEON(0): You will probably crash now ...
Package versions are as follows (dpkg -l|grep xserver):
x11-xserver-utils 7.5+1
xserver-common 2:1.7.7-2
xserver-xephyr 2:1.7.7-2
xserver-xorg 1:7.5+6
xserver-xorg-core 2:1.7.7-2
xserver-xorg-core-dbg 2:1.7.7-2
xserver-xorg-input-all 1:7.5+6
xserver-xorg-input-evdev 1:2.3.2-6
xserver-xorg-input-synaptics 1.2.2-2
xserver-xorg-input-wacom 0.10.5+20100416-1
xserver-xorg-video-ati 1:6.13.0-2
xserver-xorg-video-fbdev 1:0.4.2-2
xserver-xorg-video-mach64 6.8.2-3
xserver-xorg-video-mga 1:1.4.11.dfsg-4
xserver-xorg-video-r128 6.8.1-3
xserver-xorg-video-radeon 1:6.13.0-2
xserver-xorg-video-radeon-dbg 1:6.13.0-2
xserver-xorg-video-vesa 1:2.3.0-3
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=35502
Summary: Regression: black screen with Radeon KMS in 2.6.38
(2.6.37.4 worked fine)
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: john.lindgren(a)tds.net
Created an attachment (id=44669)
--> (https://bugs.freedesktop.org/attachment.cgi?id=44669)
Kernel log
With Linux kernel 2.6.38, loading the radeon module causes the console to go
completely blank (laptop backlight on, but nothing displayed). The system
still responds to ctrl-alt-del and reboots. This is a regression from the
previous kernel, 2.6.37.4, where kernel mode setting works flawlessly.
With radeon.modeset=0, or with the module blacklisted, the system boots fine,
and I can use X, but without the powersaving features available through KMS.
System: Toshiba Satellite A305-S6916
Graphics: ATI Radeon Mobility HD 3650
Kernel: 2.6.38 (x86_64)
Kernel log when loading the module:
Mar 21 00:57:38 localhost kernel: [drm] Initialized drm 1.1.0 20060810
Mar 21 00:57:38 localhost kernel: [drm] radeon defaulting to kernel
modesetting.
Mar 21 00:57:38 localhost kernel: [drm] radeon kernel modesetting enabled.
Mar 21 00:57:38 localhost kernel: radeon 0000:01:00.0: PCI INT A -> GSI 16
(level, low) -> IRQ 16
Mar 21 00:57:38 localhost kernel: radeon 0000:01:00.0: setting latency timer to
64
Mar 21 00:57:38 localhost kernel: [drm] initializing kernel modesetting (RV635
0x1002:0x9591).
Mar 21 00:57:38 localhost kernel: [drm] register mmio base: 0xD6300000
Mar 21 00:57:38 localhost kernel: [drm] register mmio size: 65536
Mar 21 00:57:38 localhost kernel: ATOM BIOS: Tosh_IEC_Potomac_M86_DDR2
Mar 21 00:57:38 localhost kernel: radeon 0000:01:00.0: VRAM: 512M
0x0000000000000000 - 0x000000001FFFFFFF (512M used)
Mar 21 00:57:38 localhost kernel: radeon 0000:01:00.0: GTT: 512M
0x0000000020000000 - 0x000000003FFFFFFF
Mar 21 00:57:38 localhost kernel: [drm] Detected VRAM RAM=512M, BAR=256M
Mar 21 00:57:38 localhost kernel: [drm] RAM width 128bits DDR
Mar 21 00:57:38 localhost kernel: [TTM] Zone kernel: Available graphics
memory: 2027544 kiB.
Mar 21 00:57:38 localhost kernel: [TTM] Initializing pool allocator.
Mar 21 00:57:38 localhost kernel: [drm] radeon: 512M of VRAM memory ready
Mar 21 00:57:38 localhost kernel: [drm] radeon: 512M of GTT memory ready.
Mar 21 00:57:38 localhost kernel: [drm] Supports vblank timestamp caching Rev 1
(10.10.2010).
Mar 21 00:57:38 localhost kernel: [drm] Driver supports precise vblank
timestamp query.
Mar 21 00:57:38 localhost kernel: radeon 0000:01:00.0: irq 49 for MSI/MSI-X
Mar 21 00:57:38 localhost kernel: radeon 0000:01:00.0: radeon: using MSI.
Mar 21 00:57:38 localhost kernel: [drm] radeon: irq initialized.
Mar 21 00:57:38 localhost kernel: [drm] GART: num cpu pages 131072, num gpu
pages 131072
Mar 21 00:57:38 localhost kernel: [drm] Loading RV635 Microcode
Mar 21 00:57:38 localhost kernel: radeon 0000:01:00.0: WB enabled
Mar 21 00:57:38 localhost kernel: [drm] ring test succeeded in 1 usecs
Mar 21 00:57:38 localhost kernel: [drm] radeon: ib pool ready.
Mar 21 00:57:38 localhost kernel: [drm] ib test succeeded in 0 usecs
Mar 21 00:57:38 localhost kernel: [drm] Enabling audio support
Mar 21 00:57:38 localhost kernel: HDMI hot plug event: Pin=3 Presence_Detect=0
ELD_Valid=0
If there is any more info I can provide, please ask.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=35194
Summary: [r600g] Evergreen - failed to map bo
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: rubenf3000(a)gmail.com
Created an attachment (id=44337)
--> (https://bugs.freedesktop.org/attachment.cgi?id=44337)
output generated with MESA_GLSL=dump
The game "Back to the Future: the game" crashes at many points with
the message:
radeon_bo_fixed_map failed to map bo
EE radeon_bo.c:120 radeon_bo - failed to map bo
It usually happens at random moments, altough there are specific actions
that trigger the crash reliably.
It works correctly using llvmpipe.
The "failed to map" message originates in the function "radeon_bo_fixed_map"
in "mesa/src/gallium/winsys/r600/drm/radeon_bo.c", when doing a call to mmap;
upon debugging, I found it fails with ENOMEM, despite having more than enough
free RAM available at the time (it only allocates half a megabyte, and I had
almost 1GB of free RAM at the moment of crashing)
Upon further inspection, I found that, at the moment of the crash, the game had
almost exactly 1 gigabyte of buffer objects mmap'd; could it have something to
do with my card having 1GB of video RAM? seems unlikely, since mmap maps to
system memory.
Graphics Card: ATI Technologies Inc Juniper [Radeon HD 5750 Series]
CPU: Intel Core Duo 1.8 Ghz, 2.5 GB RAM
Linux kernel 2.6.37, libdrm 2.4.24
Latest Mesa git
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=33824
Summary: [r600g, tiling] mipmap rendering errors / block
artifacts
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: liquid.acid(a)gmx.net
Hi there,
this is a update of bug #31046, where the main issue was GPU resets caused by
enabling tiling (R600_FORCE_TILING=1) with the r600g driver.
The situation however was changed, and now R600_FORCE_TILING only causes mipmap
rendering errors in a few application. Last time I tested ioquake3, doom3
(demo) and both ut2003 and ut2004.
ut03 and ut04 are still affected by the blocky rendering errors (see the other
bug for screenshots illustrating the problem), but both ioquake3 and doom3 now
look perfectly fine.
My hardware:
ATI Technologies Inc Radeon HD 4770 [RV740]
libdrm, mesa and xf86-video-ati are all git master tip.
ColorTiling is enabled in the xorg.conf, verified this by checking the Xorg
logfile.
kernel is d-r-t
Greets,
Tobias
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.