[Samus/Paine/Lulu/Relm] DisplayLinkManager crashes triggered when inducing kernel crash |
||||||||||||
Issue description<b>Version: <Kenneth, what is the frequency?></b> <b>OS: <please tell me it's not XP></b> What steps will reproduce the problem? (1) Sign in (2) Run "echo BUG > /sys/kernel/debug/provoke-crash/DIRECT" (3) Check log under /var/spool/crash What is the expected output? should only see kernel crash with no other crashes should be triggered What do you see instead? DisplayLinkManager crash dump are triggered Always on Samus Mighty, sentry, terra have no problem. Feedback log: https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lRFilter=1&lReportSearch=user:helenztest&lROrder=2&lReport=8182531987 Crash report: https://crash.corp.google.com/browse?stbtiq=8EAAA9D109FC40ED939E4DC159EEC18A
,
Apr 22 2016
,
May 16 2016
We may want to put this into the partner tracker so the DisplayLink folks can take a look at it easily. If this is triggered by inducing a kernel crash, is there any real user facing concern here? Perhaps this is not really a stable blocker?
,
May 16 2016
I don't follow - a kernel bug should result in a machine reboot. It doesn't happen when you do it manually?
,
May 24 2016
Removing releaseblock-stable as this does not appear to have any direct user consequences, this sounds like more of an annoyance in the case a kernel crash making DLM look suspect.
,
May 24 2016
,
Jun 2 2016
,
Jun 2 2016
still reproducible in ChromeOS 8172.47.0, 51.0.2704.79
,
Jun 23 2016
the issue can be seen in M51-8172.60.0 / 51.0.2704.103 on Paine too: https://crash.corp.google.com/browse?stbtiq=5ab783e600000000
,
Jul 14 2016
reproducible on Lulu in 8350.55.0/52.0.2743.75 https://crash.corp.google.com/browse?stbtiq=ac451f0200000000
,
Aug 2 2016
reproducible in relm in ChromeOS M-52 8350.66.0, 52.0.2743.113. one of displaylink crash : https://crash.corp.google.com/browse?stbtiq=c64af57e00000000
,
Feb 17 2017
,
Mar 18 2017
Activating. Please assign to the right owner and the appropriate priority.
,
Apr 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by helenzhang@google.com
, Apr 22 2016