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)…
[View More]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
[View Less]
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-…
[View More]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.
[View Less]
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)
--> (…
[View More]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.
[View Less]
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 …
[View More]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.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=34709
Summary: with r300 (rv530) kms loaded cannot suspend kernel
2.6.37+ with uswsusp
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: hramrach(a)gmail.com
After upgrading from …
[View More]kernel 2.6.36 to 2.6.37 I can no longer suspend the system
with uswsusp.
The suspend operation hangs with displays blanked before the part when "Saving
image to disk" takes place.
Suspending with "echo disk > /sys/power/state" works but is obviously useless
as the system cannot be resumed.
Upgrading to 2.6.38 does not help, not loading the radeon module allows to
suspend as usual.
A pointer to a repo with Radeon changesets between 2.6.36 and 2.6.37 without
needlessly intermingled changes to other kernel parts would be appreciated.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=32318
Summary: [r300g] Titan's atmosphere in celestia is blue with
OpenGL 2.0 rendering path.
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: rankincj(a)googlemail.…
[View More]com
Created an attachment (id=41009)
--> (https://bugs.freedesktop.org/attachment.cgi?id=41009)
Titan, as seen with OpenGL 2.0 rendering path
Celestia 1.5.1, with r300g from git, RV350 card.
When viewing Saturn's moon Titan with atmospheres enabled (Ctrl-A), the
atmosphere appears orange for basic, multitexture and OpenGL vertex program
rendering paths, but blue for OpenGL 2.0 rendering path. (Cycle through
available rendering paths using Ctrl-V.)
This inconsistency is suspicious - I suspect a bug.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=28627
Summary: 2.6.31.6 is the last kernel where KMS works well on an
RV515 card for regular PCI
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: All
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: connor.behan(a)gmail.com
After …
[View More]constant regressions, I thought I would post this.
dmesg.good: http://pastebin.com/kL3iXTU3
xorglog.good: http://pastebin.com/n7diwRCL
glxinfo.good: http://pastebin.com/aDajgYQC
dmesg.bad: http://pastebin.com/JSKSD8Dn
xorglog.bad: http://pastebin.com/QdDhfknr
glxinfo.bad: http://pastebin.com/AWabZKN8
dmesg.reallybad: http://pastebin.com/Jc4sqySK
xorglog.reallybad: http://pastebin.com/fzMEJfZH
glxinfo.reallybad: http://pastebin.com/tkJgTgKa
Good is kernel 2.6.31.6 where I get glxgears frame rates of ~300fps. This is
all I can expect from a slow PCI bus.
Bad is kenel 2.6.33.4 where the glxgears frame rates are a little slower, maybe
250fps and quitting X fails. Logging out of my desktop environment,
Ctrl+Alt+F2, Ctrl+Alt+Backspace, chvt commands, all of these freeze my system.
Reallybad is kernel 2.6.33.4 where glxgears has no consistent frame rate. It
jumps around between 5fps and 60fps and all graphical programs are incredibly
slow. This is in addition to the zapping issue described above.
I am not sure why 2.6.33.4 is sometimes bad and sometimes reallybad. It might
have to do with what USB devices are connected when it boots up.
Please do not tell me to upgrade my userspace programs. I have tried every
combination of xorg-server, mesa, xf86-video-ati and libdrm and none of them
have any effect. The kernel is the ONLY package that changes how bad this bug
is. Also please do not tell me to upgrade the kernel unless you are very sure
that the version you are suggesting fixes this bug and you can tell me why it
fixes it.
I am not looking for a kernel that works. I KNOW which kernel works. I am
trying to understand WHY it is the only one that works and hopefully help you
fix this. Thank-you very much.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=29495
Summary: [r300g] Shadowgrounds: character portraits rendered
wrong
Product: Mesa
Version: git
Platform: Other
URL: http://demofiles.linuxgamepublishing.com/shadowgrounds
/
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel(a)lists.…
[View More]freedesktop.org
ReportedBy: sa(a)whiz.se
Created an attachment (id=37778)
--> (https://bugs.freedesktop.org/attachment.cgi?id=37778)
Screenshot of the bug
Character portraits (visible during dialogue segments) in the game
Shadowgrounds are not rendered correctly. This is not a problem with r300c or
softpipe.
I'm using git master 8dd4308b5e29fd684d6e516161513d3045e5ff9e
This is reproducible with the demo of the game.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=31083
Summary: R600 misrenders irrlicht demo (01helloworld)
Product: Mesa
Version: 7.9
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: curaga(a)operamail.com
Created an attachment (id=39738)
--> (https://…
[View More]bugs.freedesktop.org/attachment.cgi?id=39738)
Software renderer (correct output)
The R600 driver misrenders the first demo of Irrlicht
(irrlicht.sourceforge.net) when edited to use OpenGL instead of irrlicht's
software renderer.
The demo loads an animated md2 model with a bmp texture.
Tested on Mesa 7.8.2 and 7.9, r600 fails on both, software renderer works on
both. Screenshots attached.
HW: Radeon HD4350
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=33825
Summary: [r600g, wine] sync/fenc GL extension missing
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
Hello,
I noticed that r600g currently neither …
[View More]implements NV_fence nor ARB_sync. Wine
needs at least one of these extensions (I think ARB_sync is preferred) to
emulate event queries for Direct3D.
Currently this results in lots of errors:
err:d3d:wined3d_event_query_test Event query created despite lack of GL support
err:d3d:IWineD3DEventQueryImpl_GetData The GL event query failed, returning
D3DERR_INVALIDCALL
So this is more a feature request...
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.
[View Less]