ProgVal <progval@gmail.com> (02/10/2010): > Hi back Hi again :) > > Can you please attach X log of the crash, as well as dmesg? > > Backtrace: > 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a1f88] > 1: /usr/bin/X (0x400000+0x64a99) [0x464a99] > 2: /lib/libpthread.so.0 (0x7f67ec62c000+0xef60) [0x7f67ec63af60] > 3: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f67e914a000+0x9ce4) > [0x7f67e9153ce4] > 4: /usr/bin/X (0x400000+0x12dbd0) [0x52dbd0] > 5: /usr/lib/xorg/modules/extensions/libextmod.so (0x7f67ea220000+0x134bd) > [0x7f67ea2334bd] > 6: /usr/bin/X (0x400000+0x31594) [0x431594] > 7: /usr/bin/X (0x400000+0x25bca) [0x425bca] > 8: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f67eb130c4d] > 9: /usr/bin/X (0x400000+0x25779) [0x425779] > Segmentation fault at address 0x7f67e5b96000 > > Fatal server error: > Caught signal 11 (Segmentation fault). Server aborting OK, good, “just” a segfault. Is there any chance to install debugging packages (xserver-xorg-core-dbg and xserver-xorg-video-nouveau-dbg), and to run X inside gdb, so as to get a full backtrace? If that makes things easier for you, you can get a core dump first, and then get the full backtrace out of it, post-mortem. > > > Kernel: Linux 2.6.32-progval3 (SMP w/2 CPU cores) > > > > Not sure which one it is, but Debian's 2.6.32 includes many > > DRM-related fixes from later kerrnel versions, which should > > improve the “graphics experience”. > > I am not sure I understand that, but I'll try to answer. I got the > sources using apt-get source ; I didn't edit anything out of the > menuconfig. Yeah, I failed to phrase my question properly. The idea was to determine whether you were running “just” a 2.6.32(.y) upstream release, or whether you had some patches on top of it. Since you're using Debian's source, that's alright, you should have DRM patches, which is good. (It might be nice to know which exact kernel version you fetched through apt-get source, though.) Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature