Debian Bug report logs - #616301
xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]

[Message part 1 (text/plain, inline)]
Package: xserver-xorg-video-radeon
Version: 1:6.13.1-2+squeeze1
Severity: important

Hi there.
After updating the packages 2. March 2011 playing youtube videos got somehow
imposible. Screen goes black after movie plays for 2-4 seconds, sound may
continue for few seconds and also stops.
I tried to login to a console but after few tries screen started blinking white
and console 'froze'. The white color stayed- I've powered down the machine the
hard way.
Tried on different browsers Firefox and opera with same effect.
I've attached information.
If more information needed dont hesitate to write.
Sincerely Slyher.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xserver-xorg-video-radeon depends on:
ii  libc6                         2.11.2-11  Embedded GNU C Library: Shared lib
ii  libdrm-radeon1                2.4.23-0.0 Userspace interface to radeon-spec
ii  libdrm2                       2.4.23-0.0 Userspace interface to kernel DRM 
ii  libpciaccess0                 0.12.1-1   Generic PCI access library for X
ii  libpixman-1-0                 0.16.4-1   pixel-manipulation library for X a
ii  libudev0                      166-1      libudev shared library
ii  xserver-xorg-core [xorg-video 2:1.7.7-11 Xorg X server - core server

xserver-xorg-video-radeon recommends no packages.

Versions of packages xserver-xorg-video-radeon suggests:
pn  firmware-linux                <none>     (no description available)

-- no debconf information

[20110303_bugreport.txt (text/plain, attachment)]
On Don, 2011-03-03 at 11:41 +0100, slyher wrote: 
> Package: xserver-xorg-video-radeon
> Version: 1:6.13.1-2+squeeze1
> Severity: important
> 
> Hi there.
> After updating the packages 2. March 2011 [...]

What packages were upgraded from/to which versions?

-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer

W dniu 03.03.2011 12:24, Michel Dänzer pisze:
> On Don, 2011-03-03 at 11:41 +0100, slyher wrote:
>> Package: xserver-xorg-video-radeon
>> Version: 1:6.13.1-2+squeeze1
>> Severity: important
>>
>> Hi there.
>> After updating the packages 2. March 2011 [...]
>
> What packages were upgraded from/to which versions?
>
>

Hi there.
What I can tell from /var/log/apt/history.log

Start-Date: 2011-03-01  17:27:00
Commandline: apt-get dist-upgrade
Upgrade: foomatic-db-engine:i386 (4.0.4-3, 4.0.7-1), dnsmasq-base:i386 
(2.55-2+b1, 2.57-1), python-markupsafe:i386 (0.9.2-3, 0.12-1), 
musescore-common:i386 (0.9.6+dfsg-1, 1.0+dfsg-2), musescore:i386 
(0.9.6+dfsg-1, 1.0+dfsg-2), gpgv:i386 (1.4.10-4, 1.4.11-3), 
foomatic-filters:i386 (4.0.5-6, 4.0.7-1), foomatic-filters-ppds:i386 
(4.0.4-3, 4.0.7-1), musescore-soundfont-gm:i386 (0.9.6+dfsg-1, 
1.0+dfsg-2), gnupg:i386 (1.4.10-4, 1.4.11-3)
End-Date: 2011-03-01  17:28:29

Start-Date: 2011-03-02  09:03:39
Commandline: apt-get dist-upgrade
Install: libclass-load-perl:i386 (0.06-1, automatic)
Upgrade: desktop-base:i386 (6.0.5, 6.0.6), libcupscgi1:i386 (1.4.5-3, 
1.4.6-1), cups-client:i386 (1.4.5-3, 1.4.6-1), libcupsmime1:i386 
(1.4.5-3, 1.4.6-1), libnspr4-0d:i386 (4.8.6-1, 4.8.7-2), cups-ppdc:i386 
(1.4.5-3, 1.4.6-1), libcupsppdc1:i386 (1.4.5-3, 1.4.6-1), 
cups-common:i386 (1.4.5-3, 1.4.6-1), libcups2:i386 (1.4.5-3, 1.4.6-1), 
libgsf-1-common:i386 (1.14.19-2, 1.14.19-3), cups:i386 (1.4.5-3, 
1.4.6-1), libcupsdriver1:i386 (1.4.5-3, 1.4.6-1), libgdata7:i386 
(0.6.4-2, 0.6.4-3), cups-bsd:i386 (1.4.5-3, 1.4.6-1), libcupsimage2:i386 
(1.4.5-3, 1.4.6-1), libdatetime-timezone-perl:i386 (1.23-1+2010n, 
1.28-1+2011b), libgsf-1-114:i386 (1.14.19-2, 1.14.19-3), 
libgdata-common:i386 (0.6.4-2, 0.6.4-3)
End-Date: 2011-03-02  09:05:00

Package: xserver-xorg-video-radeon
Version: 1:6.13.1-2+squeeze1
Severity: normal

Hi.

I'm experiencing the same problem, i.e. whenever I open a youtube.com website with 
video content my system hangs (black screen and monitor reports/gives warning of wrong 
input frequencies).

Until at least two days ago I could play youtube videos without issues using iceweasel 
with Adobe Flash Player (flashplugin-nonfree); but not today.
I also run 'aptitude update && aptitude upgrade' regularly but I doubt the following 
packages have something to do with this.

/var/log/apt/history.log:

Start-Date: 2011-03-01  03:11:17
Upgrade: libsmbclient:amd64 (3.5.6~dfsg-3, 3.5.6~dfsg-3squeeze2), smbclient:amd64 (3.5.6~dfsg-3, 3.5.6~dfsg-3squeeze2), libwbclient0:amd64 (3.5.6~dfsg-3, 3.5.6~dfsg-3squeeze2), libavahi-glib1:amd64 (0.6.27-2, 0.6.27-2+squeeze1), libavahi-common-data:amd64 (0.6.27-2, 0.6.27-2+squeeze1), libavahi-core7:amd64 (0.6.27-2, 0.6.27-2+squeeze1), samba-common:amd64 (3.5.6~dfsg-3, 3.5.6~dfsg-3squeeze2), avahi-dnsconfd:amd64 (0.6.27-2, 0.6.27-2+squeeze1), avahi-daemon:amd64 (0.6.27-2, 0.6.27-2+squeeze1), libavahi-client3:amd64 (0.6.27-2, 0.6.27-2+squeeze1), samba-common-bin:amd64 (3.5.6~dfsg-3, 3.5.6~dfsg-3squeeze2), libavahi-common3:amd64 (0.6.27-2, 0.6.27-2+squeeze1)
End-Date: 2011-03-01  03:11:24

Start-Date: 2011-03-03  02:39:51
Upgrade: libpango1.0-common:amd64 (1.28.3-1+squeeze1, 1.28.3-1+squeeze2), libpango1.0-0:amd64 (1.28.3-1+squeeze1, 1.28.3-1+squeeze2)
End-Date: 2011-03-03  02:39:57

More interesting are the syslog entries when hitting the bug (abbreviated).

/var/log/syslog:

Mar  3 10:17:01 banshee /USR/SBIN/CRON[9664]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar  3 10:18:29 banshee kernel: [27296.676053] [drm:radeon_fence_wait] *ERROR* fence(ffff880061522f40:0x0031D254) 508ms timeout going to reset GPU
Mar  3 10:18:29 banshee kernel: [27296.676064] radeon 0000:01:05.0: GPU softreset 
Mar  3 10:18:29 banshee kernel: [27296.676070] radeon 0000:01:05.0:   R_008010_GRBM_STATUS=0xE77324AC
Mar  3 10:18:29 banshee kernel: [27296.676076] radeon 0000:01:05.0:   R_008014_GRBM_STATUS2=0x00110103
Mar  3 10:18:29 banshee kernel: [27296.676081] radeon 0000:01:05.0:   R_000E50_SRBM_STATUS=0x20001040
Mar  3 10:18:29 banshee kernel: [27296.676090] radeon 0000:01:05.0:   R_008020_GRBM_SOFT_RESET=0x00007FEE
Mar  3 10:18:29 banshee kernel: [27296.676146] radeon 0000:01:05.0: R_008020_GRBM_SOFT_RESET=0x00000001
Mar  3 10:18:29 banshee kernel: [27296.676204] radeon 0000:01:05.0:   R_000E60_SRBM_SOFT_RESET=0x00000402
Mar  3 10:18:29 banshee kernel: [27296.676360] radeon 0000:01:05.0:   R_008010_GRBM_STATUS=0x00003030
Mar  3 10:18:29 banshee kernel: [27296.676365] radeon 0000:01:05.0:   R_008014_GRBM_STATUS2=0x00000003
Mar  3 10:18:29 banshee kernel: [27296.676370] radeon 0000:01:05.0:   R_000E50_SRBM_STATUS=0x20000040
<-- message loop (trying to softreset endlessly) -->
Mar  3 10:20:00 banshee kernel: [27387.493788] [drm:radeon_fence_wait] *ERROR* fence(ffff880062eb7540:0x0031D382) 516ms timeout
Mar  3 10:20:00 banshee kernel: [27387.493797] [drm:radeon_fence_wait] *ERROR* last signaled fence(0x0031D382)
Mar  3 10:20:03 banshee kernel: [27390.008063] [drm:radeon_fence_wait] *ERROR* fence(ffff880062eb7dc0:0x0031D384) 504ms timeout going to reset GPU
Mar  3 10:20:03 banshee kernel: [27390.008076] radeon 0000:01:05.0: GPU softreset 
Mar  3 10:20:03 banshee kernel: [27390.008082] radeon 0000:01:05.0:   R_008010_GRBM_STATUS=0xA0003030
Mar  3 10:20:03 banshee kernel: [27390.008089] radeon 0000:01:05.0:   R_008014_GRBM_STATUS2=0x00000003
Mar  3 10:20:03 banshee kernel: [27390.008096] radeon 0000:01:05.0:   R_000E50_SRBM_STATUS=0x20000040
Mar  3 10:20:03 banshee kernel: [27390.008106] radeon 0000:01:05.0:   R_008020_GRBM_SOFT_RESET=0x00007FEE
Mar  3 10:20:03 banshee kernel: [27390.008164] radeon 0000:01:05.0: R_008020_GRBM_SOFT_RESET=0x00000001
Mar  3 10:20:03 banshee kernel: [27390.008224] radeon 0000:01:05.0:   R_000E60_SRBM_SOFT_RESET=0x00000402
Mar  3 10:20:03 banshee kernel: [27390.008382] radeon 0000:01:05.0:   R_008010_GRBM_STATUS=0x00003030
Mar  3 10:20:03 banshee kernel: [27390.008392] radeon 0000:01:05.0:   R_008014_GRBM_STATUS2=0x00000003
Mar  3 10:20:03 banshee kernel: [27390.008401] radeon 0000:01:05.0:   R_000E50_SRBM_STATUS=0x20000040
Mar  3 10:20:03 banshee kernel: [27390.009795] [drm:radeon_fence_wait] *ERROR* fence(ffff880062eb7dc0:0x0031D384) 512ms timeout
Mar  3 10:20:03 banshee kernel: [27390.009804] [drm:radeon_fence_wait] *ERROR* last signaled fence(0x0031D384)
Mar  3 10:20:04 banshee kernel: [27391.517962] SysRq : Emergency Remount R/O

Maybe Google changed the video format which triggers a bug in the graphics driver?

Kind regards,

Matthias

-- Package-specific info:
/var/lib/x11/X.roster does not exist.

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 May 18  2010 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1889440 Jan 12 04:12 /usr/bin/Xorg

/var/lib/x11/xorg.conf.roster does not exist.

VGA-compatible devices on PCI bus:
01:05.0 VGA compatible controller: ATI Technologies Inc RS880 [Radeon HD 4200]

/var/lib/x11/xorg.conf.md5sum does not exist.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 503 Dec 16 11:30 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
## -----------------------------------------------------------------------
## Custom X.Org configuration file.
## -----------------------------------------------------------------------

#Section "Device"
#	Identifier	"NVIDIA GeForce 7800 GTX"
#	Driver		"nvidia"
#	BusID		"PCI:1:0:0"
#	Screen		0
#EndSection

#Section "Device"
#	Identifier	"AMD Radeon HD 4200"
#	Driver		"fglrx"
#	BusID		"PCI:1:5:0"
#	Screen		0
#	Option		"TexturedVideo"			"true"
#	#Option		"XaaNoOffscreenPixmaps"		"true"
#EndSection

Kernel version (/proc/version):
Linux version 2.6.32-5-amd64 (Debian 2.6.32-30) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 03:40:32 UTC 2011

Xorg X server log files on system:
-rw-r--r-- 1 root root 30115 Mar  3 16:09 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:

X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian
Current Operating System: Linux banshee 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=18f5056f-3fc8-481c-b89b-491c10763f9e ro quiet
Build Date: 12 January 2011  02:59:50AM
xorg-server 2:1.7.7-11 (Cyril Brulebois <kibi@debian.org>) 
Current version of pixman: 0.16.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Mar  3 16:08:56 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(==) No Layout section.  Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |-->Screen "Default Screen Section" (0)
(**) |   |-->Monitor "<default monitor>"
(==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
	Entry deleted from font path.
(==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/Type1,
	/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
	built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
(II) Loader magic: 0x7c8a00
(II) Module ABI versions:
	X.Org ANSI C Emulation: 0.4
	X.Org Video Driver: 6.0
	X.Org XInput driver : 7.0
	X.Org Server Extension : 2.0
(++) using VT number 7

(--) PCI:*(0:1:5:0) 1002:9710:1043:83a2 ATI Technologies Inc RS880 [Radeon HD 4200] rev 0, Mem @ 0xd0000000/268435456, 0xfe5f0000/65536, 0xfe400000/1048576, I/O @ 0x0000c000/256
(II) Open ACPI successful (/var/run/acpid.socket)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension SELinux
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.0.0
	ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.13.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.0.0
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.1.0
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(==) Matched ati as autoconfigured driver 0
(==) Matched vesa as autoconfigured driver 1
(==) Matched fbdev as autoconfigured driver 2
(==) Assigned the driver to the xf86ConfigLayout
(II) LoadModule: "ati"
(II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
(II) Module ati: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 6.13.1
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "radeon"
(II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
(II) Module radeon: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 6.13.1
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 2.3.0
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "fbdev"
(II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
	compiled for 1.7.6.901, module version = 0.4.2
	ABI class: X.Org Video Driver, version 6.0
(II) RADEON: Driver for ATI Radeon chipsets:
	ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
	ATI Radeon Mobility X300 (M24) 3152 (PCIE),
	ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
	ATI Radeon X600 (RV380) 3E50 (PCIE),
	ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
	ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
	ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
	ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
	ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
	ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
	ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
	ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
	ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
	ATI Radeon 8500 AIW BB (AGP), ATI Radeon 8500 AIW BC (AGP),
	ATI Radeon IGP320M (U1) 4336, ATI Radeon IGP330M/340M/350M (U2) 4337,
	ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
	ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
	ATI Radeon X800PRO (R420) JI (AGP),
	ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
	ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
	ATI Radeon Mobility 9800 (M18) JN (AGP),
	ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
	ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP),
	ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
	ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
	ATI Radeon Mobility M7 LW (AGP),
	ATI Mobility FireGL 7800 M7 LX (AGP),
	ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
	ATI FireGL Mobility 9000 (M9) Ld (AGP),
	ATI Radeon Mobility 9000 (M9) Lf (AGP),
	ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI Radeon 9700 Pro ND (AGP),
	ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9600TX NF (AGP),
	ATI FireGL X1 NG (AGP), ATI Radeon 9800PRO NH (AGP),
	ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP),
	ATI Radeon 9800XT NJ (AGP),
	ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
	ATI Radeon Mobility 9600 (M10) NQ (AGP),
	ATI Radeon Mobility 9600 (M11) NR (AGP),
	ATI Radeon Mobility 9600 (M10) NS (AGP),
	ATI FireGL Mobility T2 (M10) NT (AGP),
	ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
	ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
	ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
	ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
	ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
	ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
	ATI Radeon Mobility X300 (M22) 5460 (PCIE),
	ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
	ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
	ATI Radeon X800PRO (R423) UI (PCIE),
	ATI Radeon X800LE (R423) UJ (PCIE),
	ATI Radeon X800SE (R423) UK (PCIE),
	ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
	ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
	ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
	ATI FireGL unknown (R423) UR (PCIE),
	ATI FireGL unknown (R423) UT (PCIE),
	ATI Mobility FireGL V5000 (M26) (PCIE),
	ATI Mobility FireGL V5000 (M26) (PCIE),
	ATI Mobility Radeon X700 XL (M26) (PCIE),
	ATI Mobility Radeon X700 (M26) (PCIE),
	ATI Mobility Radeon X700 (M26) (PCIE),
	ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
	ATI Radeon Mobility 9100 IGP (U3) 5835,
	ATI Radeon XPRESS 200 5954 (PCIE),
	ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
	ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
	ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
	ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
	ATI Radeon XPRESS 200M 5975 (PCIE),
	ATI Radeon XPRESS 200 5A41 (PCIE),
	ATI Radeon XPRESS 200M 5A42 (PCIE),
	ATI Radeon XPRESS 200 5A61 (PCIE),
	ATI Radeon XPRESS 200M 5A62 (PCIE),
	ATI Radeon X300 (RV370) 5B60 (PCIE),
	ATI Radeon X600 (RV370) 5B62 (PCIE),
	ATI Radeon X550 (RV370) 5B63 (PCIE),
	ATI FireGL V3100 (RV370) 5B64 (PCIE),
	ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
	ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
	ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
	ATI Mobility Radeon X800 XT (M28) (PCIE),
	ATI Mobility FireGL V5100 (M28) (PCIE),
	ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
	ATI Radeon X850 XT PE (R480) (PCIE),
	ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
	ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
	ATI Radeon X850 XT (R480) (PCIE),
	ATI Radeon X800XT (R423) 5D57 (PCIE),
	ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
	ATI Radeon X700 PRO (RV410) (PCIE),
	ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
	ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
	ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
	ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
	ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
	ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
	ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
	ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
	ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
	ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
	ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
	ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
	ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
	ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
	ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
	ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
	ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
	ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
	ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
	ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
	ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
	ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
	ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
	ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
	ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
	ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
	ATI Mobility Radeon X1700, ATI Radeon X2300HD,
	ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
	ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
	ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
	ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
	ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
	ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
	ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
	ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
	ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
	ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
	ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
	ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
	ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
	ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
	ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
	ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
	ATI Radeon 4800 Series, ATI Radeon HD 4850 x2,
	ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL),
	ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2,
	ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270,
	AMD FireStream 9250, ATI FirePro V8700 (FireGL),
	ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
	ATI Mobility RADEON HD 4870, ATI Radeon 4800 Series,
	ATI Radeon 4800 Series, ATI FirePro M7750, ATI M98, ATI M98, ATI M98,
	ATI Mobility Radeon HD 4650, ATI Radeon RV730 (AGP),
	ATI Mobility Radeon HD 4670, ATI FirePro M5750,
	ATI Mobility Radeon HD 4670, ATI Radeon RV730 (AGP),
	ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
	ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
	ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
	ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
	ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
	ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI Radeon HD 4770,
	ATI FirePro M5750, ATI RV610, ATI Radeon HD 2400 XT,
	ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000,
	ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
	ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
	ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
	ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
	ATI Mobility Radeon HD 3850 X2, ATI RV670,
	ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
	ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
	ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
	ATI Radeon RV710, ATI Radeon RV710, ATI Radeon RV710,
	ATI Radeon HD 4350, ATI Mobility Radeon 4300 Series,
	ATI Mobility Radeon 4500 Series, ATI Mobility Radeon 4500 Series,
	ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
	ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
	ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
	ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
	ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
	ATI FireGL V3600, ATI Radeon HD 2600 LE,
	ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
	ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
	ATI Radeon HD 3450, ATI Radeon HD 3450, ATI Radeon HD 3430,
	ATI Radeon HD 3450, ATI FirePro V3700, ATI FireMV 2450,
	ATI FireMV 2260, ATI FireMV 2260, ATI Radeon HD 3600 Series,
	ATI Radeon HD 3650 AGP, ATI Radeon HD 3600 PRO,
	ATI Radeon HD 3600 XT, ATI Radeon HD 3600 PRO,
	ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
	ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
	ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
	ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
	ATI Radeon HD 3300 Graphics, ATI Radeon HD 3200 Graphics,
	ATI Radeon 3000 Graphics, ATI Radeon HD 4200, ATI Radeon 4100,
	ATI Mobility Radeon HD 4200, ATI Mobility Radeon 4100,
	ATI Radeon HD 4290, ATI Radeon HD 4290, CYPRESS,
	ATI FirePro (FireGL) Graphics Adapter,
	ATI FirePro (FireGL) Graphics Adapter,
	ATI FirePro (FireGL) Graphics Adapter, ATI Radeon HD 5800 Series,
	ATI Radeon HD 5800 Series, ATI Radeon HD 5800 Series,
	ATI Radeon HD 5900 Series, ATI Radeon HD 5900 Series,
	ATI Mobility Radeon HD 5800 Series,
	ATI Mobility Radeon HD 5800 Series,
	ATI FirePro (FireGL) Graphics Adapter,
	ATI FirePro (FireGL) Graphics Adapter,
	ATI Mobility Radeon HD 5800 Series, ATI Radeon HD 5700 Series,
	ATI Radeon HD 5700 Series, ATI Radeon HD 5700 Series,
	ATI Mobility Radeon HD 5000 Series,
	ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
	ATI FirePro (FireGL) Graphics Adapter,
	ATI FirePro (FireGL) Graphics Adapter, ATI Radeon HD 5670,
	ATI Radeon HD 5570, ATI Radeon HD 5500 Series, REDWOOD,
	ATI Mobility Radeon HD 5000 Series,
	ATI Mobility Radeon HD 5000 Series, CEDAR, CEDAR, CEDAR,
	ATI FirePro (FireGL) Graphics Adapter,
	ATI FirePro (FireGL) Graphics Adapter, CEDAR, ATI Radeon HD 5450,
	CEDAR
(II) VESA: driver for VESA chipsets: vesa
(II) FBDEV: driver for framebuffer: fbdev
(II) Primary Device is: PCI 01@00:05:0
(II) [KMS] Kernel modesetting enabled.
(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib/xorg/modules/linux/libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 0.0.2
	ABI class: X.Org Video Driver, version 6.0
(II) RADEON(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
(==) RADEON(0): Depth 24, (--) framebuffer bpp 32
(II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) RADEON(0): Default visual is TrueColor
(==) RADEON(0): RGB weight 888
(II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
(--) RADEON(0): Chipset: "ATI Radeon HD 4200" (ChipID = 0x9710)
(II) RADEON(0): PCI card detected
(WW) RADEON(0): Color tiling is not yet supported on R600/R700
(II) RADEON(0): KMS Color Tiling: disabled
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:05.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: drmOpenMinor returns 9
drmOpenByBusid: drmGetBusid reports pci:0000:01:05.0
(II) RADEON(0): Output VGA-0 has no monitor section
(II) RADEON(0): Output DVI-0 has no monitor section
(II) RADEON(0): EDID for output VGA-0
(II) RADEON(0): EDID for output DVI-0
(II) RADEON(0): Manufacturer: ENC  Model: 1786  Serial#: 16843009
(II) RADEON(0): Year: 2005  Week: 27
(II) RADEON(0): EDID Version: 1.3
(II) RADEON(0): Digital Display Input
(II) RADEON(0): Max Image Size [cm]: horiz.: 38  vert.: 30
(II) RADEON(0): Gamma: 2.20
(II) RADEON(0): DPMS capabilities: StandBy Suspend Off
(II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 
(II) RADEON(0): First detailed timing is preferred mode
(II) RADEON(0): redX: 0.640 redY: 0.330   greenX: 0.290 greenY: 0.605
(II) RADEON(0): blueX: 0.145 blueY: 0.075   whiteX: 0.313 whiteY: 0.329
(II) RADEON(0): Supported established timings:
(II) RADEON(0): 720x400@70Hz
(II) RADEON(0): 640x480@60Hz
(II) RADEON(0): 800x600@60Hz
(II) RADEON(0): 1024x768@60Hz
(II) RADEON(0): Manufacturer's mask: 0
(II) RADEON(0): Supported standard timings:
(II) RADEON(0): #0: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
(II) RADEON(0): Supported detailed timing:
(II) RADEON(0): clock: 108.0 MHz   Image Size:  376 x 301 mm
(II) RADEON(0): h_active: 1280  h_sync: 1328  h_sync_end 1440 h_blank_end 1688 h_border: 0
(II) RADEON(0): v_active: 1024  v_sync: 1025  v_sync_end 1028 v_blanking: 1066 v_border: 0
(II) RADEON(0): Serial No: 22233065
(II) RADEON(0): Ranges: V min: 59 V max: 61 Hz, H min: 31 H max: 64 kHz, PixClock max 115 MHz
(II) RADEON(0): Monitor name: S1910
(II) RADEON(0): EDID (in hex):
(II) RADEON(0): 	00ffffffffffff0015c3861701010101
(II) RADEON(0): 	1b0f010380261e78eae415a3544a9b25
(II) RADEON(0): 	135054a1080081800101010101010101
(II) RADEON(0): 	010101010101302a009851002a403070
(II) RADEON(0): 	1300782d1100001e000000ff00323232
(II) RADEON(0): 	33333036350a20202020000000fd003b
(II) RADEON(0): 	3d1f400b000a202020202020000000fc
(II) RADEON(0): 	0053313931300a2020202020202000cf
(II) RADEON(0): Printing probed modes for output DVI-0
(II) RADEON(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) RADEON(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) RADEON(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) RADEON(0): Modeline "640x480"x60.0   25.20  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) RADEON(0): Modeline "720x400"x70.1   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
(II) RADEON(0): Output VGA-0 disconnected
(II) RADEON(0): Output DVI-0 connected
(II) RADEON(0): Using exact sizes for initial modes
(II) RADEON(0): Output DVI-0 using initial mode 1280x1024
(II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
(II) RADEON(0): mem size init: gart size :1fdff000 vram size: s:10000000 visible:fac0000
(II) RADEON(0): EXA: Driver will allow EXA pixmaps in VRAM
(==) RADEON(0): DPI set to (96, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.0.0
	ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) Loading sub module "exa"
(II) LoadModule: "exa"
(II) Loading /usr/lib/xorg/modules/libexa.so
(II) Module exa: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 2.5.0
	ABI class: X.Org Video Driver, version 6.0
(II) UnloadModule: "vesa"
(II) Unloading /usr/lib/xorg/modules/drivers/vesa_drv.so
(II) UnloadModule: "fbdev"
(II) Unloading /usr/lib/xorg/modules/drivers/fbdev_drv.so
(II) UnloadModule: "fbdevhw"
(II) Unloading /usr/lib/xorg/modules/linux/libfbdevhw.so
(--) Depth 24 pixmap format is 32 bpp
(II) RADEON(0): [DRI2] Setup complete
(II) RADEON(0): Front buffer size: 5120K
(II) RADEON(0): VRAM usage limit set to 226483K
(==) RADEON(0): Backing store disabled
(II) RADEON(0): Direct rendering enabled
(II) RADEON(0): Setting EXA maxPitchBytes
(II) EXA(0): Driver allocated offscreen pixmaps
(II) EXA(0): Driver registered support for the following operations:
(II)         Solid
(II)         Copy
(II)         Composite (RENDER acceleration)
(II)         UploadToScreen
(II)         DownloadFromScreen
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): DPMS enabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Set up textured video
(II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
SELinux: Disabled on system, not enabling in X server
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_make_current_read
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
(II) AIGLX: Loaded and initialized /usr/lib/dri/r600_dri.so
(II) GLX: Initialized DRI2 GL provider for screen 0
(II) RADEON(0): Setting screen physical size to 338 x 270
(II) config/udev: Adding input device Power Button (/dev/input/event4)
(**) Power Button: Applying InputClass "evdev keyboard catchall"
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
	compiled for 1.7.6.901, module version = 2.3.2
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 7.0
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event4"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "de"
(**) Option "xkb_variant" "nodeadkeys"
(II) config/udev: Adding input device Power Button (/dev/input/event3)
(**) Power Button: Applying InputClass "evdev keyboard catchall"
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event3"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "de"
(**) Option "xkb_variant" "nodeadkeys"
(II) config/udev: Adding input device HID 046a:0011 (/dev/input/event1)
(**) HID 046a:0011: Applying InputClass "evdev keyboard catchall"
(**) HID 046a:0011: always reports core events
(**) HID 046a:0011: Device: "/dev/input/event1"
(II) HID 046a:0011: Found keys
(II) HID 046a:0011: Configuring as keyboard
(II) XINPUT: Adding extended input device "HID 046a:0011" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "de"
(**) Option "xkb_variant" "nodeadkeys"
(II) config/udev: Adding input device Logitech USB Gaming Mouse (/dev/input/event2)
(**) Logitech USB Gaming Mouse: Applying InputClass "evdev pointer catchall"
(**) Logitech USB Gaming Mouse: always reports core events
(**) Logitech USB Gaming Mouse: Device: "/dev/input/event2"
(II) Logitech USB Gaming Mouse: Found 20 mouse buttons
(II) Logitech USB Gaming Mouse: Found scroll wheel(s)
(II) Logitech USB Gaming Mouse: Found relative axes
(II) Logitech USB Gaming Mouse: Found x and y relative axes
(II) Logitech USB Gaming Mouse: Configuring as mouse
(**) Logitech USB Gaming Mouse: YAxisMapping: buttons 4 and 5
(**) Logitech USB Gaming Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Gaming Mouse" (type: MOUSE)
(II) Logitech USB Gaming Mouse: initialized for relative axes.
(II) config/udev: Adding input device Logitech USB Gaming Mouse (/dev/input/mouse1)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device PC Speaker (/dev/input/event5)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/event0)
(**) Macintosh mouse button emulation: Applying InputClass "evdev pointer catchall"
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found relative axes
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/mouse0)
(II) No input driver/identifier specified (ignoring)
(II) RADEON(0): EDID vendor "ENC", prod id 6022
(II) RADEON(0): Using EDID range info for horizontal sync
(II) RADEON(0): Using EDID range info for vertical refresh
(II) RADEON(0): Printing DDC gathered Modelines:
(II) RADEON(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) RADEON(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) RADEON(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) RADEON(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
(II) RADEON(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) RADEON(0): EDID vendor "ENC", prod id 6022
(II) RADEON(0): Using hsync ranges from config file
(II) RADEON(0): Using vrefresh ranges from config file
(II) RADEON(0): Printing DDC gathered Modelines:
(II) RADEON(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) RADEON(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) RADEON(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) RADEON(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
(II) RADEON(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) RADEON(0): EDID vendor "ENC", prod id 6022
(II) RADEON(0): Using hsync ranges from config file
(II) RADEON(0): Using vrefresh ranges from config file
(II) RADEON(0): Printing DDC gathered Modelines:
(II) RADEON(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) RADEON(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) RADEON(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) RADEON(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
(II) RADEON(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)

udev information:
P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4
N: input/event4
S: char/13:68
E: UDEV_LOG=3
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4
E: MAJOR=13
E: MINOR=68
E: DEVNAME=/dev/input/event4
E: SUBSYSTEM=input
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: XKBMODEL=pc105
E: XKBLAYOUT=de
E: XKBVARIANT=nodeadkeys
E: DEVLINKS=/dev/char/13:68
E: DMI_VENDOR=System manufacturer

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3/event3
N: input/event3
S: char/13:67
E: UDEV_LOG=3
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3/event3
E: MAJOR=13
E: MINOR=67
E: DEVNAME=/dev/input/event3
E: SUBSYSTEM=input
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: XKBMODEL=pc105
E: XKBLAYOUT=de
E: XKBVARIANT=nodeadkeys
E: DEVLINKS=/dev/char/13:67
E: DMI_VENDOR=System manufacturer

P: /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.0/input/input1/event1
N: input/event1
S: char/13:65
S: input/by-id/usb-046a_0011-event-kbd
S: input/by-path/pci-0000:00:12.1-usb-0:2:1.0-event-kbd
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.0/input/input1/event1
E: MAJOR=13
E: MINOR=65
E: DEVNAME=/dev/input/event1
E: SUBSYSTEM=input
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_INPUT_KEYBOARD=1
E: ID_VENDOR=046a
E: ID_VENDOR_ENC=046a
E: ID_VENDOR_ID=046a
E: ID_MODEL=0011
E: ID_MODEL_ENC=0011
E: ID_MODEL_ID=0011
E: ID_REVISION=0100
E: ID_SERIAL=046a_0011
E: ID_TYPE=hid
E: ID_BUS=usb
E: ID_USB_INTERFACES=:030101:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH=pci-0000:00:12.1-usb-0:2:1.0
E: XKBMODEL=pc105
E: XKBLAYOUT=de
E: XKBVARIANT=nodeadkeys
E: DEVLINKS=/dev/char/13:65 /dev/input/by-id/usb-046a_0011-event-kbd /dev/input/by-path/pci-0000:00:12.1-usb-0:2:1.0-event-kbd

P: /devices/pci0000:00/0000:00:12.1/usb4/4-3/4-3:1.0/input/input2/event2
N: input/event2
S: char/13:66
S: input/by-id/usb-Logitech_USB_Gaming_Mouse-event-mouse
S: input/by-path/pci-0000:00:12.1-usb-0:3:1.0-event-mouse
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:12.1/usb4/4-3/4-3:1.0/input/input2/event2
E: MAJOR=13
E: MINOR=66
E: DEVNAME=/dev/input/event2
E: SUBSYSTEM=input
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_VENDOR=Logitech
E: ID_VENDOR_ENC=Logitech
E: ID_VENDOR_ID=046d
E: ID_MODEL=USB_Gaming_Mouse
E: ID_MODEL_ENC=USB\x20Gaming\x20Mouse
E: ID_MODEL_ID=c041
E: ID_REVISION=4602
E: ID_SERIAL=Logitech_USB_Gaming_Mouse
E: ID_TYPE=hid
E: ID_BUS=usb
E: ID_USB_INTERFACES=:030102:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH=pci-0000:00:12.1-usb-0:3:1.0
E: DEVLINKS=/dev/char/13:66 /dev/input/by-id/usb-Logitech_USB_Gaming_Mouse-event-mouse /dev/input/by-path/pci-0000:00:12.1-usb-0:3:1.0-event-mouse

P: /devices/pci0000:00/0000:00:12.1/usb4/4-3/4-3:1.0/input/input2/mouse1
N: input/mouse1
S: char/13:33
S: input/by-id/usb-Logitech_USB_Gaming_Mouse-mouse
S: input/by-path/pci-0000:00:12.1-usb-0:3:1.0-mouse
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:12.1/usb4/4-3/4-3:1.0/input/input2/mouse1
E: MAJOR=13
E: MINOR=33
E: DEVNAME=/dev/input/mouse1
E: SUBSYSTEM=input
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_VENDOR=Logitech
E: ID_VENDOR_ENC=Logitech
E: ID_VENDOR_ID=046d
E: ID_MODEL=USB_Gaming_Mouse
E: ID_MODEL_ENC=USB\x20Gaming\x20Mouse
E: ID_MODEL_ID=c041
E: ID_REVISION=4602
E: ID_SERIAL=Logitech_USB_Gaming_Mouse
E: ID_TYPE=hid
E: ID_BUS=usb
E: ID_USB_INTERFACES=:030102:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH=pci-0000:00:12.1-usb-0:3:1.0
E: DEVLINKS=/dev/char/13:33 /dev/input/by-id/usb-Logitech_USB_Gaming_Mouse-mouse /dev/input/by-path/pci-0000:00:12.1-usb-0:3:1.0-mouse

P: /devices/platform/pcspkr/input/input5/event5
N: input/event5
S: char/13:69
S: input/by-path/platform-pcspkr-event-spkr
E: UDEV_LOG=3
E: DEVPATH=/devices/platform/pcspkr/input/input5/event5
E: MAJOR=13
E: MINOR=69
E: DEVNAME=/dev/input/event5
E: SUBSYSTEM=input
E: ID_INPUT=1
E: ID_SERIAL=noserial
E: ID_PATH=platform-pcspkr
E: DMI_VENDOR=System manufacturer
E: DEVLINKS=/dev/char/13:69 /dev/input/by-path/platform-pcspkr-event-spkr

P: /devices/virtual/input/input0/event0
N: input/event0
S: char/13:64
E: UDEV_LOG=3
E: DEVPATH=/devices/virtual/input/input0/event0
E: MAJOR=13
E: MINOR=64
E: DEVNAME=/dev/input/event0
E: SUBSYSTEM=input
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_SERIAL=noserial
E: DMI_VENDOR=System manufacturer
E: DEVLINKS=/dev/char/13:64

P: /devices/virtual/input/input0/mouse0
N: input/mouse0
S: char/13:32
E: UDEV_LOG=3
E: DEVPATH=/devices/virtual/input/input0/mouse0
E: MAJOR=13
E: MINOR=32
E: DEVNAME=/dev/input/mouse0
E: SUBSYSTEM=input
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_SERIAL=noserial
E: DEVLINKS=/dev/char/13:32

DRM Information from dmesg:
[    0.000000] No AGP bridge found
[    0.677519] PCI-DMA: Disabling AGP.
[    0.677603] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
[    0.684723] Linux agpgart interface v0.103
[    3.748020] [drm] Initialized drm 1.1.0 20060810
[    4.716951] [drm] radeon kernel modesetting enabled.
[    4.718498] [drm] radeon: Initializing kernel modesetting.
[    4.718624] [drm] register mmio base: 0xFE5F0000
[    4.718625] [drm] register mmio size: 65536
[    4.722999] [drm] Clocks initialized !
[    4.724731] [drm] Detected VRAM RAM=256M, BAR=256M
[    4.724734] [drm] RAM width 32bits DDR
[    4.724820] [drm] radeon: 256M of VRAM memory ready
[    4.724822] [drm] radeon: 512M of GTT memory ready.
[    4.724851] [drm] radeon: irq initialized.
[    4.724853] [drm] GART: num cpu pages 131072, num gpu pages 131072
[    4.725231] [drm] Loading RS780 Microcode
[    5.111520] [drm] ring test succeeded in 1 usecs
[    5.111595] [drm] radeon: ib pool ready.
[    5.111644] [drm] ib test succeeded in 0 usecs
[    5.111646] [drm] Enabling audio support
[    5.111740] [drm] Radeon Display Connectors
[    5.111742] [drm] Connector 0:
[    5.111743] [drm]   VGA
[    5.111745] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[    5.111747] [drm]   Encoders:
[    5.111752] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
[    5.111753] [drm] Connector 1:
[    5.111754] [drm]   DVI-D
[    5.111755] [drm]   HPD1
[    5.111757] [drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[    5.111758] [drm]   Encoders:
[    5.111759] [drm]     DFP3: INTERNAL_KLDSCP_LVTMA
[    5.261809] [drm] fb mappable at 0xD0141000
[    5.261811] [drm] vram apper at 0xD0000000
[    5.261812] [drm] size 5242880
[    5.261813] [drm] fb depth is 24
[    5.261814] [drm]    pitch is 5120
[    5.294019] fb0: radeondrmfb frame buffer device
[    5.294025] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:05.0 on minor 0

-- System Information:
Debian Release: 6.0
  APT prefers squeeze-updates
  APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/3 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xserver-xorg-video-radeon depends on:
ii  libc6                  2.11.2-10         Embedded GNU C Library: Shared lib
ii  libdrm-radeon1         2.4.21-1~squeeze3 Userspace interface to radeon-spec
ii  libdrm2                2.4.21-1~squeeze3 Userspace interface to kernel DRM 
ii  libpciaccess0          0.12.0-1          Generic PCI access library for X
ii  libpixman-1-0          0.16.4-1          pixel-manipulation library for X a
ii  libudev0               164-3             libudev shared library
ii  xserver-xorg-core [xor 2:1.7.7-11        Xorg X server - core server

xserver-xorg-video-radeon recommends no packages.

Versions of packages xserver-xorg-video-radeon suggests:
ii  firmware-linux                0.28       Binary firmware for various driver

-- no debconf information

I forgot to mention that other websites serving video via Adobe Flash do not trigger the bug - at least those I tried (http://www.tagesschau.de/, http://www.vimeo.com/, http://www.myvideo.de/).

Kind regards,

Matthias

-- 
NEU: FreePhone - kostenlos mobil telefonieren und surfen!			
Jetzt informieren: http://www.gmx.net/de/go/freephone

Hi,

Same thing here, opening any youtube video since March 3 crashes the whole
system using iceweasel 3.5.16-4. The crash has been consistent across two
identical machines and started occurring yesterday. The fact that we didn't
upgrade Flash, combined with the fact that yesterday I noticed some issues* on
youtube on another machine (without radeon), leads me to the conclusion that
the bug is triggered by some change youtube did to their player.

* red and green tinting allover the video and misaligned image, as well as
  crashes of the plugin (only, not the browser or the system). This system has
  nothing to do with the affected systems (i915, x86, lenny).

Due to this bug actually DoS'ing the whole system by simply opening a URL, IMHO
it should be marked "critical" (and possibly reassinged to the kernel?).

The hardware we're having problems with, are two x86_64 systems with:

VGA compatible controller: ATI Technologies Inc RV620 LE [Radeon HD 3450]

graphics cards.

I have tested with both, 2.6.32-5-amd64 (2.6.32-30) and 2.6.37-2-amd64 from 
sid (2.6.37-2) with the same result (crash). Also, I tried both 
xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 (squeeze) and 1:6.14.0-1 
(sid) and both keep crashing.

The problem in my system manifests with flash plugin version 10.3 r162
(64-bit). Version 10.0 r42 (which was in /var/cache/flashplugin-nonfree) works
fine.

Following are the backtraces obtained with netconsole from 2.6.32 and 
2.6.37:

2.6.32
======
[  826.144018] [drm:radeon_fence_wait] *ERROR* fence(ffff88010002a980:0x0000CA4C) 504ms timeout going
to reset GPU
[  826.144029] radeon 0000:01:00.0: GPU softreset
[  826.144033] radeon 0000:01:00.0:   R_008010_GRBM_STATUS=0xE57024E0
[  826.144038] radeon 0000:01:00.0:   R_008014_GRBM_STATUS2=0x00110103
[  826.144042] radeon 0000:01:00.0:   R_000E50_SRBM_STATUS=0x200000C0
[  826.144052] radeon 0000:01:00.0:   R_008020_GRBM_SOFT_RESET=0x00007FEE
[  826.144107] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001
[  826.144166] radeon 0000:01:00.0:   R_000E60_SRBM_SOFT_RESET=0x00000402
(death and silence)

2.6.37
======
[  491.372026] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[  491.372034] ------------[ cut here ]------------
[  491.372059] WARNING: at /build/buildd-linux-2.6_2.6.37-2-amd64-bITS0h/linux-2.6-2.6.37/debian/build
/source_amd64_none/drivers/gpu/drm/radeon/radeon_fence.c:244 radeon_fence_wait+0x235/0x2d3 [radeon]()
[  491.372065] Hardware name: OptiPlex 780
[  491.372068] GPU lockup (waiting for 0x00006E39 last fence id 0x00006E38)
[  491.372072] Modules linked in: gre netconsole configfs 8021q garp ppdev lp nf_conntrack_netlink nfn
etlink kvm_intel kvm nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_pkttype xt_tcpudp
nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables fuse bridge s
tp coretemp loop snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss
snd_pcm radeon snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundc
ore ttm drm_kms_helper drm i2c_algo_bit snd_page_alloc power_supply shpchp parport_pc joydev tpm_tis t
pm dell_wmi sparse_keymap i2c_i801 tpm_bios processor wmi parport i2c_core thermal_sys dcdbas[  491.37
3400] radeon 0000:01:00.0: GPU softreset
[  491.373403] radeon 0000:01:00.0:   R_008010_GRBM_STATUS=0xE57024E0
[  491.373406] radeon 0000:01:00.0:   R_008014_GRBM_STATUS2=0x00110103
[  491.373408] radeon 0000:01:00.0:   R_000E50_SRBM_STATUS=0x200000C0
[  491.373416] radeon 0000:01:00.0:   R_008020_GRBM_SOFT_RESET=0x00007FEE
[  491.388299] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001
[  491.404176] radeon 0000:01:00.0:   R_008010_GRBM_STATUS=0xA0003030
[  491.404179] radeon 0000:01:00.0:   R_008014_GRBM_STATUS2=0x00000003
[  491.404181] radeon 0000:01:00.0:   R_000E50_SRBM_STATUS=0x200080C0
[  491.405177] radeon 0000:01:00.0: GPU reset succeed
[  491.405200] BUG: unable to handle kernel paging request at ffffc900112013e0
[  491.405258] IP: [<ffffffffa046fa73>] rs600_gart_set_page+0x28/0x34 [radeon]
[  491.405304] PGD 12780d067 PUD 12780e067 PMD 11f44a067 PTE 0
[  491.405336] Oops: 0002 [#1] SMP
[  491.405354] last sysfs file: /sys/devices/virtual/dmi/id/chassis_asset_tag
[  491.405379] CPU 1
[  491.405388] Modules linked in: gre netconsole configfs 8021q garp ppdev lp nf_conntrack_netlink nfn
etlink kvm_intel kvm nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_pkttype xt_tcpudp
nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables fuse bridge s
tp coretemp loop snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss
snd_pcm radeon snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundc
ore ttm drm_kms_helper drm i2c_algo_bit snd_page_alloc power_supply shpchp parport_pc joydev tpm_tis t
pm dell_wmi sparse_keymap i2c_i801 tpm_bios processor wmi parport i2c_core thermal_sys dcdbas pcspkr p
smouse evdev button pci_hotplug serio_raw ext3 libahci ehci_hcd libata usbcore scsi_mod e1000e nls_bas
e [last unloaded: ip_gre]
[  491.405920]
[  491.405928] Pid: 24, comm: kworker/1:1 Tainted: G        W   2.6.37-2-amd64 #1 Dell Inc. OptiPlex 7
80                 /0C27VV
[  491.405979] RIP: 0010:[<ffffffffa046fa73>]  [<ffffffffa046fa73>] rs600_gart_set_page+0x28/0x34 [rad
eon]
[  491.406020] RSP: 0018:ffff8801234a5d28  EFLAGS: 00010202
[  491.406040] RAX: ffffc90011200000 RBX: ffff88011fe96000 RCX: 0000000000000000
[  491.406064] RDX: 0000000037c11067 RSI: ffffc900112013e0 RDI: ffff88011fe96000
[  491.406087] RBP: 0000000000000000 R08: 0000000000000000 R09: ffff8801221aae00
[  491.406111] R10: 0000000000000286 R11: ffff8801221a96a8 R12: 000000000000027d
[  491.406135] R13: 000000000000027c R14: 000000000000027c R15: 0000000000000001
[  491.406158] FS:  0000000000000000(0000) GS:ffff8800cfa40000(0000) knlGS:0000000000000000
[  491.406186] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  491.406206] CR2: ffffc900112013e0 CR3: 000000011fec4000 CR4: 00000000000406e0
[  491.406229] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  491.406253] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  491.406277] Process kworker/1:1 (pid: 24, threadinfo ffff8801234a4000, task ffff8801234a8000)
[  491.406305] Stack:
[  491.406313]  ffffffffa044efaa ffff8801221a9648 ffff880122138b80 ffff8801208ba808
[  491.406349]  ffff8801221a9730 0000000000000002 0000000000000000 ffff8801221a9690
[  491.406385]  ffffffffa044d3cc ffff880120c8fd20 ffffffffa03b3aaa ffff8801221a9648
[  491.406419] Call Trace:
[  491.406439]  [<ffffffffa044efaa>] ? radeon_gart_unbind+0xec/0x11a [radeon]
[  491.406470]  [<ffffffffa044d3cc>] ? radeon_ttm_backend_unbind+0x14/0x1c [radeon]
[  491.406499]  [<ffffffffa03b3aaa>] ? ttm_tt_unbind+0x15/0x26 [ttm]
[  491.406524]  [<ffffffffa03b4668>] ? ttm_bo_cleanup_memtype_use+0x15/0x55 [ttm]
[  491.406551]  [<ffffffffa03b53bf>] ? ttm_bo_cleanup_refs+0x163/0x195 [ttm]
[  491.406575]  [<ffffffffa03b547c>] ? ttm_bo_delayed_delete+0x8b/0xfe [ttm]
[  491.406601]  [<ffffffffa03b54ef>] ? ttm_bo_delayed_workqueue+0x0/0x26 [ttm]
[  491.406626]  [<ffffffffa03b5501>] ? ttm_bo_delayed_workqueue+0x12/0x26 [ttm]
[  491.406652]  [<ffffffff8105b7e4>] ? process_one_work+0x1d1/0x2ee
[  491.406676]  [<ffffffff8105d273>] ? worker_thread+0x12d/0x247
[  491.406696]  [<ffffffff8105d146>] ? worker_thread+0x0/0x247
[  491.406715]  [<ffffffff8105d146>] ? worker_thread+0x0/0x247
[  491.406735]  [<ffffffff8106012f>] ? kthread+0x7a/0x82
[  491.406753]  [<ffffffff8100a824>] ? kernel_thread_helper+0x4/0x10
[  491.406775]  [<ffffffff810600b5>] ? kthread+0x0/0x82
[  491.406793]  [<ffffffff8100a820>] ? kernel_thread_helper+0x0/0x10
[  491.406814] Code: 5b ff e0 85 f6 48 8b 87 58 03 00 00 78 23 3b b7 40 03 00 00 77 1b c1 e6 03 48 81
e2 00 f0 ff ff 48 63 f6 48 83 ca 67 48 8d 34 30 <48> 89 16 31 c0 c3 b8 ea ff ff ff c3 41 54 49 [  491.
407104] CR2: ffffc900112013e0

Regards,
Apollon

On Fre, 2011-03-04 at 14:51 +0200, Apollon Oikonomopoulos wrote: 
> 
> I have tested with both, 2.6.32-5-amd64 (2.6.32-30) and 2.6.37-2-amd64 from 
> sid (2.6.37-2) with the same result (crash). Also, I tried both 
> xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 (squeeze) and 1:6.14.0-1 
> (sid) and both keep crashing.

Which versions of libgl1-mesa-dri have you tried?

-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer

On 15:36 Fri 04 Mar     , Michel Dänzer wrote:
> On Fre, 2011-03-04 at 14:51 +0200, Apollon Oikonomopoulos wrote: 
> > 
> > I have tested with both, 2.6.32-5-amd64 (2.6.32-30) and 2.6.37-2-amd64 from 
> > sid (2.6.37-2) with the same result (crash). Also, I tried both 
> > xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 (squeeze) and 1:6.14.0-1 
> > (sid) and both keep crashing.
> 
> Which versions of libgl1-mesa-dri have you tried?
> 

I was using the squeeze versions:

libdrm-radeon1 2.4.21-1~squeeze3
libgl1-mesa-dri 7.7.1-4

After upgrading to the current versions in sid:

libdrm-radeon1 2.4.23-3
libgl1-mesa-dri 7.10-4

it seems to be stable. I got a flash plugin crash once (out of 4 attempts), but
the system survived.

On Fre, 2011-03-04 at 16:51 +0200, Apollon Oikonomopoulos wrote: 
> On 15:36 Fri 04 Mar     , Michel Dänzer wrote:
> > On Fre, 2011-03-04 at 14:51 +0200, Apollon Oikonomopoulos wrote: 
> > > 
> > > I have tested with both, 2.6.32-5-amd64 (2.6.32-30) and 2.6.37-2-amd64 from 
> > > sid (2.6.37-2) with the same result (crash). Also, I tried both 
> > > xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 (squeeze) and 1:6.14.0-1 
> > > (sid) and both keep crashing.
> > 
> > Which versions of libgl1-mesa-dri have you tried?
> 
> I was using the squeeze versions:
> 
> libdrm-radeon1 2.4.21-1~squeeze3
> libgl1-mesa-dri 7.7.1-4
> 
> After upgrading to the current versions in sid:
> 
> libdrm-radeon1 2.4.23-3
> libgl1-mesa-dri 7.10-4
> 
> it seems to be stable. I got a flash plugin crash once (out of 4 attempts), but
> the system survived.

So far, so good. If you can try 7.10-2 (which was still shipping the
classic r600 driver, whereas 7.10-4 is shipping the Gallium based one)
or other versions in between as well, that would be interesting.

-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer

severity 616301 critical
thanks

My system locks up whenever I click on a YouTube video link since
yesterday. I can probably live without YouTube :), but in any case this
shouldn't happen.

This isn't a singled out case nor in exotic, possibly faulty, hardware.
It's on a standard 1½-year old Dell OptiPlex 780 desktop with a Radeon
HD card (one of the standard configurations) and this is on a stock
squeeze system.

The findings so far seem to suggest this is a Mesa issue; I'd probably
file it under "Linux kernel bugs" (or even DoS bugs) but I'm not sure
where to properly file such bugs in the post-KMS stack world.

Regards,
Faidon

[Message part 1 (text/plain, inline)]
severity 616301 important
thanks

Faidon Liambotis <paravoid@debian.org> (04/03/2011):
> severity 616301 critical
> thanks

No…

> […] but in any case this shouldn't happen.

Plenty of other things shouldn't happen. That doesn't make it a
critical bug.

KiBi.

[signature.asc (application/pgp-signature, inline)]
> Datum: Fri, 04 Mar 2011 17:36:21 +0100
> Von: "Michel Dänzer" <daenzer@debian.org>
> An: Apollon Oikonomopoulos <apoikos@gmail.com>
> CC: 616301-submitter@bugs.debian.org, "Matthias Rühl" <matthias.ruehl@gmx.de>
> Betreff: Re: Bug#616301: xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]

> So far, so good. If you can try 7.10-2 (which was still shipping the
> classic r600 driver, whereas 7.10-4 is shipping the Gallium based one)
> or other versions in between as well, that would be interesting.
> 
> 
> -- 
> Earthling Michel Dänzer           |                http://www.vmware.com
> Libre software enthusiast         |          Debian, X and DRI developer

With packages 

libdrm-radeon1_2.4.23-2
libgl1-mesa-dri_7.10-2
libtalloc2_2.0.5-1

from http://snapshot.debian.org/archive/debian/20110210T084921Z/ 
iceweasel sometimes freezes when viewing youtube videos but so far this 
doesn't trigger gpu softresets.

Kind regards,

Matthias
-- 
Schon gehört? GMX hat einen genialen Phishing-Filter in die
Toolbar eingebaut! http://www.gmx.net/de/go/toolbar

[Message part 1 (text/plain, inline)]
Hi,

Herber Sylwester <slyher@oomkill.net> (03/03/2011):
> What I can tell from /var/log/apt/history.log
> […]

hmm, nothing seems related. Any chance you upgraded something in the
kernel/X stack before that, and only restarted your X or rebooted
lately?

KiBi.

[signature.asc (application/pgp-signature, inline)]
[Message part 1 (text/plain, inline)]
(Trying to gather everyone in To/Cc.)

Hi,

Apollon Oikonomopoulos <apoikos@gmail.com> (04/03/2011):
> Same thing here, opening any youtube video since March 3 crashes the whole
> system using iceweasel 3.5.16-4. The crash has been consistent across two
> identical machines and started occurring yesterday. The fact that we didn't
> upgrade Flash, combined with the fact that yesterday I noticed some issues* on
> youtube on another machine (without radeon), leads me to the conclusion that
> the bug is triggered by some change youtube did to their player.

while you're at it, could you try switching off KMS? That should get
you a working system in the interim.

> The hardware we're having problems with, are two x86_64 systems with:
> VGA compatible controller: ATI Technologies Inc RV620 LE [Radeon HD 3450]
> 
> graphics cards.
> 
> I have tested with both, 2.6.32-5-amd64 (2.6.32-30) and
> 2.6.37-2-amd64 from sid (2.6.37-2) with the same result
> (crash). Also, I tried both xserver-xorg-video-radeon
> 1:6.13.1-2+squeeze1 (squeeze) and 1:6.14.0-1 (sid) and both keep
> crashing.

If you have some more time, you might want to check what happens with
2.6.38rc* from experimental.

> Following are the backtraces obtained with netconsole from 2.6.32
> and 2.6.37:
[…]

Thanks. To reply Faidon's question on IRC, I guess we might want to
either reassign that bug to the kernel (affecting the driver + the
server, to make sure it gets noticed) and/or to clone it for now,
until further investigation happens. Michel, any preference?

KiBi.

[signature.asc (application/pgp-signature, inline)]
[Message part 1 (text/plain, inline)]
On Fri, 2011-03-04 at 21:01 +0200, Faidon Liambotis wrote:
> severity 616301 critical
> thanks

No, not unless it will affect a large proportion of users.

> My system locks up whenever I click on a YouTube video link since
> yesterday. I can probably live without YouTube :), but in any case this
> shouldn't happen.
> 
> This isn't a singled out case nor in exotic, possibly faulty, hardware.
> It's on a standard 1½-year old Dell OptiPlex 780 desktop with a Radeon
> HD card (one of the standard configurations) and this is on a stock
> squeeze system.
> 
> The findings so far seem to suggest this is a Mesa issue; I'd probably
> file it under "Linux kernel bugs" (or even DoS bugs) but I'm not sure
> where to properly file such bugs in the post-KMS stack world.

If there is a kernel driver involved then it should be assigned to the
kernel.  Even without KMS, a Mesa driver should be considered untrusted
and should not be able to trigger a crash or hang.  With KMS, this
applies to the X driver too.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[signature.asc (application/pgp-signature, inline)]
Hi,

Same thing here ... with basically same constellation in terms of
packages and update timing.

For info:

Work around on Youtube: Disable HW accel in flashplayer (Right-click /
Settings on some none-crashing flashplayer instance (some other
web-site) using iceweasel e.g.).

So it might be maybe radeon, video HW accel related ... !?

G+, Oliver

[Message part 1 (text/plain, inline)]
Hi there.

W dniu 04.03.2011 22:44, Cyril Brulebois pisze:
> Hi,
>
> Herber Sylwester<slyher@oomkill.net>  (03/03/2011):
>> What I can tell from /var/log/apt/history.log
>> […]
>
> hmm, nothing seems related. Any chance you upgraded something in the
> kernel/X stack before that, and only restarted your X or rebooted
> lately?
>
> KiBi.

Mayby the upgrade was just a time related coincidence.
After the upgrade i did niether reboot the machine nor restart the X-server.
I remeber that 2nd I've watched few Youtube videos and it was fine.
Don't know if attaching history.log for february will do any good.
I did not do any manual enhancements to the system especially the kernel 
part.
Regards,
Herber Sylwester.

[history.log.1.gz (application/x-gzip, attachment)]
Hi there.
W dniu 04.03.2011 22:44, Cyril Brulebois pisze:
> Hi,
>
> Herber Sylwester<slyher@oomkill.net>  (03/03/2011):
>> What I can tell from /var/log/apt/history.log
>> […]
>
> hmm, nothing seems related. Any chance you upgraded something in the
> kernel/X stack before that, and only restarted your X or rebooted
> lately?
>
> KiBi.

Todays update:

Start-Date: 2011-03-05  16:03:36
Commandline: apt-get dist-upgrade
Install: libglib2.0-bin:i386 (2.28.1-1+b1, automatic), gcc-4.5-base:i386 
(4.5.2-4, automatic), libboost-program-options1.42.0:i386 (1.42.0-4, 
automatic), libsoundtouch0:i386 (1.5.0-4, automatic)
Upgrade: browser-plugin-gnash:i386 (0.8.8-9, 0.8.9~git20110220-1), 
libjna-java:i386 (3.2.4-2, 3.2.7-1), libstdc++6:i386 (4.4.5-12, 
4.5.2-4), libwildmidi1:i386 (0.2.3.2-2, 0.2.3.4-1), rpm2cpio:i386 
(4.8.1-6, 4.8.1-7), librpmbuild1:i386 (4.8.1-6, 4.8.1-7), libmpfr4:i386 
(3.0.0-2, 3.0.0-7), python-mako:i386 (0.3.6-1, 0.4.0-1), 
libportaudio2:i386 (19+svn20071022-3.2, 19+svn20101113-3), xsane:i386 
(0.997-2+b1, 0.998-1), mobile-broadband-provider-info:i386 (20101106-1, 
20110218-1), libk3b6:i386 (2.0.2-1, 2.0.2-1+b1), libglib2.0-dev:i386 
(2.24.2-1, 2.28.1-1+b1), libutempter0:i386 (1.1.5-3, 1.1.5-4), 
hplip-cups:i386 (3.10.6-2, 3.11.1-2), libx11-data:i386 (1.4.1-4, 
1.4.1-5), libgfortran3:i386 (4.4.5-12, 4.5.2-4), iputils-ping:i386 
(20100418-3, 20101006-1), hpijs:i386 (3.10.6-2, 3.11.1-2), hplip:i386 
(3.10.6-2, 3.11.1-2), libsqlite3-dev:i386 (3.7.4-2, 3.7.5-1), 
librpmio1:i386 (4.8.1-6, 4.8.1-7), librpm1:i386 (4.8.1-6, 4.8.1-7), 
rpm-common:i386 (4.8.1-6, 4.8.1-7), libgomp1:i386 (4.4.5-12, 4.5.2-4), 
libpcre3:i386 (8.02-1.1, 8.12-3), libx11-xcb1:i386 (1.4.1-4, 1.4.1-5), 
libsqlite3-0:i386 (3.7.4-2, 3.7.5-1), k3b:i386 (2.0.2-1, 2.0.2-1+b1), 
libgcc1:i386 (4.4.5-12, 4.5.2-4), konqueror-plugin-gnash:i386 (0.8.8-9, 
0.8.9~git20110220-1), libhpmud0:i386 (3.10.6-2, 3.11.1-2), w3m:i386 
(0.5.3-1, 0.5.3-2), mozilla-plugin-gnash:i386 (0.8.8-9, 
0.8.9~git20110220-1), python-pysqlite2:i386 (2.6.0-1, 2.6.3-1), 
libglib2.0-data:i386 (2.24.2-1, 2.28.1-1), libfreetype6-dev:i386 
(2.4.2-2.1, 2.4.4-1), xdg-utils:i386 (1.1.0~rc1-1, 1.1.0~rc1-2), 
rpm:i386 (4.8.1-6, 4.8.1-7), gstreamer0.10-plugins-bad:i386 
(0.10.19-2+b2, 0.10.19-2.1), libgcc1-dbg:i386 (4.4.5-12, 4.5.2-4), 
xsane-common:i386 (0.997-2, 0.998-1), libemail-mime-perl:i386 (1.906-1, 
1.907-1), libfreetype6:i386 (2.4.2-2.1, 2.4.4-1), gnash:i386 (0.8.8-9, 
0.8.9~git20110220-1), libglib2.0-0:i386 (2.24.2-1, 2.28.1-1+b1), 
libk3b6-extracodecs:i386 (2.0.2-1, 2.0.2-1+b1), libsane-hpaio:i386 
(3.10.6-2, 3.11.1-2), libx11-6:i386 (1.4.1-4, 1.4.1-5), 
pkg-kde-tools:i386 (0.9.3, 0.9.5), klash:i386 (0.8.8-9, 
0.8.9~git20110220-1), libx11-dev:i386 (1.4.1-4, 1.4.1-5), libobjc2:i386 
(4.4.5-12, 4.5.2-4), gnash-common:i386 (0.8.8-9, 0.8.9~git20110220-1), 
sqlite3:i386 (3.7.4-2, 3.7.5-1), binfmt-support:i386 (2.0.2, 2.0.3), 
eject:i386 (2.1.5+deb1+cvs20081104-7.1, 2.1.5+deb1+cvs20081104-8), 
libmms0:i386 (0.6.2-1, 0.6.2-2), hplip-data:i386 (3.10.6-2, 3.11.1-2)
End-Date: 2011-03-05  16:06:20

Did not help either.
I'm starting to think it may be caussed by hardware malfunction. (wild 
goose chase?)
I've noticed that system does not hang - I'm able to go to a console 
login and reboot. The screen ends 10cm below the monitor so i have to 
gues some things. If it would be helpful I may try to record the incident.
Sincerely,
Herber Sylwester.

On Fre, 2011-03-04 at 21:04 +0100, "Matthias Rühl" wrote: 
> > Datum: Fri, 04 Mar 2011 17:36:21 +0100
> > Von: "Michel Dänzer" <daenzer@debian.org>
> > An: Apollon Oikonomopoulos <apoikos@gmail.com>
> > CC: 616301-submitter@bugs.debian.org, "Matthias Rühl" <matthias.ruehl@gmx.de>
> > Betreff: Re: Bug#616301: xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]
> 
> > So far, so good. If you can try 7.10-2 (which was still shipping the
> > classic r600 driver, whereas 7.10-4 is shipping the Gallium based one)
> > or other versions in between as well, that would be interesting.
> 
> With packages 
> 
> libdrm-radeon1_2.4.23-2
> libgl1-mesa-dri_7.10-2
> libtalloc2_2.0.5-1
> 
> from http://snapshot.debian.org/archive/debian/20110210T084921Z/ 
> iceweasel sometimes freezes when viewing youtube videos but so far this 
> doesn't trigger gpu softresets.

Good news, it might be possible to isolate an upstream fix for the
classic r600 driver and backport it to squeeze then. Can you try doing
that with git bisect?

-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer

> Datum: Sun, 06 Mar 2011 11:57:13 +0100
> Von: "Michel Dänzer" <daenzer@debian.org>
> An: "\\"Matthias" Rühl" <matthias.ruehl@gmx.de>
> CC: 616301-submitter@bugs.debian.org
> Betreff: Re: Bug#616301: xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]
> 
> Good news, it might be possible to isolate an upstream fix for the
> classic r600 driver and backport it to squeeze then. Can you try doing
> that with git bisect?
> 
> 
> -- 
> Earthling Michel Dänzer           |                http://www.vmware.com
> Libre software enthusiast         |          Debian, X and DRI developer

I'll look into it tomorrow - then I hopefully find time to do it.

If someone else also wants to work on this simultaneously or needs a workaround for squeeze:
Simply updating to "libgl1-mesa-dri_7.8.1-2" from
http://snapshot.debian.org/package/mesa/7.8.1-2/#libgl1-mesa-dri_7.8.1-2
should fix the issue.

Kind regards,

Matthias
-- 
GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit 
gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

On Fri, Mar 4, 2011 at 8:50 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Fri, 2011-03-04 at 21:01 +0200, Faidon Liambotis wrote:
>> severity 616301 critical
>> thanks
>
> No, not unless it will affect a large proportion of users.
>
>> My system locks up whenever I click on a YouTube video link since
>> yesterday. I can probably live without YouTube :), but in any case this
>> shouldn't happen.
>>
>> This isn't a singled out case nor in exotic, possibly faulty, hardware.
>> It's on a standard 1½-year old Dell OptiPlex 780 desktop with a Radeon
>> HD card (one of the standard configurations) and this is on a stock
>> squeeze system.
>>
>> The findings so far seem to suggest this is a Mesa issue; I'd probably
>> file it under "Linux kernel bugs" (or even DoS bugs) but I'm not sure
>> where to properly file such bugs in the post-KMS stack world.
>
> If there is a kernel driver involved then it should be assigned to the
> kernel.  Even without KMS, a Mesa driver should be considered untrusted
> and should not be able to trigger a crash or hang.  With KMS, this
> applies to the X driver too.
>

With or without KMS, the userspace acceleration drivers can certainly
cause GPU hangs if the 3D engine is programmed with some combination
of commands it doesn't like.

Alex

> Ben.
>
> --
> Ben Hutchings
> Once a job is fouled up, anything done to improve it makes it worse.
>
> _______________________________________________
> xorg-driver-ati mailing list
> xorg-driver-ati@lists.x.org
> http://lists.x.org/mailman/listinfo/xorg-driver-ati
>
>

[Message part 1 (text/plain, inline)]
On Sun, 2011-03-06 at 13:08 -0500, Alex Deucher wrote:
> On Fri, Mar 4, 2011 at 8:50 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > On Fri, 2011-03-04 at 21:01 +0200, Faidon Liambotis wrote:
> >> severity 616301 critical
> >> thanks
> >
> > No, not unless it will affect a large proportion of users.
> >
> >> My system locks up whenever I click on a YouTube video link since
> >> yesterday. I can probably live without YouTube :), but in any case this
> >> shouldn't happen.
> >>
> >> This isn't a singled out case nor in exotic, possibly faulty, hardware.
> >> It's on a standard 1½-year old Dell OptiPlex 780 desktop with a Radeon
> >> HD card (one of the standard configurations) and this is on a stock
> >> squeeze system.
> >>
> >> The findings so far seem to suggest this is a Mesa issue; I'd probably
> >> file it under "Linux kernel bugs" (or even DoS bugs) but I'm not sure
> >> where to properly file such bugs in the post-KMS stack world.
> >
> > If there is a kernel driver involved then it should be assigned to the
> > kernel.  Even without KMS, a Mesa driver should be considered untrusted
> > and should not be able to trigger a crash or hang.  With KMS, this
> > applies to the X driver too.
> >
> 
> With or without KMS, the userspace acceleration drivers can certainly
> cause GPU hangs if the 3D engine is programmed with some combination
> of commands it doesn't like.

You can't solve the halting problem but you can implement a watchdog,
can't you?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[signature.asc (application/pgp-signature, inline)]
I haven't heard of many chips that won't hang given the wrong 
instructsion whether it's GPU or keyboard controller.  Sounds like more 
than a driver issue but a choice of driver issue.  How are you going to 
have it both ways without an ammount of care you have no time for?

having interrupting access / watchdog is nice if your driver can do that

Ben Hutchings wrote:
> On Sun, 2011-03-06 at 13:08 -0500, Alex Deucher wrote:
>> On Fri, Mar 4, 2011 at 8:50 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
>>> On Fri, 2011-03-04 at 21:01 +0200, Faidon Liambotis wrote:
>>>> severity 616301 critical
>>>> thanks
>>> No, not unless it will affect a large proportion of users.
>>>
>>>> My system locks up whenever I click on a YouTube video link since
>>>> yesterday. I can probably live without YouTube :), but in any case this
>>>> shouldn't happen.
>>>>
>>>> This isn't a singled out case nor in exotic, possibly faulty, hardware.
>>>> It's on a standard 1½-year old Dell OptiPlex 780 desktop with a Radeon
>>>> HD card (one of the standard configurations) and this is on a stock
>>>> squeeze system.
>>>>
>>>> The findings so far seem to suggest this is a Mesa issue; I'd probably
>>>> file it under "Linux kernel bugs" (or even DoS bugs) but I'm not sure
>>>> where to properly file such bugs in the post-KMS stack world.
>>> If there is a kernel driver involved then it should be assigned to the
>>> kernel.  Even without KMS, a Mesa driver should be considered untrusted
>>> and should not be able to trigger a crash or hang.  With KMS, this
>>> applies to the X driver too.
>>>
>> With or without KMS, the userspace acceleration drivers can certainly
>> cause GPU hangs if the 3D engine is programmed with some combination
>> of commands it doesn't like.
> 
> You can't solve the halting problem but you can implement a watchdog,
> can't you?
> 
> Ben.
> 

[Message part 1 (text/plain, inline)]
On Sun, 2011-03-06 at 19:49 -0500, John D. Hendrickson and Sara Darnell
wrote:
> I haven't heard of many chips that won't hang given the wrong 
> instructsion whether it's GPU or keyboard controller.

Of course.  This is why the kernel driver filters the commands going to
the GPU - the commands come from unprivileged applications (the Mesa
driver is just a shared library) and should not be trusted.

> Sounds like more 
> than a driver issue but a choice of driver issue.  How are you going to 
> have it both ways without an ammount of care you have no time for?
> 
> having interrupting access / watchdog is nice if your driver can do that
> 
> Ben Hutchings wrote:
[...]

Don't top-post.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[signature.asc (application/pgp-signature, inline)]
of course if you ask and have that command.  just ask I'm actually not 
planning on being in the channel long.  someone might find me!  he he.

Question.  can I ask what top-post is?  I will look it up too.  debian 
rules are getting rather long to even have heard about even having read 
a good part of them once.

Ben Hutchings wrote:
> On Sun, 2011-03-06 at 19:49 -0500, John D. Hendrickson and Sara Darnell
> wrote:
>> I haven't heard of many chips that won't hang given the wrong 
>> instructsion whether it's GPU or keyboard controller.
> 
> Of course.  This is why the kernel driver filters the commands going to
> the GPU - the commands come from unprivileged applications (the Mesa
> driver is just a shared library) and should not be trusted.
> 
>> Sounds like more 
>> than a driver issue but a choice of driver issue.  How are you going to 
>> have it both ways without an ammount of care you have no time for?
>>
>> having interrupting access / watchdog is nice if your driver can do that
>>
>> Ben Hutchings wrote:
> [...]
> 
> Don't top-post.
> 
> Ben.
> 

On Sun, Mar 6, 2011 at 1:36 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Sun, 2011-03-06 at 13:08 -0500, Alex Deucher wrote:
>> On Fri, Mar 4, 2011 at 8:50 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
>> > On Fri, 2011-03-04 at 21:01 +0200, Faidon Liambotis wrote:
>> >> severity 616301 critical
>> >> thanks
>> >
>> > No, not unless it will affect a large proportion of users.
>> >
>> >> My system locks up whenever I click on a YouTube video link since
>> >> yesterday. I can probably live without YouTube :), but in any case this
>> >> shouldn't happen.
>> >>
>> >> This isn't a singled out case nor in exotic, possibly faulty, hardware.
>> >> It's on a standard 1½-year old Dell OptiPlex 780 desktop with a Radeon
>> >> HD card (one of the standard configurations) and this is on a stock
>> >> squeeze system.
>> >>
>> >> The findings so far seem to suggest this is a Mesa issue; I'd probably
>> >> file it under "Linux kernel bugs" (or even DoS bugs) but I'm not sure
>> >> where to properly file such bugs in the post-KMS stack world.
>> >
>> > If there is a kernel driver involved then it should be assigned to the
>> > kernel.  Even without KMS, a Mesa driver should be considered untrusted
>> > and should not be able to trigger a crash or hang.  With KMS, this
>> > applies to the X driver too.
>> >
>>
>> With or without KMS, the userspace acceleration drivers can certainly
>> cause GPU hangs if the 3D engine is programmed with some combination
>> of commands it doesn't like.
>
> You can't solve the halting problem but you can implement a watchdog,
> can't you?

We have lockup detection and asic reset support, but depending on the
lockup it may or may not be able to successfully reset the asic.
Also, as for the command buffer checking, we try to protect against
basic stupidity, but the chips are just too complex to check for every
possible scenario that might cause a hang.

Alex

>
> Ben.
>
> --
> Ben Hutchings
> Once a job is fouled up, anything done to improve it makes it worse.
>

On Mon, Mar 7, 2011 at 4:36 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Sun, 2011-03-06 at 13:08 -0500, Alex Deucher wrote:
>> On Fri, Mar 4, 2011 at 8:50 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
>> > On Fri, 2011-03-04 at 21:01 +0200, Faidon Liambotis wrote:
>> >> severity 616301 critical
>> >> thanks
>> >
>> > No, not unless it will affect a large proportion of users.
>> >
>> >> My system locks up whenever I click on a YouTube video link since
>> >> yesterday. I can probably live without YouTube :), but in any case this
>> >> shouldn't happen.
>> >>
>> >> This isn't a singled out case nor in exotic, possibly faulty, hardware.
>> >> It's on a standard 1½-year old Dell OptiPlex 780 desktop with a Radeon
>> >> HD card (one of the standard configurations) and this is on a stock
>> >> squeeze system.
>> >>
>> >> The findings so far seem to suggest this is a Mesa issue; I'd probably
>> >> file it under "Linux kernel bugs" (or even DoS bugs) but I'm not sure
>> >> where to properly file such bugs in the post-KMS stack world.
>> >
>> > If there is a kernel driver involved then it should be assigned to the
>> > kernel.  Even without KMS, a Mesa driver should be considered untrusted
>> > and should not be able to trigger a crash or hang.  With KMS, this
>> > applies to the X driver too.
>> >
>>
>> With or without KMS, the userspace acceleration drivers can certainly
>> cause GPU hangs if the 3D engine is programmed with some combination
>> of commands it doesn't like.
>
> You can't solve the halting problem but you can implement a watchdog,
> can't you?
>

We do, we reset the GPU 10s after it hangs, but this depends on a lot
of things going our way.

Occasionally we do reset the GPU when we shouldn't as well.

However if there is an issue in the kernel, ddx or mesa driver,
constants resets will pretty much DoS the GPU.

Dave.

On Sam, 2011-03-05 at 16:23 +0100, Herber Sylwester wrote: 
> 
> I'm starting to think it may be caussed by hardware malfunction.

No, it seems clear at this point that it's a youtube change triggering a
pre-existing bug in the Mesa r600 driver.

> I've noticed that system does not hang - I'm able to go to a console 
> login and reboot. The screen ends 10cm below the monitor so i have to 
> gues some things. If it would be helpful I may try to record the incident.

Might be nice for the sake of completeness, though most likely it'll
just be generic symptoms from GPU lockups, which unfortunately don't say
much about what triggered them. The most promising approach at this
point seems bisecting which Mesa upstream change fixed the problem.

-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer

On 14:18 Sun 06 Mar     , "Matthias Rühl" wrote:
> I'll look into it tomorrow - then I hopefully find time to do it.
> 
> If someone else also wants to work on this simultaneously or needs a workaround for squeeze:
> Simply updating to "libgl1-mesa-dri_7.8.1-2" from
> http://snapshot.debian.org/package/mesa/7.8.1-2/#libgl1-mesa-dri_7.8.1-2
> should fix the issue.
> 
> Kind regards,
> 
> 
> Matthias
> -- 
> GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit 
> gratis Handy-Flat! http://portal.gmx.net/de/go/dsl
> 
> 
> 

Hi, 

I've been trying to bisect upstream between mesa_7_7_1 and mesa-7.8, 
without any success. A large part of the commit tree for r600 between 
7.7.1 and 7.8 FTBFS with any debian libdrm-dev version I tried since 
2.4.15-1, stating:

  In file included from radeon_common.h:4,
                   from radeon_screen.c:49:
  radeon_common_context.h:405: error: array type has incomplete element type

I've searched around a bit and this seems to be due to some libdrm API 
changes.

This is taking too much time, I can't do this remotely since I have to 
be able to reboot the machine and furthermore, this is my work machine.  
Unless someone can provide some advice regarding the build process, I'll 
have to give up :(.

Regards,
Apollon

On Die, 2011-03-08 at 20:06 +0200, Apollon Oikonomopoulos wrote: 
> 
> I've been trying to bisect upstream between mesa_7_7_1 and mesa-7.8, 
> without any success. A large part of the commit tree for r600 between 
> 7.7.1 and 7.8 FTBFS with any debian libdrm-dev version I tried since 
> 2.4.15-1, stating:
> 
>   In file included from radeon_common.h:4,
>                    from radeon_screen.c:49:
>   radeon_common_context.h:405: error: array type has incomplete element type
> 
> I've searched around a bit and this seems to be due to some libdrm API 
> changes.

Can you provide a specific mesa commit hash where this happens?

-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer

On 13:39 Wed 09 Mar     , Michel Dänzer wrote:
> On Die, 2011-03-08 at 20:06 +0200, Apollon Oikonomopoulos wrote: 
> > 
> > I've been trying to bisect upstream between mesa_7_7_1 and mesa-7.8, 
> > without any success. A large part of the commit tree for r600 between 
> > 7.7.1 and 7.8 FTBFS with any debian libdrm-dev version I tried since 
> > 2.4.15-1, stating:
> > 
> >   In file included from radeon_common.h:4,
> >                    from radeon_screen.c:49:
> >   radeon_common_context.h:405: error: array type has incomplete element type
> > 
> > I've searched around a bit and this seems to be due to some libdrm API 
> > changes.
> 
> Can you provide a specific mesa commit hash where this happens?

For example, a1b9c4e22a83d2125f66c3a3af3143bc0daee9a4 (2nd bisection 
step) and the whole area around it.

For the record, the following mesa commits seem to make r600 conform to 
the new API:

$ git log --oneline origin/master | grep "new libdrm_radeon api"
bd9e0eb radeon/r600: use new libdrm_radeon api
9373287 radeon/r600: use new libdrm_radeon api
b065aec radeon/r600: use new libdrm_radeon api
(Basically the same commit on different branches)

however, they are not cleanly backportable to the affected commits I 
encountered.

Debian libdrm-dev versions prior to 2.4.18 do not ship 
/usr/include/drm/drm.h which is needed, and versions from 2.4.18 
(included) and onwards fail with the above message. Any hints as to the 
version of libdrm required to compile these revisions?

Thanks,
Apollon

On Mit, 2011-03-09 at 14:55 +0200, Apollon Oikonomopoulos wrote: 
> On 13:39 Wed 09 Mar     , Michel Dänzer wrote:
> > On Die, 2011-03-08 at 20:06 +0200, Apollon Oikonomopoulos wrote: 
> > > 
> > > I've been trying to bisect upstream between mesa_7_7_1 and mesa-7.8, 
> > > without any success. A large part of the commit tree for r600 between 
> > > 7.7.1 and 7.8 FTBFS with any debian libdrm-dev version I tried since 
> > > 2.4.15-1, stating:
> > > 
> > >   In file included from radeon_common.h:4,
> > >                    from radeon_screen.c:49:
> > >   radeon_common_context.h:405: error: array type has incomplete element type
> > > 
> > > I've searched around a bit and this seems to be due to some libdrm API 
> > > changes.
> > 
> > Can you provide a specific mesa commit hash where this happens?
> 
> For example, a1b9c4e22a83d2125f66c3a3af3143bc0daee9a4 (2nd bisection 
> step) and the whole area around it.
> 
> For the record, the following mesa commits seem to make r600 conform to 
> the new API:
> 
> $ git log --oneline origin/master | grep "new libdrm_radeon api"
> bd9e0eb radeon/r600: use new libdrm_radeon api
> 9373287 radeon/r600: use new libdrm_radeon api
> b065aec radeon/r600: use new libdrm_radeon api
> (Basically the same commit on different branches)
> 
> however, they are not cleanly backportable to the affected commits I 
> encountered.
> 
> Debian libdrm-dev versions prior to 2.4.18 do not ship 
> /usr/include/drm/drm.h which is needed, and versions from 2.4.18 
> (included) and onwards fail with the above message. Any hints as to the 
> version of libdrm required to compile these revisions?

You could try an older version of libdrm-dev with /usr/include/drm/drm.h
manually copied from a newer version. It should be backwards compatible.

-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer

[Message part 1 (text/plain, inline)]
> Datum: Tue, 8 Mar 2011 20:06:13 +0200
> Von: Apollon Oikonomopoulos <apollon@noc.grnet.gr>
> An: "Matthias Rühl" <matthias.ruehl@gmx.de>
> CC: "Michel Dänzer" <daenzer@debian.org>, 616301-submitter@bugs.debian.org
> Betreff: Re: Bug#616301: xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]
> 
> Hi, 
> 
> I've been trying to bisect upstream between mesa_7_7_1 and mesa-7.8, 
> without any success. A large part of the commit tree for r600 between 
> 7.7.1 and 7.8 FTBFS with any debian libdrm-dev version I tried since 
> 2.4.15-1, stating:
> 
>   In file included from radeon_common.h:4,
>                    from radeon_screen.c:49:
>   radeon_common_context.h:405: error: array type has incomplete element
> type
> 
> I've searched around a bit and this seems to be due to some libdrm API 
> changes.
> 
> This is taking too much time, I can't do this remotely since I have to 
> be able to reboot the machine and furthermore, this is my work machine.  
> Unless someone can provide some advice regarding the build process, I'll 
> have to give up :(.
> 
> Regards,
> Apollon

Hi,

I've encountered the same problem. :/
Seems like we need libdrm-dev 2.4.16 or some other version before that.

But I also tested libgl1-mesa-dri 7.6.1 from snapshot.debian.org which
works with current youtube videos and doesn't even crash Adobe Flash
player and Iceweasel when opening more than one such tab (unlike
libgl1-mesa-dri >= 7.8), so I'll try to bisect from that point to 7.7 too.
Apparently this gpu softreset issue is specific to the mesa 7.7
development line.

I attached my git-bisect logs for reference.
(git://git.debian.org/git/pkg-xorg/lib/mesa)

By the way:
The 'proper fix' in commit 5997501ca0d0c905025bc2a840e48e2176d64ea3
has only been partly applied to mesa-7.7.1 ... that seems odd.

Kind regards,

Matthias
-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

[bisect_dri_7.8.1-2_vs_7.7.1-2.log (application/octet-stream, attachment)]
[bisect_mesa_7.8.1-2_vs_7.7.1-2.log (application/octet-stream, attachment)]
[bisect_mesa_7.7-4_vs_7.6.1-1.log (application/octet-stream, attachment)]
On Sun, Mar 06, 2011 at 01:08:49PM -0500, Alex Deucher wrote:
> On Fri, Mar 4, 2011 at 8:50 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > On Fri, 2011-03-04 at 21:01 +0200, Faidon Liambotis wrote:
> >> This isn't a singled out case nor in exotic, possibly faulty, hardware.
> >> It's on a standard 1½-year old Dell OptiPlex 780 desktop with a Radeon
> >> HD card (one of the standard configurations) and this is on a stock
> >> squeeze system.
> >>
> >> The findings so far seem to suggest this is a Mesa issue; I'd probably
> >> file it under "Linux kernel bugs" (or even DoS bugs) but I'm not sure
> >> where to properly file such bugs in the post-KMS stack world.
> >
> > If there is a kernel driver involved then it should be assigned to the
> > kernel.  Even without KMS, a Mesa driver should be considered untrusted
> > and should not be able to trigger a crash or hang.  With KMS, this
> > applies to the X driver too.
> >
> 
> With or without KMS, the userspace acceleration drivers can certainly
> cause GPU hangs if the 3D engine is programmed with some combination
> of commands it doesn't like.

Note that the bug in question causes a *kernel* lockup, not just a GPU
hang. As indicated by the output in the bug log¹, we're getting a “BUG:
unable to handle kernel paging request” after a GPU reset on 2.6.37,
while a silent lockup on 2.6.32.

Regards,
Faidon

¹: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616301#30

Debian Bug report logs - #616301 xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]

Debian Bug report logs - #616301
xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]