https://bugs.freedesktop.org/show_bug.cgi?id=28847
Summary: Regnum Online only works in safe mode
Product: Mesa
Version: git
Platform: Other
URL: http://www.regnumonline.com.ar/
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
The game Regnum Online (MMO but …
[View More]can be downloaded and played at no cost), only
runs if "Safe Mode" is selected in the options.
With r300c, I get these errors:
drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See
dmesg for more info.
Found 4 messages leaked
[...]
[ 9468.240398] radeon 0000:01:00.0: (PW 1) Vertex array 0 need 268396832 dwords
have 47104 dwords
[ 9468.240402] [drm:r100_cs_track_check] *ERROR* Max indices 16774802
[ 9468.240404] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
With r300g, the game starts, but doesn't render correctly (see attached
screenshot).
The game is run with "Fixed pipeline" set in the options, using shaders will
apprently need the new glsl2 compiler.
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: RV570
-- Model: Asus EAX1950Pro 256MB
-- Display connector: DVI
-- xf86-video-ati: 801e83227a59a29eea425ea612083bbf2b536c30
-- xserver: 1.8.1.901
-- mesa: 75acb896c6da758d03e86f8725d6ca0cb2c6ad82
-- drm: 6ea2bda5f5ec8f27359760ce580fdad3df0464df
-- kernel: 2.6.35-rc3
--
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=28125
Summary: DRI2 prevents indirect glx
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: General
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: NightNord(a)gmail.com
When running glx programs with dri2-enabled mesa on client side, it will return
X Error of …
[View More]failed request: BadRequest (invalid request code or no such
operation)
Major opcode of failed request: 128 (DRI2)
Minor opcode of failed request: 1 (DRI2Connect)
Serial number of failed request: 19
Current serial number in output stream: 19
export LIBG_ALWAYS_INDIRECT=1
does the trick
--
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=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=28995
Summary: [r300g] dri rejects command buffers
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: aaalmosss(a)gmail.com
In some games hexadecimal numbers are printed into the console, rendering
…
[View More]errors occur and performance drops significantly. Affected games: VDrift,
Nexuiz, certain levels in Sauerbraten (eg. venice), certain places in Doom3.
--
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=29692
Summary: Lightsmark lights arent working
Product: Mesa
Version: git
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: schmaker(a)ifrit.eu
Created an attachment (id=38005)
--> (https://bugs.freedesktop.…
[View More]org/attachment.cgi?id=38005)
Not-working lights
Hello there.
Lightsmark lights are just doing crazy collors instead of light on a surface
and drop shadows. Screenshot included.
--
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]