[Bug 309077] New: Thinkpad R61 on s2ram whitelist with wrong/harmful fixes
https://bugzilla.novell.com/show_bug.cgi?id=309077 Summary: Thinkpad R61 on s2ram whitelist with wrong/harmful fixes Product: openSUSE 10.3 Version: Beta 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: behlert@novell.com ReportedBy: suse@bugs.jan.ritzerfeld.net QAContact: qa@suse.de Found By: Beta-Customer s2ram on 10.3 Beta 3 says "Fixes: 0x3 S3_BIOS S3_MODE". But this will prevent resume on my Thinkpad R61 using the (latest) NVidia driver. After suspend-to-ram from X, on resume, the screen gets garbled and the machine freezes. Suspend-to-ram from a tty yields to a black screen on resume. This is the output of "s2ram -n" from 10.2, as the machine was not on the whitelist: Machine is unknown. This machine can be identified by: sys_vendor = "LENOVO" sys_product = "89196VG" sys_version = "ThinkPad R61" bios_version = "7KET57WW (1.07 )" See http://en.opensuse.org/S2ram for details. Resuming works after "s2ram -f -a 2" from X on 10.3 Beta 3. However, there is the known rendering slowdown until X is restarted. -- 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=309077#c1 Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse@bugs.jan.ritzerfeld.net --- Comment #1 from Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> 2007-09-09 14:14:46 MST --- "s2ram -f -a 2" works well even if issued from a tty (more correctly, a virtual console) while X is running. Switching back to X works, too. -- 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=309077 Christian Zoz <zoz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zoz@novell.com AssignedTo|behlert@novell.com |seife@novell.com -- 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=309077#c2 --- Comment #2 from Stefan Seyfried <seife@novell.com> 2007-09-10 03:31:24 MST --- Which combination does work well, if you are not using the proprietary NVidia driver? -- 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=309077 Christian Zoz <zoz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |suse@bugs.jan.ritzerfeld.net -- 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=309077#c3 --- Comment #3 from Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> 2007-09-10 10:03:28 MST --- Some additional information (just booted 10.2, will test w/o NVidia driver later): 1. It seems like I am not using the latest BIOS. When using version 1.14 (not the latest, too) the fixes in s2ram of Beta 3 should work in general. But then, s2ram will not work from X. However, this was tested with 10.2 and an older Factory kernel. See http://www.mail-archive.com/suspend-devel@lists.sourceforge.net/msg02890.htm... 2. The rendering slowdown mentioned in my description is known as Bug 290385. 3. Output of "s2ram -n" on 10 Beta 3: Machine matched entry 226: sys_vendor = 'LENOVO' sys_product = '8919*' sys_version = '' bios_version = '' Fixes: 0x3 S3_BIOS S3_MODE This machine can be identified by: sys_vendor = "LENOVO" sys_product = "89196VG" sys_version = "ThinkPad R61" bios_version = "7KET57WW (1.07 )" -- 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=309077#c4 --- Comment #4 from Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> 2007-09-10 13:19:39 MST ---
From a minimal environment the following combination all result in a black virtual console (but backlight is on and I can reboot): s2ram -f -a 1 s2ram -f -a 2 s2ram -f -a 3 s2ram -f -p -m s2ram -f -p -s
I will try the remaining ones on the next 10.3 Beta 3 boot. -- 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=309077#c5 --- Comment #5 from Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> 2007-09-11 11:40:02 MST --- Again, some additional information: A simple "s2ram -f" without any options works from X. Sorry that I did not test the simplest options first. -- 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=309077#c6 Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|suse@bugs.jan.ritzerfeld.net | --- Comment #6 from Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> 2007-09-11 13:35:23 MST --- Minimal environment (init=/bin/bash, ...). On resume, * black virtual console and backlight on: s2ram -f -m -a 1 s2ram -f -s -a 1 * black virtual console and backlight off: s2ram -f -m s2ram -f -s s2ram -f -p Again, reboot did work after every test. -- 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=309077#c7 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #7 from Stefan Seyfried <seife@novell.com> 2007-09-13 03:41:23 MST --- (In reply to comment #5 from Jan Ritzerfeld)
Again, some additional information: A simple "s2ram -f" without any options works from X. Sorry that I did not test the simplest options first.
But this works only with the NVidia driver, right? We are really having problems whitelisting such a machine, where the workarounds seem to be even driver-version-dependent :-( -- 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=309077#c8 Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |suse@bugs.jan.ritzerfeld.net --- Comment #8 from Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> 2007-09-14 11:30:59 MST --- For me, with the old BIOS, yes. Didn't you get the email from the author of the article on the suspend-devel mailing list mentioned in Comment #3? He updated his BIOS to 1.14, uses openSUSE 10.2 but factory kernel 2.6.22.5-10 and factory pm-utils. There, * s2ram -f, -f -a 2, -f -a 3 DO work within a minimal environment, * s2ram -f, -f -a 2 DO work within a minimal environment AND NVidia X, and * s2ram -f -a 3 does NOT work within NVidia X. Thus, the current whitelist entry that forces -a 3 is useless in general and harmful in case of X and the NVidia driver. But I hope that I will have time to update my BIOS soon and check whether this is true for a real 10.3 installation. -- 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=309077#c9 --- Comment #9 from Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> 2007-09-28 15:54:09 MST --- I updated my BIOS. Unfortunately it did not change anything with 10.3 Beta 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=309077#c10 Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|suse@bugs.jan.ritzerfeld.net | --- Comment #10 from Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> 2007-10-03 11:36:02 MST --- This gets annoying. Not only that the success of s2ram depends on running NVidia X or not but also it is important whether the virtual consoles are using a frambuffer. s2ram -f: + works from NVidia X without framebuffer (vga=normal) - does not work from NVidia X with framebuffer (vga=0x31...) - does not work from minimal system s2ram -f -a 2: + works from NVidia X without framebuffer (vga=normal) + works from NVidia X with framebuffer (vga=0x31...) - does not work from minimal system s2ram (without options, i.e., using the whitelist fix -a 3): - does not work from NVidia X with framebuffer (vga=0x31...) - does not work from NVidia X without framebuffer (vga=normal) - does not work from minimal systen without framebuffer (vga=normal) + works from minimal system with framebuffer (vga=0x31...) -- 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=309077#c11 --- Comment #11 from Stefan Seyfried <seife@novell.com> 2007-11-27 06:49:13 MST --- We got the info from Lenovo that using no workaround (just plain "-f") should work on this machine with the NVidia driver, even with framebuffer. If this also does not work for you, i have no idea what to do here... -- 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=309077#c12 --- Comment #12 from Jan Ritzerfeld <suse@bugs.jan.ritzerfeld.net> 2007-12-03 11:29:48 MST --- My initial report was about s2ram using "Fixes: 0x3 S3_BIOS S3_MODE" aka "-a 3". To the best of my knowledge, this breaks at least two machines. If Lenovo says that no fixes are needed, s2ram should just not use any fixes. X-) -- 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=309077 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=309077#c13 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED Target Milestone|--- |Future/Later --- Comment #13 from Stefan Seyfried <seife@novell.com> 2008-09-19 07:57:05 MDT --- Well, but they only support that machine with the NVidia driver... Anyway, this will change in 11.1, so that if the nvidia driver is loaded, we will just do plain "s2ram -f", if it isn't, we will use the fixes from s2ram's whitelist. Until then, just use S2RAM_OPTS="-f" in /etc/pm/config.d/supend-opts "Resolved FIXED" in this case means "Fixed in 11.1". -- 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.
participants (1)
-
bugzilla_noreply＠novell.com