linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216474] Dell XPS 13 9360/Dell DA300: USB Type-C: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Date: Thu, 29 Dec 2022 08:22:44 +0000	[thread overview]
Message-ID: <bug-216474-208809-DCIdyojnTp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216474-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216474

Frederick Zhang (frederick888@tsundere.moe) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |frederick888@tsundere.moe

--- Comment #1 from Frederick Zhang (frederick888@tsundere.moe) ---
I recently purchased a Thunderbolt 4 dock and started seeing something similar
with 6.0 & 6.1 kernels on my Thinkpad.

Dec 29 18:51:05 FredArch systemd[1]: Starting System Suspend...
Dec 29 18:51:05 FredArch systemd-sleep[31007]: Entering sleep state
'suspend'...
Dec 29 18:51:05 FredArch kernel: PM: suspend entry (s2idle)
Dec 29 18:51:07 FredArch kernel: Filesystems sync: 1.566 seconds
Dec 29 18:52:30 FredArch kernel: Freezing user space processes ... (elapsed
0.001 seconds) done.
Dec 29 18:52:30 FredArch kernel: OOM killer disabled.
Dec 29 18:52:30 FredArch kernel: Freezing remaining freezable tasks ...
(elapsed 0.001 seconds) done.
Dec 29 18:52:30 FredArch kernel: printk: Suspending console(s) (use
no_console_suspend to debug)
Dec 29 18:52:30 FredArch kernel: ACPI: EC: interrupt blocked
Dec 29 18:52:30 FredArch kernel: ACPI: EC: interrupt unblocked
Dec 29 18:52:30 FredArch kernel: pcieport 0000:00:1d.0: AER: Multiple Corrected
error received: 0000:21:01.0
Dec 29 18:52:30 FredArch kernel: pcieport 0000:21:01.0: PCIe Bus Error:
severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 29 18:52:30 FredArch kernel: pcieport 0000:21:01.0:   device [8086:1136]
error status/mask=00001100/00002000
Dec 29 18:52:30 FredArch kernel: pcieport 0000:21:01.0:    [ 8] Rollover
Dec 29 18:52:30 FredArch kernel: pcieport 0000:21:01.0:    [12] Timeout
Dec 29 18:52:30 FredArch kernel: pcieport 0000:21:01.0: AER:   Error of this
Agent is reported first
Dec 29 18:52:30 FredArch kernel: pcieport 0000:23:00.0: PCIe Bus Error:
severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 29 18:52:30 FredArch kernel: pcieport 0000:23:00.0:   device [8086:0b26]
error status/mask=00001000/00002000
Dec 29 18:52:30 FredArch kernel: pcieport 0000:23:00.0:    [12] Timeout
Dec 29 18:52:30 FredArch kernel: pcieport 0000:00:1d.0: AER: Corrected error
received: 0000:21:01.0
Dec 29 18:52:30 FredArch kernel: pcieport 0000:21:01.0: PCIe Bus Error:
severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 29 18:52:30 FredArch kernel: pcieport 0000:21:01.0:   device [8086:1136]
error status/mask=00001100/00002000
Dec 29 18:52:30 FredArch kernel: pcieport 0000:21:01.0:    [ 8] Rollover
Dec 29 18:52:30 FredArch kernel: pcieport 0000:21:01.0:    [12] Timeout

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2022-12-29  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 12:52 [Bug 216474] New: Dell XPS 13 9360/Dell DA300: USB Type-C: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) bugzilla-daemon
2022-12-29  8:22 ` bugzilla-daemon [this message]
2022-12-29  8:27 ` [Bug 216474] " bugzilla-daemon
2022-12-29 12:14 ` bugzilla-daemon
2022-12-29 12:19 ` bugzilla-daemon
2022-12-29 13:13 ` bugzilla-daemon
2024-02-07 19:27 ` bugzilla-daemon

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=bug-216474-208809-DCIdyojnTp@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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;
as well as URLs for NNTP newsgroup(s).