Bug 42968 (Laryllan)
Summary: | Lenovo S12 doesn't suspend | ||
---|---|---|---|
Product: | Drivers | Reporter: | laryllan |
Component: | USB | Assignee: | Greg Kroah-Hartman (greg) |
Status: | NEEDINFO --- | ||
Severity: | normal | CC: | laryllan, lenb, stern, tianyu.lan |
Priority: | P1 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 3.2.0-19-generic #30-Ubuntu i686 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 56331 | ||
Attachments: | useful information about my system |
Description
laryllan
2012-03-20 18:13:57 UTC
did you follow the debugging steps in Documentation/power/basic-pm-debugging.txt (in kernel source tree)? I did not see the results of those tests in the ubuntu bug report. Hi Len, what exactly do you need? I did the following tests: # echo devices > /sys/power/pm_test # echo platform > /sys/power/disk # echo disk > /sys/power/state # dmesg > /tmp/dmesg-devices-platform.txt # echo core > /sys/power/pm_test # echo platform > /sys/power/disk # echo disk > /sys/power/state # dmesg > /tmp/dmesg-core-platform.txt # echo core > /sys/power/pm_test # echo reboot > /sys/power/disk # echo disk > /sys/power/state # dmesg > /tmp/dmesg-core-reboot.txt These tests seem to be the very same suggested in basic-pm-debugging.txt. None of them gave any output. You can find the dmesg logs in the attachment. It's a problem of the hardware wireless switch. If wireless is turned off by hardware first, suspend works flawlessly. There is a workaround for this bug that works on the S12, see http://thecodecentral.com/2011/01/18/fix-ubuntu-10-10-suspendhibernate-not-working-bug I had to add 'ohci' to the DRIVERS= line of the script. This script is to unbind the ohci_hcd driver when suspend and bind the driver when resume. This seems a usb bug. Hi Lary: Could you verify whether this bug exist in the latest upstream kernel(v3.9-rc5)? Hi Alan: At this point, I think this is a usb ohci driver bug. Could you have a look? Is it really the WiFi device that causes the problem, or is it the Bluetooth device? Both of them get turned off by rfkill. Try turning off just one or the other. Also, what happens if you do echo 0 >/sys/bus/usb/devices/4-2/bConfigurationValue before starting the test? |