| Summary: | card detects non-existent monitor on display port | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Daniel <danadam7> | ||||||||||
| Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||||
| Severity: | normal | ||||||||||||
| Priority: | medium | ||||||||||||
| Version: | unspecified | ||||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Daniel
2016-09-19 00:41:16 UTC
Please attach your full xorg log and dmesg output. Created attachment 126639 [details]
dmesg, kernel 4.5.0-1, debug
Created attachment 126640 [details]
xorg, kernel 4.5.0-1
Created attachment 126641 [details]
dmesg, kernel 4.5.0-2, debug
Created attachment 126642 [details]
xorg, kernel 4.5.0-2
I'm seeing this as well (on mobile Kaveri), but I think it's more likely a kernel driver issue. E.g. I only noticed this a few months ago, but I can reproduce it with xf86-video-ati 7.6.1, which was released almost a year ago. Can you try older kernels? If it doesn't happen with an older kernel, can you narrow it down to at least the kernel version which introduced it, or ideally bisect the Git commit which did? > can you narrow it down to at least the kernel version which introduced it
But I did, in my description: "Since kernel 4.5.0-2 my Xorg.0.log shows that something is also connected to display port...".
Up to 4.5.0-1 everything was fine.
(In reply to Daniel from comment #7) > But I did, in my description: "Since kernel 4.5.0-2 my Xorg.0.log shows that > something is also connected to display port...". > > Up to 4.5.0-1 everything was fine. Oops, sorry, I somehow missed that before. :( I think the most likely culprit is https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ff0bd441bdfbfa09d05fdba9829a0401a46635c1 then, or maybe https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1a738347df2ee4977459a8776fe2c62196bdcb1b Can you try if reverting either of those fixes the problem? Alex, any ideas? (In reply to Michel Dänzer from comment #8) > (In reply to Daniel from comment #7) > > But I did, in my description: "Since kernel 4.5.0-2 my Xorg.0.log shows that > > something is also connected to display port...". > > > > Up to 4.5.0-1 everything was fine. > > Oops, sorry, I somehow missed that before. :( > > I think the most likely culprit is > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/ > ?id=ff0bd441bdfbfa09d05fdba9829a0401a46635c1 > I doubt this is the culprit. The link training parameters aren't used until a monitor is already detected. This wouldn't result in a fake monitor showing up. > then, or maybe > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/ > ?id=1a738347df2ee4977459a8776fe2c62196bdcb1b That is a possibility. > > Can you try if reverting either of those fixes the problem? > > Alex, any ideas? Maybe some core drm/dp change? Any chance you could bisect? (In reply to Alex Deucher from comment #9) > Maybe some core drm/dp change? Any chance you could bisect? I can try, but probably not before next week. FWIW, according to the attached dmesg outputs, the regression happened between upstream versions 4.5.1 and 4.5.5. (In reply to Alex Deucher from comment #9) > > [...] or maybe > > > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/ > > ?id=1a738347df2ee4977459a8776fe2c62196bdcb1b > > That is a possibility. Indeed, reverting just this change fixes the problem for me. |
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.