Kernel update broke wake from suspend, fixed time shift

[crmrhm]

I updated 11.1 to kernel 2.6.27.19-3.2pae with on-line update. It's running KDE 4.1.2 on a Thinkpad T23, dual boot with WinXP Pro.

Before the update, Fn+F4 on the laptop keyboard suspended to RAM. Pressing a key woke it to a login window, then into normal state. Now after the update, Fn+F4 still suspends correctly, but on waking, the display is some color streaks on the top quarter of the monitor screen. I have been unable to get anywhere from there, and have to hold the power button to force shutdown.

Any idea what I can adjust to get wake working?

On the plus side, I also had the clock time shift on reboot that has been discussed quite a bit in this forum. Now with the kernel update, that problem is gone.

Best regards,
Howard

[deano_ferrari]

Have a look at

/var/log/pm-suspend.log

This file may offer a clue about the problem. (Your graphics driver may require updating perhaps).

[crmrhm]

/var/log/pm-suspend.log is:

2009-03-01 09:43:07.838473839 +0900: running 'suspend'/'suspend'/'' hooks.
===== 2009-03-01 09:43:08.549801874 running hook: /usr/lib/pm-utils/sleep.d/00clear =====
===== 2009-03-01 09:43:08.676782294 running hook: /usr/lib/pm-utils/sleep.d/01logging =====
suspend initiated: Sun Mar 1 09:43:08 KST 2009

Linux linux-sd6h 2.6.27.19-3.2-pae #1 SMP 2009-02-25 15:40:44 +0100 i686 i686 i386 GNU/Linux
kernel command line: 'root=/dev/disk/by-id/ata-ST96812A_3PJ1TEJY-part5 resume=/dev/disk/by-id/ata-ST96812A_3PJ1TEJY-part10 splash=silent vga=0x314'
Module Size Used by
xt_tcpudp 2728 6
xt_pkttype 1560 3
ipt_LOG 5708 10
xt_limit 2056 10
af_packet 16412 2
binfmt_misc 7732 1
snd_pcm_oss 43040 0
snd_mixer_oss 14288 1 snd_pcm_oss
snd_seq 51916 0
snd_seq_device 7168 1 snd_seq
savage 28284 1
drm 74632 2 savage
xt_NOTRACK 1544 2
ipt_REJECT 2760 3
xt_state 1904 5
iptable_raw 2056 1
iptable_filter 2548 1
nf_conntrack_netbios_ns 2152 0
nf_conntrack_ipv4 10480 5
nf_conntrack 67400 4 xt_NOTRACK,xt_state,nf_conntrack_netbios_ns,nf_conntrack_ipv4
ip_tables 11348 2 iptable_raw,iptable_filter
ip6_tables 12580 0
x_tables 14500 9 xt_tcpudp,xt_pkttype,ipt_LOG,xt_limit,xt_NOTRACK,ipt_REJECT,xt_state,ip_tables,ip6_tables
microcode 12952 0
cpufreq_conservative 6476 0
cpufreq_userspace 3112 0
cpufreq_powersave 1640 0
speedstep_ich 3556 0
speedstep_lib 3884 1 speedstep_ich
nls_iso8859_1 3768 1
nls_cp437 5432 1
vfat 9676 1
fat 45792 1 vfat
fuse 50596 5
loop 14612 0
dm_mod 62540 0
ohci_hcd 30984 0
ohci1394 27664 0
ieee1394 83756 1 ohci1394
ehci_hcd 47420 0
pcmcia 32684 0
ppdev 6876 0
rtc_cmos 10896 0
rtc_core 17384 1 rtc_cmos
rtc_lib 2816 1 rtc_core
pcspkr 2344 0
battery 11176 0
ac 4480 0
video 20308 0
output 2736 1 video
parport_pc 34912 0
nsc_ircc 14988 0
parport 33128 2 ppdev,parport_pc
floppy 52764 0
irda 112392 1 nsc_ircc
crc_ccitt 1884 1 irda
yenta_socket 22884 3
e100 32212 0
mii 4968 1 e100
rsrc_nonstatic 10936 1 yenta_socket
snd_intel8x0 28352 6
pcmcia_core 33208 3 pcmcia,yenta_socket,rsrc_nonstatic
snd_ac97_codec 99756 1 snd_intel8x0
ac97_bus 1584 1 snd_ac97_codec
snd_pcm 76904 4 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 20204 3 snd_seq,snd_pcm
snd 56784 18 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
thermal 19984 1
button 6568 0
soundcore 6660 1 snd
processor 43656 2 thermal
snd_page_alloc 8184 2 snd_intel8x0,snd_pcm
i2c_i801 10500 0
i2c_core 29916 1 i2c_i801
sr_mod 13360 0
intel_agp 24780 1
cdrom 32288 1 sr_mod
shpchp 28308 0
iTCO_wdt 10016 0
pci_hotplug 27392 1 shpchp
agpgart 32308 2 drm,intel_agp
iTCO_vendor_support 3368 1 iTCO_wdt
sg 29408 0
usbhid 45596 0
hid 35568 1 usbhid
ff_memless 7132 1 usbhid
sd_mod 31604 9
crc_t10dif 1704 1 sd_mod
uhci_hcd 23080 0
usbcore 165932 5 ohci_hcd,ehci_hcd,usbhid,uhci_hcd
fan 4712 1
thermal_sys 11364 4 video,thermal,processor,fan
hwmon 2916 1 thermal_sys
edd 8616 0
ext3 123952 5
mbcache 7592 1 ext3
jbd 52872 1 ext3
ide_pci_generic 3428 0
piix 5868 0
ide_core 97492 2 ide_pci_generic,piix
ata_generic 4484 0
ata_piix 16460 8
libata 160776 2 ata_generic,ata_piix
scsi_mod 149336 4 sr_mod,sg,sd_mod,libata
dock 11804 1 libata

total used free shared buffers cached
Mem: 1021052 961648 59404 0 38228 465528
-/+ buffers/cache: 457892 563160
Swap: 2388920 0 2388920

===== 2009-03-01 09:43:08.934557586 running hook: /usr/lib/pm-utils/sleep.d/02rtcwake =====
rtcwake alarm not enabled in /etc/pm/config.d/rtcwake.config, doing nothing...
===== 2009-03-01 09:43:08.990671437 running hook: /usr/lib/pm-utils/sleep.d/05led =====
===== 2009-03-01 09:43:09.079420171 running hook: /usr/lib/pm-utils/sleep.d/06autofs =====
===== 2009-03-01 09:43:09.448283077 running hook: /usr/lib/pm-utils/sleep.d/10NetworkManager =====
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
===== 2009-03-01 09:43:09.719067568 running hook: /usr/lib/pm-utils/sleep.d/30s2disk-check =====
===== 2009-03-01 09:43:09.736089848 running hook: /usr/lib/pm-utils/sleep.d/45pcmcia =====
ejecting PCMCIA cards...
===== 2009-03-01 09:43:11.935223034 running hook: /usr/lib/pm-utils/sleep.d/50modules =====
===== 2009-03-01 09:43:11.985258736 running hook: /usr/lib/pm-utils/sleep.d/80acpi-fan =====
===== 2009-03-01 09:43:12.179268923 running hook: /usr/lib/pm-utils/sleep.d/80videobios =====
===== 2009-03-01 09:43:12.227110771 running hook: /usr/lib/pm-utils/sleep.d/94cpufreq =====
===== 2009-03-01 09:43:12.511452576 running hook: /usr/lib/pm-utils/sleep.d/95led =====
===== 2009-03-01 09:43:12.553389482 running hook: /usr/lib/pm-utils/sleep.d/95packagekit =====
===== 2009-03-01 09:43:12.602026123 running hook: /usr/lib/pm-utils/sleep.d/99Zgrub =====
===== 2009-03-01 09:43:12.668618405 running hook: /usr/lib/pm-utils/sleep.d/99info =====
2009-03-01 09:43:12.734606977: done running suspend/suspend hooks.
INFO: going to suspend. In case of problems with the selected suspend options,
INFO: please read /usr/share/doc/packages/pm-utils/README.smart-suspend-to-RAM
INFO: machine is in s2ram database, using it.
+ /usr/sbin/s2ram
Switching from vt7 to vt1
fbcon fb0 state 1
fbcon fb0 state 0
switching back to vt7
+ RET=0
+ set +x
2009-03-01 13:36:31.236536552 +0900: running 'suspend'/'resume'/'reverse' hooks.
===== 2009-03-01 13:36:31.617567208 running hook: /usr/lib/pm-utils/sleep.d/99info =====
===== 2009-03-01 13:36:31.649885291 running hook: /usr/lib/pm-utils/sleep.d/99Zgrub =====
===== 2009-03-01 13:36:31.685225267 running hook: /usr/lib/pm-utils/sleep.d/95packagekit =====
method return sender=:1.49 -> dest=:1.48 reply_serial=2
===== 2009-03-01 13:36:34.195557030 running hook: /usr/lib/pm-utils/sleep.d/95led =====
===== 2009-03-01 13:36:34.219470412 running hook: /usr/lib/pm-utils/sleep.d/94cpufreq =====
===== 2009-03-01 13:36:34.319773970 running hook: /usr/lib/pm-utils/sleep.d/80videobios =====
===== 2009-03-01 13:36:34.341825102 running hook: /usr/lib/pm-utils/sleep.d/80acpi-fan =====
===== 2009-03-01 13:36:34.372026435 running hook: /usr/lib/pm-utils/sleep.d/50modules =====
===== 2009-03-01 13:36:34.425378482 running hook: /usr/lib/pm-utils/sleep.d/45pcmcia =====
inserting PCMCIA cards...
===== 2009-03-01 13:36:34.594924659 running hook: /usr/lib/pm-utils/sleep.d/30s2disk-check =====
===== 2009-03-01 13:36:34.618739145 running hook: /usr/lib/pm-utils/sleep.d/10NetworkManager =====
method return sender=:1.7 -> dest=:1.51 reply_serial=2
===== 2009-03-01 13:36:34.779103426 running hook: /usr/lib/pm-utils/sleep.d/06autofs =====
===== 2009-03-01 13:36:34.845429752 running hook: /usr/lib/pm-utils/sleep.d/05led =====
===== 2009-03-01 13:36:34.877651454 running hook: /usr/lib/pm-utils/sleep.d/02rtcwake =====
===== 2009-03-01 13:36:34.909201003 running hook: /usr/lib/pm-utils/sleep.d/01logging =====
===== 2009-03-01 13:36:34.969014767 running hook: /usr/lib/pm-utils/sleep.d/00clear =====
2009-03-01 13:36:35.044238594: done running suspend/resume hooks.

Do you see a clue?
Thanks,
Howard

[deano_ferrari]

Nothing obvious there. After googling around, it does appear to be a known issue for this model (along with others)...

Have a look at this:

Problem with display remaining black after resume - ThinkWiki

You may also like to try adding

acpi=off

to the grub boot line in /boot/grub/menu.lst

Have a look here for more info concerning ACPI parameters.

Anyone else using similar hardware?

[crmrhm]

Thanks for the suggestions, but none helped yet. I tried all the options at ThinkWiki, but none of them got a resume. I booted with acpi=off and acpi=oldboot. The system hung on booting with acpi=off. With acpi=oldboot, suspend and resume behaved the same as a normal boot. On trying to resume, the system is doing something, because I can reboot it with the left Alt + SysRq + r s e i u b sequence.

Is there a Yast log of on-line updates so I can see what changes were recently made? The kernel update was combined with several others, but I cannot remember what they were. Suspend and resume worked correctly before that batch of updates, but not since.

Thanks,
Howard

[Magic31]

Hello Howard,

I don't think the kernel update is the cause here. I'm also having similar issues with suspend.. my laptop now hangs when trying to enter suspend by closing the lid or using the option in gnome-power manager.

Two questions for you:
1) are you using GNOME? or KDE? or Other?
2) Do you have an Intel chipset?

Suspend issues started here after applying the updates this week. I'm just looking at the /var/log/zypp/history to see which of the updates could be causing this... none of the updates seem to stick out as suspect.

As a workaround I'm currently running ' su -c s2ram ' from within a terminal console, which works fine.

I'll try reverting to the previous kernel to see if that helps, but I'd like to see if I can find the cause first. Will let you know how that goes..

Cheers,
Wj

[crmrhm]

Hi Wj / Magic31,
1) The system runs KDE 4.1.3
2) The T23 has an Intel chipset

Fn+F4 works to suspend, but the system does not resume correctly. I used 'su -c s2ram' from within a terminal console, which suspended OK, but resume still gave a screen with scattered colored bits, that could be fixed only by rebooting.

I looked at /var/log/zypp/history (Thanks for the pointer.) and noticed the line:
# insserv: Script jexec is broken: incomplete LSB comment.

I had some boot & shutdown trouble related to jexec, so it is disabled. The forum has discussion on this, seems related to java updates. I will try the fix that has been posted and re-enable jexec, and see what happens.

Please post what happens when you revert to the previous kernel. I considered that, but it would be new territory for me.
Thanks,
Howard

[Magic31]

Well... I was looking for an issue related to X, GNOME or other. My suspend lockup issue does however seem to be related to the new kernel as you suspected... downgrading fixed the lockup. Bummer as the new kernel does contain some other useful fixes!

Downgrading the kernel is not such a big deal in this case.. the packages are there, it's just a question of installing the version you want to have effective.
Open YaST > Software Management, look for packages starting with 'kernel-',, select to install/downgrade to the previous 2.6.27.7-9.1 version.

In my case I downgraded the 1) kernel-pae, 2) kernel-pae-base & 3) kernel-pae-extra packages to the initial versions found in the openSUSE-11.1-Oss (or use the 11.1 install media repo).

I also have kernel-source installed. Downgrading this package gave me an error about some link that could not be removed.. To remedy this I first removed the installed kernel-source package and then installed the older version. All is now well again.

Hope that helps...

If you have the time, it would be a good thing to open a bug report against your issue so the regression gets fixed.

Cheers!
Wj

[crmrhm]

Wj / Magic31,
I enabled jexec after confirming it was linked to the right folders, but that made no difference in resuming from suspend - it still will not.

I plan to go back to kernel 2.6.27.7-9.1. Thanks for the guidance on how to do that. I was really pleased that OpenSuSE 11.1 could correctly suspend and resume this T23, and I used it regularly.

Now to open a bug report.

Regards,
Howard

[crmrhm]

I switched back to kernel 2.6.27.7-9.1, and resuming works correctly again.
Regards,
Howard