| View previous topic :: View next topic |
| Author |
Message |
frankjr
n00b
Joined: 13 Sep 2002
Posts: 55
|
 Posted: Mon Dec 13, 2004 11:38 am Post subject: Suspend-to-ram with swsusp2 |
 |
|
| On my notebook, I have swsusp2 up and running perfectly fine when using suspend-to-disk (PowerDownMethod set to 4 or 5 in /etc/hibernate/hibernate.conf), but whenever I try using suspend-to-ram with swsusp2 (PowerDownMethod 3 in the config file), it suspends to that state (with the power light blinking) but whenever I press the power button to resume, the notebook turns back on quickly and then it turns off completely, which requires me to turn my system on and resume from the data that was recorded to disk before suspending. Any solutions to get suspend-to-ram working properly? |
|
| Back to top |
|
 |
nightfrost
Apprentice
Joined: 07 Dec 2004
Posts: 293
Location: Sweden
|
|
| Back to top |
|
|
Archangel1
Veteran
Joined: 21 Apr 2004
Posts: 1212
Location: Work
|
| Posted: Tue Jan 11, 2005 10:04 pm Post subject: |
|
|
I had a quick play with it, and I can't see the point. It suspends to RAM instead of turning off... so what? It still seems to write everything to disk first, so isn't as fast as a straight suspend to RAM.
And unfortunately mine doesn't resume from either kind of suspend to RAM 
_________________
What are you, stupid? |
|
| Back to top |
|
|
mkrisch
n00b
Joined: 22 Nov 2004
Posts: 59
|
| Posted: Tue Jan 11, 2005 10:27 pm Post subject: Re: Suspend-to-ram with swsusp2 |
|
|
| frankjr wrote: | | On my notebook, I have swsusp2 up and running perfectly fine when using suspend-to-disk (PowerDownMethod set to 4 or 5 in /etc/hibernate/hibernate.conf), but whenever I try using suspend-to-ram with swsusp2 (PowerDownMethod 3 in the config file), it suspends to that state (with the power light blinking) but whenever I press the power button to resume, the notebook turns back on quickly and then it turns off completely, which requires me to turn my system on and resume from the data that was recorded to disk before suspending. Any solutions to get suspend-to-ram working properly? |
i believe this is unrelated to swsusp2, and just an acpi suspend issue, as i have it as well on a kernel without swsusp2. what i suspect is happening is that the power button event is waking up the system, but as soon as it comes up, that same event triggers the system shutdown. what i suspect is required is some modification to the sleep script disabling the powerbutton shutdown event (see /etc/acpi) and then reenabling it when you wake up. |
|
| Back to top |
|
|
Earthwings
Bodhisattva
Joined: 14 Apr 2003
Posts: 7753
Location: Germany
|
| Posted: Tue Jan 11, 2005 10:36 pm Post subject: Re: Suspend-to-ram with swsusp2 |
|
|
| mkrisch wrote: | | frankjr wrote: | | On my notebook, I have swsusp2 up and running perfectly fine when using suspend-to-disk (PowerDownMethod set to 4 or 5 in /etc/hibernate/hibernate.conf), but whenever I try using suspend-to-ram with swsusp2 (PowerDownMethod 3 in the config file), it suspends to that state (with the power light blinking) but whenever I press the power button to resume, the notebook turns back on quickly and then it turns off completely, which requires me to turn my system on and resume from the data that was recorded to disk before suspending. Any solutions to get suspend-to-ram working properly? |
i believe this is unrelated to swsusp2, and just an acpi suspend issue, as i have it as well on a kernel without swsusp2. what i suspect is happening is that the power button event is waking up the system, but as soon as it comes up, that same event triggers the system shutdown. what i suspect is required is some modification to the sleep script disabling the powerbutton shutdown event (see /etc/acpi) and then reenabling it when you wake up. |
Indeed, IIRC the default /etc/acpi/default.sh has a "init 0" call for the power button event. |
|
| Back to top |
|
|
TaTaE
n00b
Joined: 15 Nov 2004
Posts: 13
Location: Romania
|
| Posted: Sat Jan 15, 2005 9:33 pm Post subject: |
|
|
I also have this problem with suspend to ram. The computer wakes up and for a second I can see the desktop, but the display quickly turns black and remains like this, the only solution I have being the reset button.
If anyone has any idea, he is welcome.
PS Also I tried to recompile my DSDT table and found one error I couldn't debug, something about an "Unexpected PARSEOP_AND" on line 43.
Here is what I found in the system log:
| Code: |
Jan 12 14:24:28 TATAE-PC kernel: Stopping tasks: ===================================================|
Jan 12 14:24:28 TATAE-PC kernel: Freeing memory... ^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/ ^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/ ^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/ ^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/ ^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/ ^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/ ^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/ ^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^Hdone (63458pages freed)
Jan 12 14:24:28 TATAE-PC kernel: usb usb2: no poweroff yet, suspending instead
Jan 12 14:24:28 TATAE-PC kernel: usb usb1: no poweroff yet, suspending instead
Jan 12 14:24:28 TATAE-PC kernel: NVRM: RmPowerManagement: 3
Jan 12 14:24:28 TATAE-PC kernel: .....................................swsusp: Need to copy 11652 pages
Jan 12 14:24:28 TATAE-PC kernel: ..<7>PCI: Setting latency timer of device 0000:00:1f.2 to 64
Jan 12 14:24:28 TATAE-PC kernel: PCI: Setting latency timer of device 0000:00:1f.4 to 64
Jan 12 14:24:28 TATAE-PC kernel: ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 11 (level, low) -> IRQ 11
Jan 12 14:24:28 TATAE-PC kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64
Jan 12 14:24:28 TATAE-PC kernel: NVRM: RmPowerManagement: 4
Jan 12 14:24:28 TATAE-PC kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Jan 12 14:24:28 TATAE-PC kernel: Restarting tasks... done
Jan 12 14:39:13 TATAE-PC kernel: Stopping tasks: ===================================================================|
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }
Jan 12 14:39:13 TATAE-PC kernel: ide: failed opcode was: unknown
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }
Jan 12 14:39:13 TATAE-PC kernel: ide: failed opcode was: unknown
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }
Jan 12 14:39:13 TATAE-PC kernel: ide: failed opcode was: unknown
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }
Jan 12 14:39:13 TATAE-PC kernel: ide: failed opcode was: unknown
Jan 12 14:39:13 TATAE-PC kernel: hda: DMA disabled
Jan 12 14:39:13 TATAE-PC kernel: ide0: reset: success
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }
Jan 12 14:39:13 TATAE-PC kernel: ide: failed opcode was: unknown
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }
Jan 12 14:39:13 TATAE-PC kernel: ide: failed opcode was: unknown
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }
Jan 12 14:39:13 TATAE-PC kernel: ide: failed opcode was: unknown
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }
Jan 12 14:39:13 TATAE-PC kernel: ide: failed opcode was: unknown
Jan 12 14:39:13 TATAE-PC kernel: ide0: reset: success
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 12 14:39:13 TATAE-PC kernel: hda: task_no_data_intr: error=0x04 { DriveStatusError }
Jan 12 14:39:13 TATAE-PC kernel: ide: failed opcode was: unknown
Jan 12 14:39:13 TATAE-PC kernel: NVRM: RmPowerManagement: 3
Jan 12 14:39:13 TATAE-PC kernel: Back to C!
Jan 12 14:39:13 TATAE-PC kernel: MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.
Jan 12 14:39:13 TATAE-PC kernel: Bank 1: f200000000000005
Jan 12 14:39:13 TATAE-PC kernel: PCI: Setting latency timer of device 0000:00:1f.2 to 64
Jan 12 14:39:13 TATAE-PC kernel: PCI: Setting latency timer of device 0000:00:1f.4 to 64
Jan 12 14:39:13 TATAE-PC kernel: ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 11 (level, low) -> IRQ 11
Jan 12 14:39:13 TATAE-PC kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64
Jan 12 14:39:13 TATAE-PC kernel: NVRM: RmPowerManagement: 4
Jan 12 14:39:13 TATAE-PC kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Jan 12 14:39:13 TATAE-PC kernel: Restarting tasks... done
Jan 12 14:39:16 TATAE-PC kernel: Unable to handle kernel paging request at virtual address 00010502
Jan 12 14:39:16 TATAE-PC kernel: printing eip:
Jan 12 14:39:16 TATAE-PC kernel: c03113ee
Jan 12 14:39:16 TATAE-PC kernel: *pde = 00000000
Jan 12 14:39:16 TATAE-PC kernel: Oops: 0002 [#1]
Jan 12 14:39:16 TATAE-PC kernel: PREEMPT
Jan 12 14:39:16 TATAE-PC kernel: Modules linked in: iptable_mangle iptable_nat ipt_LOG ipt_state ip_conntrack ipt_limit iptable_filter ip_tables snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device analog ns558 gameport parport_pc parport pcspkr 8139cp snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd soundcore snd_page_alloc intel_agp agpgart evdev w83627hf eeprom i2c_sensor i2c_isa i2c_i801 i2c_core nvidia
Jan 12 14:39:16 TATAE-PC kernel: CPU: 0
Jan 12 14:39:16 TATAE-PC kernel: EIP: 0060:[memcpy+30/64] Tainted: P M VLI
Jan 12 14:39:16 TATAE-PC kernel: EIP: 0060:[<c03113ee>] Tainted: P M VLI
Jan 12 14:39:16 TATAE-PC kernel: EFLAGS: 00010213 (2.6.10-gentoo-r2)
Jan 12 14:39:16 TATAE-PC kernel: EIP is at memcpy+0x1e/0x40
Jan 12 14:39:16 TATAE-PC kernel: eax: 0000003b ebx: d3bea000 ecx: 0000000e edx: 00010502
Jan 12 14:39:16 TATAE-PC kernel: esi: ce5b6c60 edi: 00010502 ebp: cf5990e0 esp: d3beaee4
Jan 12 14:39:16 TATAE-PC kernel: ds: 007b es: 007b ss: 0068
Jan 12 14:39:16 TATAE-PC kernel: Process vesafb (pid: 766, threadinfo=d3bea000 task=d3ba20c0)
Jan 12 14:39:16 TATAE-PC kernel: Stack: 00000000 0000003b d3beaf54 c03527a0 00010502 ce5b6c60 0000003b c05370f8
Jan 12 14:39:16 TATAE-PC kernel: d3bea000 d3bea000 d3beaf54 d3beaf6c c0352bc5 00004000 fffffff6 00000001
Jan 12 14:39:16 TATAE-PC kernel: 00060000 00000007 13460000 13480000 d3bea000 d3460000 00000000 00000000
Jan 12 14:39:16 TATAE-PC kernel: Call Trace:
Jan 12 14:39:16 TATAE-PC kernel: [vesafb_handle_tasks+256/928] vesafb_handle_tasks+0x100/0x3a0
Jan 12 14:39:16 TATAE-PC kernel: [<c03527a0>] vesafb_handle_tasks+0x100/0x3a0
Jan 12 14:39:16 TATAE-PC kernel: [vesafb_thread+389/704] vesafb_thread+0x185/0x2c0
Jan 12 14:39:16 TATAE-PC kernel: [<c0352bc5>] vesafb_thread+0x185/0x2c0
Jan 12 14:39:16 TATAE-PC kernel: [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60
Jan 12 14:39:16 TATAE-PC kernel: [<c012e290>] autoremove_wake_function+0x0/0x60
Jan 12 14:39:16 TATAE-PC kernel: [deactivate_task+30/48] deactivate_task+0x1e/0x30
Jan 12 14:39:16 TATAE-PC kernel: [<c011591e>] deactivate_task+0x1e/0x30
Jan 12 14:39:16 TATAE-PC kernel: [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60
Jan 12 14:39:16 TATAE-PC kernel: [<c012e290>] autoremove_wake_function+0x0/0x60
Jan 12 14:39:16 TATAE-PC kernel: [exit_notify+1610/2272] exit_notify+0x64a/0x8e0
Jan 12 14:39:16 TATAE-PC kernel: [<c011ba8a>] exit_notify+0x64a/0x8e0
Jan 12 14:39:16 TATAE-PC kernel: [schedule_tail+23/80] schedule_tail+0x17/0x50
Jan 12 14:39:16 TATAE-PC kernel: [<c0115db7>] schedule_tail+0x17/0x50
Jan 12 14:39:16 TATAE-PC kernel: [ret_from_fork+6/20] ret_from_fork+0x6/0x14
Jan 12 14:39:16 TATAE-PC kernel: [<c0102ff2>] ret_from_fork+0x6/0x14
Jan 12 14:39:16 TATAE-PC kernel: [vesafb_thread+0/704] vesafb_thread+0x0/0x2c0
Jan 12 14:39:16 TATAE-PC kernel: [<c0352a40>] vesafb_thread+0x0/0x2c0
Jan 12 14:39:16 TATAE-PC kernel: [vesafb_thread+0/704] vesafb_thread+0x0/0x2c0
Jan 12 14:39:16 TATAE-PC kernel: [<c0352a40>] vesafb_thread+0x0/0x2c0
Jan 12 14:39:16 TATAE-PC kernel: [kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18
Jan 12 14:39:16 TATAE-PC kernel: [<c01012ad>] kernel_thread_helper+0x5/0x18
Jan 12 14:39:16 TATAE-PC kernel: Code: 31 d2 b8 f2 ff ff ff c3 90 90 90 90 90 83 ec 0c 8b 44 24 18 89 74 24 04 8b 54 24 1089 7c 24 08 8b 74 24 14 89 c1 c1 e9 02 89 d7 <f3> a5 a8 02 74 02 66 a5 a8 01 74 01 a4 8b 74 24 04 89 d0 8b 7c
|
mod edit: wrapped long lines --Earthwings |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
