I have Thinkpad X230 and the external monitor support was working well on 3.10-3-amd64. Thinkpad external monitor settings are supposed to be controlled using Fn+F7 shortcut. You can switch between single monitor (external or laptop only), two monitors cloning each other and two monitors extending each other. On 3.16-2-amd64 this shortcut is not working properly. I can switch the modes like before but only one external monitor is showing picture (on the modes it is supposed to show picture). After switching the Fn+F7 cycle (pressing 5-6 times to complete one cycle) over one or two times Gnome freezes and I have to restart my computer. I had to downgrade back to 3.10-3-amd64 to be able to work normally with two extending each other. I'm running Debian (testing).
What video is present - Intel or AMD ?
> What video is present - Intel or AMD ? lspci | grep VGA: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
Please post dmesg with drm.debug=14, all the way from boot to the problem (trying the key combo), for both 3.10 and 3.16.
Sorry for the delay Jani. Here is dmesg with 3.10: http://pastebin.com/9dwy9ks3 Here is dmesg with 3.16: http://pastebin.com/tYxwtDTs Just ask if you need any more info, I'll try to be faster next time.
dp aux seems to get pissed in 3.16 and worked in 3.10. Backtraces look like mostly fallout from that (plus more paranoid checks). But an awful lot happened in that timeframe, so can you please try to bisect which exact commit introduced this regression? That usually helps a lot in tracking such bugs down.
(In reply to Daniel Vetter from comment #5) > dp aux seems to get pissed in 3.16 and worked in 3.10. Backtraces look like > mostly fallout from that (plus more paranoid checks). > > But an awful lot happened in that timeframe, so can you please try to bisect > which exact commit introduced this regression? That usually helps a lot in > tracking such bugs down. Ping for either a bisect or a test on the most recent kernels. An awful lot has also happened since 3.16...
Timeout. Please reopen if the problem persists with new kernels.