From: bugzilla-daemon@bugzilla.kernel.org
To: bugzilla.pci@gmail.com
Subject: [Bug 199631] New: WARNING: at drivers/thunderbolt/switch.c:587 tb_switch_add+0x63e/0x730 [thunderbolt]
Date: Sun, 06 May 2018 05:20:27 +0000 [thread overview]
Message-ID: <bug-199631-193951@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=199631
Bug ID: 199631
Summary: WARNING: at drivers/thunderbolt/switch.c:587
tb_switch_add+0x63e/0x730 [thunderbolt]
Product: Drivers
Version: 2.5
Kernel Version: 4.17.0-0.rc3.git4.1.fc29.x86_64
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PCI
Assignee: drivers_pci@kernel-bugs.osdl.org
Reporter: bugzilla@colorremedies.com
Regression: No
Soon after boot, I'm getting a warning and a call trace
[ 36.051674] thunderbolt 0000:03:00.0: timeout reading config space 1 from
0x36
[ 36.051757] ------------[ cut here ]------------
[ 36.051769] thunderbolt 0000:03:00.0: 0:1: non switch port without a PHY
[ 36.051881] WARNING: CPU: 3 PID: 1511 at drivers/thunderbolt/switch.c:587
tb_switch_add+0x63e/0x730 [thunderbolt]
Does not happen with 4.16.6.
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2018-05-07 14:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-199631-193951@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=bugzilla.pci@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox