Skip to contentSkip to conversation

S3: no resume, not even a beep - LG R700

Bug 11255 Rogério Brito 2 participants 4 messages Oct 7, 2009 – Oct 26, 2009 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]/

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw

Hi, Rafael and other people.

First some context:

Quoted 12 lines · Rogério Brito

Well, I have some quite detailed debugging information on the bug that I reported and that was considered as a duplicate of this one.

"My bug" is http://bugzilla.kernel.org/show_bug.cgi?id=11717, where I detail a lot of what has been done. Actually, I even filmed what the notebook does, but I, then, deleted it, given the 10 or more months that have already passed since I first reported this issue.

I can film it again, if it is desired.

I can really understand what other bug reporters feel (frustration is the right word) given that we spent so much on this. :-(

(...)

Quoted 3 lines · Rafael J. Wysocki

Rogério, thanks a lot for the information.

Did you try any tests with /sys/power/pm_test or did you try to use PM_TRACE?

I did a good amount of tests.

Yes, I did do tests with /sys/power/pm_test. The results (in an ascii-art table) that I got with kernel 2.6.31-rc5 were:

test with /s/p/pm_test | result
-----------------------+------------------------

core                   | comes back from "sleep"
processors             | comes back from "sleep"
devices                | comes back from "sleep"
"none"                 | hangs in the real test

I'm writing this from memory, but I can repeat the tests, of course. It would be nice if other reporters also did the same, so that we can isolate the problem here.

Or, if they already did the tests, it would be nice if they could summarize the tests.

I also tried to use /sys/power/pm_trace, but without much success. I don't remember any hash or matches line, but I can, of course, try it again.

Oh, just so that you get an idea of what happens with my computer (and I would love it if the other reporters confirmed what they are seeing), here is what happens when I press the sleep button under any kernel that I tried:

,----

| * the machine goes to sleep, staying with the light on the power button
|   blinking;
| 
| * if I press the button again, the notebook gives all symptoms of
|   resuming;
| 
| * just when you think that it will wake up, it turns itself off;
| 
| * after 1 or 2 seconds, when you think that it is powered off, it
|   turns itself on again (yes, "out of the blue");
| 
| * after that, it hangs with a black screen and no responses, no
|   feedback, no network activity (I tried to ssh into it), no pings, no
|   Magic SysRq, no nothing.

`----

Under Windows Vista (that came preinstalled), I do:

,----

| * press the power/sleep button;
| * the machine goes to sleep;
| * press the power/sleep button again;
| * the machine comes from sleep.

`----

I have already tried to:

* enable and disable Kernel Modesetting (it's an ICH8-based chipset);
* booted with a full system;
* booted with init=/bin/bash (so, no acpid taking over /proc/acpi/event);
* upgrade and downgrade the BIOS version;
* used kernels from 2.6.24 to 2.6.31-rc8.

I also tried ykzhao's suggestion of

"echo mem > /sys/power/state; dmesg > dmesg_after; sync;"

but, as I naively would expect, there's no time for a dmesg to be written to the disk, apparently.

Oh, I read some of the other bug reports and it seems that the other posters also have a realtek 8169-driven ethernet card (can you confirm, people?).

I tried "ifconfig eth0 down"'ing and even removing the module before putting it to sleep, but no success either.

Well, as you can see, there's something highly magical that Windows seems to be doing here that Linux can't (up to now).

As always, I am open to any suggestions and can perform any tests that you want me to (and I can reconduct anything that was done already).

Thanks, Rogério Brito.

Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
#4 lore raw
Quoted 17 lines · Rogério Brito

Hi, Rafael and other people.

First some context:

Quoted 8 lines · Rogério Brito

Well, I have some quite detailed debugging information on the bug that I reported and that was considered as a duplicate of this one.

"My bug" is http://bugzilla.kernel.org/show_bug.cgi?id=11717, where I detail a lot of what has been done. Actually, I even filmed what the notebook does, but I, then, deleted it, given the 10 or more months that have already passed since I first reported this issue.

Quoted 4 lines

I can film it again, if it is desired.

I can really understand what other bug reporters feel (frustration is the right word) given that we spent so much on this. :-(

Quoted 8 lines

(...)

Quoted 3 lines · Rafael J. Wysocki

Rogério, thanks a lot for the information.

Did you try any tests with /sys/power/pm_test or did you try to use PM_TRACE?

I did a good amount of tests.

Replied in the Bugzilla, sorry for failing to notice you sent it as e-mail.

Rafael

#5 lore raw
In reply to a message not in the archive

Hi, people.

First of all, to the bug reporters: please, let's get a bit more closer and try to join our forces.

Triaging the bug report, seeing what still happens with the current kernels etc. would all be helpful if we want to get our notebooks working.

OK, now to the problem itself.

After some time without internet connection (humpf), I am back online and I just did a git pull and a new kernel is being baked, soon to be served. :-)

I did collect quite a bunch of extra information (including newer blobs of dsdt, after the firmware upgrade from the firmware from MSI) and I will upload those in a moment.

I hope that this will help us to better decide what is the culprit and how we can better address this problem (perhaps asking MSI for some involvement?).

Anyway, just as an extra piece of information, my notebook is what MSI calls an MSI Aesthetic PR200 (well, at least after flashing it, that's what it reports :) and it didn't die with this upgrade).

Some extra pointers (a script, actually) of what I did to create a boot USB "disk" are outlined here: http://rb.doesntexist.org/diary/2009.xhtml

Hope this helps so far, Rogério Brito.

Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
#6 lore raw
Quoted 23 lines · Rogério Brito

Hi, people.

First of all, to the bug reporters: please, let's get a bit more closer and try to join our forces.

Triaging the bug report, seeing what still happens with the current kernels etc. would all be helpful if we want to get our notebooks working.

OK, now to the problem itself.

After some time without internet connection (humpf), I am back online and I just did a git pull and a new kernel is being baked, soon to be served. :-)

I did collect quite a bunch of extra information (including newer blobs of dsdt, after the firmware upgrade from the firmware from MSI) and I will upload those in a moment.

I hope that this will help us to better decide what is the culprit and how we can better address this problem (perhaps asking MSI for some involvement?).

Quoted 6 lines

Anyway, just as an extra piece of information, my notebook is what MSI calls an MSI Aesthetic PR200 (well, at least after flashing it, that's what it reports :) and it didn't die with this upgrade).

Some extra pointers (a script, actually) of what I did to create a boot USB "disk" are outlined here: http://rb.doesntexist.org/diary/2009.xhtml

Thanks for being persistent.

Can you please attach the output of dmesg from 2.6.32-rc5 and the output of lspci from the system to the bug entry?