Bug#699815: linux-image-3.7-trunk-amd64: kernel call trace in dmesg when trying to use HDMI video output via xrandr

["K. Posern" <quickhelp@gmail.com>]

Thanks!

I was at my parents home when the bug occured.
Now I am back home and I realized that I don't have any HDMI display I 
could use to do further tests :/
I will try going into a shop and "try out" an HDMI display ;)
I hope I can get that done in the next 1 or 2 days.

On 11/02/13 02:24, Ben Hutchings wrote:
> Control: tag -1 upstream moreinfo
>
> On Tue, 2013-02-05 at 16:03 +0100, K. Posern wrote:
> > Package: src:linux
> > Version: 3.7.3-1~experimental.1
> > Severity: normal
> >
> > Dear Maintainer,
> > *** Please consider answering these questions, where appropriate ***
> >
> >      * What led up to the situation?
> >      Trying to display my notebook screen via HDMI on a television.
> >
> >      * What exactly did you do (or not do) that was effective (or
> >        ineffective)?
> > Plugging HDMI video target (external monitor) to HDMI port.
> >       xrandr -q
> > Shows everything fine - the HDMI target monitor with the supported
> > resolutions get recognized correctly
> > ... but the moment I try to /use/ it (as clone or not) via:
> >
> >       XFCE + xrandr --output HDMI1 --right-of eDP1
> >           or
> >       XFCE + xrandr --output HDMI1 --auto --right-of eDP1
> >           or
> >       XFCE + xrandr --output HDMI1 --mode 1920x1080 --right-of eDP1
> >           or
> >       KDE + its configurator that popped up when plugging in the HDMI
> >
> >      * What was the outcome of this action?
> >      Nothing visibly changed at some point I got the feeling there might
> > have been an impact on the main display (eDP1)... but not sure.
> >      For sure: Nothing appeared on the HDMI device!
> >
> >      And dmesg showed this call trace everytime I tried (e.g. issued a
> > new xrandr command)!
> >           http://paste.debian.net/231934/
> [...]
>
> Please report this upstream at <https://bugs.freedesktop.org/> under
> product 'DRI', component 'DRM/Intel'.
>
> But before you do that, you should gather some more debugging
> information from the driver: boot with the added kernel parameter
> 'drm.debug=0xe', try to enable the HDMI monitor, and then save the
> output of dmesg.
>
> Let us know the URL of the upstream bug report so we can track it.
>
> Ben.