[Bug 364474] New: Getting suspend to ram errors
https://bugzilla.novell.com/show_bug.cgi?id=364474 User doiggl@velocitynet.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c1 Summary: Getting suspend to ram errors Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: doiggl@velocitynet.com.au QAContact: qa@suse.de Found By: --- How can I turn the message off ? Kernel # uname -a Linux orac 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC x86_64 x86_64 x86_64 GNU/Linux Attachments to follow. -- 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=364474 User doiggl@velocitynet.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c1 --- Comment #1 from Glenn Doig <doiggl@velocitynet.com.au> 2008-02-25 01:47:31 MST --- Created an attachment (id=196865) --> (https://bugzilla.novell.com/attachment.cgi?id=196865) suspend to ram error listing -- 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=364474 User doiggl@velocitynet.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c2 --- Comment #2 from Glenn Doig <doiggl@velocitynet.com.au> 2008-02-25 01:49:35 MST --- Created an attachment (id=196866) --> (https://bugzilla.novell.com/attachment.cgi?id=196866) number of popups overnight - 420 -- 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=364474 User doiggl@velocitynet.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c3 --- Comment #3 from Glenn Doig <doiggl@velocitynet.com.au> 2008-02-25 01:52:30 MST --- Created an attachment (id=196867) --> (https://bugzilla.novell.com/attachment.cgi?id=196867) hwinfo 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=364474 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com AssignedTo|kernel-maintainers@forge.provo.novell.com |pavel@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=364474 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c4 Pavel Machek <pavel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pavel@novell.com AssignedTo|pavel@novell.com |seife@novell.com --- Comment #4 from Pavel Machek <pavel@novell.com> 2008-03-20 16:00:45 MST --- See... http://en.opensuse.org/S2ram . You need to add your machine to whitelist. -- 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=364474 User doiggl@velocitynet.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c5 --- Comment #5 from Glenn Doig <doiggl@velocitynet.com.au> 2008-03-20 21:31:03 MST --- # rpm -qa | grep -i powersave powersave-0.15.17-10 powersave-libs-0.15.17-10 kpowersave-0.7.3-7.1 # s2ram -i This machine can be identified by: sys_vendor = "ASUSTeK Computer INC." sys_product = "A6T" sys_version = "1.0" bios_version = "080012 " I did the following I started with init=/bin/bash at the boot prompt into a minimal environment, then: # mount /proc # mount /sys # s2ram -f Result was the screen went blank, I could still hear the fan going, nothing was responding on keyboard I had to reboot. Question: How do I add the machine to whitelist ?. -- 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=364474 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c6 Pavel Machek <pavel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Enhancement --- Comment #6 from Pavel Machek <pavel@novell.com> 2008-03-21 05:06:18 MST --- See the link http://en.opensuse.org/S2ram . You need to find working send of options, then it makes sense to whitelist. I guess stefan will add it into the whitelist once you post working set of options 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=364474 User doiggl@velocitynet.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c7 --- Comment #7 from Glenn Doig <doiggl@velocitynet.com.au> 2008-03-22 06:07:19 MST --- I tried all the following tests options listed in http://en.opensuse.org/S2ram after starting with a minimal system init=/bin/bash mount /proc mount /sys Then I tried each test: (rebooted between each test) s2ram -f s2ram -f -a 1 s2ram -f -a 2 s2ram -f -a 3 s2ram -f -p -m s2ram -f -p -s s2ram -f -m s2ram -f -s s2ram -f -p s2ram -f -a 1 -m s2ram -f -a 1 -s s2ram -v -f -a 1 s2ram -v -f -a 2 s2ram -v -f -a 3 s2ram -v -f -p -m s2ram -v -f -p -s s2ram -v -f -m s2ram -v -f -s s2ram -v -f -p s2ram -v -f -a 1 -m s2ram -v -f -a 1 -s Result: Each test FAILED. The result was on each option I tried the screen went blank, I pressed the Caps Lock key on - I saw the Caps Lock key light came on but the lcd display did NOT come on,the disk I could see the disk access light flashing when a key was pressed, the only option was to reboot the laptop via a reset pin in a hole, as the on/off button did not respond at all. [21 reboots takes a while!] Question: What can I try/do next ?. -- 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=364474 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c8 --- Comment #8 from Pavel Machek <pavel@novell.com> 2008-03-24 15:10:05 MST --- Not sure what's next, we've ran out of tricks here. The last one is to write your own video driver from available documentation... What kind of machine is that, with what graphics card? -- 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=364474 User doiggl@velocitynet.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c9 --- Comment #9 from Glenn Doig <doiggl@velocitynet.com.au> 2008-03-25 08:28:00 MST --- Machine is: Asus A6T series - details below http://www.asus.com/products.aspx?l1=5&l2=24&l3=134&l4=0&model=1185&modelmenu=1 http://www.asus.com/products.aspx?l1=5&l2=24&l3=134&l4=0&model=1185&modelmenu=2 http://support.asus.com/download/download.aspx?SLanguage=en-us&model=A6T Included hwinfo output in comment #3 Video is: Geforce GO 7600 lspci output # lspci 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3) 00:0a.3 Co-processor: nVidia Corporation MCP51 PMU (rev a3) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) 02:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce Go 7600] (rev a1) 03:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b3) 03:01.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 08) 03:01.2 Generic system peripheral [Class 0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 17) 03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 08) 03:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) -- 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=364474 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c10 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #10 from Stefan Seyfried <seife@novell.com> 2008-04-01 09:31:54 MST --- For NVIDIA it sometimes helps to use the binary only nvidia driver and then no options to s2ram at all - just plain "s2ram -f". This probably only works from X and only if you are lucky and the nvidia driver of the day supports suspend to RAM (sometimes they do). Sorry, not much i can 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=364474 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=364474#c11 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #11 from Stefan Seyfried <seife@novell.com> 2008-05-07 11:01:57 MST --- as i said in the comment before, there is not much i can do here for you :-( So this wontfix really is a "cantfix". With recent nvidia drivers you might actually be lucky and it might work with plain "s2ram -f". Good luck :-) -- 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