On Fri, Jun 01, 2007 at 11:54:34AM +0100, Amit Walambe wrote: > Stefan Seyfried wrote: > >> [EMAIL PROTECTED]:~ # dmesg | grep ACPI.*supports > >> 132:ACPI: (supports S0 S1 S4 S5) > > > > Your BIOS does not support suspend to RAM. Maybe you need to turn on some > > option in the BIOS. > Perfect! I should have tried this before. Sorry for making the earlier > noise. > > Following is listing of different modes I tried and the outputs. Now, to > be honest, I didn't try to know the logic behind all the options, so I > might be redundant in trying them. If any output is interesting and if I > am required to do more testing, I will be glad to be of help. > > #s2ram -f > Resumed with oops : > BUG: unable to handle kernel NULL pointer dereference at virtual address > 0000000c > printing eip: > c0177a12 > *pde = 00000000 > Oops: 0000 [#1] > SMP > Modules linked in: i915 drm thermal fan button processor ipv6 > nls_iso8859_1 cifs smbfs nfs lockd nfs_acl sunrpc snd_hda_intel > snd_pcm_oss snd_mixer_oss snd_pcm psmouse ehci_hcd uhci_hcd snd_timer > snd_page_alloc parport_pc ide_cd pcspkr i2c_i801 evdev serio_raw usbcore > parport rtc cdrom floppy > CPU: 0 > EIP: 0060:[<c0177a12>] Not tainted VLI > EFLAGS: 00010206 (2.6.22-rc3 #12) > EIP is at rw_verify_area+0x22/0xb0 > eax: 00000000 ebx: f0a2fa80 ecx: f0a3bfa0 edx: f0a2fa80 > esi: 08068540 edi: 00000800 ebp: f0a2fa80 esp: f0a3bf58 > ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 > Process gnome-vfs-daemo (pid: 2507, ti=f0a3a000 task=f0cd0a00 > task.ti=f0a3a000) > Stack: 00000001 00000001 08068540 00000000 f0a2fa80 08068540 f0a3bfa0 > fffffff2 > c017826c 00000800 b7d76ff4 f0a3a000 f0a2fa80 fffffff7 08068540 > f0a3a000 > c01787e1 f0a3bfa0 00000088 00000000 00000000 00000008 08066b88 > c010406a > Call Trace: > [<c017826c>] vfs_read+0x7c/0x160 > [<c01787e1>] sys_read+0x41/0x70 > [<c010406a>] sysenter_past_esp+0x5f/0x85 > ======================= > Code: 90 90 90 90 90 90 90 90 90 83 ec 20 89 7c 24 18 8b 7c 24 24 89 6c > 24 1c 89 d5 89 5c 24 10 89 74 24 14 89 44 24 0c 8b 42 0c 85 ff <8b> 70 > 0c 78 4d 8b 59 04 8b 09 85 db 78 44 89 f8 31 d2 01 c8 11 > EIP: [<c0177a12>] rw_verify_area+0x22/0xb0 SS:ESP 0068:f0a3bf58 > VFS: Close: file count is 0
Kernel problem, report to LKML. This should have happened with all the options, so it is probably a transient error. > #s2ram -f -a 1 > Worked perfect. Showed a 4-5 line (colourfully-worded) BIOS message. > > #s2ram -f -a 2 > Hanged during resume. > > #s2ram -f -a 3 > #s2ram -f -p -m > Works ok, but can't switch to text console. LCD compains 'out of range'. > > #s2ram -f -p -s > Resumes with blank display and shows Gnome cursor (only) at same > intervals and then hangs after some time. /var/log/Xorg.0.log had the > following : > Fatal server error: > lockup > > (II) AIGLX: Suspending AIGLX clients for VT switch > Error in I830WaitLpRing(), now is -422167744, start is -422169745 > pgetbl_ctl: 0xbffc0001 pgetbl_err: 0x0 > ipeir: 0 iphdr: 42555247 > LP ring tail: a18 head: 0 len: 1f001 start 0 > eir: 0 esr: 0 emr: ffff > instdone: ffc1 instpm: 0 > memmode: 108 instps: 14ce > hwstam: fffe ier: 82 imr: 0 iir: 0 > space: 128480 wanted 131064 > > FatalError re-entered, aborting > lockup Yes, i sometimes see this also, X server problem in i810 and intel. > # s2ram -f -m > Resumes ok with following : > Switching from vt7 to vt1 > Calling get_mode > Calling set_vbe_mode > Error: something went wrong performing real mode interrupt > switching back to vt7 Those errors are harmless, as long as it works :-) > # s2ram -f -s > Resumes ok with following : > Switching from vt7 to vt1 > Calling save_state > Can't get video state buffer size (vm86 failure) > Get video state buffer size failed > Allocated buffer at 0x2010 (base is 0x0) > ES: 0x0201 EBX: 0x0000 > Can't save video state (vm86 failure) > Save video state failed > Calling restore_state_from > Error: something went wrong performing real mode interrupt > Can't restore video state (vm86 failure) Again, probably harmless, if it works anyway :-) It is probably just luck if you did not get the X server problems with this one, i'm pretty sure it will appear sooner or later. > Following message was common with all the methods that worked : > ACPI: Unable to turn cooling device [c28f45a0] 'off' > Can anyone decipher it for me? I have no idea, but this is an ACPI error, so the acpi-devel list should be apropriate. -- Stefan Seyfried QA / R&D Team Mobile Devices | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out." This footer brought to you by insane German lawmakers: SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
