From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Dell XPS 13 9360/Dell DA300: USB Type-C: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Date: Mon, 12 Sep 2022 15:59:09 +0200 [thread overview]
Message-ID: <cd8d05ba-8bf4-486e-3e5d-9afb68698555@molgen.mpg.de> (raw)
In-Reply-To: <Yx858docsDh/ARiL@kuha.fi.intel.com>
Dear Heikki,
Am 12.09.22 um 15:53 schrieb Heikki Krogerus:
> On Mon, Sep 12, 2022 at 03:36:09PM +0200, Paul Menzel wrote:
>> 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:
>
>> [ 18.895120] ucsi_acpi USBC000:00: UCSI_GET_PDOS returned 0 bytes
>
> This warning you already reported [1]. I will send a patch for this
> once I'm sure I understand what's going on. I'm fairly sure I now know
> what is causing that, but I will still run a few more tests to be
> absolutely sure.
>
> The warning is in any case not critical.
The line slipped through. Sorry for the noise, and thank you for your
reply. This thread was supposed to be for the PCIe bus errors.
Kind regards,
Paul
> [1] https://lore.kernel.org/linux-usb/726661bf-b95f-02fc-e7c5-c222820ee257@molgen.mpg.de/
next prev parent reply other threads:[~2022-09-12 13:59 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 [this message]
2022-09-13 20:53 ` Bjorn Helgaas
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=cd8d05ba-8bf4-486e-3e5d-9afb68698555@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=bhelgaas@google.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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