From: Bjorn Helgaas <helgaas@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-usb@vger.kernel.org,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: Dell XPS 13 9360/Dell DA300: USB Type-C: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Date: Tue, 13 Sep 2022 15:53:55 -0500 [thread overview]
Message-ID: <20220913205355.GA622822@bhelgaas> (raw)
In-Reply-To: <ae28dabe-d339-b56d-4a8e-ce4291c9b836@molgen.mpg.de>
On Mon, Sep 12, 2022 at 03:36:09PM +0200, Paul Menzel wrote:
> Dear Linux folks,
>
>
> On a Dell XPS 13 9360/0596KF, BIOS 2.21.0 06/02/2022, connect a Dell DA300
> to the only USB Type-C port on the left side (with a network cable connect),
> Linux logs the warnings below:
> Linux version 5.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 11.3.0-5) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.6-1 (2022-09-01)
> [ 5.710957] pci 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
> [ 5.710959] pci 0000:01:00.0: device [8086:1576] error status/mask=00000080/00002000
> [ 5.710962] pci 0000:01:00.0: [ 7] BadDLLP
Your dmesg log has many (51!) BadDLLP errors (which are corrected) and
one Replay Timer Timeout error (also corrected). I'm not a hardware
person, but I don't know how software could cause these errors.
Unless this is a regression, I suspect a hardware issue like a bad
cable or connector.
> I created the bug report #216474 [1] with the output of `lspci -nn`, `lsusb`
> and `dmesg`.
>
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=216474
> "Bug 216474 - Dell XPS 13 9360/Dell DA300: USB Type-C: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)"
prev parent reply other threads:[~2022-09-13 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 13:36 Dell XPS 13 9360/Dell DA300: USB Type-C: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Paul Menzel
2022-09-12 13:53 ` Heikki Krogerus
2022-09-12 13:59 ` Paul Menzel
2022-09-13 20:53 ` Bjorn Helgaas [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=20220913205355.GA622822@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox