[Bug 555821] New: Dell Inspiron 531 - Suspend to RAM regression (from OS-11.1)
http://bugzilla.novell.com/show_bug.cgi?id=555821 Summary: Dell Inspiron 531 - Suspend to RAM regression (from OS-11.1) Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: rob.opensuse.linux@googlemail.com QAContact: qa@suse.de Found By: --- Blocker: --- --- Comment #0 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-11-16 14:16:47 UTC --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.5) Gecko/20091103 SUSE/3.5.5-2.1 Firefox/3.5.5 Machine very similar config to this SLED certified one : http://developer.novell.com/yes/91887.htm Main differences from that spec, are fully up to date Dell BIOS 1.0.13, advised to install by Novell Engineer in past, when investigated CPUfreq Cool N' Quiet issues. ATI Radeon HD 4650 card which new in 2.6.31 has Kernel Mode Setting.NO binary grafix drivers installed, have clean 'taint free' system AFAIK. Suspend to RAM option from KDE executes something, but immediately returns without suspending. In OS-11.1 cleanly installed it Suspends as good as Windows does, and hibernates faster. Hibernation is working correctly in 11.2. Tried s2ram at commandline, discovered machine is unknown, but the same is true on 11.1, also "s2ram -f" fails 11.1 as well as 11.2 (suspends but doesn't resume from standby). Reproducible: Always Steps to Reproduce: 1.Obtain use of similar hardware 2.Install 11.1 KDE Desktop, Suspend to RAM works with & without Updates 3.Install 11.2 KDE Desktop, Suspend to RAM does not go into Standby Mode, returns immediatly Actual Results: 11.2 regresses the functionality of 11.1 Expected Results: 11.2 should Suspend to RAM just like 11.1. Whilst this is not a laptop, putting Desktop in Standby mode is great Green feature, and very convenient when taking a break, offering very fast resume to working. I have tried to append hwinfo for both 11.1 & 11.2 with Mozilla FF-3.5.5 (OBS) but attachments aren't attaching at moment for me :( -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821#c Robert Davies <rob.opensuse.linux@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com AssignedTo|kernel-maintainers@forge.pr |rjw@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c1 --- Comment #1 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-11-25 01:31:37 UTC --- Created an attachment (id=329354) --> (http://bugzilla.novell.com/attachment.cgi?id=329354) hwinfo output -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c2 --- Comment #2 from Rafael Wysocki <rjw@novell.com> 2009-11-25 20:54:05 UTC --- Does suspend/resume work from a framebuffer console (ie. at runlevel 3)? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c Rafael Wysocki <rjw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |rob.opensuse.linux@googlema | |il.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c3 Robert Davies <rob.opensuse.linux@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|rob.opensuse.linux@googlema | |il.com | --- Comment #3 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-11-26 10:16:49 UTC --- Not with "s2ram" I was going to try the options described in s2rams docs and work through those setting init=/bin/sh. I am not sure if there's a better way to do suspend & hibernate, as I haven't investigated what the menu's actually do. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c4 --- Comment #4 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-11-26 11:50:38 UTC --- The other reason I wasn't sure that s2ram was interesting, was because it didn't work in 11.1 either, whilst the KDM & KDE menu options do. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c5 Rafael Wysocki <rjw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |rob.opensuse.linux@googlema | |il.com --- Comment #5 from Rafael Wysocki <rjw@novell.com> 2009-11-26 20:29:59 UTC --- (In reply to comment #3)
Not with "s2ram" I was going to try the options described in s2rams docs and work through those setting init=/bin/sh. I am not sure if there's a better way to do suspend & hibernate, as I haven't investigated what the menu's actually do.
Basically, they execute 'powersave -u'. You can call it directly from the console (as root) to suspend using the same scripts. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c6 Robert Davies <rob.opensuse.linux@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|rob.opensuse.linux@googlema | |il.com | --- Comment #6 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-11-27 01:42:36 UTC --- On 11.2, this is what I noted down. # init 3 # sync && powersave -u resuming ... method return sender: 1.0 -> dest := 1.13 reply serial=2 int32 127 Like in menu, it returned immediately. On 11.1, the command Suspended to RAM # sync && powersave -u resuming ... method return sender: 1.0 -> dest := 1.12 reply serial=2 int32 0 Hope this is helpful. Thanks for your timely response. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c7 --- Comment #7 from Rafael Wysocki <rjw@novell.com> 2009-11-27 22:24:58 UTC --- Please attach /var/log/pm-suspend.log generated after a failing attempt to suspend. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c8 --- Comment #8 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-11-27 23:55:10 UTC --- Created an attachment (id=329861) --> (http://bugzilla.novell.com/attachment.cgi?id=329861) pm-suspend.log request. This is the log from the attempt made this morning described above. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c9 --- Comment #9 from Rafael Wysocki <rjw@novell.com> 2009-11-29 00:38:35 UTC --- Please try to set S2RAM_OPTS="-f" in /usr/lib/pm-utils/defaults and retest. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c10 --- Comment #10 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-11-29 13:20:52 UTC --- Created an attachment (id=329903) --> (http://bugzilla.novell.com/attachment.cgi?id=329903) Recent suspend log after setting "-f" option in pm-utils/defaults as requested. Things are starting to make some sense. Unsurprisingly the s2ram option "-f" did same as when I ran the command by hand at console. It "did not work" as expected with a resume from keyboard. But I found pushing power button once, actually was causing the machine to resume. However the video & keyboard remain inactive (dpms off, Magic SysRq didn't appear to work), logging in via ssh I find that the Xorg server is 100% in Sys, and signals had no effect. Am using RadeonHD with Xorg, not ATI "blob" video driver. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c11 --- Comment #11 from Rafael Wysocki <rjw@novell.com> 2009-11-29 20:06:12 UTC --- Does your keyboard is PS/2 or USB? Anyway, please test if suspend/resume works without X, ie. at runlevel 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c12 Robert Davies <rob.opensuse.linux@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #12 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-12-01 02:18:40 UTC --- Better news for you, real progress! :) Thank you for the work on the very nice feature! One observation, if the Docs on system had not been misleading then I would have proceeded with advice I found, and come with "works if you.." report. I found reference to deprecated powersave daemon for compatability, and with s2ram not showing anything useful with 11.1 (or seemingly working), I really did not know how things were supposed to work. I am now confused how it worked in 11.1, but perhaps there's a good reason. The advice to use init=/bin/bash results in a not over-professional error message about ninja system, due to /sys file for power state being missing. USB keyboard, I found from X numlock light would go on/off going back & forth to virtual console 1, then off with X after CNTRL-ALT-F7. Sometimes (depending on s2ram options) the keyboard would respond, sometimes the machine would be alive just temporarily headless until rebooted via net login. Now patching so, it seems to work on console & from X (-f -p -m): fir:/usr/lib/pm-utils # rcsdiff -c /usr/lib/pm-utils/defaults =================================================================== RCS file: /usr/lib/pm-utils/RCS/defaults,v retrieving revision 1.1 diff -c -r1.1 /usr/lib/pm-utils/defaults *** /usr/lib/pm-utils/defaults 2009/11/29 12:21:22 1.1 --- /usr/lib/pm-utils/defaults 2009/12/01 01:57:33 *************** *** 19,25 **** # what options should be passed to s2ram? # see http://en.opensuse.org/S2ram for more information # If this option is set, it overrides S2RAM_QUIRKS_SOURCE below ! S2RAM_OPTS="" # where should pm-utils get the s2ram quirks from? # s2ram - use the whitelist in s2ram, if the machine is known. --- 19,25 ---- # what options should be passed to s2ram? # see http://en.opensuse.org/S2ram for more information # If this option is set, it overrides S2RAM_QUIRKS_SOURCE below ! S2RAM_OPTS="-f -p -m" # where should pm-utils get the s2ram quirks from? # s2ram - use the whitelist in s2ram, if the machine is known. fir:/usr/lib/pm-utils # s2ram -n Machine unknown This machine can be identified by: sys_vendor = "Dell Inc." sys_product = "Inspiron 531" sys_version = "00" bios_version = "1.0.13" See http://en.opensuse.org/S2ram for details. If you report a problem, please include the complete output above. If you report success, please make sure you tested it from both X and the text console and preferably without proprietary drivers. So if this continues to work for me, I can test with 11.1 and send email to suspend-devel@lists.sourceforge.net following advice at http://en.opensuse.org/S2ram#How_to_contact_the_authors_of_s2ram.3F. I have possibility to re-flash BIOS and test with 1.0.3 DELL OEM BIOS, plus versions 1.0.{8,9,12} as well as current 1.0.13, if you really need that doing. Similarly I could make suggestions and submit patch to Docs I found misleading, if I know the effort will not be wasted and go down /dev/null. Please let me know if patch plus email submission, is sufficient to fix this for future releases, may be s2ram database can get updated? Then when you don't want any more testing, after a few days I'll confirm this as FIXED. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c13 --- Comment #13 from Rafael Wysocki <rjw@novell.com> 2009-12-02 00:00:09 UTC --- Thanks a lot for the information, no more testing is necessary. I'm going to update the s2ram database with your system's data, which is then going to be included in future openSUSE releases. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=555821 http://bugzilla.novell.com/show_bug.cgi?id=555821#c14 Robert Davies <rob.opensuse.linux@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #14 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-12-02 07:58:17 UTC --- Info on Other BIOS versions Dell Inspiron 531 BIOS page - http://support.euro.dell.com/support/downloads/previousversions.aspx?c=uk&cs=ukdhs1&l=en&s=dhs&SystemID=INSP_DSKTP_D531&releaseid=R210331&formatid=-1&deviceid=14246&formatcnt=1&dateid=-1&releasetype=BIOS&servicetag=&typeid=-1&catid=-1&libid=1&impid=-1&osl=en&vercnt=7&os=WLH Latest (& last) 1.0.13 support new CPU 1.0.12 - supported new CPU 1.0.11 - 1. fix the S3 resume balck screen issue for hynix memory CPU: AMD PRC,X2,4400+,2.3,1MB,2C,65W (Dell P/N: RU363) Memory: Hynix;512M;667;1R*16 (Dell P/N: HT212) 2. Support new 5600+ cpu 1.0.10 - Window XP Home Support 1.0.9 - 1: Add support for new processors 2: Improve USB subsystem operation 1.0.8 - cpu enhancement 1.0.7 .. 1.0.4 - had issues and were rapidly withdrawn 1.0.3 - .Update for latest AMD errata 2.Improved Utility Partition compatibility -- Configure bugmail: http://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