Public bug reported:
I've filed with ubuntu-bug so additional logging should be available.
Starting with 19.10 there has been a regression in my CalDigit
thunderbolt 3 dock. With Bionic and Disco the dock has been stable
across two laptops. After upgrading to Eaon and running 5.3.0-18-generic
** Changed in: charm-neutron-openvswitch
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux-meta-hwe (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-meta-hwe (Ubuntu)
** No longer affects: linux-meta-hwe (Ubuntu Yakkety)
** No longer affects: linux-meta-hwe (Ubuntu Zesty)
--
You received this bug notification because you are a
Great, this should fix it for you then. I ran between 40 min and 3 hours
between crashes. I've been running daily (this is my daily use laptop
for work) and after the above fix it's completely stable.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Javi, see comment 25 above I'm booting with a work around on the 9550 with
PM951.
However, also note that this bug shouldn't crash "on boot". I had a seperate
issue with the 9550 with tlp and external usb devices causing an on boot crash
which is not related to this. I recommend you run w/o any
Nils, from above use 'nvme-core.nvme_core.default_ps_max_latency_us=0'
to turn APST off.
That as my first step to confirm this is indeed related to APST and the
same bug. If that doesn't do it, I'm afraid you might have another
issue.
--
You received this bug notification because you are a
I can now confirm that I've had a stable machine for more than 7 hours
using 6k for latency. I think the longest I had with out the option was
~3 hours and generally it was ~45 minutes to crash.
Nils, I'm setting the parameter in /etc/default/grub by appending it to
the
I have an xps15 9550 same as above, same controller, same issue. I set
nvme_core.default_ps_max_latency_us=6000 this morning and have ~1 hour
right now with no crash. I'll continue to run it today and report back.
The only issue I have seen with the 6k setting which I didn't not see
with a
I've just noticed this has resolved for me. See below, the errors do not
repeat and I connect to the network. However, I have recently updated my
router firmware to my knowledge it's still configured like it was (40/80
Mhz channels). I'm running the same nvidia-375 that was causing errors
before.
This appears to be a conflict with the Nvidia driver (at least for me).
I've tried:
nvidia-378 (open source)
nvidia-370 (open source)
nvidia-375 (proprietary)
All three give the exact same results as above on both 2.4 and 5 Ghz.
Switching to the intel graphics driver completely clears this up.
XPS-15 (9550), Yakkety, 4.8.0-41-generic, 40Mhz channels also unable to
connect to Wifi any longer. Happy to provide testing or any additional
information.
dmesg | grep brcm
[5.481593] usbcore: registered new interface driver brcmfmac
[5.481639] brcmfmac :02:00.0: enabling device
11 matches
Mail list logo
