Bugzilla – Bug 496954
linux next: kernel does not enter S3 (s2ram)
Last modified: 2009-05-23 10:38:41 UTC
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE If I install kernel-default-2.6.28-34.1 from http://download.opensuse.org/repositories/Kernel:/linux-next/openSUSE_11.1/ my machine will refuse to enter S3 featuring the text mode console still being shown. Besides this the repo linux-next repo does not work; one needs to dld the packages by hand. Reproducible: Always
Created attachment 287216 [details] pm-suspend.log
I've just updated the master branch to 2.6.30-rc6-git3. Can you see if you can reproduce with a kernel from http://ftp.suse.com/pub/projects/kernel/kotd/master/ ?
S2ram works quite well with kernel-2.6.30-rc5-git1-master_20090515173431_9c6d4c14-default although waking the machine up again will now require a couple of close-lid hints instead of normal keypresses which it does not respond upon (at the first wakeup the notebook screen addtionally stayed dimmed down). For me s2ram has worked best with vmlinux-2.6.29.2-rt10-1-rt although Appparmor does not work with vmlinux-rt. Besides this the resuspend-bug after resume from s2ram occurs on all kernel flavours (also 2.6.27).
Created attachment 293259 [details] errors on installing kernel-default-2.6.30 There occur still a lot of errors when installing kernel-default-2.6.30.
Those errors are annoying, but aren't as bad as they seem. See bug #491959 for more information.
Unfortunately I am not authorized to see bug #491959? Would you mind granting me acess to view it? - or if you cann`t tell me whom I may ask?
Ok, I've opened that bug up.
What about the many other warnings (unknown symbol, no dependencies for kernel module xx found.) when installing kernel-default and kernel-default-extra? Please notify me if they are gone and it is safe to use kernel-2.6.30 with OpenSuse11.1 (f.i. only headphones, no front speaker work).
Those are because we've included those modules into the main "vmlinuz" image instead of having them as separate modules. If you were install an earlier kernel again, you would still need those modules listed in your $INITRD_MODULES. So you can see how this isn't an easy problem to solve. The 2.6.30-rc6-git3 kernel _does_ work in general. I have it running on several of my machines. There may be driver issues, but since we haven't shipped it in a released product, we're only looking to fix bugs in the openSUSE-specific code that we add onto the vanilla kernel. Until we have an official release using a specific kernel version, the appropriate place to report and fix bugs is upstream. The most common test cycle for anything newer than a released product is to test it again with kernel-vanilla. If it's still broken, then it's an openSUSE bug. If it's not, then the bug is upstream and a report needs to be filed at bugzilla.kernel.org.
Isn`t there any method of extracting a list of 'in-compiled' modules fromout of a ready-to-use kernel image? Will there be any official linux-next release for OpenSuse11.1 in order to fix bug Bug 465039, marked as critical? i.e. if it is not broken in kernel-vanilla then it is an openSUSE bug.
marking as resolved: kernel 2.6.30 s2rams well.