On 12/06/12 06:02, Jonathan Nieder wrote:
Eugen Dedu wrote:
Here it is: another freeze during resume, with kernel 3.3 too.
Thanks for the quick feedback. (As a reminder to myself, the message
is
BUG: unable to handle kernel paging request at fffffff(lens flare)
IP: [<ffffffff810514c7>] kthread_data+0x7/0xc
PGD 1607067 PUD 1608067 PMD 0
Oops: 0000 [#2] SMP
CPU 0
[...]
Code: 3f 48 c1 e5 03 48 c1 e0 06 48 8d b0 50 54 40 81 29 ee e8 62 c0 00 00 81
4b 14 00 00 00 04 41 59 5b 5d c3 48 8b 87 a0 02 00 00<48> 8b 40 f8 c8 48 3b 3d
95 43 72 00 75 08 0f bf 87 6a 06 00 00
[...]
Fixing recursive fault but reboot is needed!
Call trace involves trying to handle a page fault in
led_trigger_unregister, called by power_supply_unregister, called by
acpi_battery_notify. The first oops looks similar but scrolled off
the screen. This is a 3.3.y kernel with virtualbox modules loaded.)
Ideas for moving forward:
- please attach:
- full "dmesg" output from a normal boot
- "acpidump" output
- see Documentation/power/basic-pm-debugging.txt from [1] or the
kernel-doc-3.2 package. Does suspend-to-disk work? Do pm_test
modes work? Are any warnings shown at suspend time that can be
captured using a serial console or netconsole with
no_console_suspend? Does unloading the "battery" module before
suspend avoid trouble?
(I still do not understand why my previous messages do not appear at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677016.)
Here it is:
First, note that I have indeed a problem with the battery, since the
icon of gnome is not working properly: it shows an empty battery, whice
it is fully loaded, or viceversa. However, its tooltip (showing
percentage of battery) is correct.
snoopy:/home/ededu# echo reboot > /sys/power/disk
snoopy:/home/ededu# echo disk > /sys/power/state
[screen got black for ~2 secs, it shows "Cannot find swap device, try
swapon -a.\nCannot get swap writer" - which is normal since I do not
have one - and afterwards comes back]
bash: echo: write error: No such device
snoopy:/home/ededu#
I tested it for 20 times in a row and it worked each time.
Afterwards, I tested:
snoopy:~# echo platform > /sys/power/disk
snoopy:~# echo disk > /sys/power/state
bash: echo: write error: No such device
snoopy:~#
for 15 times in a row and it worked each time too.
As a side note, the link http://en.opensuse.org/s2ram at the bottom of
http://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt is
not valid anymore.
I tried:
snoopy:~# echo freezer >/sys/power/pm_test
snoopy:~# echo mem > /sys/power/state
and
snoopy:~# s2ram
KMS graphics driver is in use, skipping quirks.
and they worked 10 times in a row.
The same for:
snoopy:~# echo devices >/sys/power/pm_test
snoopy:~# for i in `seq 10`; do echo mem > /sys/power/state; done
It works too:
snoopy:~# echo platform >/sys/power/pm_test ; for i in `seq 10`; do echo
mem > /sys/power/state; s2ram; done
[s2ram prints: "KMS graphics driver is in use, skipping quirks."
This works too:
snoopy:~# echo processors >/sys/power/pm_test ; for i in `seq 10`; do
echo mem > /sys/power/state; s2ram; done
This works too:
snoopy:~# echo core >/sys/power/pm_test ; for i in `seq 10`; do echo mem
> /sys/power/state; sleep 2; s2ram; sleep 2; done
This works too:
snoopy:~# echo none >/sys/power/pm_test ; for i in `seq 10`; do echo mem
> /sys/power/state; sleep 2; s2ram; sleep 2; done
As all this worked, I have not tried unloading battery module before
suspend2ram.
I have not tried either using a serial console either...
What should I do?
--
Eugen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
