Dear Maintainer,

version 6.14.4-1 does crash on startup. going back to 6.14.3-2 (which has
been done to make this report) did make my computer start again.

here is the backtrace from Xorg.o.log:

[  1300.808] (II) XINPUT: Adding extended input device "AT Translated Set 2
keyboard" (type: KEYBOARD, id 9)
[  1300.808] (**) Option "xkb_rules" "evdev"
[  1300.808] (**) Option "xkb_model" "pc105"
[  1300.808] (**) Option "xkb_layout" "de"
[  1300.808] (**) Option "xkb_options" "lv3:ralt_switch"
[  1300.808] (II) config/udev: Adding input device PC Speaker
(/dev/input/event4)
[  1300.808] (II) No input driver specified, ignoring this device.
[  1300.808] (II) This device may have been added with another device file.
[  1304.252]
Backtrace:
[  1304.252] 0: /usr/bin/X (xorg_backtrace+0x37) [0xb76d0cc7]
[  1304.252] 1: /usr/bin/X (0xb754c000+0x1887ba) [0xb76d47ba]
[  1304.252] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb752e40c]
[  1304.252] 3: /usr/lib/xorg/modules/drivers/radeon_drv.so
(0xb6eab000+0xb51f2) [0xb6f601f2]
[  1304.252] 4: /usr/lib/xorg/modules/drivers/radeon_drv.so
(0xb6eab000+0xab91f) [0xb6f5691f]
[  1304.252] 5: /usr/lib/xorg/modules/drivers/radeon_drv.so
(0xb6eab000+0xae537) [0xb6f59537]
[  1304.252] 6: /usr/lib/xorg/modules/libexa.so (0xb6cf5000+0x9cfb)
[0xb6cfecfb]
[  1304.252] 7: /usr/lib/xorg/modules/libexa.so (0xb6cf5000+0xa05c)
[0xb6cff05c]
[  1304.252] 8: /usr/bin/X (miCopyRegion+0x17c) [0xb76ad1fc]
[  1304.252] 9: /usr/bin/X (miDoCopy+0x428) [0xb76ad758]
[  1304.252] 10: /usr/lib/xorg/modules/libexa.so (0xb6cf5000+0x825a)
[0xb6cfd25a]
[  1304.252] 11: /usr/bin/X (0xb754c000+0x10f552) [0xb765b552]
[  1304.252] 12: /usr/bin/X (0xb754c000+0x370a3) [0xb75830a3]
[  1304.252] 13: /usr/bin/X (0xb754c000+0x3b6a5) [0xb75876a5]
[  1304.252] 14: /usr/bin/X (0xb754c000+0x2926a) [0xb757526a]
[  1304.252] 15: /lib/i386-linux-gnu/i686/cmov/libc.so.6
(__libc_start_main+0xe6) [0xb71dae46]
[  1304.252] 16: /usr/bin/X (0xb754c000+0x295a9) [0xb75755a9]
[  1304.253] Segmentation fault at address 0x89
[  1304.253]
Fatal server error:
[  1304.253] Caught signal 11 (Segmentation fault). Server aborting
[  1304.253]
[  1304.253]
Please consult the The X.Org Foundation support
	 at http://wiki.x.org
 for help.
[  1304.253] Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
[  1304.253]
[  1304.268] (II) evdev: Power Button: Close
[  1304.268] (II) UnloadModule: "evdev"
[  1304.268] (II) Unloading evdev

Hi Elmar,

Elmar Haneke <elmar@haneke.de> (04/04/2012):

Bonus points if:
 - you can get us a full backtrace. Some hints available at:
http://x.debian.net/howto/use-gdb.html (even though the one for
   gdm3 won't work anymore).
 - you can forward this upstream at bugs.freedesktop.org and let us
   know about the URL for tracking.
 - you can tell us why you're disable KMS (in modprobe's config).

Mraw,
KiBi.

Switching on KMS did make the problem vanish.

https://bugs.freedesktop.org/show_bug.cgi?id=48326

I did that in 2010, presumably due to an error message regarding KMS.

I just encountered the same bug yesterday. I was running a custom kernel
that did not have KMS enabled, and the radeon driver (6.14.4-1) crashes
with a segfault upon startup (regardless of the KMS setting in modprobe,
so it's not the setting but the KMS itself that made the difference).
Downgrading to 6.14.3-2 resolves the problem.

Today, I rebuilt the kernel with KMS enabled, and now 6.14.4-1 works
without any problem.


T

Hi

I am using a standard Debian kernel (linux-image-3.2.0-4-686-pae) but
apparently no KMS, I suppose my graphics card (Mobility Radeon HD 3200)
does not support it.

I also ran into this bug on my last upgrade. I could solve it by manually
downgrading xorg and some related packages using http://snapshot.debian.org/

Here's are the packages and versions that I used:

xserver-xorg-core		1.11.4-1
xserver-xorg-input-evdev	2.6.0-3+b1
xserver-xorg-input-synaptics	1.5.0-2
xserver-xorg-video-ati		6.14.3-2
xserver-xorg-video-mach64	6.9.0-1+b1
xserver-xorg-video-r128		6.8.0-2
xserver-xorg-video-radeon	6.14.3-2

(xserver-xorg-video-radeon might be enough, if you use a
xorg.conf-snipplet and not the auto detection.)

After downgrading the packages should, for now, be set on hold.

Kind regards,
Meike

Not sure why it wouldn't, please provide your dmesg output.

Yups I had done the same by downgrading and setting then in hold.

Jiun Shyong
在 2012-11-9 下午4:15，"Meike Reichle" <meike@debian.org>写道：

Michel Dänzer @ 09/11/12 10:03:

I've attached it to this mail.

Regards,
Meike

Hmm, thanks, but it doesn't show why KMS is disabled. Is it disabled
in /etc/modprobe.d/radeon-kms.conf?

If that still doesn't explain it, can you try passing radeon.modeset=1
on the kernel command line and see if that enables it?

Michel Dänzer @ 09/11/12 15:32:

It seems to be already enabled there:

mre@jet:~$ cat /etc/modprobe.d/radeon-kms.conf
options radeon modeset=1
mre@jet:~$

That did the trick. With that command line I got KMS. I've attached the
dmesg from that boot. I guess the question now it why it isn't enabled by
/etc/modprobe.d/radeon-kms.conf ...

Regards,
Meike

Indeed... The only explanations I can think of:

      * /etc/modprobe.d/radeon-kms.conf says modeset=0 in the initrd.
        'sudo update-initramfs -k $(uname -r) -u' should fix it in this
        case.
      * There's another configuration file on your system that says
        modeset=0.

Michel Dänzer @ 23/11/12 17:36:

update-initramfs fixed it. After that I could also re-upgrade the packages
I had put on hold (see earlier mail for the list and versions).

Thank you very much for helping me out on this!

Kind regards,
Meike