[Bug 381162] [NEW] KDM crashes after resume from suspend (S3)
Murz
murznn at gmail.com
Thu May 28 04:00:09 UTC 2009
Public bug reported:
I have using Kubuntu Jaunty AMD64 on ASUS M3N78-EM (NVIDIA GeForce 8300 chipset) with internal video and NVIDIA Driver Version 180.44. KDM version is 4:4.2.2-0ubuntu2.
At default, it each time didn't resume nomally after S3 suspend, because it didn't start HDD after resume. I have added "pci=nomsi" parameter to kernel, after this it goes to suspend with hands and wakes up normally: after resume I see my locked KDE session with all loaded programs.
My computer go to S3 suspend after 15 minuts of inactivity.
But 7 of 10 times after automatic suspend and resume I see clear KDM login screen instead of suspended active KDE session!
At this time in /var/log/kdm.log I see:
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66]
1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61]
2: /lib/libc.so.6 [0x7f0f70b36040]
3: /usr/bin/X [0x4b77f7]
4: /usr/bin/X [0x4b7b95]
5: /usr/bin/X(xf86Wakeup+0x46d) [0x48629d]
6: /usr/bin/X(WakeupHandler+0x4b) [0x451e6b]
7: /usr/bin/X(WaitForSomething+0x1ef) [0x4ef5ef]
8: /usr/bin/X(Dispatch+0x80) [0x44e020]
9: /usr/bin/X(main+0x3bd) [0x433d8d]
10: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f0f70b215a6]
11: /usr/bin/X [0x433219]
Saw signal 11. Server aborting.
ddxSigGiveUp: Closing log
ddxSigGiveUp: re-raising 11
X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-15-server x86_64 Ubuntu
Current Operating System: Linux kit 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64
Build Date: 09 April 2009 02:11:54AM
xorg-server 2:1.6.0-0ubuntu14 (buildd at crested.buildd)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
.....
.....
.....
What additional info I can give for describing and solving this problem?
** Affects: kdebase-workspace (Ubuntu)
Importance: Undecided
Status: New
** Tags: kdm resume suspend
** Description changed:
- I have using Kubuntu Jaunty AMD64 on ASUS M3N78-EM (NVIDIA GeForce 8300 chipset) with internal video and NVIDIA Driver Version 180.44.
+ I have using Kubuntu Jaunty AMD64 on ASUS M3N78-EM (NVIDIA GeForce 8300 chipset) with internal video and NVIDIA Driver Version 180.44. KDM version is 4:4.2.2-0ubuntu2.
At default, it each time didn't resume nomally after S3 suspend, because it didn't start HDD after resume. I have added "pci=nomsi" parameter to kernel, after this it goes to suspend with hands and wakes up normally: after resume I see my locked KDE session with all loaded programs.
My computer go to S3 suspend after 15 minuts of inactivity.
But 7 of 10 times after automatic suspend and resume I see clear KDM login screen instead of suspended active KDE session!
At this time in /var/log/kdm.log I see:
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66]
1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61]
2: /lib/libc.so.6 [0x7f0f70b36040]
3: /usr/bin/X [0x4b77f7]
4: /usr/bin/X [0x4b7b95]
5: /usr/bin/X(xf86Wakeup+0x46d) [0x48629d]
6: /usr/bin/X(WakeupHandler+0x4b) [0x451e6b]
7: /usr/bin/X(WaitForSomething+0x1ef) [0x4ef5ef]
8: /usr/bin/X(Dispatch+0x80) [0x44e020]
9: /usr/bin/X(main+0x3bd) [0x433d8d]
10: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f0f70b215a6]
11: /usr/bin/X [0x433219]
Saw signal 11. Server aborting.
ddxSigGiveUp: Closing log
ddxSigGiveUp: re-raising 11
X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-15-server x86_64 Ubuntu
Current Operating System: Linux kit 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64
Build Date: 09 April 2009 02:11:54AM
xorg-server 2:1.6.0-0ubuntu14 (buildd at crested.buildd)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
.....
.....
.....
What additional info I can give for describing and solving this problem?
** Tags added: kdm resume suspend
--
KDM crashes after resume from suspend (S3)
https://bugs.launchpad.net/bugs/381162
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
More information about the kubuntu-bugs
mailing list