[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04
I used the mainline tool to install kernel 5.12. The dock is back again and everything appears to work. ``` mulhollandd@mulhollandd-XPS-13-9360:~$ uname -a Linux mulhollandd-XPS-13-9360 5.12.0-051200-generic #202104252130 SMP Sun Apr 25 21:33:13 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux mulhollandd@mulhollandd-XPS-13-9360:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.04 Release:21.04 Codename: hirsute mulhollandd@mulhollandd-XPS-13-9360:~$ sudo dmesg --level=err [sudo] password for mulhollandd: [0.011338] efi: Failed to lookup EFI memory descriptor for 0x7b014000 [ 14.615560] xhci_hcd :39:00.0: xHCI host controller not responding, assume dead [ 14.615574] xhci_hcd :39:00.0: HC died; cleaning up [ 15.030088] usb 4-1.3: device not accepting address 3, error -108 [ 15.030150] usb 4-1-port3: couldn't allocate usb_device [ 15.030198] usb 3-1-port5: couldn't allocate usb_device [ 112.758908] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb b3a810eb port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed mulhollandd@mulhollandd-XPS-13-9360:~$ ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926809 Title: WD19 dock stops working in Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04
** Description changed: - This morning I upgraded to Ubuntu 21.04. + This morning I upgraded to Kubuntu 21.04. I use two external monitors connected to my Dell XPS laptop via a Dell WD19 dock. Post-upgrade the monitors and also network functionality through the dock appear to have completely stopped functioning. When the dock is plugged in and the computer is booted the monitors do not enable. When the dock is not plugged in the computer boots normally. When I look at the dmesg output there appears to be some notable errors when I plug the dock in: [ 516.173451] xhci_hcd :39:00.0: xHCI host controller not responding, assume dead [ 516.207480] xhci_hcd :39:00.0: HC died; cleaning up [ 521.313422] pcieport :02:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 555.140320] xhci_hcd :39:00.0: xHCI host controller not responding, assume dead [ 555.140343] xhci_hcd :39:00.0: HC died; cleaning up [ 560.291086] pcieport :02:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 850.385934] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 850.499763] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 851.717630] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 851.815190] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 856.231021] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 856.301269] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 856.320487] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 856.343208] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun [ 856.382831] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.704920] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.765138] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.894454] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.965337] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 861.115198] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 861.182111] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 866.232326] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 866.351715] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 866.454536] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 866.473097] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 866.534697] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful With the dock plugged in: * neither monitor displays although they are present under display configuration * since my laptop screen is not usually on if both monitors are present on the dock the immediate result was no display at all under the dock was detached * network connectivity is not established although the network device appears under networks Unfortunately I lack the skills to diagnose this further without assistance or to install a more recent kernel to see if it is resolved there. It appears that communications between the laptop and the Dock are not going well to my eyes (is this what link training is on Thunderbolt) I'm happy to provide further information... although in a few days the lack of Dock and monitors will be a bit of an issue and I may have to roll something back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: mulhollandd 1940 F pulseaudio - /dev/snd/controlC1: mulhollandd 1940 F pulseaudio - /dev/snd/controlC0: mulhollandd 1940 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: mulhollandd 1940 F pulseaudio + /dev/snd/controlC1: mulhollandd 1940 F pulseaudio + /dev/snd/controlC0: mulhollandd 1940 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat May 1 08:57:26 2021 InstallationDate: Installed on 2020-06-13 (321 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgkubuntu-root ro quiet splash
[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04
It may be that this (fixed) bug is related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903969 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926809 Title: WD19 dock stops working in Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04
When I boot to use an older kernel, initially things appear no better -- no monitors except the laptop and after logging into Kubuntu no monitors at all. After removing the USB-C connection and plugging it back in again both monitors come back, headphones work but the wired network connection does not work. Here's some dmesg output for this: mulhollandd@mulhollandd-XPS-13-9360:~$ sudo dmesg --level=err [ 95.459529] xhci_hcd :39:00.0: xHCI host controller not responding, assume dead [ 95.459573] xhci_hcd :39:00.0: HC died; cleaning up [ 100.553294] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 100.553301] pcieport :00:1c.0: AER: device [8086:9d10] error status/mask=0001/2000 [ 100.553306] pcieport :00:1c.0: AER:[ 0] RxErr [ 100.630562] pcieport :02:00.0: can't change power state from D3cold to D0 (config space inaccessible) mulhollandd@mulhollandd-XPS-13-9360:~$ # no monitors but when I unplug and replug both monitors come back mulhollandd@mulhollandd-XPS-13-9360:~$ # now a new dmesg output mulhollandd@mulhollandd-XPS-13-9360:~$ sudo dmesg --level=err [ 95.459529] xhci_hcd :39:00.0: xHCI host controller not responding, assume dead [ 95.459573] xhci_hcd :39:00.0: HC died; cleaning up [ 100.553294] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 100.553301] pcieport :00:1c.0: AER: device [8086:9d10] error status/mask=0001/2000 [ 100.553306] pcieport :00:1c.0: AER:[ 0] RxErr [ 100.630562] pcieport :02:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 158.228726] pcieport :00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 158.228734] pcieport :00:1c.4: AER: device [8086:9d14] error status/mask=1000/2000 [ 158.228739] pcieport :00:1c.4: AER:[12] Timeout mulhollandd@mulhollandd-XPS-13-9360:~$ # we are on an older kernel now mulhollandd@mulhollandd-XPS-13-9360:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.04 Release:21.04 Codename: hirsute mulhollandd@mulhollandd-XPS-13-9360:~$ uname -a Linux mulhollandd-XPS-13-9360 5.8.0-50-generic #56-Ubuntu SMP Mon Apr 12 17:18:36 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux mulhollandd@mulhollandd-XPS-13-9360:~$ I should note that the AER PCIe Bus Errors have been present I think for many years and versions of Ubuntu so I think they are unrelated. However the power state transition from "D3cold to D0 (config space inaccessible)" is I think new. Happy to provide further information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926809 Title: WD19 dock stops working in Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926809] [NEW] WD19 dock stops working in Ubuntu 21.04
Public bug reported: This morning I upgraded to Ubuntu 21.04. I use two external monitors connected to my Dell XPS laptop via a Dell WD19 dock. Post-upgrade the monitors and also network functionality through the dock appear to have completely stopped functioning. When the dock is plugged in and the computer is booted the monitors do not enable. When the dock is not plugged in the computer boots normally. When I look at the dmesg output there appears to be some notable errors when I plug the dock in: [ 516.173451] xhci_hcd :39:00.0: xHCI host controller not responding, assume dead [ 516.207480] xhci_hcd :39:00.0: HC died; cleaning up [ 521.313422] pcieport :02:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 555.140320] xhci_hcd :39:00.0: xHCI host controller not responding, assume dead [ 555.140343] xhci_hcd :39:00.0: HC died; cleaning up [ 560.291086] pcieport :02:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 850.385934] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 850.499763] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 851.717630] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 851.815190] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 856.231021] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 856.301269] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 856.320487] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 856.343208] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun [ 856.382831] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.704920] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.765138] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.894454] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.965337] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 861.115198] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 861.182111] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 866.232326] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 866.351715] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 866.454536] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 866.473097] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 866.534697] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful With the dock plugged in: * neither monitor displays although they are present under display configuration * since my laptop screen is not usually on if both monitors are present on the dock the immediate result was no display at all under the dock was detached * network connectivity is not established although the network device appears under networks Unfortunately I lack the skills to diagnose this further without assistance or to install a more recent kernel to see if it is resolved there. It appears that communications between the laptop and the Dock are not going well to my eyes (is this what link training is on Thunderbolt) I'm happy to provide further information... although in a few days the lack of Dock and monitors will be a bit of an issue and I may have to roll something back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mulhollandd 1940 F pulseaudio /dev/snd/controlC1: mulhollandd 1940 F pulseaudio /dev/snd/controlC0: mulhollandd 1940 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat May 1 08:57:26 2021 InstallationDate: Installed on 2020-06-13 (321 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-30 (0 days ago) dmi.bios.date: 03/09/2021 dmi.bios.release: 2.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.15.1 dmi.board.name: 0115N5 dmi.board.vendor: Dell Inc.
[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04
Some functionality still appears to work correctly -- headphones plugged into the Dock appear to function. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926809 Title: WD19 dock stops working in Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907936] Re: Does not appear to function out of the box or at all
apport information ** Tags added: apport-collected groovy ** Description changed: I've been testing oomd and hoping it would just work out of the box. From what I can tell it doesn't seem to work at all for excess CPU (or memory for that matter) although I may be misunderstanding important matters but current documentation is insufficient for me to do better. I've been trying to check the cpu related rules: * User pressure above 60 for 30 s * System pressure above 80 for 60 s I disable oomd on the system using $ systemctl stop oomd I then run it using the command: $ sudo /usr/bin/oomd --config /etc/oomd/oomd.json --cgroup-fs /sys/fs/cgroup/unified The oomd.json is the default for the Ubuntu 20.10 package. I have previously changed my linux boot parameters on the command line to include systemd.unified_cgroup_hierarchy=1. I am running Ubuntu 20.10: $ uname -a Linux XPS-13-9360 5.8.0-33-generic #36-Ubuntu SMP Wed Dec 9 09:14:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.10 Release:20.10 Codename: groovy I then test by doing a command like: $ stress -c 150 and monitor the system pressure using something like: $ cat /proc/pressure/cpu some avg10=98.91 avg60=79.66 avg300=29.70 total=107155291 As far as I can tell oomd takes and tries to take no action. I'd be happy to take some debugging suggestions or provide further information. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.2 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2020-06-13 (183 days ago) + InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: oomd 0.4.0-1 [modified: lib/systemd/system/oomd.service] + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 + Tags: groovy + Uname: Linux 5.8.0-33-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2020-10-28 (46 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1907936/+attachment/5443058/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907936 Title: Does not appear to function out of the box or at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oomd/+bug/1907936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907936] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1907936/+attachment/5443060/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907936 Title: Does not appear to function out of the box or at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oomd/+bug/1907936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907936] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1907936/+attachment/5443059/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907936 Title: Does not appear to function out of the box or at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oomd/+bug/1907936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907936] Re: Does not appear to function out of the box or at all
I should add that when using these commands I see no comment in the console output of oomd, my process is not terminated even when waiting for 3-4 minutes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907936 Title: Does not appear to function out of the box or at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oomd/+bug/1907936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907936] [NEW] Does not appear to function out of the box or at all
Public bug reported: I've been testing oomd and hoping it would just work out of the box. >From what I can tell it doesn't seem to work at all for excess CPU (or memory >for that matter) although I may be misunderstanding important matters but >current documentation is insufficient for me to do better. I've been trying to check the cpu related rules: * User pressure above 60 for 30 s * System pressure above 80 for 60 s I disable oomd on the system using $ systemctl stop oomd I then run it using the command: $ sudo /usr/bin/oomd --config /etc/oomd/oomd.json --cgroup-fs /sys/fs/cgroup/unified The oomd.json is the default for the Ubuntu 20.10 package. I have previously changed my linux boot parameters on the command line to include systemd.unified_cgroup_hierarchy=1. I am running Ubuntu 20.10: $ uname -a Linux XPS-13-9360 5.8.0-33-generic #36-Ubuntu SMP Wed Dec 9 09:14:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.10 Release:20.10 Codename: groovy I then test by doing a command like: $ stress -c 150 and monitor the system pressure using something like: $ cat /proc/pressure/cpu some avg10=98.91 avg60=79.66 avg300=29.70 total=107155291 As far as I can tell oomd takes and tries to take no action. I'd be happy to take some debugging suggestions or provide further information. ** Affects: oomd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907936 Title: Does not appear to function out of the box or at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oomd/+bug/1907936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
FWIW With a Dell XPS 9360 and Kubuntu 17.10, same issue on the latest kernel and many previous: uname -a Linux mulhollandd-XPS-13-9360 4.16.2-041602-generic #201804121130 SMP Thu Apr 12 11:32:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lsb _release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful I will test the solution mentioned by @s-breedveld of applying: "pci=nomsi iommu=soft" and report if this helps. In my case this is a bluetooth mouse which disappears after suspend. A dmesg output indicates: [ 3380.759427] xhci_hcd :00:14.0: xHC is not running. [ 3380.774604] xhci_hcd :00:14.0: xHCI host controller not responding, assume dead [ 3380.774627] xhci_hcd :00:14.0: HC died; cleaning up [ 3380.775306] usb 2-1: USB disconnect, device number 2 [ 3381.059095] usb 1-1: USB disconnect, device number 2 [ 3381.059098] usb 1-1.2: USB disconnect, device number 4 [ 3381.059408] usb 1-3: USB disconnect, device number 3 [ 3381.059735] usb 1-5: USB disconnect, device number 5 A power-down is usually required to fix this, a reboot does bring the device back to life. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1413440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1521173] Re: AER: Corrected error received: id=00e0
I have experienced the same issue. Linux kernel 4.12 (easily installed using Ukuu http://www.omgubuntu.co.uk/2017/02/ukuu-easy-way-to-install-mainline-kernel-ubuntu) completely resolved this issue with the PCIe bus for me. On Fri, Jul 21, 2017 at 8:26 PM, Stephan Ruegamer < 1521...@bugs.launchpad.net> wrote: > Just saw this message the first time: > > Ubuntu Artful (Devel) latest packages. > > Jul 21 10:15:18 sruegamer-xps13 kernel: [ 3949.594315] pcieport > :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, > id=00e4(Transmitter ID) > Jul 21 10:15:18 sruegamer-xps13 kernel: [ 3949.594323] pcieport > :00:1c.4: device [8086:9d14] error status/mask=1000/2000 > Jul 21 10:15:18 sruegamer-xps13 kernel: [ 3949.594329] pcieport > :00:1c.4:[12] Replay Timer Timeout > Jul 21 10:15:36 sruegamer-xps13 kernel: [ 3967.818653] pcieport > :00:1c.4: AER: Corrected error received: id=00e4 > Jul 21 10:15:36 sruegamer-xps13 kernel: [ 3967.818666] pcieport > :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, > id=00e4(Transmitter ID) > Jul 21 10:15:36 sruegamer-xps13 kernel: [ 3967.818671] pcieport > :00:1c.4: device [8086:9d14] error status/mask=1000/2000 > Jul 21 10:15:36 sruegamer-xps13 kernel: [ 3967.818674] pcieport > :00:1c.4:[12] Replay Timer Timeout > Jul 21 10:16:01 sruegamer-xps13 gnome-terminal-[6368]: Unable to load > blank_cursor from the cursor theme > Jul 21 10:16:43 sruegamer-xps13 kernel: [ 4034.583189] pcieport > :00:1c.4: AER: Corrected error received: id=00e4 > Jul 21 10:16:43 sruegamer-xps13 kernel: [ 4034.583201] pcieport > :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, > id=00e4(Transmitter ID) > Jul 21 10:16:43 sruegamer-xps13 kernel: [ 4034.583205] pcieport > :00:1c.4: device [8086:9d14] error status/mask=1000/2000 > Jul 21 10:16:43 sruegamer-xps13 kernel: [ 4034.583207] pcieport > :00:1c.4:[12] Replay Timer Timeout > Jul 21 10:16:46 sruegamer-xps13 kernel: [ 4037.002195] pcieport > :00:1c.4: AER: Corrected error received: id=00e4 > Jul 21 10:16:46 sruegamer-xps13 kernel: [ 4037.002201] pcieport > :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, > id=00e4(Transmitter ID) > Jul 21 10:16:46 sruegamer-xps13 kernel: [ 4037.002204] pcieport > :00:1c.4: device [8086:9d14] error status/mask=1000/2000 > Jul 21 10:16:46 sruegamer-xps13 kernel: [ 4037.002206] pcieport > :00:1c.4:[12] Replay Timer Timeout > > Laptop is Dell XPS 13 Dev Edition (9360) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1521173 > > Title: > AER: Corrected error received: id=00e0 > > Status in Linux: > Unknown > Status in linux package in Ubuntu: > Confirmed > Status in linux source package in Xenial: > Triaged > > Bug description: > Note: Current workaround is to add pci=noaer to your kernel command > line: > > 1) edit /etc/default/grub and and add pci=noaer to the line starting > with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: > GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" > 2) run "sudo update-grub" > 3) reboot > > > > My dmesg gets completely spammed with the following messages appearing > over and over again. It stops after one s3 cycle; it only happens > after reboot. > > [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: > id=00e0 > [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 > [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: > id=00e0 > [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: > severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) > [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error > status/mask=0001/2000 > [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error > [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: > id=00e0 > [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: > severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) > [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error > status/mask=0001/2000 > [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error > [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: > id=00e0 > [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: > severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) > [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error > status/mask=0001/2000 > [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: > boot/vmlinuz-4.2.0-19-generic] > ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 > Uname: Linux 4.2.0-19-generic x86_64 > ApportVersion: 2.19.2-0ubuntu8 > Architecture:
[Bug 1521173] Re: AER: Corrected error received: id=00e0
FWIW, running Kubuntu 17.04 with kernel 4.12.0-041200rc4-generic on a Dell XPS 9360 (late 2016) model, I get this error: 9825.550655] pcieport :00:1c.4: AER: Corrected error received: id=00e4 [ 9825.550661] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) [ 9825.550664] pcieport :00:1c.4: device [8086:9d14] error status/mask=1000/2000 [ 9825.550666] pcieport :00:1c.4:[12] Replay Timer Timeout [ 9825.846925] pcieport :00:1c.4: AER: Corrected error received: id=00e4 [ 9825.846951] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) [ 9825.846966] pcieport :00:1c.4: device [8086:9d14] error status/mask=1000/2000 [ 9825.846974] pcieport :00:1c.4:[12] Replay Timer Timeout [ 9825.852701] pcieport :00:1c.4: AER: Corrected error received: id=00e4 [ 9825.852715] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) [ 9825.852724] pcieport :00:1c.4: device [8086:9d14] error status/mask=1000/2000 [ 9825.852730] pcieport :00:1c.4:[12] Replay Timer Timeout [ 9826.680756] pcieport :00:1c.4: AER: Corrected error received: id=00e4 [ 9826.680767] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) [ 9826.680774] pcieport :00:1c.4: device [8086:9d14] error status/mask=1000/2000 [ 9826.680780] pcieport :00:1c.4:[12] Replay Timer Timeout [ 9826.938346] pcieport :00:1c.4: AER: Corrected error received: id=00e4 [ 9826.938362] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) [ 9826.938370] pcieport :00:1c.4: device [8086:9d14] error status/mask=1000/2000 [ 9826.938375] pcieport :00:1c.4:[12] Replay Timer Timeout [ 9828.079556] pcieport :00:1c.4: AER: Corrected error received: id=00e4 [ 9828.079566] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) [ 9828.079573] pcieport :00:1c.4: device [8086:9d14] error status/mask=1000/2000 [ 9828.079577] pcieport :00:1c.4:[12] Replay Timer Timeout [ 9828.278507] pcieport :00:1c.4: AER: Corrected error received: id=00e4 [ 9828.278531] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) [ 9828.278548] pcieport :00:1c.4: device [8086:9d14] error status/mask=1000/2000 [ 9828.278559] pcieport :00:1c.4:[12] Replay Timer Timeout I think this is likely the same issue as in this thread, however the type is "Data Link Layer" rather than "Physical Layer". Happy to run diagnostics on suggestion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665829] Re: MonoDevelop.exe assert failure: *** Error in `monodevelop': free(): invalid pointer: 0x000055bf61a2e6b0 ***
I think the same bug for me in Ubuntu 17.04. When I go to File > Open before I have even selected a file I get ** Error in `monodevelop': free(): invalid pointer: 0x7fb3c0011840 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x7908b)[0x7fb4157e408b] /lib/x86_64-linux-gnu/libc.so.6(+0x826fa)[0x7fb4157ed6fa] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7fb4157f112c] [0x409ae260] with a memory map following this backtrace which I have not included. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665829 Title: MonoDevelop.exe assert failure: *** Error in `monodevelop': free(): invalid pointer: 0x55bf61a2e6b0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/1665829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
