Public bug reported:
After some time in sleep mode, the laptop turns off completely and the
session lost with all program crashed.
When the laptop starts again, I have to log in to a new session.
This may be related to the fact that the laptop dual-boots Windows 8.1
pro that is configured to
I've tried running the mainline 3.19, and it exhibits the same problem -
though when the system comes up after a failed sleep, the error reporter
says that I can't report problems with mainline kernels and opens up the
kernel bug tracker :-)
--
You received this bug notification because you are
This seems to be a firmware / hardware issue with Dell Laptops - the
BIOS reports ASF2 force off events when these shutdown happens, which
is a problem experienced by many other Dell customers, as can be seen
here - http://en.community.dell.com/support-
forums/laptop/f/3518/t/19612919 - and
Sorry, I missed the important line from the dmesg log. It should be:
[72735.678702] xhci_hcd :0e:00.0: ERROR unknown event type 15
[72740.609531] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint
command.
[72740.609850] xhci_hcd :0e:00.0: xHCI host controller not
I've been running a few days now with the main line kernel 4.18.3 (from
Ubuntu's main line kernel downloads), and I just got this again:
[72740.609531] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint
command.
[72740.609850] xhci_hcd :0e:00.0: xHCI host controller not
Apparently there's a firmware update (I was running 1.10, which is about
a month old - I've updated the firmware several times during the life
time of this bug). I'll update and wait for it to happen again.
BTW - the behavior is usually that after this disconnect happens once, I
can reset the USB
I had to downgrade the BIOS back to 1.10.1 (fwupdmgr installed 1.11) as
under the new firmware suspend to RAM caused the system to completely
power off (i.e. boot from scratch when powering on). I'll try to update
again when the new update is released on Dell's website (the current
version on the
The last TB firmware was released 2018-04, and it is up to date (also
according to fwupdmgr).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766076
Title:
USB over thunderbolt turns
Public bug reported:
I'm using a USB hub in the Dell TB16 (240W) connected to a Dell
Precision 5520 using Thunderbolt 3.
Every so often (can be several times in an hour if I'm really unlucky,
some days it is less of a problem), the USB hub disconnects from the
computer and the devices connected
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125523/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125526/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125521/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766076
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125529/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125528/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125522/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125527/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
I'm using a USB hub in the Dell TB16 (240W) connected to a Dell
Precision 5520 using Thunderbolt 3.
Every so often (can be several times in an hour if I'm really unlucky,
some days it is less of a problem),
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125524/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766076
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125525/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125532/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125531/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125530/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1766076/+attachment/5125533/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I had this issue previously under Zesty and I think it was gone under
Artful (though I'm not sure - the dock started having hardware issues at
that point). I just upgraded to Bionic *and* got a new dock, and almost
immediately started having these issues.
I'll try the mainline build tomorrow.
--
Just got hit with the problem again, after the 1.11.0 firmware upgrade,
on Cosmic:
[428188.916420] xhci_hcd :0e:00.0: ERROR unknown event type 15
[428193.955247] xhci_hcd :0e:00.0: xHCI host not responding to stop
endpoint command.
[428193.955570] xhci_hcd :0e:00.0: xHCI host
On my system, the Precision 5520 is powered by the TB16 dock.
I have updated the firmware to 1.11.0 a couple of days ago, and so far
no crashes - though there have been stretches of weeks in the past
without a crash. I'll update the next time it does stop working.
--
You received this bug
I'm using the USB port at the back on the TB16, chained through a couple
of Dell U2718Q to a Logitech unified receiver and a Das Keyboard
(original) and a few USB cables that get attached to various Android and
iOS devices from time to time, though most issues occur when no phone
device is
Ah, in addition to the USB port, I'm also using:
- 2 display ports (to the screens), though these continue to work even when
xhci break.
- The gigabit ethernet port
- The audio out port
I'm attaching the kernel log that includes the discovery of the dock
during resume from suspend (minus a lot
Just got the issue again with latest Bionic kernel (Precision 5520 +
TB16):
[253938.395439] xhci_hcd :0e:00.0: ERROR unknown event type 15
[253943.344375] xhci_hcd :0e:00.0: xHCI host not responding to stop
endpoint command.
[253943.344704] xhci_hcd :0e:00.0: xHCI host controller not
BTW, I think this is a problem specifically with Dell custom thunderbolt
docs - they do a bit more than straight forward TB3 docs, at the minimum
they have overspeced power output to handle Precisions' huge power
budget, but maybe they do more stuff?
I also run my Precision with a standard TB3
I've been running disco for a while with `generic` Ubuntu kernel 5.0.0
(currently 5.0.0-8), and I haven't experienced that problem for a while.
I still get some USB issues from time to time with the Dell dock - where
the USB does not connect when I plug the dock to the laptop, at which
point I
My current complete workaround is documented here:
https://gist.github.com/guss77/1356e5f3be4f2acbc73053cc6d3c0b1c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766076
Title:
USB over
I haven't had that issue for a while, since kernel 4.20, I think, but I
just had this issue again, on up to date 19.04 with kernel 5.0.0-13:
[376539.800632] xhci_hcd :0e:00.0: ERROR unknown event type 15
[376544.914548] xhci_hcd :0e:00.0: xHCI host not responding to stop
endpoint
I just went back to using my Precision 5520 with the TB16 dock, after
that duo was benched for a few months while I waited for a replacement
battery to be shipped, and now the situation is similar but worse:
Every time I connect the dock cable, Linux tries to attached the USB
hub, fails and
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311961/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311957/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311956/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311959/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311958/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311963/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311962/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311964/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311960/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The delay to connect the USB devices seems to be a feature of the new
firmware or something - on MS-Windows it takes even longer, about 30
seconds for all the devices to finish connecting. Could it be that the
xhci_hcd failure is caused by the fact that the dock is now so slow to
respond?
Anyway,
apport information
** Tags added: apport-collected
** Description changed:
Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell
Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB
bus connects very slowly (15~20 seconds) and sometimes does not connect
Public bug reported:
Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell
Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB
bus connects very slowly (15~20 seconds) and sometimes does not connect
at all and a failure is reported in dmesg:
[ 117.834621]
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311955/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856161
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311953/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311952/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311951/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856161
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1856161/+attachment/5311954/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856161
with the lp1766076 kernel, removing all the parameters after "quiet"
(I'm thinking the ones before that are required for successful boot),
the thunderbolt connects successfully on boot.
Attached dmesg log.
** Attachment added: "lp1766076-boot-dmesg-tbconnected.log"
Also connect/disconnect succeeds. See attached logs.
There are other problems now, which the kernel flags were supposed to
solve. I'd need to reboot a few times to figure out which flag causes
the problem.
** Attachment added: "lp1766076-tb-reconnect-success.log"
What I currently do, is to detach the USB cable from the dock, connect
the thunderbolt cable to the computer, wait for everything to settle
(either by looking at the dmesg log or just waiting for the dock audio
device to be registered - which shows on the OSD), then connecting the
USB cable. See
Sorry, the joy was (relatively) short-lived: Even with
`/etc/default/grub` `GRUB_CMDLINE_LINUX_DEFAULT` setting set to empty, I
can still reproduce this problem with the lp1766076 kernel: it
definitely happens less - maybe 1 in 3 times instead of almost always -
but it still happens.
Here's a
The current situation is that I can't use the thunderbolt dock's USB hub
normally: it almost always fails to connect - with the generic Ubuntu
kernel or with the "5.3.0-25-generic #27~lp1766076" kernel suggested in
the comment above.
Trying to boot with the lp1766076 kernel (which I'm currently
Additionaly, with the lp1766076 kernel, after disconnecting the
thunderbolt cable, reconnecting it again fails - attached a short dmesg
log of just that.
** Attachment added: "lp1766076-tb-reconnect-fail-dmesg.log"
I also just saw this during a forced XHCI reset (after the USB bus
failed to connect):
8<
[ 247.130032] usb 3-1.6.2.4: new low-speed USB device number 9 using xhci_hcd
[ 247.388286] usb 3-1.6.2.4: New USB device found, idVendor=04d9,
idProduct=2013, bcdDevice= 1.03
[ 247.388287] usb
@David - as far as I know, before reporting kernel issues, Ubuntu users
are expected to try a repro with a mainline kernel. I've read (some of)
the discussion in the Freedesktop bug report where people have proposed
that various patches have possibly solved the problem, so I hit the
mainline PPA
The problem didn't reproduce with mainline PPA kernel 5.5.6. I'm now
running "5.4.0-14-generic #17+lp1853044v1", which is fine so far, but
due to the flu and extended weekend - I didn't have enough time to
properly stress test this. Likely will happen tomorrow.
--
You received this bug
Just got this triggered with 5.4.0-15-generic #18-Ubuntu from focal-
proposed.
Logs below.
If you want me to run another kernel, or try patched kernels, I can do
that.
Kernel log:
8<
Feb 25 10:08:08 vesho kernel: i915 :00:02.0: GPU HANG: ecode
9:1:0x, hang on rcs0
Feb 25
I think I'm triggering this problem with focal 5.4.0-14-generic
#17-Ubuntu.
Kernel log says:
8<
Feb 24 15:27:53 vesho kernel: Asynchronous wait on fence i915:Xorg[2401]:1d16c
timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Feb 24 15:27:53 vesho kernel: Asynchronous wait on
After updating to kernel mainline build 5.4.22-050422-generic
#202002240833, I couldn't immediately trigger the problem (including
scrubbing through a YouTube video on Chrome, as mentioned in upstream
freedesktop ticket), even though previously I could usually get the
problem triggered within a
I just got the same freeze with the mainline 5.4.22. I'm trying the
proposed kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861395
Title:
system hang: i915 Resetting rcs0 for
Just had an i915 crash on 5.4.0-14-generic #17+lp1853044v1. There appear
to be 3 crashes right after the other, I'm not sure what it means. It
could be related to the fact that I have a script running that detects
these crashes, waits 30 seconds and then restarts the display manager -
but if it is
After an update to 5.3.0-26-generic (and then some time passed), got a
connection fail when unsuspending.
The attached log is from journalctl -b -k with dyndbg enabled, from
suspending (Jan 21, 23:58) through complete failure of the connection at
09:08:16 and a disconnect and reconnect that
With the `dyndbg` flag, I can't seem to reproduce the problem: I tried
to connect and disconnect the cable a few times as well as rebooting
(which was almost 100% guaranteed to cause this issue).
I attached logs of the successful thunderbolt connection while running
and a boot log with the dock
The `logitech-hidpp-device` is the Logitech unified receiver I have
connected to the dock. It always generates lots of error messages like
this, even when connected directly to the computer's built-in USB port.
There's another Logitech unified receiver connected to the computer
itself, for the
And now, I managed to get a repro of the stated problem: USB controller
fails to complete initialization when connecting the thunderbolt cable.
This was 100% reproduceable for a few runs (logs 1 through 5), and only
stopped reproducing when I removed an Android device that was sitting at
the end
Attached kernel log of trying to recover from lp1766076 and failing.
The log starts at the point where we do `echo -n $id >
/sys/bus/pci/drivers/xhci_hcd/bind` at 13:05:44, and the driver gives up
at 13:05:55.
I'm actually not sure how relevant this is to this issue...
** Attachment added:
As I mentioned in comment 22, connecting the thunderbolt dock without
any additional USB devices plugged in, works well. After the controller
initializes, I can plug in the rest of the devices and they get set up
properly.
Comment 22 has a dmesg log off that.
I haven't tried booting with the
Tries booting with the chain disconnected from the dock, and as expected
- the system boots correctly with the dock attached and built-in USB
devices present, after which plugging the USB cable in works well.
The problem seems to only be when external USB devices are connected to
the dock.
Just had the "unknown event type 15" error happen again, with the
lp1766076 kernel and current firmware:
---8<---
Dec 25 11:19:34 vesho kernel: xhci_hcd :0e:00.0: ERROR unknown event type 15
Dec 25 11:19:39 vesho kernel: xhci_hcd :0e:00.0: xHCI host not responding
to stop endpoint
Since I started getting the bug 1766076 xhci failure, this problem has
become more acute as the automatic workaround described in 1766076 no
longer works - when resetting the xhci bus, the bus fails to be set up
properly due to this issue and I'm left with a non-functioning system.
See attached
With the current setup, I didn't manage to reproduce the problem yet
today. Here's the debug log that you asked that includes booting with
the thunderbolt connected, then disconnecting and reconnecting - all
completing successfully.
** Attachment added: "okconnect.log"
Sorry for the long delay in testing - I've been cooped up at home due to
illness, where my ability to test with different display configurations
in severely limited.
That being said, I've been running the canonical-kernel-team/unstable
5.4.0-17.21 for about a week now, including two days in the
@sanette - the problem you describe doesn't seem to be the same problem
originally reported in this ticket: that problem was with kernel 5.4 and
was causing a complete hang - not for a few seconds, but complete
failure with a graphical system reset the only resolution.
You may be experiencing an
I just started experiencing this issue again, last week. Same hardware:
Precision 5520 with thunderbolt dock Dell TB-16. Kernel
5.11.0-22-generic on hirsute.
---8<---
Jun 27 14:53:11 vesho kernel: xhci_hcd :0e:00.0: ERROR unknown event type 15
Jun 27 14:53:16 vesho kernel: xhci_hcd
#110 (Toumas) - I no longer experience this problem when running 20.10
with the latest kernel and the latest Dell firmware update (fwupdmgr
works reasonably well, but you can also just download the firmware file
from Dell, put it on a USB dok and the preboot screen lets you apply it
directly - no
79 matches
Mail list logo
