Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751139AbcDGE0Z (ORCPT ); Thu, 7 Apr 2016 00:26:25 -0400 Received: from mail-wm0-f41.google.com ([74.125.82.41]:38034 "EHLO mail-wm0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750760AbcDGE0X (ORCPT ); Thu, 7 Apr 2016 00:26:23 -0400 To: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org From: "Alexander E. Patrakov" Subject: Haswell IOMMU bug that gets no response from maintainers Message-ID: <5705E16B.3070401@gmail.com> Date: Thu, 7 Apr 2016 09:26:19 +0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 723 Lines: 19 Hello. In August 2013, I have reported this bug: https://bugzilla.kernel.org/show_bug.cgi?id=60769 . It has been determined on October 2013 to be a bug with IOMMU. The bug manifests itself as either unreliable or completely non-working HDMI audio on Haswell systems. However, there have been no reaction of IOMMU experts to the bug, except two messages from David Woodhouse in November 2013. On PulseAudio mailing list and IRC channel we still have affected users (who blame PulseAudio and thus spread FUD), and I myself have to apply the "iommu=on,igfx_off" workaround. Where and how do I escalate the bug? What other info (except DMAR dumps which are already in the bug) is needed? -- Alexander E. Patrakov