Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
timrichardsonOffline
Post subject: kdm crashing when I interact with the screen saver dialog  PostPosted: 05.03.2011, 04:19



Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline
kdm crashes intermittently but too often when I interact with the screen saver dialog. The crash causes data loss since the kde session dies.
I have kdm set to restart x on a log out, but since I'm getting kdm segfaults guess this is not relevant.

This has been happening for about two weeks (definitely after squeeze release).
This happens sometimes when resuming from suspend or hibernate, but just now I got a crash simply by clicking "cancel" on the unlock dialog twice. (suspend/resume was not involved). This happens both with an external monitor attached or not It's intermittent; I guess I'm seeing it about once a day, but I don'tknow how to reproduce it at will yet. .

I've hesitated reporting this because I find bugs in this area of the system hard to report. I honestly don't know if it's a kdm bug, an xserver bug or a kernel bug. I do see a segfault in the kdm log. I reported it to debian, but if the developer suspects its related to the kernel, I won't get any support (not a debian kernel).

I'd appreciate some ideas to help debug this. It's the most serious problem I've had since using sidux/aptosid.

_________________
There are some who call me Tim
 
 View user's profile Send private message Visit poster's website Yahoo Messenger  
Reply with quote Back to top
timrichardsonOffline
Post subject: RE: kdm crashing when I interact with the screen saver dialo  PostPosted: 05.03.2011, 04:26



Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline
kdm.log

      Code:

Region for name 6 already exists but is not compatible

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80adddb]
1: /usr/bin/X (0x8048000+0x59a65) [0x80a1a65]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb78df40c]
3: /usr/lib/dri/i965_dri.so (0xb6e74000+0x545f7) [0xb6ec85f7]
4: /usr/lib/dri/i965_dri.so (0xb6e74000+0x43e58) [0xb6eb7e58]
5: /usr/lib/dri/i965_dri.so (0xb6e74000+0x12a2fc) [0xb6f9e2fc]
6: /usr/lib/dri/i965_dri.so (0xb6e74000+0x1277d7) [0xb6f9b7d7]
7: /usr/lib/dri/i965_dri.so (0xb6e74000+0x127818) [0xb6f9b818]
8: /usr/lib/dri/i965_dri.so (0xb6e74000+0x203f71) [0xb7077f71]
9: /usr/lib/xorg/modules/extensions/libglx.so (0xb7458000+0x8411) [0xb7460411]
10: /usr/lib/xorg/modules/extensions/libglx.so (0xb7458000+0x32274) [0xb748a274]
11: /usr/lib/xorg/modules/extensions/libglx.so (0xb7458000+0x36c42) [0xb748ec42]
12: /usr/bin/X (0x8048000+0x2bfb7) [0x8073fb7]
13: /usr/bin/X (0x8048000+0x1e63a) [0x806663a]
14: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0xb75edc76]
15: /usr/bin/X (0x8048000+0x1e211) [0x8066211]
Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting


Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.


X.Org X Server 1.9.4
Release Date: 2011-02-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32.29-dsa-ia32 i686 Debian
Current Operating System: Linux newton 2.6.37-2.slh.4-aptosid-686 #1 SMP PREEMPT Fri Mar 4 01:02:34 UTC 2011 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.37-2.slh.4-aptosid-686 root=UUID=7a26f8f4-37e1-4ac0-bafa-2fbe3e1fd78f ro quiet elevator=cfq
Build Date: 20 February 2011  05:47:22AM
xorg-server 2:1.9.4-3 (Cyril Brulebois <kibi>)
Current version of pixman: 0.21.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: Sat Mar  5 14:53:24 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
FATAL: Module fbcon not found.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(EE) Query no Synaptics: 6003C8
(EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware.
(EE) PreInit returned NULL for "SynPS/2 Synaptics TouchPad"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error:            Meta_R added to symbol map for multiple modifiers
>                   Using Mod4, ignoring Mod1.
> Error:            Meta_L added to symbol map for multiple modifiers
>                   Using Mod4, ignoring Mod1.
> Error:            Key <META> added to map for multiple modifiers
>                   Using Mod4, ignoring Mod1.
Errors from xkbcomp are not fatal to the X server
Region for name 3 already exists but is not compatible

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80adddb]
1: /usr/bin/X (0x8048000+0x59a65) [0x80a1a65]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb788540c]
3: /usr/lib/dri/i965_dri.so (0xb6e1a000+0x545f7) [0xb6e6e5f7]
4: /usr/lib/dri/i965_dri.so (0xb6e1a000+0x43e58) [0xb6e5de58]
5: /usr/lib/dri/i965_dri.so (0xb6e1a000+0x12a2fc) [0xb6f442fc]
6: /usr/lib/dri/i965_dri.so (0xb6e1a000+0x1277d7) [0xb6f417d7]
7: /usr/lib/dri/i965_dri.so (0xb6e1a000+0x127818) [0xb6f41818]
8: /usr/lib/dri/i965_dri.so (0xb6e1a000+0x203f71) [0xb701df71]
9: /usr/lib/xorg/modules/extensions/libglx.so (0xb73fe000+0x8411) [0xb7406411]
10: /usr/lib/xorg/modules/extensions/libglx.so (0xb73fe000+0x32274) [0xb7430274]
11: /usr/lib/xorg/modules/extensions/libglx.so (0xb73fe000+0x36c42) [0xb7434c42]
12: /usr/bin/X (0x8048000+0x2bfb7) [0x8073fb7]
13: /usr/bin/X (0x8048000+0x1e63a) [0x806663a]
14: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0xb7593c76]
15: /usr/bin/X (0x8048000+0x1e211) [0x8066211]
Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting


Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.


X.Org X Server 1.9.4
Release Date: 2011-02-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32.29-dsa-ia32 i686 Debian
Current Operating System: Linux newton 2.6.37-2.slh.4-aptosid-686 #1 SMP PREEMPT Fri Mar 4 01:02:34 UTC 2011 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.37-2.slh.4-aptosid-686 root=UUID=7a26f8f4-37e1-4ac0-bafa-2fbe3e1fd78f ro quiet elevator=cfq
Build Date: 20 February 2011  05:47:22AM
xorg-server 2:1.9.4-3 (Cyril Brulebois <kibi>)
Current version of pixman: 0.21.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: Sat Mar  5 15:19:19 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
FATAL: Module fbcon not found.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(EE) Query no Synaptics: 6003C8
(EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware.
(EE) PreInit returned NULL for "SynPS/2 Synaptics TouchPad"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error:            Meta_R added to symbol map for multiple modifiers
>                   Using Mod4, ignoring Mod1.
> Error:            Meta_L added to symbol map for multiple modifiers
>                   Using Mod4, ignoring Mod1.
> Error:            Key <META> added to map for multiple modifiers
>                   Using Mod4, ignoring Mod1.
Errors from xkbcomp are not fatal to the X server

_________________
There are some who call me Tim
 
 View user's profile Send private message Visit poster's website Yahoo Messenger  
Reply with quote Back to top
redsidOffline
Post subject:   PostPosted: 05.03.2011, 16:45



Joined: 2011-02-08
Posts: 32
Location: Lake Otsego
Status: Offline
Well, if the developer thinks it's a kernel problem, why don't you use another kernel for awhile. You can have as many kernels as you wish and pick the one to use on bootup. I would never, ever, rely on one kernel. I don't use suspend, hibernate or screensaver so no experience there but their actions do seem related.
 
 View user's profile Send private message  
Reply with quote Back to top
DeepDayzeOffline
Post subject:   PostPosted: 05.03.2011, 17:26



Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline
Why not put up your system info so someone can help you with this. From the xorg log you are using the Intel driver, so there may be a bug the Intel driver triggers. Why not start from there and file a bug report on the Intel driver?
 
 View user's profile Send private message  
Reply with quote Back to top
Ilinsekt
Post subject:   PostPosted: 05.03.2011, 22:17



Joined: 2010-10-29
Posts: 43

      Quote:

15: /usr/bin/X (0x8048000+0x1e211) [0x8066211]
Segmentation fault at address (nil)


I'm not an expert on this, but the above suggests there is a NULL pointer somewhere. Since the last printout is from /usr/bin/X, I would start there.
 
 View user's profile Send private message  
Reply with quote Back to top
DeepDayzeOffline
Post subject:   PostPosted: 05.03.2011, 22:46



Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline
      Ilinsekt wrote:
      Quote:

15: /usr/bin/X (0x8048000+0x1e211) [0x8066211]
Segmentation fault at address (nil)


I'm not an expert on this, but the above suggests there is a NULL pointer somewhere. Since the last printout is from /usr/bin/X, I would start there.


That could be a logical place but it could be the driver itself that could be the actual culprit though as X probably got a bad pointer from the driver
 
 View user's profile Send private message  
Reply with quote Back to top
timrichardsonOffline
Post subject:   PostPosted: 06.03.2011, 05:51



Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline
If it was a driver problem, odd that an application-level action (responding to a dialog or presenting a dialog) causes the problem ...
Is there a standard way to summarise system info?
I'm running 32 bit aptosid on a toshiba laptop, usually dual screen.
Mobile GM965/GL960 Integrated Graphics Controller

_________________
There are some who call me Tim
 
 View user's profile Send private message Visit poster's website Yahoo Messenger  
Reply with quote Back to top
timrichardsonOffline
Post subject:   PostPosted: 07.03.2011, 04:39



Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline
Based on one other report of similar problems on OpenSuse, it may well be a Intel driver problem triggered by OpenGL screen savers. I don't really know what that means but I've turned off random screensaver and I'm only using the ascii fish screensaver (which I think is 110% awesome anyway), guessing that is not an OpenGL screensaver.

_________________
There are some who call me Tim
 
 View user's profile Send private message Visit poster's website Yahoo Messenger  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio