Bug#422008: xserver-xorg-core: running 'xvinfo' crashes the server
reassign 422008 xserver-xorg-video-v4l forcemerge 413640 422008 thank you Gabor Gombas wrote: > On Thu, May 03, 2007 at 12:03:47AM +0200, Brice Goglin wrote: > > >> I can't reproduce this here on a Radeon X300. Could you try with a >> simple xorg.conf (or even with no xorg.conf at all to use the default >> config)? You have lots of options in your current xorg.conf, it would be >> good to see if any of them causes the problem. >> > > Yep, those options accumulated over the years. However this was a good > tip: I started disabling them, and disabling the loading of the "v4l" > module made the segfault go away. > Ok, thanks, this has been reported as [1] and forwarded upstream at [2] with a workaround, but no reply so far. I'll ping them. Brice [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413640 [2] https://bugs.freedesktop.org/show_bug.cgi?id=10276 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#422008: xserver-xorg-core: running 'xvinfo' crashes the server
Processing commands for [EMAIL PROTECTED]: > reassign 422008 xserver-xorg-video-v4l Bug#422008: xserver-xorg-core: running 'xvinfo' crashes the server Bug reassigned from package `xserver-xorg-core' to `xserver-xorg-video-v4l'. > forcemerge 413640 422008 Bug#413640: xserver-xorg-video-v4l: xserver crashes when v4l module is loaded Bug#422008: xserver-xorg-core: running 'xvinfo' crashes the server Forcibly Merged 413640 422008. > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#422008: xserver-xorg-core: running 'xvinfo' crashes the server
On Thu, May 03, 2007 at 12:03:47AM +0200, Brice Goglin wrote: > I can't reproduce this here on a Radeon X300. Could you try with a > simple xorg.conf (or even with no xorg.conf at all to use the default > config)? You have lots of options in your current xorg.conf, it would be > good to see if any of them causes the problem. Yep, those options accumulated over the years. However this was a good tip: I started disabling them, and disabling the loading of the "v4l" module made the segfault go away. > This 6.6.99 could be the previous 6.6.3-5 which has been in experimental > about a month ago. It was a daily snapshot, probably less stable than > both 6.6.3 and 6.6.191. Yes it's 6.6.3-5; 6.6.191 is not available for amd64: xserver-xorg-video-ati: Installed: 1:6.6.3-5 Candidate: 1:6.6.3-5 Version table: *** 1:6.6.3-5 0 101 http://ftp.hu.debian.org experimental/main Packages 101 http://ftp.fi.debian.org experimental/main Packages 100 /home/gombasg/tmp/debian/x86_64/status 1:6.6.3-2 0 500 http://ftp.hu.debian.org etch/main Packages 500 http://ftp.fi.debian.org etch/main Packages 990 http://ftp.hu.debian.org sid/main Packages 990 http://ftp.fi.debian.org sid/main Packages Gabor -- - MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences, Laboratory of Parallel and Distributed Systems Address : H-1132 Budapest Victor Hugo u. 18-22. Hungary Phone/Fax : +36 1 329-78-64 (secretary) W3: http://www.lpds.sztaki.hu - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#422008: xserver-xorg-core: running 'xvinfo' crashes the server
Gabor Gombas wrote: > I wanted to try out Beryl but the X server always crashed. Now I found a > much simpler trigger: simply running 'xvinfo' reliably crashes the > server with the same backtrace as Beryl. Attached is the strace output > of xvinfo in case you may want to figure out what request did cause the > segfault. > I can't reproduce this here on a Radeon X300. Could you try with a simple xorg.conf (or even with no xorg.conf at all to use the default config)? You have lots of options in your current xorg.conf, it would be good to see if any of them causes the problem. > (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so > (II) Module ati: vendor="X.Org Foundation" > compiled for 7.2.0, module version = 6.6.99 > Module class: X.Org Video Driver > Which ATI driver is this? We currently have 6.6.3 in unstable and 6.6.191 in experimental. It would be good to try with these. This 6.6.99 could be the previous 6.6.3-5 which has been in experimental about a month ago. It was a daily snapshot, probably less stable than both 6.6.3 and 6.6.191. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]