[Bug 695758] New: Suspend-to-RAM/Resume doesn't work with 4GB of RAM (works only up to ~ 3 GB)
https://bugzilla.novell.com/show_bug.cgi?id=695758 https://bugzilla.novell.com/show_bug.cgi?id=695758#c0 Summary: Suspend-to-RAM/Resume doesn't work with 4GB of RAM (works only up to ~ 3 GB) Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: 32bit OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: oldrich.klimanek@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24 When using 4 GB of RAM, resuming from sleep doesn't work anymore. Works with 1 GB, 2 GB, 3 GB. (None of RAM modules is faulty.). Confirmed many times, even in different systems, such as Ubuntu. When booted kernel without PAE, and kernel sees only 3,3 GB of RAM, suspend-to-ram (s2ram) works. When PAE is enabled, and 4 GB of RAM is available, system won't resume. OpenSUSE 11.3 32bit, CPU AMD Turion 64 x2 TL-58, ATI Mobility Radeon HD 2400XT with fglrx (independent, the same results with radeon driver) [notebook Acer 5520G]. Additional information <a href="http://forums.opensuse.org/english/get-technical-help-here/hardware/460176-suspend-resume-doesnt-work-4-gb-ram-works-up-3-gb.html">here</a>. Dmesg output attached. Reproducible: Always Steps to Reproduce: 1. 2. 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=695758 https://bugzilla.novell.com/show_bug.cgi?id=695758#c1 --- Comment #1 from Oldrich Klimanek <oldrich.klimanek@gmail.com> 2011-05-24 17:27:42 UTC --- Created an attachment (id=431112) --> (http://bugzilla.novell.com/attachment.cgi?id=431112) Dmesg output -- 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=695758 https://bugzilla.novell.com/show_bug.cgi?id=695758#c2 --- Comment #2 from Oldrich Klimanek <oldrich.klimanek@gmail.com> 2011-05-24 18:51:22 UTC --- Created an attachment (id=431124) --> (http://bugzilla.novell.com/attachment.cgi?id=431124) Dmesg output for 4 GB RAM -- 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=695758 https://bugzilla.novell.com/show_bug.cgi?id=695758#c3 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jslaby@novell.com InfoProvider| |oldrich.klimanek@gmail.com --- Comment #3 from Jiri Slaby <jslaby@novell.com> 2011-05-24 21:36:43 UTC --- (In reply to comment #0)
Confirmed many times, even in different systems, such as Ubuntu. When booted kernel without PAE, and kernel sees only 3,3 GB of RAM, suspend-to-ram (s2ram) works. When PAE is enabled, and 4 GB of RAM is available, system won't resume.
What does it mean "won't resume"? Could you boot with no_console_suspend kernel parameter? -- 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=695758 https://bugzilla.novell.com/show_bug.cgi?id=695758#c4 --- Comment #4 from Oldrich Klimanek <oldrich.klimanek@gmail.com> 2011-05-25 14:20:06 UTC ---
What does it mean "won't resume"? Could you boot with no_console_suspend kernel parameter?
With 3 GB (2+1 modules) everything works. With 3.2 GB available, too (when PAE is disabled, RAM 2x2 GB). With 4 GB available, it looks like that: System is in a sleep mode (no problem suspending to RAM). When trying to resume, during the first 2 or 3 seconds everything looks fine. A hard drive wakes up, keyboard works, backlight turns on. However, then the backlight turns off, keyboard doesn't respond and the fan seems to run too fast (ACPI problem?) I've tried no_console_suspend with no luck. One person from openSUSE forum suggested that it might be BIOS problem (or BIOS vs kernel), namely the way BIOS is maping my RAM. Here is what he wrote: ****************************
# dmesg | grep e820 [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009dc00 (usable)
The above region is 0 - 640 KB
[ 0.000000] BIOS-e820: 000000000009dc00 - 00000000000a0000 (reserved) [ 0.000000] BIOS-e820: 00000000000d2000 - 0000000000100000 (reserved) [ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfe80000 (usable)
1 MB - 3.488 GB
[ 0.000000] BIOS-e820: 00000000cfe80000 - 00000000cfe92000 (ACPI data) [ 0.000000] BIOS-e820: 00000000cfe92000 - 00000000cfe94000 (ACPI NVS) [ 0.000000] BIOS-e820: 00000000cfe94000 - 00000000d0000000 (reserved) [ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) [ 0.000000] BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved) [ 0.000000] BIOS-e820: 0000000100000000 - 0000000130000000 (usable)
4.294 GB - 5.1000 GB
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) [ 0.000000] e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved) [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable) [ 0.000000] e820 update range: 00000000d0000000 - 0000000100000000 (usable) ==> (reserved)
Your BIOS is mapping memory with extra holes, which seems to be screwing up the save to memory. ************************* I guess some would say to upgrade the BIOS. Unfortunately I am using the latest BIOS, there has not been any upgrade for past few years. This bug seems to affect more users (according to various forum posts from around the web). I don't know whether the argument about BIOS is right -- if so, is there any way not to use the certain range in RAM? That would confirm it. And, if you look at the dmesg output you see the following (about Phoenix BIOS) [ 0.000000] BIOS-e820: 0000000100000000 - 0000000130000000 (usable) [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] DMI present. [ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it. [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) [ 0.000000] e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved) [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable) [ 0.000000] last_pfn = 0x130000 max_arch_pfn = 0x1000000 "Phoenix BIOS detected: BIOS may corrupt low RAM, working around" -- I found this about a kernel patch which seems important: [patch 03/49] x86: reserve low 64K on AMI and Phoenix BIOS boxen http://fixunix.com/kernel/557785-%5Bpatch-03-49%5D-x86-reserve-low-64k-ami-p... -- 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=695758 https://bugzilla.novell.com/show_bug.cgi?id=695758#c Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|oldrich.klimanek@gmail.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=695758 https://bugzilla.novell.com/show_bug.cgi?id=695758#c5 Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #5 from Jeff Mahoney <jeffm@suse.com> 2012-03-05 23:28:32 UTC --- openSUSE 11.3 is out of maintenance. If you can reproduce this issue with 11.4 or 12.1, please re-open with an updated Product field. -- 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