[Bug 299099] New: Suspend to Ram Fails with KPowersave
https://bugzilla.novell.com/show_bug.cgi?id=299099 Summary: Suspend to Ram Fails with KPowersave Product: openSUSE 10.3 Version: Beta 1 Platform: 32bit OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: behlert@novell.com ReportedBy: cddesjardins@gmail.com QAContact: qa@suse.de Found By: --- Hi I have a lenovo 3000 n100 and when I click 'suspend to ram' it fails with the following error very unhelpful error. An unknown error occurred while Suspend to RAM. The errorcode is: '127' My kernel is 2.6.22.1-16-default. This error does not occur on other distributions with the same kernel (Fedora, Debian, and Ubuntu). Cheers, Chris -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299099#c1
Christopher Stender
https://bugzilla.novell.com/show_bug.cgi?id=299099#c2
--- Comment #2 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099#c3
Christopher Stender
https://bugzilla.novell.com/show_bug.cgi?id=299099#c4
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=299099#c5
Holger Macht
https://bugzilla.novell.com/show_bug.cgi?id=299099#c6
--- Comment #6 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099#c7
--- Comment #7 from Holger Macht
Sun Aug 12 11:22:45 CDT 2007: done running suspend hooks. + /usr/sbin/s2ram Machine is unknown. This machine can be identified by: sys_vendor = "LENOVO" sys_product = "076804U" sys_version = "3000 N100 " bios_version = "63ET59WW" See http://en.opensuse.org/S2ram for details.
Please start reading at http://en.opensuse.org/S2ram#My_machine_is_not_in_the_whitelist.2C_what_can_... and check if any of the options listed there works for you. Please report back. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299099#c8
--- Comment #8 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=299099#c9
--- Comment #9 from Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=299099#c10
--- Comment #10 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099#c11
--- Comment #11 from Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=299099#c12
--- Comment #12 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099#c13
--- Comment #13 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099#c14
--- Comment #14 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099#c15
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=299099#c16
--- Comment #16 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099#c17
Felix Möller
I have tried removing the aforementioned modules but with no success (except acpi_cpufreq). Oddly s2ram -f works about 1/2 of the time and it says this when it's successful. What do you mean with "no success (except acpi_cpufreq)"?
Christopher: if you have lots of time you could try stop all modules from
loading that are loaded in normal operation but not with init=/bin/sh. You can
try to find the module preventing resume. To do that you should divide all
modules into two halves and see which prevents the system from resuming and do
that recursively. From my own experience and can just give you the hint to do a
real reboot for every try... :-(
To really prevent a module from loading you must enter "install
https://bugzilla.novell.com/show_bug.cgi?id=299099#c18
--- Comment #18 from Christopher Desjardins
What do you mean with "no success (except acpi_cpufreq)"?
I just meant that I couldn't try acpi_cpufreq because rmmod said that acpi_cpufreq was in use and could not be removed. I am a little confused about: lsmod | cut -f 1 -d " " | while read mod ; do echo "install $mod /bin/true"; done But I think if I am correct I could start a file called 'testsuspend' in /etc/modprobe.d/ and, for example, remove the module (let's say bcm43xx) by the following: install bcm43xx /bin/true Is that correct? Also I am a little confused at least regarding what you mean when you say split the modules in half. I am certainly willing to spend a little bit of time trying to track done this bug as I thoroughly enjoy opensuse and want to see it get better ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299099#c19
--- Comment #19 from Felix Möller
If I add the modules to /etc/modprobe.d/blacklist would that work as well? yes, that works too you just have to put lines like "install bcm43xx /bin/true " there. This executes nothing (/bin/true) instead of loading the module.
What do you mean with "no success (except acpi_cpufreq)"?
I just meant that I couldn't try acpi_cpufreq because rmmod said that acpi_cpufreq was in use and could not be removed. ok.
I am a little confused about: lsmod | cut -f 1 -d " " | while read mod ; do echo "install $mod /bin/true"; done This is just a little shell commandline that gives you a list of all loaded modules in a form you could put into your /etc/modprobe.d/-file.
But I think if I am correct I could start a file called 'testsuspend' in /etc/modprobe.d/ and, for example, remove the module (let's say bcm43xx) by the following:
install bcm43xx /bin/true yes, that is correct exactly.
Is that correct? Also I am a little confused at least regarding what you mean when you say split the modules in half. You can try to add all lines my command spits out into /etc/modprobe.d/testsuspend except those that are really required. So probably all except those that are loaded with init=/bin/sh is a good idea. After doing that your system should suspend after a normal boot. To get the graphical environment working again you might have to deblacklist i915 and drm, maybe something else. ;)
Deblacklisting is done by adding an "#" in front of the "install bcm43xx /bin/true"-line. If you have a "working" (boots and the GUI starts, certainly the network will not work as long as you blacklist the network drivers;) ) system again, you can start to search the module which prevents the system from suspending correctly. Start with putting an "#" in front of the first half of entries in /etc/modprobe.d/testsuspend. Now reboot. See if the system still suspends. - If yes, put a "#" in front of half of the entries of the half which does not begin with a "#" yet and reboot and suspend again. - If no, blacklist the other half and see again. I hope you see the "logic".
I am certainly willing to spend a little bit of time trying to track done this bug as I thoroughly enjoy opensuse and want to see it get better ;) great!
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299099#c20
--- Comment #20 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099#c21
--- Comment #21 from Felix Möller
I was able to successful suspend and recover by booting with init=/bin/bash by passing the following parameters to s2ram
s2ram -f -p -m s2ram -f -s s2ram -f -a 1 -s have you tried these? Otherwise I have have no idea, but it does not seem to be module related at all.
Does suspending work from runlevel 3 (i.e. "init 3")? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299099#c22
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=299099
User cddesjardins@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=299099#c23
--- Comment #23 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099
User felix@derklecks.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=299099#c24
--- Comment #24 from Felix Möller
https://bugzilla.novell.com/show_bug.cgi?id=299099
User cddesjardins@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=299099#c25
--- Comment #25 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099
User cddesjardins@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=299099#c26
--- Comment #26 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099
User cddesjardins@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=299099#c27
Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099
User felix@derklecks.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=299099#c28
Felix Möller
https://bugzilla.novell.com/show_bug.cgi?id=299099
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=299099#c29
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=299099
User cddesjardins@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=299099#c30
--- Comment #30 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=299099#c31
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=299099
User cddesjardins@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=299099#c32
--- Comment #32 from Christopher Desjardins
https://bugzilla.novell.com/show_bug.cgi?id=299099
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=299099#c33
Stefan Seyfried
participants (1)
-
bugzilla_noreply@novell.com