System Shuts Down after successful resume from suspend to ram - Portable

This is a discussion on System Shuts Down after successful resume from suspend to ram - Portable ; I've got a Tecra M1. I was running SuSE 9.1 with a hand-built 2.6.11.3 kernel and the latest NVidia drivers. In that config both suspend to ram and suspend to disk both worked fine. I've now rebuilt the box and ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: System Shuts Down after successful resume from suspend to ram

  1. System Shuts Down after successful resume from suspend to ram

    I've got a Tecra M1. I was running SuSE 9.1 with a hand-built 2.6.11.3
    kernel and the latest NVidia drivers. In that config both suspend to
    ram and suspend to disk both worked fine.

    I've now rebuilt the box and installed SuSE 9.3. The (stock) kernel is
    2.6.11.4-20a-default. I am also now running gdm (something I've never
    done before.) Suspend to disk works just fine. Suspend to ram also
    works fine, but about 20 seconds after resuming, the system starts a
    shutdown. The kernel reports "Received signal 15, shutting down
    cleanly". This is somehow related to gconfd.

    What I see in my /var/log/messages follows a bit further below.

    I am looking for advice on having the system not shutdown this way.

    Thanks
    John

    Apr 24 08:40:49 linux kernel: Stopping tasks:
    ================================================== ================================================== |
    Apr 24 08:40:49 linux kernel: eth1: Going into suspend...
    Apr 24 08:40:49 linux kernel: NVRM: RmPowerManagement: 3
    Apr 24 08:40:49 linux kernel: Back to C!
    Apr 24 08:40:49 linux kernel: Warning: CPU frequency is 1600000,
    cpufreq assumed 600000 kHz.
    Apr 24 08:40:49 linux kernel: PCI: Setting latency timer of device
    0000:00:1d.0 to 64
    Apr 24 08:40:49 linux kernel: PCI: Setting latency timer of device
    0000:00:1d.1 to 64
    Apr 24 08:40:49 linux kernel: PCI: Setting latency timer of device
    0000:00:1d.2 to 64
    Apr 24 08:40:49 linux kernel: PCI: cache line size of 32 is not
    supported by device 0000:00:1d.7
    Apr 24 08:40:49 linux kernel: ehci_hcd 0000:00:1d.7: USB 2.0 restarted,
    EHCI 1.00, driver 10 Dec 2004
    Apr 24 08:40:49 linux kernel: ACPI: PCI interrupt 0000:00:1f.1[A] ->
    GSI 11 (level, low) -> IRQ 11
    Apr 24 08:40:49 linux kernel: ACPI: PCI interrupt 0000:00:1f.5[B] ->
    GSI 11 (level, low) -> IRQ 11
    Apr 24 08:40:49 linux kernel: PCI: Setting latency timer of device
    0000:00:1f.5 to 64
    Apr 24 08:40:49 linux kernel: NVRM: RmPowerManagement: 4
    Apr 24 08:40:49 linux kernel: eth1: Coming out of suspend...
    Apr 24 08:40:49 linux kernel: ACPI: PCI interrupt 0000:02:05.0[A] ->
    GSI 11 (level, low) -> IRQ 11
    Apr 24 08:40:49 linux kernel: ACPI: PCI interrupt 0000:02:07.0[A] ->
    GSI 11 (level, low) -> IRQ 11
    Apr 24 08:40:49 linux kernel: ACPI: PCI interrupt 0000:02:09.0[A] ->
    GSI 11 (level, low) -> IRQ 11
    Apr 24 08:40:49 linux kernel: Restarting tasks...<6>usb 3-2: USB
    disconnect, address 2
    Apr 24 08:40:49 linux kernel: done
    Apr 24 08:40:50 linux kernel: Enabling hardware tapping
    Apr 24 08:40:50 linux kernel: usb 3-2: new low speed USB device using
    uhci_hcd and address 3
    Apr 24 08:40:50 linux su: (to jrh) root on none
    Apr 24 08:40:50 linux kernel: input: USB HID v1.10 Mouse [Logitech USB
    Receiver] on usb-0000:00:1d.1-2
    Apr 24 08:40:50 linux kernel: input: DualPoint Stick on isa0060/serio1
    Apr 24 08:40:50 linux kernel: input: AlpsPS/2 ALPS DualPoint TouchPad
    on isa0060/serio1
    Apr 24 08:41:05 linux gconfd (jrh-9358): Received signal 15, shutting
    down cleanly
    Apr 24 08:41:05 linux gconfd (jrh-9358): Exiting
    Apr 24 08:41:07 linux init: Switching to runlevel: 0


  2. Re: System Shuts Down after successful resume from suspend to ram

    On Sun, 24 Apr 2005 08:33:28 -0700, JohnRHarlow wrote:

    > I've got a Tecra M1. I was running SuSE 9.1 with a hand-built 2.6.11.3
    > kernel and the latest NVidia drivers. In that config both suspend to ram
    > and suspend to disk both worked fine.
    >
    > I've now rebuilt the box and installed SuSE 9.3. The (stock) kernel is
    > 2.6.11.4-20a-default. I am also now running gdm (something I've never done
    > before.) Suspend to disk works just fine. Suspend to ram also works fine,
    > but about 20 seconds after resuming, the system starts a shutdown. The
    > kernel reports "Received signal 15, shutting down cleanly". This is
    > somehow related to gconfd.


    I had the same thing. In the end it was because resuming from
    suspend-to-ram triggered an ACPI powerbutton event, which caused the
    laptop to shut down.

    I currently avoid it this way:

    In my suspend script, i call
    touch /tmp/acpi_sleep

    then, in my acpi powerbutton script; i check if the file exists, if it
    does i remove it, otherwise i powerdown.

    This works wonderfully for me.

    Hope it helps,

    Jan

    --
    precious (i686) running GNU/Linux 2.6.11.7 #1 Mon Apr 11 08:13:45 CEST 2005
    Objects in mirror may be closer than they appear.

  3. Re: System Shuts Down after successful resume from suspend to ram

    Thanks,

    I'll give that a try. I had gotten around it by changing init level to
    3 also but this sounds better.


    John


+ Reply to Thread