linux-kernel - Re: Discrete Thunderbold Controller 8086:1137 throws DMAR and thunderbolt fails to work

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 9 Dec 2021 12:08:47 +0200
From:   Mika Westerberg <mika.westerberg@...ux.intel.com>
To:     Chris Chiu <chris.chiu@...onical.com>
Cc:     andreas.noever@...il.com, michael.jamet@...el.com,
        YehezkelShB@...il.com, linux-usb@...r.kernel.org,
        Linux Kernel <linux-kernel@...r.kernel.org>,
        Lu Baolu <baolu.lu@...ux.intel.com>
Subject: Re: Discrete Thunderbold Controller 8086:1137 throws DMAR and
 thunderbolt fails to work

[+Baolu]

Hi,

On Thu, Dec 09, 2021 at 05:39:41PM +0800, Chris Chiu wrote:
> Hi,
>     We created a ticket
> https://bugzilla.kernel.org/show_bug.cgi?id=215265 that is pretty
> similar to https://bugzilla.kernel.org/show_bug.cgi?id=214259. So I
> tried the patch on https://lkml.org/lkml/2020/6/17/751 but it doesn't
> fix the issue. I also tried to boot with the kernel parameter
> `pci=nocrs` but it changed nothing either. I attached the kernel log
> with thunderbolt dynamic debug on and lspci output on the ticket. Also
> tried to disable the intel_iommu, the DMAR failure seems to go away
> but thunderbolt still fails to work. Can anyone suggest what kind of
> information is required to help identify the cause of the problem?
> Thanks

At least the RTX370 log seem to have lots of issues, not just
Thunderbolt. The PCIe root port has AER enabled and it seems to be
getting errors from the Maple Ridge card. Typically using AER with
hotpluggable PCIe devices is not a good idea.

Can you get rid of the patch that adds these:

  arch_remove_reservations remove e820 region

and boot with "intel_iommu=off", and provide full dmesg? Did not find
one from the bugzilla bug.

Also does the USB 3.x work? I mean if you have IOMMU enabled and you
plug in USB 3.x device does that work, or you get similar DMAR faults?

Alos is this a production system and do you have installed the latest
firmware upgrades?