Comment 0 for bug 860542
Revision history for this message
| Abhishek Paliwal (abhishek-paliwal) wrote Snowball: Serial console control is lost after DUT goes to suspend mode. | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Description:
==========
Testing Suspend and resume funtionality.
Screen timeout value is set to 15 seconds, after 15 seconds DUT goes into suspend mode.
After this serial console control is lost, can't enter any text on serial console.
Reproducible:
===========
Not seen all the time , but observed quite frequently. ~3/10 time
Logs:
====
Serial Logs snippet (Logcat):
[Tue Sep 27 18:14:12 2011] #
[Tue Sep 27 18:14:12 2011] # [ 78.262725] request_
[Tue Sep 27 18:14:41 2011] I/power ( 1519): *** set_screen_state 0
[Tue Sep 27 18:14:41 2011] D/SurfaceFlinger( 1519): About to give-up screen, flinger = 0x8e150
[Tue Sep 27 18:14:41 2011] [ 78.317749] PM: Syncing filesystems ... done.
[Tue Sep 27 18:14:41 2011] [ 78.323394] Freezing user space processes ... (elapsed 0.02 seconds) done.
[Tue Sep 27 18:14:41 2011] [ 78.350982] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[Tue Sep 27 18:14:41 2011] [ 78.370910] Suspending console(s) (use no_console_suspend to debug)
Steps:
==========
1. Bootup DUT
2. Set Settings-
3. Wait 15 seconds(do not provide any interrupt to DUT)
Observation: After 15 seconds once DUT goes to suspend mode - unable to get control of serial console. can'e enter any text.
Expected: Serial console should be accessible even if DUT goes to suspend mode.
Hardware:
==========
Snowball: V5
HDMI Out to TV - via HDMI cable
USB-Serial Logging
(No ethernet connection)
Software:
==========
https:/
build 1