[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#673806: [wheezy] suspend to ram not working using `echo mem > /sys/power/state`



Dear Jonathan,


first let me thank you for your great – first wanted to write
»tremendous« but `ding` showed it also means terrible, so I changed it –
work on Debian (especially the Linux kernel) and helping users like me.


Am Donnerstag, den 28.06.2012, 00:20 -0500 schrieb Jonathan Nieder:

> Paul Menzel wrote:
> 
> > testing suspend to RAM using [1]
> >
> >     $ echo mem | sudo tee /sys/power/state
> >
> > the fans and power supply do not turn off. A reboot is the only way to solve the issue.
> >
> > Using `sudo pm-suspend` from the package `pm-utils` works though.

That statement was wrong. See below.

> > Is that supposed to work or is that a bug.
> 
> It's supposed to work, yes.

First I need to add more information regarding this report.

Shut down also does not work sometimes, that means, it writes `Power
down` to the monitor but the fans keep running. Testing this further
with

    $ echo mem | sudo tee /sys/power/state

and

    $ sudo pm-suspend

I could reproduce this bug also with `pm-suspend` and sometimes it also
worked with writing `mem` to `/sys/power/state`.

To summarize, suspend to RAM and shut down *arbitrarily* have this
problem and I did not find a way yet to 

> Does 3.4.y from experimental exhibit the same problem?

I did not have time yet to test 3.4.y since I am using fglrx now and I
do not know if fglrx will work with 3.4.y.

> Please attach full "dmesg" output from booting and reproducing the bug.

To get further debugging information I set up netconsole by loading the
module with `modprobe` and doing `dmesg -n debug`. Furthermore I removed
`quiet` from the Linux commandline and added `debug` and
`no_console_suspend`.

Since adding `no_console_suspend` suspending to RAM worked as expected,
that means the power supply/fans were turned off.

The output (same between both methods) is the following.

        [  357.855551] PM: Syncing filesystems ... [  357.855551] PM: Syncing filesystems ... done.
        done.
        [  358.142767] Freezing user space processes ... [  358.142767] Freezing user space processes ... (elapsed 0.01 seconds) done.
        [  358.156343] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
        [  358.156343] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
        (elapsed 0.01 seconds) done.
        [  358.173230] sd 5:0:0:0: [sda] Synchronizing SCSI cache
        [  358.173230] sd 5:0:0:0: [sda] Synchronizing SCSI cache
        [  358.174338] sd 5:0:0:0: [sda] Stopping disk
        [  358.174710] serial 00:0a: disabled
        [  358.174338] sd 5:0:0:0: [sda] Stopping disk
        [  358.174823] serial 00:0a: wake-up capability disabled by ACPI
        [  358.174710] serial 00:0a: disabled
        [  358.174823] serial 00:0a: wake-up capability disabled by ACPI

*But* waking up does not work. :/ I cannot SSH into the system and
netconsole does not send anything either although fans are on and the
LEDs at the Ethernet jack light up too.

Furthermore I found out that there is a BIOS upgrade [1], where the
changelog is the following.

    Fix Ubuntu 11.04 can not shut down issue.

So I will do some further testing – I guess the easiest is the BIOS
upgrade – and report back.


Thanks,

Paul


[1] http://www.asrock.com/mb/download.asp?Model=E350M1&o=BIOS

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: