linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>, email-ext@laposte.net
Subject: [bugzilla-daemon@bugzilla.kernel.org: [Bug 206657] New: Lenovo C940 freeze during Thunderbolt3 dock connection/disconnection unless plugged before boot]
Date: Mon, 24 Feb 2020 18:00:45 -0600	[thread overview]
Message-ID: <20200225000045.GA153739@google.com> (raw)

----- Forwarded message from bugzilla-daemon@bugzilla.kernel.org -----

Date: Mon, 24 Feb 2020 20:55:05 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: bjorn@helgaas.com
Subject: [Bug 206657] New: Lenovo C940 freeze during Thunderbolt3 dock
	connection/disconnection unless plugged before boot
Message-ID: <bug-206657-41252@https.bugzilla.kernel.org/>

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

            Bug ID: 206657
           Summary: Lenovo C940 freeze during Thunderbolt3 dock
                    connection/disconnection unless plugged before boot
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.6-rc2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: PCI
          Assignee: drivers_pci@kernel-bugs.osdl.org
          Reporter: email-ext@laposte.net
        Regression: No

Created attachment 287591
  --> https://bugzilla.kernel.org/attachment.cgi?id=287591&action=edit
Dmesg log when disconnecting dock

Hello,

I have a Lenovo C940 under Manjaro with unstable packages and Kernel 5.6-rc2
using a OWC Thunderbolt3 dock. If I connect the dock before boot, it will work
correctly. However, if a connect/disconnect it after boot it won't be recognize
and will lead soon after to system crash. The gnome icons start to disappear
and when using commands on terminal input/output failure errors appear.

I found another bug which seems related to mine, but in my case it leads to
system crash:
https://bugzilla.kernel.org/show_bug.cgi?id=206459. 

I am encountering another problem with USB-C drive on thunderbolt3 ports
working if connected before boot and not otherwise. But without leading to
system crash:
https://bugzilla.kernel.org/show_bug.cgi?id=206649

I joined dmesg where disconnection starts at time 185 with some errors occuring
just after like:
[  184.038519] usb usb6: USB disconnect, device number 1
[  184.038523] usb 6-3: USB disconnect, device number 2
[  184.167256] usb 5-4: Not enough bandwidth for altsetting 1
[  184.167260] usb 5-4: 1:1: usb_set_interface failed (-19)

Also the journalctl shows some errors:

fév 23 17:55:06 pc-de-user kernel: usb usb6: USB disconnect, device number 1
fév 23 17:55:06 pc-de-user kernel: usb 6-3: USB disconnect, device number 2
fév 23 17:55:06 pc-de-user kernel: usb 5-4: Not enough bandwidth for altsetting
1
fév 23 17:55:06 pc-de-user kernel: usb 5-4: 1:1: usb_set_interface failed (-19)

Then the system crashes showing "input/output failures" just by using some
commands like "ls" or "cat".

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

----- End forwarded message -----

                 reply	other threads:[~2020-02-25  0:00 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=20200225000045.GA153739@google.com \
    --to=helgaas@kernel.org \
    --cc=email-ext@laposte.net \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.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 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).