| Summary: | [BAT][SKL] Serial console hung in kms_flip when running IGT | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Tomi Sarvela <tomi.p.sarvela> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | CLOSED INVALID | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | DRI git | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | SKL | i915 features: | |
|
Description
Tomi Sarvela
2017-03-17 16:04:33 UTC
Each character has a 1s timeout in wait_for_xmitr. If the string was log enough and the serial console bust, it can easily appear to be hung. As wait_for_xmitr keeps poking the nmi watchdog. the slow loop will not be caught. If that is correct, this appears to be a hw issue. An alternative hypothesis is that the usb device struct sent garbage to be printed and it really is stuck printing out all of memory, 1 character at a time. Kasan might help. I don't think the vtcon switch of modes is significant. What would be useful is the dmesg before to see if we can identify what usb event triggered. (In reply to Chris Wilson from comment #1) > Each character has a 1s timeout in wait_for_xmitr. If the string was log > enough and the serial console bust, it can easily appear to be hung. As > wait_for_xmitr keeps poking the nmi watchdog. the slow loop will not be > caught. If that is correct, this appears to be a hw issue. > > An alternative hypothesis is that the usb device struct sent garbage to be > printed and it really is stuck printing out all of memory, 1 character at a > time. Kasan might help. > > I don't think the vtcon switch of modes is significant. > > What would be useful is the dmesg before to see if we can identify what usb > event triggered. Hello, Is this bug still valid? If so, could you attach the dmesg mentioned before or any other relevant information? Thank you. Hello, I asked Tomi about this case. The problem couldn't be reproduced again, if this is pointed up again it will be reopened. Thank you. |
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.