lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 13 Mar 2015 23:19:51 -0400
From:	Paul Moore <paul@...l-moore.com>
To:	Dave Airlie <airlied@...hat.com>, intel-gfx@...ts.freedesktop.org
Cc:	linux-kernel@...r.kernel.org
Subject: Commit 0e32b39c ("drm/i915: add DP 1.2 MST support (v0.7)") breaking
 DP audio on T440s

Ever since v3.17 I've had a problem with displayport audio on my
system, but until lately I haven't had a chance to bisect the problem.
After a few rounds I've isolated the buggy commit to 0e32b39c
("drm/i915: add DP 1.2 MST support (v0.7)").

Simply put, prior to v3.17 everything worked correctly: audio from my
system was routed to my monitor via the DP connection and finally out
to the speakers connected to the monitor.  However, starting with
kernel v3.17 this no longer works.  The various PulseAudio tools all
indicate that the HDMI/DP audio output is unplugged/not-available.
I've tried a few different xrandr commands found via google and
manpages but nothing short of reverting to v3.16 solves the problem.
I'm hoping that someone with more understanding of the Intel graphics
drivers will be able to make some sense of it all and provide a fix.
I'm more than happy to provide additional information and test any
patches you may have.

For reference, my system is a ThinkPad T440s with a "Intel Corporation
Haswell-ULT Integrated Graphics Controller (rev 0b)" (according to
lspci) connected to a Dell U3011 via a Gefen DP KVM.

-Paul

-- 
paul moore
www.paul-moore.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists