| Summary: | [ILK regression] Change from X-window to text terminal causes Call Trace | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | cancan,feng <cancan.feng> | ||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Severity: | major | ||||||
| Priority: | medium | CC: | cancan.feng | ||||
| Version: | unspecified | ||||||
| Hardware: | Other | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
cancan,feng
2013-03-27 06:07:36 UTC
Additional information: ----------------------------- Platform: Calpella This issue happens when eDP and DP both plugged in, but it will go away if unplug DP. I never tested this with DP and eDP both plugged in before. So I'm sorry I can't find a good commit though I have back to kernel 3.8.. There seem to be two things: The WARN about pipe_wait_off timeout is probably old and a dupe of bug #54687. But the link train failure is a bit more ugly. Can you please test whether reverting commit 3b4f819d5eac94ba8fe5e8c061f6dabfe8d7b22c Author: Takashi Iwai <tiwai@suse.de> Date: Mon Mar 11 18:40:16 2013 +0100 Revert "drm/i915: try to train DP even harder" improves the situation? (In reply to comment #2) > There seem to be two things: The WARN about pipe_wait_off timeout is > probably old and a dupe of bug #54687. But the link train failure is a bit > more ugly. Can you please test whether reverting commit > 3b4f819d5eac94ba8fe5e8c061f6dabfe8d7b22c Author: Takashi Iwai > <tiwai@suse.de> Date: Mon Mar 11 18:40:16 2013 +0100 Revert > "drm/i915: try to train DP even harder" improves the situation? I test what you said, but it doesn't improve the situation, Call Trace still there. :'( If you need any special information, just to let me know. Just to check: Is there anything broken (DP screen not working) or is the issue just the WARN backtrace? (In reply to comment #4) > Just to check: Is there anything broken (DP screen not working) or is the > issue just the WARN backtrace? After call trace, I can chvt to X window, then do glxgears, then chvt to text terminal, all of these seem no problem but call trace. So is this just a WARN backtrace? If the training failure is just a red herring, let's just treat this as a simple dupe. *** This bug has been marked as a duplicate of bug 54686 *** Sorry, Chris, but I really don't think you intended to mark this bug as a duplicate of bug 54686. Or is there something with percent signs in LibreOffice that the Intel driver does not like? ;-) *** This bug has been marked as a duplicate of bug 54687 *** Closing verified+duplicate as duplicate of closed+fixed. |
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.