Snowball: Hang when DUT goes to suspend, (USB OTG port is free - no cables connected)

Bug #860542 reported by Abhishek Paliwal
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
IglooCommunity
Confirmed
Wishlist
Unassigned
Linaro Android
Won't Fix
High
Abhishek Paliwal

Bug Description

Description:
==========
Testing Suspend and resume funtionality. Keep USB OTG port free of any connection.
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. DUT hangs completely. Need to reboot now.
Issue is only seen when there is no connection on USB OTG port. (i.e - keep USB OTG port free from any physical connection) otherwise not observed.

Reproducible:
===========
Yes, 5/5

Logs:
====
Serial Logs snippet (Logcat):

[Tue Sep 27 18:14:12 2011] #
[Tue Sep 27 18:14:12 2011] # [ 78.262725] request_suspend_state: sleep (0->3) at 69044704539 (2000-01-01 22:46:23.381814537 UTC)
[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:
==========
Precondition: Remove any cable connected to USB OTG port.
1. Bootup DUT
2. Set Settings->Display->Screen Timeout = 15 seconds
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://android-build.linaro.org/builds/~linaro-android/staging-snowball-11.09-release/
build 1

Tags: snowball
Revision history for this message
Abhishek Paliwal (abhishek-paliwal) wrote :
tags: removed: 11.09 console linaro-android resume serial suspend
description: updated
summary: - Snowball: Serial console control is lost after DUT goes to suspend mode.
+ Snowball: Hang when DUT goes to suspend when USB OTG port is free
summary: - Snowball: Hang when DUT goes to suspend when USB OTG port is free
+ Snowball: Hang when DUT goes to suspend, (USB OTG port is free - no
+ cables connected)
description: updated
Zach Pfeffer (pfefferz)
Changed in linaro-android:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Mathieu Poirier (mathieu.poirier)
milestone: none → 11.10
Changed in linaro-landing-team-ste:
status: New → Confirmed
Revision history for this message
Scott Bambrough (scottb) wrote :

Expected: Serial console should be accessible even if DUT goes to suspend mode.

Not sure I agree with this. Not entirely sure what DUT is. Assuming it means display unit.

Messages indicate the system is suspending. This means all consoles will be disabled unless you specifically do something to ensure they are enabled for debugging (hence the text: use no_console_suspend to debug). This isn't just the display blanking, but the entire system sleeping. This will require a hardware interrupt to wake the system (something like a touch on a touchscreen, or pressing a hardware button, input from a USB HID device, etc). What is the expected means of waking up a Snowball board?

Revision history for this message
Mathieu Poirier (mathieu.poirier-deactivatedaccount) wrote :

This is a known issue that has been coming an going. Sometimes the console is still responsive after a suspend, sometimes it is not. It is currently hard to reproduce the problem due to the mmc issue (823313).

Revision history for this message
Abhishek Paliwal (abhishek-paliwal) wrote :

Here DUT stands for : Device Under Test
Expected behavior: When DUT goes to suspend mode - behavior should be consistent with USB OTG port free or busy.
As of now:
if USB (OTG)port is free - DUT does becomes unresponsive to serial port keyevents.
if USB(OTG) port is connected to some device like USB-Mouse/Keyboard - DUT remains responsive to serial port keyevents even during suspend mode.

Revision history for this message
Abhishek Paliwal (abhishek-paliwal) wrote :
Lee Jones (lag)
Changed in linaro-landing-team-ste:
importance: Undecided → High
assignee: nobody → Mathieu Poirier (mathieu.poirier)
Lee Jones (lag)
Changed in linaro-landing-team-ste:
importance: High → Low
importance: Low → Wishlist
Anmar Oueja (anmar)
Changed in linaro-android:
assignee: Mathieu Poirier (mathieu.poirier) → Abhishek Paliwal (abhishek-paliwal)
Revision history for this message
Mathieu Poirier (mathieu.poirier-deactivatedaccount) wrote :

This is dependent on bug #804091 and can't be addressed until the OTG driver is working properly.

Changed in linaro-android:
milestone: 11.10 → backlog
Revision history for this message
Abhishek Paliwal (abhishek-paliwal) wrote :
Revision history for this message
Abhishek Paliwal (abhishek-paliwal) wrote :
Anmar Oueja (anmar)
Changed in igloocommunity:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
supriya karanth (supriya-karanth) wrote :

When a usb cable is connected, a wakelock acquired while enabling the USB phy. This prevents the platform from going to suspend. Once the cable is removed we release the wakelock and the platform is allowed to go to suspend

Revision history for this message
FadilSG (fadil-a) wrote :

I had problems whether or not the USB OTG is connected to the cable. When it is, the board suspends by itself within a few sec of the OS booting. When I used the 5V supply (removing the USB cable), i get some pretty weird symbols on my remote terminal's display. Till today I don't know how to resolve it.

vishal (vishalbhoj)
Changed in linaro-android:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.