From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Chris Chiu <chris.chiu@canonical.com>
Cc: andreas.noever@gmail.com, michael.jamet@intel.com,
YehezkelShB@gmail.com, linux-usb@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Discrete Thunderbold Controller 8086:1137 throws DMAR and thunderbolt fails to work
Date: Mon, 13 Dec 2021 08:11:21 +0200 [thread overview]
Message-ID: <YbbkCdUKwgB0P6y3@lahna> (raw)
In-Reply-To: <CABTNMG1-ZzoKr024G1beGdZyNONbRp0_1mpeTRnDXcEuE_VNkA@mail.gmail.com>
On Mon, Dec 13, 2021 at 01:37:10PM +0800, Chris Chiu wrote:
> On Thu, Dec 9, 2021 at 5:39 PM Chris Chiu <chris.chiu@canonical.com> 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
> >
> > Chris
>
> Gentle ping. Mika, could you give some advice on this? Thanks
Hm, didn't I already answered?
https://lore.kernel.org/linux-usb/YbHVryQ+QTnyMmTB@lahna/
prev parent reply other threads:[~2021-12-13 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 9:39 Discrete Thunderbold Controller 8086:1137 throws DMAR and thunderbolt fails to work Chris Chiu
2021-12-09 10:08 ` Mika Westerberg
2021-12-13 5:37 ` Chris Chiu
2021-12-13 6:11 ` Mika Westerberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YbbkCdUKwgB0P6y3@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=chris.chiu@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.