[Kernel-packages] [Bug 1873194] Re: clipit interface not working in 20.04
On Ubuntu 20.04 stable, the Clipit interface does not work on Xorg either. The hotekeys do not work, the preferences do not open and the program does not shut down properly. -- 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/1873194 Title: clipit interface not working in 20.04 Status in clipit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When running clipit in focal fossa beta the interface will crash when opening the history list via shortcut (ctr + alt + h). Starting it from cli shows this error message: (clipit:7248): Gdk-CRITICAL **: 10:42:40.873: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Clipit version is 1.4.4+git20190202-1 from https://launchpad.net/ubuntu/focal/+package/clipit Ubuntu version is Ubuntu Focal Fossa (development branch) from 15.4.2020 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-04-29 (1447 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal third-party-packages Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-15 (0 days ago) UserGroups: adm cdrom dip docker kismet kvm lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clipit/+bug/1873194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I have the same issue with Dell TB18DC tb dock and Dell Precision 7530 laptop. Using ukuu mainline kernel 4.19.4-041904-generic. I think latest system bios update 1.4.2 (https://www.dell.com/support/home/us/en/04 /product-support/product/precision-15-7530-laptop/drivers) made this problem appear a lot more often than earlier. -- 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 off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: 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 to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
This is now happening to me about every 10-20 minutes or so. Very frustrating. With TB18DC I'm using - onboard sound port - onboard ethernet port - mouse dongle - fingerprint reader - 1 large external monitor with DP After reboot this tends to happen after longer period of time (several hours), but once it happens, it repeats itself pretty soon. -- 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 off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: 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 to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
No, for me lspci works fine after this issue: 00:00.0 Host bridge: Intel Corporation Device 3ec4 (rev 07) 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device a379 (rev 10) 00:14.0 USB controller: Intel Corporation Device a36d (rev 10) 00:14.2 RAM memory: Intel Corporation Device a36f (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10) 00:16.0 Communication controller: Intel Corporation Device a360 (rev 10) 00:17.0 SATA controller: Intel Corporation Device a353 (rev 10) 00:1b.0 PCI bridge: Intel Corporation Device a32c (rev f0) 00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0) 00:1c.5 PCI bridge: Intel Corporation Device a33d (rev f0) 00:1c.6 PCI bridge: Intel Corporation Device a33e (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10) 00:1f.3 Audio device: Intel Corporation Device a348 (rev 10) 00:1f.4 SMBus: Intel Corporation Device a323 (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a324 (rev 10) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10) 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1cba (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev ff) 02:00.0 Non-Volatile memory controller: Device 1c5c:1504 03:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 04:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 04:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 04:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 04:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 05:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] (rev 06) 3a:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 3b:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 3b:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 3d:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 3e:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 3e:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 3f:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller 6e:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5260 (rev 01) 6f:00.0 Network controller: Intel Corporation Device 2526 (rev 29) -- 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 off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: 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 to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] u
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Okay, after yet another occurrence of the issue: lspci -vv 00:00.0 Host bridge: Intel Corporation Device 3ec4 (rev 07) Subsystem: Dell Device 0831 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (prog-if 00 [VGA controller]) Subsystem: Dell Device 0831 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 07) Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model Subsystem: Dell Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:12.0 Signal processing controller: Intel Corporation Device a379 (rev 10) Subsystem: Dell Device 0831 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:14.0 USB controller: Intel Corporation Device a36d (rev 10) (prog-if 30 [XHCI]) Subsystem: Dell Device 0831 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:14.2 RAM memory: Intel Corporation Device a36f (rev 10) Subsystem: Dell Device 0831 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10) Subsystem: Dell Device 0831 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10) Subsystem: Dell Device 0831 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller: Intel Corporation Device a360 (rev 10) Subsystem: Dell Device 0831 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller: Intel Corporation Device a353 (rev 10) (prog-if 01 [AHCI 1.0]) Subsystem: Dell Device 0831 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci 00:1b.0 PCI bridge: Intel Corporation Device a32c (rev f0) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
It seems that this problem with TB18DC has gone away for me after updating my Dell Precision 7530 bios to the latest 1.6.0 version. There's still another USB problem with dock but symptoms are different than earlier: for example usb mouse stops working after some time, but still after that is visible for the system (lsusb)). Network and sound from dock work now well. I would try updating dock bios, if I just could install windows. -- 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 off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: 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 to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
And now the rest of issues seem to have been gone away when I also updated my TB18DC to the latest firmware (1.0.8). -- 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 off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: 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 to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I updated BIOS by saving exe file to usb stick and used bios update option from BIOS boot menu. For TB18DC firmware upgrade, I installed Windows 10. Actually firmware upgrade did not go too smoothly (it upgraded successfully some subsystems, but not all, failed with MTS1, MTS2). Here are some bios settings that might be related: Thunderbolt Adapter configuration: - Thunderbolt: Yes - Enable thunderbolt ... modules: no - Enable thunderbolt boot support: no - No security: yes - Always allow dell docks: yes - Enable USB Boot support: Yes - Enable external usb port: yes - Enable usb powershare: no - Thunderbolt Auto switch: no - Bios Assist enumeration: yes -- 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 off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: 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 to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Updated kernel to 4.19.15-041915-generic (ukuu), and still this reproduces. Right after boot it works fine, then after one working day I disconnect thunderbolt and suspend the machine. Then next morning it reproduces within first hour. With the current setup I don't have any usb devices connected to the dock (TB18DC), only integrated devices (ethernet and audio) and DP ports are in use. Dmesg looks about the same as earlier. [30714.740801] xhci_hcd :3f:00.0: ERROR unknown event type 15 [30719.651705] xhci_hcd :3f:00.0: xHCI host not responding to stop endpoint command. [30719.652032] xhci_hcd :3f:00.0: xHCI host controller not responding, assume dead [30719.652070] r8152 4-1.2:1.0 enxe4b97a92fb26: Tx status -108 [30719.652074] r8152 4-1.2:1.0 enxe4b97a92fb26: Tx status -108 [30719.652079] r8152 4-1.2:1.0 enxe4b97a92fb26: Tx status -108 [30719.652082] r8152 4-1.2:1.0 enxe4b97a92fb26: Tx status -108 [30719.652099] xhci_hcd :3f:00.0: HC died; cleaning up [30719.652127] usb 4-1.1: Failed to suspend device, error -19 -- 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 off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: 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 to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Few months ago I gave up and stopped using my TB18. Easier to connect few cables once a day than fight with this. I'm much happier now. TB18 serves as an expensive laptop stand for me (elevates laptop 5 cm from table). -- 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 off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: 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 to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: Seri
[Kernel-packages] [Bug 1486316] Re: lpc_ich: Resource conflict(s) found affecting gpio_ich
** Tags added: bionic -- 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/1486316 Title: lpc_ich: Resource conflict(s) found affecting gpio_ich Status in linux package in Ubuntu: Triaged Bug description: This nearly identical to the following bug: (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027370). (sorry not sure how to make links here) however, this is not effecting iTCO_wdt, but is effecting gpio_ich ACPI Warning: SystemIO range 0x0828-0x082F conflicts with OpRegion 0x0800-0x084F (\PMRG) (20150410/utaddress-254) [ ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver lpc_ich: Resource conflict(s) found affecting gpio_ich This error occurs in 15,04 and the latest build of 15.10. i meant to post this up with the last report i made but i ended up getting distracted. sorry. LSB: Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 --- ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: testusr1632 F...m pulseaudio /dev/snd/controlC0: testusr1632 F pulseaudio /dev/snd/controlC1: testusr1632 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=df53ef11-a582-4795-81e6-4666c7ba9eb7 InstallationDate: Installed on 2015-08-15 (3 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150815.1) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: Gateway FX6840 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2244254b-eee5-4fa6-bb16-d4e811b01f42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.1.0-3-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FX6840 dmi.board.vendor: Gateway dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd05/17/2010:svnGateway:pnFX6840:pvr:rvnGateway:rnFX6840:rvr:cvnGateway:ct3:cvr: dmi.product.name: FX6840 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666650] Re: lpc_ich: Resource conflict(s) found affecting gpio_ich
*** This bug is a duplicate of bug 1486316 *** https://bugs.launchpad.net/bugs/1486316 ** This bug has been marked a duplicate of bug 1486316 lpc_ich: Resource conflict(s) found affecting gpio_ich -- 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/150 Title: lpc_ich: Resource conflict(s) found affecting gpio_ich Status in linux package in Ubuntu: Invalid Bug description: dmesg: [5.509144] lpc_ich: Resource conflict(s) found affecting gpio_ich ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-8-generic 4.10.0-8.10 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2151 F...m pulseaudio /dev/snd/controlC0: caravena 2151 F pulseaudio CurrentDesktop: GNOME Date: Tue Feb 21 16:28:18 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (576 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-8-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-8-generic N/A linux-backports-modules-4.10.0-8-generic N/A linux-firmware1.163 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752251] Re: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy
@#9, Supposedly rasdaemon could handle MCEs on bionic+. Have not yet witnessed it working though, even on hardware that had dozen reports/year shown with mcelog. -- 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/1752251 Title: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy Status in linux package in Ubuntu: Confirmed Status in mcelog package in Ubuntu: Confirmed Bug description: There is no mcelog package in bionic. $ sudo apt install mcelog Reading package lists... Done Building dependency tree Reading state information... Done Package mcelog is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'mcelog' has no installation candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881505] Re: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7
I have the same problem with Lenovo T14 (Gen 1), which seems to have a similar sound device: 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:02c8] (prog-if 80) Subsystem: Lenovo Device [17aa:22b1] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee00858 Data: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci This is what I've got to my dmesg when the sound stopped working: [127623.194131] sof-audio-pci :00:1f.3: error : DSP panic! [127623.194155] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [127623.194394] sof-audio-pci :00:1f.3: error: can't enter idle [127623.194398] sof-audio-pci :00:1f.3: error: trace point 4000 [127623.194402] sof-audio-pci :00:1f.3: error: panic at src/lib/agent.c:50 [127623.194409] sof-audio-pci :00:1f.3: error: DSP Firmware Oops [127623.194427] sof-audio-pci :00:1f.3: EXCCAUSE 0x003f EXCVADDR 0x PS 0x00060925 SAR 0x [127623.194431] sof-audio-pci :00:1f.3: EPC1 0x EPC2 0xbe00d30e EPC3 0x EPC40x [127623.194434] sof-audio-pci :00:1f.3: EPC5 0x EPC6 0x EPC7 0x DEPC0x [127623.194438] sof-audio-pci :00:1f.3: EPS2 0x00060d20 EPS3 0x EPS4 0x EPS50x [127623.194440] sof-audio-pci :00:1f.3: EPS6 0x EPS7 0x INTENABL 0x INTERRU 0x0222 [127623.194443] sof-audio-pci :00:1f.3: stack dump from 0xbe04f5b0 [127623.194451] sof-audio-pci :00:1f.3: 0xbe04f5b0: be00fc00 be04f5e0 be062380 [127623.194454] sof-audio-pci :00:1f.3: 0xbe04f5b4: 0032 [127623.194457] sof-audio-pci :00:1f.3: 0xbe04f5b8: fb35de00 fc28026c 7a64e018 952e [127623.194461] sof-audio-pci :00:1f.3: 0xbe04f5bc: 0090be70 a4f2 c0edc5f9 [127623.194463] sof-audio-pci :00:1f.3: 0xbe04f5c0: a9716c98 6ead97c0 952e [127623.194467] sof-audio-pci :00:1f.3: 0xbe04f5c4: [127623.194471] sof-audio-pci :00:1f.3: 0xbe04f5c8: 002cbb98 a4f2 0090bf48 a4f2 [127623.194475] sof-audio-pci :00:1f.3: 0xbe04f5cc: [127623.194478] sof-audio-pci :00:1f.3: error: waking up any trace sleepers [127714.180370] sof-audio-pci :00:1f.3: error: ipc timed out for 0x6005 size 12 [127714.180387] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [127714.180652] sof-audio-pci :00:1f.3: error: can't enter idle [127714.180659] sof-audio-pci :00:1f.3: error: trace point 4000 [127714.180664] sof-audio-pci :00:1f.3: error: panic at src/lib/agent.c:50 [127714.180670] sof-audio-pci :00:1f.3: error: DSP Firmware Oops [127714.180676] sof-audio-pci :00:1f.3: EXCCAUSE 0x003f EXCVADDR 0x PS 0x00060925 SAR 0x [127714.180682] sof-audio-pci :00:1f.3: EPC1 0x EPC2 0xbe00d30e EPC3 0x EPC40x [127714.180687] sof-audio-pci :00:1f.3: EPC5 0x EPC6 0x EPC7 0x DEPC0x [127714.180692] sof-audio-pci :00:1f.3: EPS2 0x00060d20 EPS3 0x EPS4 0x EPS50x [127714.180695] sof-audio-pci :00:1f.3: EPS6 0x EPS7 0x INTENABL 0x INTERRU 0x0222 [127714.180698] sof-audio-pci :00:1f.3: stack dump from 0xbe04f5b0 [127714.180705] sof-audio-pci :00:1f.3: 0xbe04f5b0: be00fc00 be04f5e0 be062380 [127714.180709] sof-audio-pci :00:1f.3: 0xbe04f5b4: 0032 [127714.180713] sof-audio-pci :00:1f.3: 0xbe04f5b8: d02a5b00 530f4b8a 700a71f8 952e [127714.180717] sof-audio-pci :00:1f.3: 0xbe04f5bc: 952e 530f4b8a [127714.180720] sof-audio-pci :00:1f.3: 0xbe04f5c0: 000c 700a7198 952e [127714.180724] sof-audio-pci :00:1f.3: 0xbe04f5c4: 6f156000 952e [127714.180728] sof-audio-pci :00:1f.3: 0xbe04f5c8: 000c 6005 0009 952e [127714.180732] sof-audio-pci :00:1f.3: 0xbe04f5cc: [127714.180749] sof-audio-pci :00:1f.3: error: hda irq intsts 0x intlctl 0xc085 rirb 00 [127714.180752] sof-audio-pci :00:1f.3: error: dsp irq ppsts 0x adspis 0x [127714.180765] sof-audio-pci :00:1f.3: error: host status 0x dsp status 0x mask 0x0003 [127714.180768] sof-audio-pci :00:1f.3: error: waking up any trace sleepers [127714.181386] HDA Analog: ASoC: trigger FE cmd: 0 failed: -110 [127714.69242
[Kernel-packages] [Bug 1881505] Re: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7
If this is indeed the same issue as in https://github.com/thesofproject/sof/issues/2828, then the problem should be fixed by upgrading the SOF firmware to 1.6 version. I'll give it a try by installing directly from https://github.com/thesofproject/sof-bin/tree/stable-v1.6 I will let you know if that fixed the issue. So far it looks good, but I'll have to use the system for couple days to be sure. If the newer firmware fixes the issue, is it possible to get it to the linux-firmware package for Ubuntu 20.04? ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/thesofproject/sof/issues #2828 https://github.com/thesofproject/sof/issues/2828 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1881505 Title: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Now and then, the notebooks stops producing any sound, and program that try to use sound output freeze for many seconds. There is a repeating sequence on messages in `dmesg`: [116525.402057] sof-audio-pci :00:1f.3: error: ipc timed out for 0x8001 size 120 [116525.402081] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [116525.402338] sof-audio-pci :00:1f.3: error: can't enter idle [116525.402342] sof-audio-pci :00:1f.3: error: trace point 4000 [116525.402346] sof-audio-pci :00:1f.3: error: panic at src/lib/agent.c:50 [116525.402350] sof-audio-pci :00:1f.3: error: DSP Firmware Oops [116525.402356] sof-audio-pci :00:1f.3: EXCCAUSE 0x003f EXCVADDR 0x PS 0x00060925 SAR 0x [116525.402361] sof-audio-pci :00:1f.3: EPC1 0x EPC2 0xbe00d30e EPC3 0x EPC40x [116525.402365] sof-audio-pci :00:1f.3: EPC5 0x EPC6 0x EPC7 0x DEPC0x [116525.402369] sof-audio-pci :00:1f.3: EPS2 0x00060d20 EPS3 0x EPS4 0x EPS50x [116525.402374] sof-audio-pci :00:1f.3: EPS6 0x EPS7 0x INTENABL 0x INTERRU 0x0222 [116525.402378] sof-audio-pci :00:1f.3: stack dump from 0xbe04f5b0 [116525.402385] sof-audio-pci :00:1f.3: 0xbe04f5b0: be00fc00 be04f5e0 be062180 0001 [116525.402391] sof-audio-pci :00:1f.3: 0xbe04f5b4: 0032 [116525.402396] sof-audio-pci :00:1f.3: 0xbe04f5b8: 69cd0100 15655b6c 602aeaf8 93a4 [116525.402401] sof-audio-pci :00:1f.3: 0xbe04f5bc: 93a4 303a3030 [116525.402406] sof-audio-pci :00:1f.3: 0xbe04f5c0: 0078 602aea98 93a4 [116525.402411] sof-audio-pci :00:1f.3: 0xbe04f5c4: 6bdcfb58 93a4 5d006830 93a4 [116525.402416] sof-audio-pci :00:1f.3: 0xbe04f5c8: 6ba37218 93a4 82317aaf bca5 [116525.402421] sof-audio-pci :00:1f.3: 0xbe04f5cc: 6ba37220 93a4 023179f8 bca5 [116525.402446] sof-audio-pci :00:1f.3: error: hda irq intsts 0x intlctl 0xc081 rirb 00 [116525.402450] sof-audio-pci :00:1f.3: error: dsp irq ppsts 0x adspis 0x [116525.402471] sof-audio-pci :00:1f.3: error: host status 0x dsp status 0x mask 0x0003 [116525.402475] sof-audio-pci :00:1f.3: error: waking up any trace sleepers [116525.402481] sof-audio-pci :00:1f.3: error: failed to set dai config for iDisp1 [116525.402486] sof-audio-pci :00:1f.3: ASoC: can't set iDisp1 Pin hw params: -110 [116525.402498] iDisp1: ASoC: hw_params BE failed -110 [116525.402502] HDMI1: ASoC: hw_params BE failed -110 This _might_ be the upstream bug https://github.com/thesofproject/sof/issues/2828 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crosser 42712 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 20:40:20 2020 InstallationDate: Installed on 2020-01-02 (149 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) MachineType: LENOVO 20QDCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fres
[Kernel-packages] [Bug 1881505] Re: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7
It seems that the 1.6 version of the SOF firmware fixes the issue for me. Haven't got any of those DSP panic messages anymore after the update and before the update they occurred almost every day. Is there anything I can do to help in making this fix to be included to linux-firmware package? Eugene: Have you tried if your issue is fixed by the newer firmware? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1881505 Title: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Now and then, the notebooks stops producing any sound, and program that try to use sound output freeze for many seconds. There is a repeating sequence on messages in `dmesg`: [116525.402057] sof-audio-pci :00:1f.3: error: ipc timed out for 0x8001 size 120 [116525.402081] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [116525.402338] sof-audio-pci :00:1f.3: error: can't enter idle [116525.402342] sof-audio-pci :00:1f.3: error: trace point 4000 [116525.402346] sof-audio-pci :00:1f.3: error: panic at src/lib/agent.c:50 [116525.402350] sof-audio-pci :00:1f.3: error: DSP Firmware Oops [116525.402356] sof-audio-pci :00:1f.3: EXCCAUSE 0x003f EXCVADDR 0x PS 0x00060925 SAR 0x [116525.402361] sof-audio-pci :00:1f.3: EPC1 0x EPC2 0xbe00d30e EPC3 0x EPC40x [116525.402365] sof-audio-pci :00:1f.3: EPC5 0x EPC6 0x EPC7 0x DEPC0x [116525.402369] sof-audio-pci :00:1f.3: EPS2 0x00060d20 EPS3 0x EPS4 0x EPS50x [116525.402374] sof-audio-pci :00:1f.3: EPS6 0x EPS7 0x INTENABL 0x INTERRU 0x0222 [116525.402378] sof-audio-pci :00:1f.3: stack dump from 0xbe04f5b0 [116525.402385] sof-audio-pci :00:1f.3: 0xbe04f5b0: be00fc00 be04f5e0 be062180 0001 [116525.402391] sof-audio-pci :00:1f.3: 0xbe04f5b4: 0032 [116525.402396] sof-audio-pci :00:1f.3: 0xbe04f5b8: 69cd0100 15655b6c 602aeaf8 93a4 [116525.402401] sof-audio-pci :00:1f.3: 0xbe04f5bc: 93a4 303a3030 [116525.402406] sof-audio-pci :00:1f.3: 0xbe04f5c0: 0078 602aea98 93a4 [116525.402411] sof-audio-pci :00:1f.3: 0xbe04f5c4: 6bdcfb58 93a4 5d006830 93a4 [116525.402416] sof-audio-pci :00:1f.3: 0xbe04f5c8: 6ba37218 93a4 82317aaf bca5 [116525.402421] sof-audio-pci :00:1f.3: 0xbe04f5cc: 6ba37220 93a4 023179f8 bca5 [116525.402446] sof-audio-pci :00:1f.3: error: hda irq intsts 0x intlctl 0xc081 rirb 00 [116525.402450] sof-audio-pci :00:1f.3: error: dsp irq ppsts 0x adspis 0x [116525.402471] sof-audio-pci :00:1f.3: error: host status 0x dsp status 0x mask 0x0003 [116525.402475] sof-audio-pci :00:1f.3: error: waking up any trace sleepers [116525.402481] sof-audio-pci :00:1f.3: error: failed to set dai config for iDisp1 [116525.402486] sof-audio-pci :00:1f.3: ASoC: can't set iDisp1 Pin hw params: -110 [116525.402498] iDisp1: ASoC: hw_params BE failed -110 [116525.402502] HDMI1: ASoC: hw_params BE failed -110 This _might_ be the upstream bug https://github.com/thesofproject/sof/issues/2828 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crosser 42712 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 20:40:20 2020 InstallationDate: Installed on 2020-01-02 (149 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) MachineType: LENOVO 20QDCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version:
[Kernel-packages] [Bug 1900809] Re: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to v1.6
This update would also fix at least bug #1881505. Basically, my audio on Lenovo T14 was working very unreliably and jammed with a DSP panic quite often with the 1.4.2 version, but seems to work just fine with 1.6. It would be great to get this update included soon, since it's very inconvenient to reboot the laptop about 1-2 times a day, because that seems to be the only way to get audio working after the DSP paic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1900809 Title: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to v1.6 Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Focal: Triaged Status in linux-firmware source package in Groovy: Triaged Bug description: BugLink: https://bugs.launchpad.net/bugs/1900809 [Impact] Intel released the sof-firmware v1.6, and in our oem projects, the Dell TGL machines and the machines with soundwire audio need the new firmware, otherwise they will fail to load the firmware or the audio can't work well. [Fix] replace the old sof-firmware-v1.4.2 with sof-firmware-v1.6 [Test] Tested on the Dell cml/tgl soundwire machines, all audio functions worked well, and those audio functions didn't work with old firmware. Tested on Lenovo dimc machines, all audio functions worked as well as before. [Regression Potential] Intel tested the new firmware with the 5.8 and 5.9 kernel, but we need the new firmware to work with 5.4 and 5.6 kernel as well, so there is some possibility that the 5.4/5.6 kernel can't work well with the new sof-firmware. I have tested the new firmware with 5.4/5.6 kernel on some Lenovo machines, so far no issues were found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1900809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649144] Re: Bluetooth audio quality bad
I think this was written in error, unfortunately. It now appears to me that the cause of the problem described here was actually not due to Ubuntu touch as I have been able to reproduce it on an android device with the same headset. So it is likely a hardware issue related to the headset in question. Given that it only occurs in specific context (i.e using certain kind of audio) it was difficult to notice at first. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1649144 Title: Bluetooth audio quality bad Status in bluez package in Ubuntu: New Bug description: Listening to music using a2dp compatible bt headphones, the audio is bad. Let me explain. If I plug in a pare of headphones with a 3.5 mm stereo plug and compare it to the bluetooth audio, I cannot tell the difference in most devices. I know that a2dp is done with lossy compression, so in theory the audio quality suffers. However, the difference is minimal, something that you can either barely notice, or at times other links in the audio-to-ear chain are way worse masking the quality difference from compression. I have tested this on Android, Debian, Ubuntu etc. and I have to admit that most of the time there appears to be no difference to me. However, on Ubuntu touch (arale OTA-14) there is a difference that any one can notice immediately. The bluetooth audio is really poor, sounds as if it were distoreted and compressed or sample rate lowered or something. Not poor enough to make it unusable but poor enough that you notice it right away. I have no idea what package is causing this, but I suspect that it has something to do with either audio mixer or bluetooth. But everything seems to be OK. AFAIK the audio settings are as I would expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1649144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1360731] [NEW] Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht)
Public bug reported: Boot hangs if acpi is not entirely disabled on Acer Aspire V3-111P. Bios 1.05, newer (undocumented) version 1.11 untested so far. This hang does not occur on Ubuntu 12.04 LTS, but does on 14.04(.1) LTS, unless using "acpi=off". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 1777 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 24 04:20:31 2014 HibernationDevice: RESUME=UUID=cd1b13ba-5c85-4c64-bf69-aefe3e92c2dc InstallationDate: Installed on 2014-08-21 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer Aspire V3-111P ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5a0c649c-474a-4809-851e-70f69f035055 ro quiet splash acpi=off RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd04/11/2014:svnAcer:pnAspireV3-111P:pvrV1.05:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V3-111P dmi.product.version: V1.05 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1360731 Title: Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht) Status in “linux” package in Ubuntu: New Bug description: Boot hangs if acpi is not entirely disabled on Acer Aspire V3-111P. Bios 1.05, newer (undocumented) version 1.11 untested so far. This hang does not occur on Ubuntu 12.04 LTS, but does on 14.04(.1) LTS, unless using "acpi=off". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 1777 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 24 04:20:31 2014 HibernationDevice: RESUME=UUID=cd1b13ba-5c85-4c64-bf69-aefe3e92c2dc InstallationDate: Installed on 2014-08-21 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer Aspire V3-111P ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5a0c649c-474a-4809-851e-70f69f035055 ro quiet splash acpi=off RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd04/11/2014:svnAcer:pnAspireV3-111P:pvrV1.05:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V3-111P dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1360731] Re: Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht)
** Attachment added: "dmidecode.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360731/+attachment/4185639/+files/dmidecode.txt ** Description changed: Boot hangs if acpi is not entirely disabled on Acer Aspire V3-111P. - Bios 1.05, newer (undocumented) version 1.11 untested so far). + Bios 1.05, newer (undocumented) version 1.11 untested so far. This hang does not occur on Ubuntu 12.04 LTS, but does on 14.04(.1) LTS, unless using "acpi=off". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: iheino 1777 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: iheino 1777 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 24 04:20:31 2014 HibernationDevice: RESUME=UUID=cd1b13ba-5c85-4c64-bf69-aefe3e92c2dc InstallationDate: Installed on 2014-08-21 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer Aspire V3-111P ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5a0c649c-474a-4809-851e-70f69f035055 ro quiet splash acpi=off RelatedPackageVersions: - linux-restricted-modules-3.13.0-34-generic N/A - linux-backports-modules-3.13.0-34-generic N/A - linux-firmware 1.127.5 + linux-restricted-modules-3.13.0-34-generic N/A + linux-backports-modules-3.13.0-34-generic N/A + linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd04/11/2014:svnAcer:pnAspireV3-111P:pvrV1.05:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V3-111P dmi.product.version: V1.05 dmi.sys.vendor: Acer -- 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/1360731 Title: Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht) Status in “linux” package in Ubuntu: New Bug description: Boot hangs if acpi is not entirely disabled on Acer Aspire V3-111P. Bios 1.05, newer (undocumented) version 1.11 untested so far. This hang does not occur on Ubuntu 12.04 LTS, but does on 14.04(.1) LTS, unless using "acpi=off". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 1777 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 24 04:20:31 2014 HibernationDevice: RESUME=UUID=cd1b13ba-5c85-4c64-bf69-aefe3e92c2dc InstallationDate: Installed on 2014-08-21 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer Aspire V3-111P ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5a0c649c-474a-4809-851e-70f69f035055 ro quiet splash acpi=off RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd04/11/2014:svnAcer:pnAspireV3-111P:pvrV1.05:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V3-111P dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1360731] Re: Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht)
I currently don't have access to the hardware, as that system was decommissioned/repurposed. May have access to it during xmas break. In any case patrick's observations suggest that next step should be https://wiki.ubuntu.com/Kernel/KernelBisection between 3.13.0.32-generic and 3.13.0-34-generic to find which commit introduced the regression. Although older kernel might just as well behave similarly to acpi=off; hard to say whether it does without access to the hw atm. ** 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. https://bugs.launchpad.net/bugs/1360731 Title: Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht) Status in “linux” package in Ubuntu: Confirmed Bug description: Boot hangs if acpi is not entirely disabled on Acer Aspire V3-111P. Bios 1.05, newer (undocumented) version 1.11 untested so far. This hang does not occur on Ubuntu 12.04 LTS, but does on 14.04(.1) LTS, unless using "acpi=off". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 1777 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 24 04:20:31 2014 HibernationDevice: RESUME=UUID=cd1b13ba-5c85-4c64-bf69-aefe3e92c2dc InstallationDate: Installed on 2014-08-21 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer Aspire V3-111P ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5a0c649c-474a-4809-851e-70f69f035055 ro quiet splash acpi=off RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd04/11/2014:svnAcer:pnAspireV3-111P:pvrV1.05:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V3-111P dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 588993] Re: mcelog does not work due to lack of kernel support
For the record, first ever CE reported by mcelog below on the hardware I have access to. No UCEs nor even repeating CEs seen. Have not tested mce-inject and/or apei/einj.ko kernel module. mcelog: failed to prefill DIMM database from DMI data Hardware event. This is not a software error. MCE 0 CPU 0 BANK 0 TIME 1422983269 Tue Feb 3 19:07:49 2015 MCG status: MCi status: Corrected error Error enabled MCA: Internal parity error STATUS 904f0005 MCGSTATUS 0 MCGCAP c09 APICID 0 SOCKETID 0 CPUID Vendor Intel Family 6 Model 60 Syslog entries for mcelog startup on up-to-date trusty do still mention that page-offlining is unsupported: Feb 19 08:26:04 gx1 mcelog: failed to prefill DIMM database from DMI data Feb 19 08:26:04 gx1 mcelog: Kernel does not support page offline interface ** Tags added: trusty -- 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/588993 Title: mcelog does not work due to lack of kernel support Status in linux package in Ubuntu: Confirmed Bug description: mcelog does not seem to be happy with the current Ubuntu kernel. This is all I get in /var/log/syslog: # grep mce /var/log/syslog Jun 2 18:14:15 x mcelog: failed to prefill DIMM database from DMI data Jun 2 18:14:15 x mcelog: Kernel does not support page offline interface I can disable memory database prefill option in /etc/mcelog/mcelog.conf which silences the first error message. However, dmidecode seems to work just fine and produces reasonably looking output so I am not sure why prefill option of mcelog fails. Also, mcelog never outputs anything so I suspect it is not functional. I have a cluster of identical hardware and I can simulate a constant stream of MCE errors by misconfiguring memory settings in BIOS. The errors are successfully fetched and reported by mcelog on the nodes with CentOS 5 installed (kernel 2.6.18-164.15.1.el5). Nothing is reported under Ubuntu Server 10.04 LTS on this same hardware. # lsb_release -rd Description:Ubuntu 10.04 LTS Release:10.04 # uname -a Linux x 2.6.32-22-server #33-Ubuntu SMP Wed Apr 28 14:34:48 UTC 2010 x86_64 GNU/Linux # apt-cache policy mcelog mcelog: Installed: 1.0~pre3-1 Candidate: 1.0~pre3-1 Version table: *** 1.0~pre3-1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649144] [NEW] Bluetooth audio quality bad
Public bug reported: Listening to music using a2dp compatible bt headphones, the audio is bad. Let me explain. If I plug in a pare of headphones with a 3.5 mm stereo plug and compare it to the bluetooth audio, I cannot tell the difference in most devices. I know that a2dp is done with lossy compression, so in theory the audio quality suffers. However, the difference is minimal, something that you can either barely notice, or at times other links in the audio-to-ear chain are way worse masking the quality difference from compression. I have tested this on Android, Debian, Ubuntu etc. and I have to admit that most of the time there appears to be no difference to me. However, on Ubuntu touch (arale OTA-14) there is a difference that any one can notice immediately. The bluetooth audio is really poor, sounds as if it were distoreted and compressed or sample rate lowered or something. Not poor enough to make it unusable but poor enough that you notice it right away. I have no idea what package is causing this, but I suspect that it has something to do with either audio mixer or bluetooth. But everything seems to be OK. AFAIK the audio settings are as I would expect. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1649144 Title: Bluetooth audio quality bad Status in bluez package in Ubuntu: New Bug description: Listening to music using a2dp compatible bt headphones, the audio is bad. Let me explain. If I plug in a pare of headphones with a 3.5 mm stereo plug and compare it to the bluetooth audio, I cannot tell the difference in most devices. I know that a2dp is done with lossy compression, so in theory the audio quality suffers. However, the difference is minimal, something that you can either barely notice, or at times other links in the audio-to-ear chain are way worse masking the quality difference from compression. I have tested this on Android, Debian, Ubuntu etc. and I have to admit that most of the time there appears to be no difference to me. However, on Ubuntu touch (arale OTA-14) there is a difference that any one can notice immediately. The bluetooth audio is really poor, sounds as if it were distoreted and compressed or sample rate lowered or something. Not poor enough to make it unusable but poor enough that you notice it right away. I have no idea what package is causing this, but I suspect that it has something to do with either audio mixer or bluetooth. But everything seems to be OK. AFAIK the audio settings are as I would expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1649144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1211035] [NEW] nvidia-settings-325 crash with pressing exit button
Public bug reported: When im using nvidia-settings. When im change resolutions 1360x768 and apply and saved. Then im pressing exit button. Program crashed. my log say: kernel: [ 1773.710033] traps: nvidia-settings[5065] trap invalid opcode ip:7f515895e8f4 sp:7fff2857eb08 error:0 in libpixbufloader- xpm.so[7f515895a000+6000] Im using latest Nvidia drivers 325.15 drivers with NV Control 1.29. Ubuntu 12.10 64 bit. ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1211035 Title: nvidia-settings-325 crash with pressing exit button Status in “nvidia-settings” package in Ubuntu: New Bug description: When im using nvidia-settings. When im change resolutions 1360x768 and apply and saved. Then im pressing exit button. Program crashed. my log say: kernel: [ 1773.710033] traps: nvidia-settings[5065] trap invalid opcode ip:7f515895e8f4 sp:7fff2857eb08 error:0 in libpixbufloader- xpm.so[7f515895a000+6000] Im using latest Nvidia drivers 325.15 drivers with NV Control 1.29. Ubuntu 12.10 64 bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1211035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265475] [NEW] Please apply patches supporting Haswell based Chromebooks
Public bug reported: Hi! Would it be possible to apply these patches for the trusty kernel so that the next LTS would fully work on the new Haswell based Chromebooks (Acer C720, HP Chromebook 14) out of the box? Currently and without these patches e.g. touchpad doesn't work. https://patchwork.kernel.org/bundle/bleung/chromeos-laptop-deferring- and-haswell/ The patches apply cleanly against linux 3.12.0-7.15 in trusty. This would most likely also fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1257879. Individual links to the raw patches: https://patchwork.kernel.org/patch/3078491/raw/ https://patchwork.kernel.org/patch/3078481/raw/ https://patchwork.kernel.org/patch/3074391/raw/ https://patchwork.kernel.org/patch/3074441/raw/ https://patchwork.kernel.org/patch/3074421/raw/ https://patchwork.kernel.org/patch/3074401/raw/ https://patchwork.kernel.org/patch/3074431/raw/ https://patchwork.kernel.org/patch/3074411/raw/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1265475 Title: Please apply patches supporting Haswell based Chromebooks Status in “linux” package in Ubuntu: New Bug description: Hi! Would it be possible to apply these patches for the trusty kernel so that the next LTS would fully work on the new Haswell based Chromebooks (Acer C720, HP Chromebook 14) out of the box? Currently and without these patches e.g. touchpad doesn't work. https://patchwork.kernel.org/bundle/bleung/chromeos-laptop-deferring- and-haswell/ The patches apply cleanly against linux 3.12.0-7.15 in trusty. This would most likely also fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1257879. Individual links to the raw patches: https://patchwork.kernel.org/patch/3078491/raw/ https://patchwork.kernel.org/patch/3078481/raw/ https://patchwork.kernel.org/patch/3074391/raw/ https://patchwork.kernel.org/patch/3074441/raw/ https://patchwork.kernel.org/patch/3074421/raw/ https://patchwork.kernel.org/patch/3074401/raw/ https://patchwork.kernel.org/patch/3074431/raw/ https://patchwork.kernel.org/patch/3074411/raw/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265475] Re: Please apply patches supporting Haswell based Chromebooks
No need to gather logs, it's just a request for new hardware enablement in the kernel. These patches have been submitted to upstream for merge, but haven't been merged yet to submaintainer tree and Linus tree. ** 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. https://bugs.launchpad.net/bugs/1265475 Title: Please apply patches supporting Haswell based Chromebooks Status in “linux” package in Ubuntu: Confirmed Bug description: Hi! Would it be possible to apply these patches for the trusty kernel so that the next LTS would fully work on the new Haswell based Chromebooks (Acer C720, HP Chromebook 14) out of the box? Currently and without these patches e.g. touchpad doesn't work. https://patchwork.kernel.org/bundle/bleung/chromeos-laptop-deferring- and-haswell/ The patches apply cleanly against linux 3.12.0-7.15 in trusty. This would most likely also fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1257879. Individual links to the raw patches: https://patchwork.kernel.org/patch/3078491/raw/ https://patchwork.kernel.org/patch/3078481/raw/ https://patchwork.kernel.org/patch/3074391/raw/ https://patchwork.kernel.org/patch/3074441/raw/ https://patchwork.kernel.org/patch/3074421/raw/ https://patchwork.kernel.org/patch/3074401/raw/ https://patchwork.kernel.org/patch/3074431/raw/ https://patchwork.kernel.org/patch/3074411/raw/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038749] [NEW] amdgpu mst power saving null ptr deref
Public bug reported: Amdgpu tends to crash when attempting to unlock screen after power saving has been triggered on MST screen(s). Further details to be filled in post-reboot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 8 11:03:13 2023 InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038749 Title: amdgpu mst power saving null ptr deref Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Amdgpu tends to crash when attempting to unlock screen after power saving has been triggered on MST screen(s). Further details to be filled in post-reboot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 8 11:03:13 2023 InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038749] Re: amdgpu mst power saving null ptr deref
Duplicate of #2038748 which apparently got some more logs than this one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038749 Title: amdgpu mst power saving null ptr deref Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Amdgpu tends to crash when attempting to unlock screen after power saving has been triggered on MST screen(s). Further details to be filled in post-reboot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 8 11:03:13 2023 InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038749] Re: amdgpu mst power saving null ptr deref
** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Incomplete ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038749 Title: amdgpu mst power saving null ptr deref Status in linux-signed-hwe-6.2 package in Ubuntu: Invalid Bug description: Amdgpu tends to crash when attempting to unlock screen after power saving has been triggered on MST screen(s). Further details to be filled in post-reboot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 8 11:03:13 2023 InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038748] Re: Xorg freeze amdgpu mst powersaving
** Package changed: xorg (Ubuntu) => linux-signed-hwe-6.2 (Ubuntu) ** Summary changed: - Xorg freeze amdgpu mst powersaving + amdgpu mst power saving null ptr deref -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038748 Title: amdgpu mst power saving null ptr deref Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Reoccurrence of amdgpu MST power saving related null pointer deref. Likely should be against kernel instead, but let's see whether ubuntu- bug attached sensible part of logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Sun Oct 8 10:23:57 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038748] Re: amdgpu mst power saving null ptr deref
A fix may already be available at https://gitlab.freedesktop.org/drm/amd/-/issues/2486 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2486 https://gitlab.freedesktop.org/drm/amd/-/issues/2486 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038748 Title: amdgpu mst power saving null ptr deref Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Reoccurrence of amdgpu MST power saving related null pointer deref. Likely should be against kernel instead, but let's see whether ubuntu- bug attached sensible part of logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Sun Oct 8 10:23:57 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption
@toekneefan I know the workforce is always limited and I don't want to blame anyone. After all, I'm not paying for support. However, silent data corruption in a file system that is supposed to first and foremost prevent silent data corruption is a serious defect, and I understand that people are worried about the apparent inactivity on this bug. I'm also using ZFS on FreeBSD and there the patch was rushed out as soon as it was available. So it would be great to get some kind of indication if this is being worked on (such as triaging the bug). If we know that shipping the patch is going to take very long, then at least affected users can make an informed decision if they are just going to live with the bug or start looking for alternative solutions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952747] [NEW] amdgpu PSP load sos failed after hwe 5.11.0-27 -> -41 update
Public bug reported: Regression to be analyzed further later. 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5) Most relevant part of boot logs: Nov 30 13:08:00 ub3ff kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13 Nov 30 13:08:00 ub3ff kernel: Linux version 5.11.0-41-generic (buildd@lgw01-amd64-005) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 (Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22) Nov 30 13:08:00 ub3ff kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro drm.debug=0x4 splash vt.handoff=7 [...] Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: Will use PSP to load VCN firmware Nov 30 13:08:04 ub3ff systemd[1]: Finished Flush Journal to Persistent Storage. Nov 30 13:08:04 ub3ff kernel: snd_hda_intel :03:00.1: refused to change power state from D0 to D3hot Nov 30 13:08:04 ub3ff kernel: [drm:psp_hw_start [amdgpu]] *ERROR* PSP load sos failed! Nov 30 13:08:04 ub3ff kernel: [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed Nov 30 13:08:04 ub3ff kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block failed -22 Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: amdgpu_device_ip_init failed Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: Fatal error during GPU init Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: amdgpu: finishing device. Nov 30 13:08:04 ub3ff kernel: [ cut here ] Nov 30 13:08:04 ub3ff kernel: Memory manager not clean during takedown. Nov 30 13:08:04 ub3ff kernel: WARNING: CPU: 4 PID: 424 at drivers/gpu/drm/drm_mm.c:998 drm_mm_takedown+0x23/0x30 [drm] Nov 30 13:08:04 ub3ff kernel: Modules linked in: amdgpu(+) snd_hda_codec_realtek intel_rapl_msr 8021q garp mrp snd_hda_codec_generic mei_hdcp ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_common snd_hda_codec x86_pkg_temp_thermal intel_powerclamp snd_hda_core snd_hwdep input_leds coretemp soundwire_bus snd_soc_core iommu_v2 snd_compress ac97_bus kvm_intel gpu_sched joydev snd_pcm_dmaengine drm_ttm_helper ttm snd_pcm kvm snd_seq_midi drm_kms_helper snd_seq_midi_event crct10dif_pclmul ghash_clmulni_intel snd_rawmidi aesni_intel cec rc_core i2c_algo_bit crypto_simd snd_seq fb_sys_fops snd_seq_device cryptd snd_timer bridge glue_helper syscopyarea snd rapl sysfillrect soundcore stp sysimgblt intel_cstate llc wmi_bmof eeepc_wmi mei_me serio_raw efi_pstore at24 mei ie31200_edac mac_hid sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic usbhid hid uas usb_storage mfd_aaeon asus_wmi Nov 30 13:08:04 ub3ff kernel: sparse_keymap crc32_pclmul psmouse firewire_ohci mpt3sas firewire_core i2c_i801 ahci i2c_smbus crc_itu_t xhci_pci raid_class e1000e lpc_ich libahci xhci_pci_renesas scsi_transport_sas wmi video Nov 30 13:08:04 ub3ff kernel: CPU: 4 PID: 424 Comm: systemd-udevd Not tainted 5.11.0-41-generic #45~20.04.1-Ubuntu Nov 30 13:08:04 ub3ff kernel: Hardware name: System manufacturer System Product Name/P8B WS, BIOS 2106 07/16/2012 Nov 30 13:08:04 ub3ff kernel: RIP: 0010:drm_mm_takedown+0x23/0x30 [drm] Nov 30 13:08:04 ub3ff kernel: Code: 00 00 00 00 00 66 90 0f 1f 44 00 00 48 8b 47 38 48 83 c7 38 48 39 f8 75 01 c3 55 48 c7 c7 08 30 45 c0 48 89 e5 e8 13 86 98 e0 <0f> 0b 5d c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 Nov 30 13:08:04 ub3ff kernel: RSP: :bc5d00da3930 EFLAGS: 00010286 Nov 30 13:08:04 ub3ff kernel: RAX: RBX: 970a454c60e8 RCX: 0027 Nov 30 13:08:04 ub3ff kernel: RDX: 0027 RSI: dfff RDI: 97111f518ac8 Nov 30 13:08:04 ub3ff kernel: RBP: bc5d00da3930 R08: 97111f518ac0 R09: bc5d00da36f0 Nov 30 13:08:04 ub3ff kernel: R10: 0001 R11: 0001 R12: 970a454c60e8 Nov 30 13:08:04 ub3ff kernel: R13: 970a454c R14: 970a454c60d0 R15: 970a454c60e8 Nov 30 13:08:04 ub3ff kernel: FS: 7f147a343880() GS:97111f50() knlGS: Nov 30 13:08:04 ub3ff kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 30 13:08:04 ub3ff kernel: CR2: 56070c14 CR3: 000103772006 CR4: 001706e0 Nov 30 13:08:04 ub3ff kernel: Call Trace: Nov 30 13:08:04 ub3ff kernel: amdgpu_vram_mgr_fini+0xb3/0x130 [amdgpu] Nov 30 13:08:04 ub3ff kernel: amdgpu_ttm_fini+0xab/0x100 [amdgpu] Nov 30 13:08:04 ub3ff kernel: amdgpu_bo_fini+0x12/0x40 [amdgpu] Nov 30 13:08:04 ub3ff kernel: gmc_v10_0_sw_fini+0x33/0x40 [amdgpu] Nov 30 13:08:04 ub3ff kernel: amdgpu_device_fini+0x2ea/0x52f [amdgpu] Nov 30 13:08:04 ub3ff kernel: amdgpu_driver_unload_kms+0x43/0x70 [amdgpu] Nov 30 13:08:04 ub3ff kernel:
[Kernel-packages] [Bug 1952747] Re: amdgpu PSP load sos failed after hwe 5.11.0-27 -> -41 update
Turning off secondary and tertiary monitors for the duration of the initial boot appears to work around this issue. Suspend-to-ram works with all monitors powered (same hardware configuration as in #1926400). ** Attachment added: "journalctl -b -1 -k | egrep -v 'audit|dbus-daemon'" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1952747/+attachment/5544367/+files/jou-b-k.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1952747 Title: amdgpu PSP load sos failed after hwe 5.11.0-27 -> -41 update Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Regression to be analyzed further later. 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5) Most relevant part of boot logs: Nov 30 13:08:00 ub3ff kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13 Nov 30 13:08:00 ub3ff kernel: Linux version 5.11.0-41-generic (buildd@lgw01-amd64-005) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 (Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22) Nov 30 13:08:00 ub3ff kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro drm.debug=0x4 splash vt.handoff=7 [...] Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: Will use PSP to load VCN firmware Nov 30 13:08:04 ub3ff systemd[1]: Finished Flush Journal to Persistent Storage. Nov 30 13:08:04 ub3ff kernel: snd_hda_intel :03:00.1: refused to change power state from D0 to D3hot Nov 30 13:08:04 ub3ff kernel: [drm:psp_hw_start [amdgpu]] *ERROR* PSP load sos failed! Nov 30 13:08:04 ub3ff kernel: [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed Nov 30 13:08:04 ub3ff kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block failed -22 Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: amdgpu_device_ip_init failed Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: Fatal error during GPU init Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: amdgpu: finishing device. Nov 30 13:08:04 ub3ff kernel: [ cut here ] Nov 30 13:08:04 ub3ff kernel: Memory manager not clean during takedown. Nov 30 13:08:04 ub3ff kernel: WARNING: CPU: 4 PID: 424 at drivers/gpu/drm/drm_mm.c:998 drm_mm_takedown+0x23/0x30 [drm] Nov 30 13:08:04 ub3ff kernel: Modules linked in: amdgpu(+) snd_hda_codec_realtek intel_rapl_msr 8021q garp mrp snd_hda_codec_generic mei_hdcp ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_common snd_hda_codec x86_pkg_temp_thermal intel_powerclamp snd_hda_core snd_hwdep input_leds coretemp soundwire_bus snd_soc_core iommu_v2 snd_compress ac97_bus kvm_intel gpu_sched joydev snd_pcm_dmaengine drm_ttm_helper ttm snd_pcm kvm snd_seq_midi drm_kms_helper snd_seq_midi_event crct10dif_pclmul ghash_clmulni_intel snd_rawmidi aesni_intel cec rc_core i2c_algo_bit crypto_simd snd_seq fb_sys_fops snd_seq_device cryptd snd_timer bridge glue_helper syscopyarea snd rapl sysfillrect soundcore stp sysimgblt intel_cstate llc wmi_bmof eeepc_wmi mei_me serio_raw efi_pstore at24 mei ie31200_edac mac_hid sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic usbhid hid uas usb_storage mfd_aaeon asus_wmi Nov 30 13:08:04 ub3ff kernel: sparse_keymap crc32_pclmul psmouse firewire_ohci mpt3sas firewire_core i2c_i801 ahci i2c_smbus crc_itu_t xhci_pci raid_class e1000e lpc_ich libahci xhci_pci_renesas scsi_transport_sas wmi video Nov 30 13:08:04 ub3ff kernel: CPU: 4 PID: 424 Comm: systemd-udevd Not tainted 5.11.0-41-generic #45~20.04.1-Ubuntu Nov 30 13:08:04 ub3ff kernel: Hardware name: System manufacturer System Product Name/P8B WS, BIOS 2106 07/16/2012 Nov 30 13:08:04 ub3ff kernel: RIP: 0010:drm_mm_takedown+0x23/0x30 [drm] Nov 30 13:08:04 ub3ff kernel: Code: 00 00 00 00 00 66 90 0f 1f 44 00 00 48 8b 47 38 48 83 c7 38 48 39 f8 75 01 c3 55 48 c7 c7 08 30 45 c0 48 89 e5 e8 13 86 98 e0 <0f> 0b 5d c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 Nov 30 13:08:04 ub3ff kernel: RSP: :bc5d00da3930 EFLAGS: 00010286 Nov 30 13:08:04 ub3ff kernel: RAX: RBX: 970a454c60e8 RCX: 0027 Nov 30 13:08:04 ub3ff kernel: RDX: 0027 RSI: dfff RDI: 97111f518ac8 Nov 30 13:08:04 ub3ff kernel: RBP: bc5d00da3930 R08: 97111f518ac0 R09: bc5d00da36f0 Nov 30 13:08:04 ub3ff kernel: R10: 0001 R11: 0001 R12: 970a454c60e8 Nov 30 13:08:04 ub3ff kernel: R13: 970a454c R14: 970a454c60d0 R15: 970a454c60e8
[Kernel-packages] [Bug 1952747] Re: amdgpu PSP load sos failed after hwe 5.11.0-27 -> -41 update
** Description changed: Regression to be analyzed further later. 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5) - Most relevant part of boot logs: + Most relevant part of boot logs (more in attachment): Nov 30 13:08:00 ub3ff kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13 Nov 30 13:08:00 ub3ff kernel: Linux version 5.11.0-41-generic (buildd@lgw01-amd64-005) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 (Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22) Nov 30 13:08:00 ub3ff kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro drm.debug=0x4 splash vt.handoff=7 [...] Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: Will use PSP to load VCN firmware Nov 30 13:08:04 ub3ff systemd[1]: Finished Flush Journal to Persistent Storage. Nov 30 13:08:04 ub3ff kernel: snd_hda_intel :03:00.1: refused to change power state from D0 to D3hot Nov 30 13:08:04 ub3ff kernel: [drm:psp_hw_start [amdgpu]] *ERROR* PSP load sos failed! Nov 30 13:08:04 ub3ff kernel: [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed Nov 30 13:08:04 ub3ff kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block failed -22 Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: amdgpu_device_ip_init failed Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: Fatal error during GPU init Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: amdgpu: finishing device. - Nov 30 13:08:04 ub3ff kernel: [ cut here ] - Nov 30 13:08:04 ub3ff kernel: Memory manager not clean during takedown. - Nov 30 13:08:04 ub3ff kernel: WARNING: CPU: 4 PID: 424 at drivers/gpu/drm/drm_mm.c:998 drm_mm_takedown+0x23/0x30 [drm] - Nov 30 13:08:04 ub3ff kernel: Modules linked in: amdgpu(+) snd_hda_codec_realtek intel_rapl_msr 8021q garp mrp snd_hda_codec_generic mei_hdcp ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_common snd_hda_codec x86_pkg_temp_thermal intel_powerclamp snd_hda_core snd_hwdep input_leds coretemp soundwire_bus snd_soc_core iommu_v2 snd_compress ac97_bus kvm_intel gpu_sched joydev snd_pcm_dmaengine drm_ttm_helper ttm snd_pcm kvm snd_seq_midi drm_kms_helper snd_seq_midi_event crct10dif_pclmul ghash_clmulni_intel snd_rawmidi aesni_intel cec rc_core i2c_algo_bit crypto_simd snd_seq fb_sys_fops snd_seq_device cryptd snd_timer bridge glue_helper syscopyarea snd rapl sysfillrect soundcore stp sysimgblt intel_cstate llc wmi_bmof eeepc_wmi mei_me serio_raw efi_pstore at24 mei ie31200_edac mac_hid sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic usbhid hid uas usb_storage mfd_aaeon asus_wmi - Nov 30 13:08:04 ub3ff kernel: sparse_keymap crc32_pclmul psmouse firewire_ohci mpt3sas firewire_core i2c_i801 ahci i2c_smbus crc_itu_t xhci_pci raid_class e1000e lpc_ich libahci xhci_pci_renesas scsi_transport_sas wmi video - Nov 30 13:08:04 ub3ff kernel: CPU: 4 PID: 424 Comm: systemd-udevd Not tainted 5.11.0-41-generic #45~20.04.1-Ubuntu - Nov 30 13:08:04 ub3ff kernel: Hardware name: System manufacturer System Product Name/P8B WS, BIOS 2106 07/16/2012 + [...] Nov 30 13:08:04 ub3ff kernel: RIP: 0010:drm_mm_takedown+0x23/0x30 [drm] - Nov 30 13:08:04 ub3ff kernel: Code: 00 00 00 00 00 66 90 0f 1f 44 00 00 48 8b 47 38 48 83 c7 38 48 39 f8 75 01 c3 55 48 c7 c7 08 30 45 c0 48 89 e5 e8 13 86 98 e0 <0f> 0b 5d c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 - Nov 30 13:08:04 ub3ff kernel: RSP: :bc5d00da3930 EFLAGS: 00010286 - Nov 30 13:08:04 ub3ff kernel: RAX: RBX: 970a454c60e8 RCX: 0027 - Nov 30 13:08:04 ub3ff kernel: RDX: 0027 RSI: dfff RDI: 97111f518ac8 - Nov 30 13:08:04 ub3ff kernel: RBP: bc5d00da3930 R08: 97111f518ac0 R09: bc5d00da36f0 - Nov 30 13:08:04 ub3ff kernel: R10: 0001 R11: 0001 R12: 970a454c60e8 - Nov 30 13:08:04 ub3ff kernel: R13: 970a454c R14: 970a454c60d0 R15: 970a454c60e8 - Nov 30 13:08:04 ub3ff kernel: FS: 7f147a343880() GS:97111f50() knlGS: - Nov 30 13:08:04 ub3ff kernel: CS: 0010 DS: ES: CR0: 80050033 - Nov 30 13:08:04 ub3ff kernel: CR2: 56070c14 CR3: 000103772006 CR4: 001706e0 - Nov 30 13:08:04 ub3ff kernel: Call Trace: - Nov 30 13:08:04 ub3ff kernel: amdgpu_vram_mgr_fini+0xb3/0x130 [amdgpu] - Nov 30 13:08:04 ub3ff kernel: amdgpu_ttm_fini+0xab/0x100 [amdgpu] - Nov 30 13:08:04 ub3ff kernel: amdgpu_bo_fini+0x12/0x40 [amdgpu] - Nov 30 13:08:04 ub3ff kernel: gmc_v10_0_sw_fini+0x33/0x40 [amdgpu] - Nov 30 13:08:04 ub3f
[Kernel-packages] [Bug 1971095] [NEW] mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot)
Public bug reported: mpt2sas card driver failed to start properly after normal poweroff + restart. Logs attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 2287 F pulseaudio /dev/snd/controlC1: iheino 2287 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 1 20:54:28 2022 InstallationDate: Installed on 2022-04-27 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "journalctl -b 0 -g mpt2sas # failed / latest boot" https://bugs.launchpad.net/bugs/1971095/+attachment/5585633/+files/journalctl_b_0_g_mpt2sas -- 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/1971095 Title: mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot) Status in linux package in Ubuntu: New Bug description: mpt2sas card driver failed to start properly after normal poweroff + restart. Logs attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 2287 F pulseaudio /dev/snd/controlC1: iheino 2287 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 1 20:54:28 2022 InstallationDate: Installed on 2022-04-27 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : ht
[Kernel-packages] [Bug 1971095] Re: mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot)
** Attachment added: "previous (successful) boot logs for comparison" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971095/+attachment/5585653/+files/journalctl_b_-1_g_mpt2sas -- 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/1971095 Title: mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot) Status in linux package in Ubuntu: New Bug description: mpt2sas card driver failed to start properly after normal poweroff + restart. Logs attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 2287 F pulseaudio /dev/snd/controlC1: iheino 2287 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 1 20:54:28 2022 InstallationDate: Installed on 2022-04-27 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971095] Re: mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot)
$ journalctl -g 'Linux version' Apr 27 17:57:21 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic 5.15.30) -- Boot 05683256b29947edb0c968d647346b52 -- Apr 28 03:04:05 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic 5.15.30) -- Boot ce4c821e541d4983807d163d6651a939 -- May 01 18:48:21 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic 5.15.30) -- Boot 8ae1e85dbd854870b942a4bf3a3c8d48 -- May 01 20:16:08 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic 5.15.30) -- Boot c4f4000bf3094dceacbe78cd01e97ac6 -- May 01 21:41:27 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic 5.15.30) ... So far this has happened only once, hasn't been reproduced with same nor later kernels. -- 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/1971095 Title: mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot) Status in linux package in Ubuntu: Incomplete Bug description: mpt2sas card driver failed to start properly after normal poweroff + restart. Logs attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 2287 F pulseaudio /dev/snd/controlC1: iheino 2287 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 1 20:54:28 2022 InstallationDate: Installed on 2022-04-27 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881505] Re: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7
Now that the new SOF firmware is included in the linux-firmware package (see bug #1900809) the audio stack has been much more stable for me. Unfortunately there has been still one audio stack crash after the firmware upgrade, but it probably was another issue, since the dmesg didn't contain similar "DSP panic" messages then. If that new crash happens again, I'll open a new bug. However, I think this issue could be closed as fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1881505 Title: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Now and then, the notebooks stops producing any sound, and program that try to use sound output freeze for many seconds. There is a repeating sequence on messages in `dmesg`: [116525.402057] sof-audio-pci :00:1f.3: error: ipc timed out for 0x8001 size 120 [116525.402081] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [116525.402338] sof-audio-pci :00:1f.3: error: can't enter idle [116525.402342] sof-audio-pci :00:1f.3: error: trace point 4000 [116525.402346] sof-audio-pci :00:1f.3: error: panic at src/lib/agent.c:50 [116525.402350] sof-audio-pci :00:1f.3: error: DSP Firmware Oops [116525.402356] sof-audio-pci :00:1f.3: EXCCAUSE 0x003f EXCVADDR 0x PS 0x00060925 SAR 0x [116525.402361] sof-audio-pci :00:1f.3: EPC1 0x EPC2 0xbe00d30e EPC3 0x EPC40x [116525.402365] sof-audio-pci :00:1f.3: EPC5 0x EPC6 0x EPC7 0x DEPC0x [116525.402369] sof-audio-pci :00:1f.3: EPS2 0x00060d20 EPS3 0x EPS4 0x EPS50x [116525.402374] sof-audio-pci :00:1f.3: EPS6 0x EPS7 0x INTENABL 0x INTERRU 0x0222 [116525.402378] sof-audio-pci :00:1f.3: stack dump from 0xbe04f5b0 [116525.402385] sof-audio-pci :00:1f.3: 0xbe04f5b0: be00fc00 be04f5e0 be062180 0001 [116525.402391] sof-audio-pci :00:1f.3: 0xbe04f5b4: 0032 [116525.402396] sof-audio-pci :00:1f.3: 0xbe04f5b8: 69cd0100 15655b6c 602aeaf8 93a4 [116525.402401] sof-audio-pci :00:1f.3: 0xbe04f5bc: 93a4 303a3030 [116525.402406] sof-audio-pci :00:1f.3: 0xbe04f5c0: 0078 602aea98 93a4 [116525.402411] sof-audio-pci :00:1f.3: 0xbe04f5c4: 6bdcfb58 93a4 5d006830 93a4 [116525.402416] sof-audio-pci :00:1f.3: 0xbe04f5c8: 6ba37218 93a4 82317aaf bca5 [116525.402421] sof-audio-pci :00:1f.3: 0xbe04f5cc: 6ba37220 93a4 023179f8 bca5 [116525.402446] sof-audio-pci :00:1f.3: error: hda irq intsts 0x intlctl 0xc081 rirb 00 [116525.402450] sof-audio-pci :00:1f.3: error: dsp irq ppsts 0x adspis 0x [116525.402471] sof-audio-pci :00:1f.3: error: host status 0x dsp status 0x mask 0x0003 [116525.402475] sof-audio-pci :00:1f.3: error: waking up any trace sleepers [116525.402481] sof-audio-pci :00:1f.3: error: failed to set dai config for iDisp1 [116525.402486] sof-audio-pci :00:1f.3: ASoC: can't set iDisp1 Pin hw params: -110 [116525.402498] iDisp1: ASoC: hw_params BE failed -110 [116525.402502] HDMI1: ASoC: hw_params BE failed -110 This _might_ be the upstream bug https://github.com/thesofproject/sof/issues/2828 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crosser 42712 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 20:40:20 2020 InstallationDate: Installed on 2020-01-02 (149 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) MachineType: LENOVO 20QDCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Informat
[Kernel-packages] [Bug 2007722] [NEW] amdgpu updateMST crash 43s after resume
Public bug reported: Amdgpu has tendency of crashing after resume when MST responses of the displays waking up aren't what it expects. Sadly launchpad does not provide a way to review the logs sent by ubuntu-bug before submit button here, apparently can preview only locally prior to sending report. More details to be added after reboot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: iheino 3038 F pulseaudio /dev/snd/controlC0: iheino 3038 F pulseaudio /dev/snd/pcmC0D0c: iheino 3038 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Feb 17 21:23:03 2023 InstallationDate: Installed on 2022-04-27 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy -- 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/2007722 Title: amdgpu updateMST crash 43s after resume Status in linux package in Ubuntu: Confirmed Bug description: Amdgpu has tendency of crashing after resume when MST responses of the displays waking up aren't what it expects. Sadly launchpad does not provide a way to review the logs sent by ubuntu-bug before submit button here, apparently can preview only locally prior to sending report. More details to be added after reboot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: iheino 3038 F pulseaudio /dev/snd/controlC0: iheino 3038 F pulseaudio /dev/snd/pcmC0D0c: iheino 3038 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Feb 17 21:23:03 2023 InstallationDate: Installed on 2022-04-27 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Man
[Kernel-packages] [Bug 1870597] Re: libinput says "your system is too slow"
I have two laptops with Ubuntu 22.04 and only one laptop has random freezes with this syslog: Aug 29 15:20:23 pulse /usr/libexec/gdm-x-session[1287]: (II) event6 - Logitech M705: SYN_DROPPED event - some input events have been lost. Aug 29 15:20:23 pulse /usr/libexec/gdm-x-session[1287]: (EE) client bug: timer event6 debounce: scheduled expiry is in the past (-1246ms), your system is too slow Aug 29 15:20:23 pulse /usr/libexec/gdm-x-session[1287]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-1259ms), your system is too slow $ uname -a Linux pulse 6.2.0-31-generic #31~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Aug 16 13:45:26 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Once X got frozen permanently and I had to login via SSH to restart the X system. -- 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/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Fix Released Status in libinput: Fix Released Status in Linux: Confirmed Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2097035] Re: Recurring i915 hangs
In case this is not an RPLDIE issue, apt history shows these as latest
mesa upgrades and the issue was first observed shortly afterwards:
Start-Date: 2024-12-14 14:43:07
Commandline: aptdaemon role='role-commit-packages' sender=':1.760'
Upgrade: ovmf:amd64 (2024.02-2, 2024.02-2ubuntu0.1), libglx-mesa0:amd64
(24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3), libglx-mesa0:i386 (24.0.9-0ubuntu0.2,
24.0.9-0ubuntu0.3), packagekit-tools:amd64 (1.2.8-2build3, 1.2.8-2ubuntu1),
gstreamer1.0-packagekit:amd64 (1.2.8-2build3, 1.2.8-2ubuntu1), apport-gtk:amd64
(2.28.1-0ubuntu3.1, 2.28.1-0ubuntu3.3), libgbm1:amd64 (24.0.9-0ubuntu0.2,
24.0.9-0ubuntu0.3), libgbm1:i386 (24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3),
sssd-proxy:amd64 (2.9.4-1.1ubuntu6.1, 2.9.4-1.1ubuntu6.2),
gir1.2-udisks-2.0:amd64 (2.10.1-6build1, 2.10.1-6ubuntu1), udisks2:amd64
(2.10.1-6build1, 2.10.1-6ubuntu1), sssd-ad-common:amd64 (2.9.4-1.1ubuntu6.1,
2.9.4-1.1ubuntu6.2), sssd-ipa:amd64 (2.9.4-1.1ubuntu6.1, 2.9.4-1.1ubuntu6.2),
libxatracker2:amd64 (24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3),
gir1.2-packagekitglib-1.0:amd64 (1.2.8-2build3, 1.2.8-2ubuntu1),
mesa-va-drivers:amd64 (24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3),
mesa-va-drivers:i386 (24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3), libgl1-mes
a-dri:amd64 (24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3), libgl1-mesa-dri:i386
(24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3), libosmesa6:amd64 (24.0.9-0ubuntu0.2,
24.0.9-0ubuntu0.3), libosmesa6:i386 (24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3),
packagekit:amd64 (1.2.8-2build3, 1.2.8-2ubuntu1), libudisks2-0:amd64
(2.10.1-6build1, 2.10.1-6ubuntu1), sssd-krb5-common:amd64 (2.9.4-1.1ubuntu6.1,
2.9.4-1.1ubuntu6.2), libsss-nss-idmap0:amd64 (2.9.4-1.1ubuntu6.1,
2.9.4-1.1ubuntu6.2), mesa-vulkan-drivers:amd64 (24.0.9-0ubuntu0.2,
24.0.9-0ubuntu0.3), mesa-vulkan-drivers:i386 (24.0.9-0ubuntu0.2,
24.0.9-0ubuntu0.3), libpackagekit-glib2-18:amd64 (1.2.8-2build3,
1.2.8-2ubuntu1), python3-sss:amd64 (2.9.4-1.1ubuntu6.1, 2.9.4-1.1ubuntu6.2),
libglapi-mesa:amd64 (24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3), libglapi-mesa:i386
(24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3), sssd:amd64 (2.9.4-1.1ubuntu6.1,
2.9.4-1.1ubuntu6.2), python3-apport:amd64 (2.28.1-0ubuntu3.1,
2.28.1-0ubuntu3.3), libnss-sss:amd64 (2.9.4-1.1ubuntu6.1, 2.9.4-1.1ubu
ntu6.2), sssd-krb5:amd64 (2.9.4-1.1ubuntu6.1, 2.9.4-1.1ubuntu6.2),
libipa-hbac0t64:amd64 (2.9.4-1.1ubuntu6.1, 2.9.4-1.1ubuntu6.2), thermald:amd64
(2.5.6-2build2, 2.5.6-2ubuntu0.24.04.1), libegl-mesa0:amd64 (24.0.9-0ubuntu0.2,
24.0.9-0ubuntu0.3), apport-core-dump-handler:amd64 (2.28.1-0ubuntu3.1,
2.28.1-0ubuntu3.3), libsss-idmap0:amd64 (2.9.4-1.1ubuntu6.1,
2.9.4-1.1ubuntu6.2), sssd-ad:amd64 (2.9.4-1.1ubuntu6.1, 2.9.4-1.1ubuntu6.2),
mesa-vdpau-drivers:amd64 (24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3),
mesa-vdpau-drivers:i386 (24.0.9-0ubuntu0.2, 24.0.9-0ubuntu0.3),
sssd-common:amd64 (2.9.4-1.1ubuntu6.1, 2.9.4-1.1ubuntu6.2), libpam-sss:amd64
(2.9.4-1.1ubuntu6.1, 2.9.4-1.1ubuntu6.2), python3-problem-report:amd64
(2.28.1-0ubuntu3.1, 2.28.1-0ubuntu3.3), sssd-ldap:amd64 (2.9.4-1.1ubuntu6.1,
2.9.4-1.1ubuntu6.2), libsss-certmap0:amd64 (2.9.4-1.1ubuntu6.1,
2.9.4-1.1ubuntu6.2), apport:amd64 (2.28.1-0ubuntu3.1, 2.28.1-0ubuntu3.3)
End-Date: 2024-12-14 14:43:34
--
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/2097035
Title:
Recurring i915 hangs
Status in linux package in Ubuntu:
New
Bug description:
These igpu hangs have been recurring for a few weeks now:
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm] GPU
HANG: ecode 12:1:84db, in minetest [1588230]
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
Resetting chip for GuC failed to reset engine mask=0x1
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm]
minetest[1588230] context reset due to GPU hang
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
GuC firmware i915/tgl_guc_70.bin version 70.20.0
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
HuC firmware i915/tgl_huc.bin version 7.9.3
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
HuC: authenticated for all workloads
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
GUC: submission enabled
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
GUC: SLPC enabled
$ journalctl -S 2024-01-12 -g 'GT
[Kernel-packages] [Bug 2097035] Re: Recurring i915 hangs
Related debugging info appears to be available at
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11429
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11429
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11429
--
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/2097035
Title:
Recurring i915 hangs
Status in linux package in Ubuntu:
New
Bug description:
These igpu hangs have been recurring for a few weeks now:
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm] GPU
HANG: ecode 12:1:84db, in minetest [1588230]
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
Resetting chip for GuC failed to reset engine mask=0x1
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm]
minetest[1588230] context reset due to GPU hang
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
GuC firmware i915/tgl_guc_70.bin version 70.20.0
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
HuC firmware i915/tgl_huc.bin version 7.9.3
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
HuC: authenticated for all workloads
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
GUC: submission enabled
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
GUC: SLPC enabled
$ journalctl -S 2024-01-12 -g 'GT0: rcs0 reset request timed out'
-- Boot .. Boot --
Jan 04 06:39:26 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 04 06:39:26 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
-- Boot 9ebbdae32b6e4304a5071dc57ff08b19 --
-- Boot 72fa0c71974d405d8ffab206e8a3ee37 --
-- Boot 2c1b85d189d24cb1be5264bd92d04f72 --
-- Boot 57d3c0c8315246d581840bc9b8fff4c3 --
Jan 10 22:14:26 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 10 22:14:26 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
-- Boot 78111f5c8ffe45048502529477e6c715 --
Jan 18 21:18:37 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 18 21:18:37 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
-- Boot e8f5a7a754a34ff8b5b582ca03246126 --
Jan 25 09:27:04 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 25 09:27:04 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
-- Boot .. Boot until most recent one --
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-51-generic 6.8.0-51.52
ProcVersionSignature: Ubuntu 6.8.0-51.52-generic 6.8.12
Uname: Linux 6.8.0-51-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:iheino 5103 F pipewire
/dev/snd/pcmC0D0p: iheino 5103 F...m pipewire
/dev/snd/controlC0: iheino 5103 F pipewire
iheino 5110 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Jan 30 22:47:22 2025
MachineType: LENOVO 30HACTO1WW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-51-generic
root=UUID=e74c4a8a-f088-466f-b588-b6615e813570 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.8.0-51-generic N/A
linux-backports-modules-6.8.0-51-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.7
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/27/2024
dmi.bios.release: 1.45
dmi.bios.vendor: LENOVO
dmi.bios.version: S0JKT2DA
dmi.board.name: 1066
dmi.board.vendor: LENOVO
dmi.board.version: NOK
dmi.chas
[Kernel-packages] [Bug 2097035] Re: Recurring i915 hangs
INTEL_DEBUG=reemit does indeed appear to prevent this crash as well.
--
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/2097035
Title:
Recurring i915 hangs
Status in linux package in Ubuntu:
New
Bug description:
These igpu hangs have been recurring for a few weeks now:
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm] GPU
HANG: ecode 12:1:84db, in minetest [1588230]
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
Resetting chip for GuC failed to reset engine mask=0x1
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm]
minetest[1588230] context reset due to GPU hang
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
GuC firmware i915/tgl_guc_70.bin version 70.20.0
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
HuC firmware i915/tgl_huc.bin version 7.9.3
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
HuC: authenticated for all workloads
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
GUC: submission enabled
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
GUC: SLPC enabled
$ journalctl -S 2024-01-12 -g 'GT0: rcs0 reset request timed out'
-- Boot .. Boot --
Jan 04 06:39:26 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 04 06:39:26 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
-- Boot 9ebbdae32b6e4304a5071dc57ff08b19 --
-- Boot 72fa0c71974d405d8ffab206e8a3ee37 --
-- Boot 2c1b85d189d24cb1be5264bd92d04f72 --
-- Boot 57d3c0c8315246d581840bc9b8fff4c3 --
Jan 10 22:14:26 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 10 22:14:26 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
-- Boot 78111f5c8ffe45048502529477e6c715 --
Jan 18 21:18:37 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 18 21:18:37 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
-- Boot e8f5a7a754a34ff8b5b582ca03246126 --
Jan 25 09:27:04 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
Jan 25 09:27:04 localhost.localdomain kernel: i915 :00:02.0: [drm]
*ERROR* GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
-- Boot .. Boot until most recent one --
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-51-generic 6.8.0-51.52
ProcVersionSignature: Ubuntu 6.8.0-51.52-generic 6.8.12
Uname: Linux 6.8.0-51-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:iheino 5103 F pipewire
/dev/snd/pcmC0D0p: iheino 5103 F...m pipewire
/dev/snd/controlC0: iheino 5103 F pipewire
iheino 5110 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Jan 30 22:47:22 2025
MachineType: LENOVO 30HACTO1WW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-51-generic
root=UUID=e74c4a8a-f088-466f-b588-b6615e813570 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.8.0-51-generic N/A
linux-backports-modules-6.8.0-51-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.7
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/27/2024
dmi.bios.release: 1.45
dmi.bios.vendor: LENOVO
dmi.bios.version: S0JKT2DA
dmi.board.name: 1066
dmi.board.vendor: LENOVO
dmi.board.version: NOK
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.17
dmi.modalias:
dmi:bvnLENOVO:bvrS0JKT2DA:bd12/27/2024:br1.45:ef
[Kernel-packages] [Bug 2097035] [NEW] Recurring i915 hangs
Public bug reported:
These igpu hangs have been recurring for a few weeks now:
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm] *ERROR*
GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm] GPU
HANG: ecode 12:1:84db, in minetest [1588230]
Jan 30 22:07:13 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
Resetting chip for GuC failed to reset engine mask=0x1
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] *ERROR*
GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] *ERROR*
GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm]
minetest[1588230] context reset due to GPU hang
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0: GuC
firmware i915/tgl_guc_70.bin version 70.20.0
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0: HuC
firmware i915/tgl_huc.bin version 7.9.3
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
HuC: authenticated for all workloads
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
GUC: submission enabled
Jan 30 22:07:14 localhost.localdomain kernel: i915 :00:02.0: [drm] GT0:
GUC: SLPC enabled
$ journalctl -S 2024-01-12 -g 'GT0: rcs0 reset request timed out'
-- Boot .. Boot --
Jan 04 06:39:26 localhost.localdomain kernel: i915 :00:02.0: [drm] *ERROR*
GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 04 06:39:26 localhost.localdomain kernel: i915 :00:02.0: [drm] *ERROR*
GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
-- Boot 9ebbdae32b6e4304a5071dc57ff08b19 --
-- Boot 72fa0c71974d405d8ffab206e8a3ee37 --
-- Boot 2c1b85d189d24cb1be5264bd92d04f72 --
-- Boot 57d3c0c8315246d581840bc9b8fff4c3 --
Jan 10 22:14:26 localhost.localdomain kernel: i915 :00:02.0: [drm] *ERROR*
GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 10 22:14:26 localhost.localdomain kernel: i915 :00:02.0: [drm] *ERROR*
GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
-- Boot 78111f5c8ffe45048502529477e6c715 --
Jan 18 21:18:37 localhost.localdomain kernel: i915 :00:02.0: [drm] *ERROR*
GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 18 21:18:37 localhost.localdomain kernel: i915 :00:02.0: [drm] *ERROR*
GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
-- Boot e8f5a7a754a34ff8b5b582ca03246126 --
Jan 25 09:27:04 localhost.localdomain kernel: i915 :00:02.0: [drm] *ERROR*
GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 25 09:27:04 localhost.localdomain kernel: i915 :00:02.0: [drm] *ERROR*
GT0: rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
-- Boot .. Boot until most recent one --
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-51-generic 6.8.0-51.52
ProcVersionSignature: Ubuntu 6.8.0-51.52-generic 6.8.12
Uname: Linux 6.8.0-51-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:iheino 5103 F pipewire
/dev/snd/pcmC0D0p: iheino 5103 F...m pipewire
/dev/snd/controlC0: iheino 5103 F pipewire
iheino 5110 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Jan 30 22:47:22 2025
MachineType: LENOVO 30HACTO1WW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-51-generic
root=UUID=e74c4a8a-f088-466f-b588-b6615e813570 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.8.0-51-generic N/A
linux-backports-modules-6.8.0-51-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.7
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/27/2024
dmi.bios.release: 1.45
dmi.bios.vendor: LENOVO
dmi.bios.version: S0JKT2DA
dmi.board.name: 1066
dmi.board.vendor: LENOVO
dmi.board.version: NOK
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.17
dmi.modalias:
dmi:bvnLENOVO:bvrS0JKT2DA:bd12/27/2024:br1.45:efr1.17:svnLENOVO:pn30HACTO1WW:pvrThinkStationP3Ultra:rvnLENOVO:rn1066:rvrNOK:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_30HA_BU_Think_FM_ThinkStationP3Ultra:
dmi.product.family: ThinkStation P3 Ultra
dmi.product.name: 30HACTO1WW
dmi.product.sku: LENOVO_MT_30HA_BU_Think_FM_ThinkStation P3 Ultra
dmi.product.version: ThinkStation P3 Ultra
dmi.sys.vendor: LENOVO
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 appo
