Bug 97543 - ChromeOS locks up, never recovers gracefully.
Summary: ChromeOS locks up, never recovers gracefully.
Status: CLOSED NOTOURBUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other other
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-30 18:40 UTC by pfk
Modified: 2016-08-31 06:27 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Error from /sys/class/drm/card0/error (5.26 MB, text/plain)
2016-08-30 18:40 UTC, pfk
no flags Details

Description pfk 2016-08-30 18:40:58 UTC
Created attachment 126121 [details]
Error from /sys/class/drm/card0/error

ChromeOS on an Acer Chromebase 24 (2016) will lock up while video conferencing on a  Jitsi Meet session.  The screen usually goes black, and does not recover gracefully.  

Moving into Developer Mode and recreating the issue, we can find the message logs attached as well as the error log from /sys/class/drm/card0/error.  

This is reproducible on two Chromebases, but does not occur on a third of the same model (purchased in a different country).  All are on the latest ChromeOS version as of 08-30-2016.


2016-08-30T13:48:30.243258-04:00 INFO kernel: [  981.120682] [drm] stuck on bsd ring
2016-08-30T13:48:30.243278-04:00 INFO kernel: [  981.120698] [drm] GPU crash dump saved to /sys/class/drm/card0/error
2016-08-30T13:48:30.243284-04:00 INFO kernel: [  981.120709] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
2016-08-30T13:48:30.243288-04:00 INFO kernel: [  981.120723] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
2016-08-30T13:48:30.243292-04:00 INFO kernel: [  981.120737] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
2016-08-30T13:48:30.243295-04:00 INFO kernel: [  981.120751] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
2016-08-30T13:48:30.281906-04:00 INFO crash_reporter[18077]: Consent given - collect udev crash info.
2016-08-30T13:48:32.242320-04:00 INFO kernel: [  983.121897] [drm] RC6 on
2016-08-30T13:48:35.209770-04:00 INFO crash_reporter[18077]: Log command "  echo "===i915/parameters===";   grep '' /sys/module/i915/parameters/* |     sed -e 's!^/sys/module/i915/parameters/!!';   for dri in /sys/kernel/debug/dri/*; do 
    echo "===$dri/i915_error_state===";     cat $dri/i915_error_state;     echo "===$dri/i915_capabilities===";     cat $dri/i915_capabilities;     echo "===$dri/i915_wa_registers===";     cat $dri/i915_wa_registers;   done" exited with 
1
2016-08-30T13:48:35.209791-04:00 ERR crash_reporter[18077]: Error reading udev log info crash_reporter-udev-collection-change-card0-drm
2016-08-30T13:48:36.242810-04:00 INFO kernel: [  987.123183] [drm] stuck on render ring
2016-08-30T13:48:36.263945-04:00 INFO crash_reporter[18101]: Consent given - collect udev crash info.


2016-08-30T13:49:09.282118-04:00 INFO kernel: [ 1020.176626] Watchdog[2489]: segfault at 0 ip 00007fb896f4fbe3 sp 00007fb892b1e6e0 error 6 in chrome[7fb895a8d000+6585000]
2016-08-30T13:49:09.299459-04:00 WARNING crash_reporter[18223]: [user] Received crash notification for chrome[2436] sig 11, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2016-08-30T13:49:09.310131-04:00 WARNING crash_reporter[18225]: Received crash notification for chrome[2436] user 1000 (called directly)
Comment 1 Chris Wilson 2016-08-30 19:52:40 UTC
The kernel is broken, the bsd ring was not advanced correctly. Please report this to the maintainer of that kernel.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.