Bug 305629

Summary:	NetworkManager causes Suspend2Disk to fail
Product:	[openSUSE] openSUSE 10.3	Reporter:	Forgotten User Drfk9mafMw <forgotten_Drfk9mafMw>
Component:	Mobile Devices	Assignee:	Holger Macht <hmacht>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	sndirsch
Version:	Beta 2
Target Milestone:	---
Hardware:	i686
OS:	openSUSE 10.3
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	/var/log/kdm.log /var/log/messages /var/log/NetworkManager /var/log/pm-suspend.log /var/log/warn /var/log/Xorg.0.log output of lspci tar.gz of the /var/log folder

Description Forgotten User Drfk9mafMw 2007-08-28 21:18:43 UTC

Hello,

when I use the traditional networking methods with ifup I can use Suspend2Disk with no problem. 5 suspend-resume cycles are no problem, more I have not yet tried. 

With the NetworkManager method I can use S2D *only* when I have freshly booted and not yet logged on to any user. As soon as I log in, I can -- at best -- suspend and resume once. Usually X crashed after the second time upon resume and sometimes even the suspend fails (black screen and the laptop is dead). It is impossible to switch to a terminal then (and since the network is down, too, also no ssh-access is possible).

S2D has worked flawless in the Alpha version so this seems as some kind of regression. I have reported this very behavior for openSUSE 10.2 already, unfortunately no one could/wanted to track it down.

I am experiencing this on an Intel Centrino laptop with i810 graphics chipset. In order to help you to my best I will attach all kinds of error logs that do sound reasonable to me, along with the output of lspci.

Comment 1 Forgotten User Drfk9mafMw 2007-08-28 21:19:26 UTC

Created attachment 160493 [details]
/var/log/kdm.log

Comment 2 Forgotten User Drfk9mafMw 2007-08-28 21:19:46 UTC

Created attachment 160494 [details]
/var/log/messages

Comment 3 Forgotten User Drfk9mafMw 2007-08-28 21:20:04 UTC

Created attachment 160495 [details]
/var/log/NetworkManager

Comment 4 Forgotten User Drfk9mafMw 2007-08-28 21:20:25 UTC

Created attachment 160496 [details]
/var/log/pm-suspend.log

Comment 5 Forgotten User Drfk9mafMw 2007-08-28 21:20:46 UTC

Created attachment 160497 [details]
/var/log/warn

Comment 6 Forgotten User Drfk9mafMw 2007-08-28 21:21:11 UTC

Created attachment 160498 [details]
/var/log/Xorg.0.log

Comment 7 Forgotten User Drfk9mafMw 2007-08-28 21:21:45 UTC

Created attachment 160499 [details]
output of lspci

Comment 8 Holger Macht 2007-08-29 11:13:02 UTC

Please do

$ chmod -x /usr/lib/pm-utils/sleep.d/10NetworkManager

and try again. Has NetworkManager already connected to a network when trying to suspend to disk?

Comment 9 Forgotten User Drfk9mafMw 2007-08-29 11:24:42 UTC

Thank you for the quick response! I will try your suggestion this evening -- currently I am at work.

As far as I can tell it does not make any difference if NM is connected or not: in both cases it breaks S2D.

Comment 10 Forgotten User Drfk9mafMw 2007-08-29 18:33:59 UTC

Hello, I have tried it, but it did not help at all. And what's worse: I found that I can not even log out now without killing my machine:

Reboot -> Login -> Logout => Black screen of death

So this might be the explanation for the behavior that I am experiencing: X hangs the machine when that new suspend splash is about to come up because something weird happens?!

I will attach a tar.gz of /var/log, maybe that helps. Could this trouble be related to the problems with the i855 graphics chipset described in on of the Most Annoying Bugs for 10.3-dev? I am running on 800x600 because sax2 fails and RandR complains, too...

Comment 11 Forgotten User Drfk9mafMw 2007-08-29 18:35:23 UTC

Created attachment 160795 [details]
tar.gz of the /var/log folder

Comment 12 Holger Macht 2007-08-29 19:24:11 UTC

(In reply to comment #10 from Daniel Mader)
> Hello, I have tried it, but it did not help at all. And what's worse: I found
> that I can not even log out now without killing my machine:

Always? Or only after a suspend to disk?

> So this might be the explanation for the behavior that I am experiencing: X
> hangs the machine when that new suspend splash is about to come up because
> something weird happens?!

Does it work without the new splash? (set 'splash = no' in /etc/suspend.conf)

Comment 13 Stefan Dirsch 2007-08-29 19:54:47 UTC

Another duplicate ...

Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x2ffe0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 7f000275
LP ring tail: 1648 head: d68 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: c1 instpm: 0
memmode: 108 instps: 33
hwstam: ffff ier: a2 imr: 9 iir: 0
Ring at virtual 0xafa3a000 head 0xd68 tail 0x1648 count 568
	00000ce8: 44480800
	00000cec: 00000000
	00000cf0: 3f000000
	00000cf4: 3f800000
	00000cf8: ff343d0b
	00000cfc: 3f777777
	00000d00: 3f777777
	00000d04: 3e000000
	00000d08: 44160000
	00000d0c: 3f000000
	00000d10: 3f800000
	00000d14: ff5a6a13
	00000d18: 3d088889
	00000d1c: 3d088889
	00000d20: 44480800
	00000d24: 44160000
	00000d28: 3f000000
	00000d2c: 3f800000
	00000d30: ff4b5810
	00000d34: 3f777777
	00000d38: 3d088889
	00000d3c: 44480800
	00000d40: 00000000
	00000d44: 3f000000
	00000d48: 3f800000
	00000d4c: ff343d0b
	00000d50: 3f777777
	00000d54: 3f777777
	00000d58: 3e000000
	00000d5c: 00000000
	00000d60: 3f000000
	00000d64: 3f800000
	00000d68: ff343d0b
Ring end
space: 128792 wanted 131064
(II) intel(0): [drm] removed 1 reserved context for kernel
(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xefc2d000 at 0xb7bbd000

Fatal server error:
lockup

Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x2ffe0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 7f000275
LP ring tail: 1650 head: d68 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: c1 instpm: 0
memmode: 108 instps: 33
hwstam: ffff ier: 0 imr: ffff iir: 0
Ring at virtual 0xafa3a000 head 0xd68 tail 0x1650 count 570
	00000ce8: 44480800
	00000cec: 00000000
	00000cf0: 3f000000
	00000cf4: 3f800000
	00000cf8: ff343d0b
	00000cfc: 3f777777
	00000d00: 3f777777
	00000d04: 3e000000
	00000d08: 44160000
	00000d0c: 3f000000
	00000d10: 3f800000
	00000d14: ff5a6a13
	00000d18: 3d088889
	00000d1c: 3d088889
	00000d20: 44480800
	00000d24: 44160000
	00000d28: 3f000000
	00000d2c: 3f800000
	00000d30: ff4b5810
	00000d34: 3f777777
	00000d38: 3d088889
	00000d3c: 44480800
	00000d40: 00000000
	00000d44: 3f000000
	00000d48: 3f800000
	00000d4c: ff343d0b
	00000d50: 3f777777
	00000d54: 3f777777
	00000d58: 3e000000
	00000d5c: 00000000
	00000d60: 3f000000
	00000d64: 3f800000
	00000d68: ff343d0b
Ring end
space: 128784 wanted 131064

FatalError re-entered, aborting
lockup

Comment 14 Stefan Dirsch 2007-08-29 19:55:26 UTC


*** This bug has been marked as a duplicate of bug 159962 ***