New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 644382 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[Samus] Device is not working after waking up the device from suspend state.

Project Member Reported by son...@google.com, Sep 6 2016

Issue description

Version: 8743.8.0
OS: ChromeOS

What steps will reproduce the problem?
(1) Sign in to the device.
(2) Run "powerd_dbus_suspned" to suspend the device.
(3) Close and open lid to wake up the device.

What is the expected output?
Device should work properly.

What do you see instead?
Device is not working.
Able to open tabs but not able to navigate to any site.
Not able to open crosh (Ctrl + Alt + t).
Not able to open any apps.


Note: This issue is not consistent.(2/20)
Device is working fine after reboot.

Please use labels and text to provide additional information.
 
crash report link:
https://crash.corp.google.com/browse?stbtiq=1d2b75e500000000



 

Comment 2 by son...@google.com, Sep 6 2016

Labels: -M-53 M-54
Components: Internals>Graphics
Owner: marc...@chromium.org
The crash seems frecon related. marcheu?
Status: Assigned (was: Untriaged)
Can you paste the backtrace or error message? I don't see where it is in there
Project Member

Comment 6 by sheriffbot@chromium.org, Sep 7 2016

Labels: Hotlist-Google
Owner: dbehr@chromium.org
Hmm ok it's in the crash link, somehow it didn't work before. Yes frecon crash, but I think it's fixed now

Comment 8 by enne@chromium.org, Jan 25 2017

Components: -Internals>Graphics Internals>GPU
Status: Fixed (was: Assigned)
Closing as per comment #7.  dbehr, please reopen if needed.

Comment 9 by son...@google.com, Feb 6 2017

Status: Verified (was: Fixed)
Verified on build 9202.17.0

Sign in to add a comment