[Kernel-packages] [Bug 1848318] Re: [DELL][BIONICS] Observed firmware assert during backgroung scan.
** Changed in: linux-oem (Ubuntu Bionic) Status: Invalid => Fix Committed ** Changed in: linux-oem (Ubuntu Bionic) Assignee: (unassigned) => Ganapathi Raju Kondraju (ganapathiraju) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1848318 Title: [DELL][BIONICS] Observed firmware assert during backgroung scan. Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Committed Bug description: SRU Justification: -- Impact: --- Observed firmware assert(non responsive state) just 2 min after connection. Test case: -- 1) Power up the device, Redpine modules are loaded by default, Nmcli initiates the connection and device starts background scan after connection. After 2-3 min issue will be replicated. Result: --- Observed firmware assert while performing background scan. Root cause analysis: There is a redundant null check for ssid info while preparing probe request in background scan case, which blocks the probe request pkt length update, leads to assert no-71(if probe-req-length is 0 or greater the max probe length 120) in firmware. Fix: Removed the redundant null check. Regression Potential: - This is observed just 2 min after connection, fixed and checked the driver stability. Every thing ran smooth. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848318/+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 1856161] Re: Thunderbolt dock fails to connect USB devices
As I mentioned in comment 22, connecting the thunderbolt dock without any additional USB devices plugged in, works well. After the controller initializes, I can plug in the rest of the devices and they get set up properly. Comment 22 has a dmesg log off that. I haven't tried booting with the dock connected without the additional USB devices, as that is not my use case (I don't usually shut down or reboot my computer), but I can try that later today. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin:
[Kernel-packages] [Bug 1857181] Re: Kernel driver updates caused BlueTooth to not start
Can you please identify which version the BT works and which version does not? -- 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/1857181 Title: Kernel driver updates caused BlueTooth to not start Status in linux package in Ubuntu: Confirmed Bug description: If this report is a duplicate it is because my first attempt resulted in a time-out error. Ubuntu 18.04, with latest updates. On 20th December I did my weekly disk image as part of my back-up (BU) routine. At that time BlueTooth (BT) was working correctly. I completed the BU, rebooted and once I was signed in again the Software Updater showed updates to be installed, which included KERNEL DRIVERS. On completion of the update BT no longer functioned, with an error message like Daemon Bluez not started. (i can't be sure exactly of the text). I hunted for fixes on-line by removing and re-installing the BT packages, even using a different version of the Bluez package, subscripted :i386. I did realise from the queries on-line that this area of Linux has proved difficult for many over the years, but for me this is the first difficulty I have had. In summary, Restoring the most recent BU image gave me back BT, but the Software Updater tried repeatedly to install the new kernel drivers, even when the box was unticked. So I have uninstalled Software Updater and will rely upon a manual update periodically until the kernel drivers problem is resolved. It's just that I haven't worked out how to filter out the kernel updates anyway! That's all I can give you for now, regards, Steve. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 4022 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 21 04:12:55 2019 HibernationDevice: RESUME=UUID=5eee2769-becc-4d7b-804a-d4c188a257f6 InstallationDate: Installed on 2018-06-13 (555 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: TOSHIBA SATELLITE P770 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ac16a96e-c63e-4723-bade-267625ad9d80 ro quiet splash reboot=bios vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-25 (329 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.80 dmi.board.asset.tag: NULL dmi.board.name: PHRAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr1.80:bd12/14/2011:svnTOSHIBA:pnSATELLITEP770:pvrPSBY3E-02800HEN:rvnTOSHIBA:rnPHRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: SATELLITE P770 dmi.product.version: PSBY3E-02800HEN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857181/+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 1850681] Re: TREKSTOR Primebook C11B touchpad and touchscreen not working
$ sudo apt install linux-generic-hwe-18.04-edge -- 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/1850681 Title: TREKSTOR Primebook C11B touchpad and touchscreen not working Status in linux package in Ubuntu: Incomplete Bug description: touchpad not working, only usb-mouse is recognized. touchscreen functionality not working, but that would be rather less important. Everything else is perfectly fine. (18.04 LTS) TREKSTOR Primebook C11B Thanks :-) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 18:43:32 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2019-10-26 (4 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TREKSTOR Primebook C11B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=efc3c4a6-eb3c-4dc1-8a8e-0f53d786817d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.1.2 dmi.board.asset.tag: Default string dmi.board.name: Apollolake_alk_V01 dmi.board.vendor: TS_weibu dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.1.2:bd05/03/2018:svnTREKSTOR:pnPrimebookC11B:pvrDefaultstring:rvnTS_weibu:rnApollolake_alk_V01:rvrDefaultstring:cvn:ct31:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: Primebook C11B dmi.product.sku: CFALKWW03 dmi.product.version: Default string dmi.sys.vendor: TREKSTOR version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850681/+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 1857307] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1857307 Title: Wireless wouldn't turn on. Status in linux package in Ubuntu: Confirmed Bug description: I used Ubuntu on this machine starting with 16.04 LTS. The network PCI never worked but USB D-Link card did work... up to recently and then it stopped. I installed 18.04 LTS -- it read Airplane Mode On and nothing could be done. rfkill gave me phy0 soft block no, hard block yes. But f8+Fn only caused a pop-up message that Airplane Mod On or Off but not in the status bar -- there it was always on with an instruction to use hardware switch and setting wireless never worked. I installed KDE over Ubuntu 19 now and Airplane Mode can be turned On and Off but WiFi never turns on. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anatoly1081 F pulseaudio /dev/snd/pcmC0D0p: anatoly1081 F...m pulseaudio CurrentDesktop: KDE Date: Sun Dec 22 20:58:33 2019 InstallationDate: Installed on 2019-12-20 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20LQS0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=5f3b3bd7-d68f-47e0-99e0-7d5c8befd27a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: yes SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0TET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LQS0 dmi.board.vendor: LENOVO dmi.board.version: SDK0K13476 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0TET37W(1.11):bd03/01/2018:svnLENOVO:pn20LQS0:pvrThinkPad11e5thGen:rvnLENOVO:rn20LQS0:rvrSDK0K13476WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad 11e 5th Gen dmi.product.name: 20LQS0 dmi.product.sku: LENOVO_MT_20LQ_BU_Think_FM_ThinkPad 11e 5th Gen dmi.product.version: ThinkPad 11e 5th Gen dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857307/+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 1857307] [NEW] Wireless wouldn't turn on.
Public bug reported: I used Ubuntu on this machine starting with 16.04 LTS. The network PCI never worked but USB D-Link card did work... up to recently and then it stopped. I installed 18.04 LTS -- it read Airplane Mode On and nothing could be done. rfkill gave me phy0 soft block no, hard block yes. But f8+Fn only caused a pop-up message that Airplane Mod On or Off but not in the status bar -- there it was always on with an instruction to use hardware switch and setting wireless never worked. I installed KDE over Ubuntu 19 now and Airplane Mode can be turned On and Off but WiFi never turns on. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anatoly1081 F pulseaudio /dev/snd/pcmC0D0p: anatoly1081 F...m pulseaudio CurrentDesktop: KDE Date: Sun Dec 22 20:58:33 2019 InstallationDate: Installed on 2019-12-20 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20LQS0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=5f3b3bd7-d68f-47e0-99e0-7d5c8befd27a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: yes SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0TET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LQS0 dmi.board.vendor: LENOVO dmi.board.version: SDK0K13476 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0TET37W(1.11):bd03/01/2018:svnLENOVO:pn20LQS0:pvrThinkPad11e5thGen:rvnLENOVO:rn20LQS0:rvrSDK0K13476WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad 11e 5th Gen dmi.product.name: 20LQS0 dmi.product.sku: LENOVO_MT_20LQ_BU_Think_FM_ThinkPad 11e 5th Gen dmi.product.version: ThinkPad 11e 5th Gen dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1857307 Title: Wireless wouldn't turn on. Status in linux package in Ubuntu: New Bug description: I used Ubuntu on this machine starting with 16.04 LTS. The network PCI never worked but USB D-Link card did work... up to recently and then it stopped. I installed 18.04 LTS -- it read Airplane Mode On and nothing could be done. rfkill gave me phy0 soft block no, hard block yes. But f8+Fn only caused a pop-up message that Airplane Mod On or Off but not in the status bar -- there it was always on with an instruction to use hardware switch and setting wireless never worked. I installed KDE over Ubuntu 19 now and Airplane Mode can be turned On and Off but WiFi never turns on. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anatoly1081 F pulseaudio /dev/snd/pcmC0D0p: anatoly1081 F...m pulseaudio CurrentDesktop: KDE Date: Sun Dec 22 20:58:33 2019 InstallationDate: Installed on 2019-12-20 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20LQS0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Proc
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
Does this happen when nothing is plugged to the dock? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId: d83854e8c81f5d47b0b99c8a3b42ae5127c75eb8 ParentDeviceId: 84edf0
[Kernel-packages] [Bug 1835176] Re: Flexible All Core Turbo (FACT) support
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1835176 Title: Flexible All Core Turbo (FACT) support Status in intel: Invalid Status in linux package in Ubuntu: Expired Bug description: Description: Add Linux support for Flexible All Core Turbo feature newly added to ICX -SP POR. Target Release: 19.10 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835176/+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 1834418] Re: GPIO support for Idaville
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1834418 Title: GPIO support for Idaville Status in intel: Won't Fix Status in linux package in Ubuntu: Expired Bug description: Description: Enable GPIO support for Idaville. This needs to be enabled in some customer setups. Target Kernel: TBD Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834418/+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 1855235] Re: Intel Wireless-AC 9560 Bluetooth, whenever connected to BLE devices, causes UI freeze when re-logging in after resumed from suspend
** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Invalid ** Changed in: hwe-next Status: New => Fix Released -- 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/1855235 Title: Intel Wireless-AC 9560 Bluetooth, whenever connected to BLE devices, causes UI freeze when re-logging in after resumed from suspend Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Disco: Fix Released Status in linux-firmware source package in Eoan: Fix Released Bug description: [Steps to Reproduce] 1. Pair some Bluetooth BLE device. Open a terminal and run `dmesg -w` to make sure Bluetooth is receiving advertisement events and repeatedly printing: Bluetooth: hci0: advertising data len corrected ... 2. Turn off dim display/blank screen on idle in Settings 3. Shorten long idle suspend time to 2 minutes by: $ gsettings set org.gnome.settings-daemon.plugins.power \ sleep-inactive-ac-timeout 120 4. Idle wait for 2 minute and let system suspend. 5. Resume after 20 seconds suspend or so. [Expected result] System resumes normally. [Actual result] * Screen lighted up, sent to GDM greeter as expected, but UI freeze when pressed ENTER to submit filled account name/password. * No console switch is possible. * Kernel alive because rescue magic key is the only way to escape. * The last line in syslog is: kernel [...] PM: suspend entry (deep) * When Bluetooth is rfkilled, this issue is not happening. When Bluetooth has never paired to BLE devices, this issue is no happening, either. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X21 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-02 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux-firmware 1.173.12 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-1028.32-oem-osp1 5.0.21 Tags: bionic Uname: Linux 5.0.0-1028-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855235/+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 1802652] Re: keyboard backlight not working on Asus GM501
dmesg: [ 14.503395] asus_wmi: ASUS WMI generic driver loaded [ 14.505116] asus_wmi: Initialization: 0x1 [ 14.505180] asus_wmi: BIOS WMI version: 9.0 [ 14.505219] asus_wmi: SFUN value: 0x21 [ 14.505221] asus-nb-wmi asus-nb-wmi: Detected ATK, not ASUSWMI, use DSTS [ 14.505223] asus-nb-wmi asus-nb-wmi: Detected ATK, enable event queue [ 14.507229] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input29 [ 14.662354] asus_wmi: Number of fans: 0 -- 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/1802652 Title: keyboard backlight not working on Asus GM501 Status in linux package in Ubuntu: Confirmed Bug description: The keyboard lights and most of the F keys aren't working. Kernel = 4.15.0-20-generic System linux mint 19 ls -hal /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Nov 10 15:47 . drwxr-xr-x 72 root root 0 Nov 10 15:43 .. lrwxrwxrwx 1 root root 0 Nov 10 15:43 asus::lightbar -> ../../devices/platform/asus-nb-wmi/leds/asus::lightbar lrwxrwxrwx 1 root root 0 Nov 10 15:47 asus-wireless::airplane -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::capslock -> ../../devices/platform/i8042/serio0/input/input4/input4::capslock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::numlock -> ../../devices/platform/i8042/serio0/input/input4/input4::numlock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::scrolllock -> ../../devices/platform/i8042/serio0/input/input4/input4::scrolllock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::capslock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::compose -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::compose lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::kana -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::kana lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::numlock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::scrolllock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::capslock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::compose -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::compose lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::kana -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::kana lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::numlock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::scrolllock lrwxrwxrwx 1 root root 0 Nov 10 15:47 phy0-led -> ../../devices/pci:00/:00:14.3/leds/phy0-led To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+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 1802652] Re: keyboard backlight not working on Asus GM501
Confirming for newer model: DMI: ASUSTeK COMPUTER INC. Zephyrus S GX502GW_GX502GW/GX502GW, BIOS GX502GW.306 09/25/2019 Same key issue as this: - F5 (fan overboost, that's ok if it doesn't work) - F6 (don't know what it is) - F7 (screen brightness down) - F8 (screen brightness up) - F10 (disable touchpad) - F11 (screen sleep) - F12 (airplane mode) - keyboard arrow up (brightness keyboard light up) - keyboard arrow down (brightness keyboard light down) And also some shortcut buttons above F1-F4: - disable mic button - rog button (it's ok if it doesn't work, but if works we can change it to something?) # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Pop!_OS 19.10 Release:19.10 Codename: eoan # uname -r 5.3.0-7625-generic # ls -l /sys/class/leds lrwxrwxrwx 0 root 23 Dec 15:41 asus-wireless::airplane -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane lrwxrwxrwx 0 root 23 Dec 15:41 asus::lightbar -> ../../devices/platform/asus-nb-wmi/leds/asus::lightbar lrwxrwxrwx 0 root 23 Dec 15:41 input4::capslock -> ../../devices/platform/i8042/serio0/input/input4/input4::capslock lrwxrwxrwx 0 root 23 Dec 15:41 input4::numlock -> ../../devices/platform/i8042/serio0/input/input4/input4::numlock lrwxrwxrwx 0 root 23 Dec 15:41 input4::scrolllock -> ../../devices/platform/i8042/serio0/input/input4/input4::scrolllock lrwxrwxrwx 0 root 23 Dec 15:41 input38::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-5/1-5:1.2/0003:046D:C52B.0007/0003:046D:406F.0008/input/input38/input38::capslock lrwxrwxrwx 0 root 23 Dec 15:41 input38::compose -> ../../devices/pci:00/:00:14.0/usb1/1-5/1-5:1.2/0003:046D:C52B.0007/0003:046D:406F.0008/input/input38/input38::compose lrwxrwxrwx 0 root 23 Dec 15:41 input38::kana -> ../../devices/pci:00/:00:14.0/usb1/1-5/1-5:1.2/0003:046D:C52B.0007/0003:046D:406F.0008/input/input38/input38::kana lrwxrwxrwx 0 root 23 Dec 15:41 input38::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-5/1-5:1.2/0003:046D:C52B.0007/0003:046D:406F.0008/input/input38/input38::numlock lrwxrwxrwx 0 root 23 Dec 15:41 input38::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-5/1-5:1.2/0003:046D:C52B.0007/0003:046D:406F.0008/input/input38/input38::scrolllock lrwxrwxrwx 0 root 23 Dec 15:41 input43::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.000A/input/input43/input43::capslock lrwxrwxrwx 0 root 23 Dec 15:41 input43::compose -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.000A/input/input43/input43::compose lrwxrwxrwx 0 root 23 Dec 15:41 input43::kana -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.000A/input/input43/input43::kana lrwxrwxrwx 0 root 23 Dec 15:41 input43::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.000A/input/input43/input43::numlock lrwxrwxrwx 0 root 23 Dec 15:41 input43::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.000A/input/input43/input43::scrolllock lrwxrwxrwx 0 root 23 Dec 15:41 input63::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.001E/input/input63/input63::capslock lrwxrwxrwx 0 root 23 Dec 15:41 input63::compose -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.001E/input/input63/input63::compose lrwxrwxrwx 0 root 23 Dec 15:41 input63::kana -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.001E/input/input63/input63::kana lrwxrwxrwx 0 root 23 Dec 15:41 input63::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.001E/input/input63/input63::numlock lrwxrwxrwx 0 root 23 Dec 15:41 input63::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.001E/input/input63/input63::scrolllock lrwxrwxrwx 0 root 23 Dec 15:41 phy0-led -> ../../devices/pci:00/:00:14.3/leds/phy0-led -- 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/1802652 Title: keyboard backlight not working on Asus GM501 Status in linux package in Ubuntu: Confirmed Bug description: The keyboard lights and most of the F keys aren't working. Kernel = 4.15.0-20-generic System linux mint 19 ls -hal /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Nov 10 15:47 . drwxr-xr-x 72 root root 0 Nov 10 15:43 .. lrwxrwxrwx 1 root root 0 Nov 10 15:43 asus::lightbar -> ../../devices/platform/asus-nb-wmi/leds/asus::lightbar lrwxrwxrwx 1 root root 0 Nov 10 15:47 asus-wireless::airplane -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::capslock -> ../../devices/platform/i8042/serio0/input/input4/input4::capslock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::numlock -> ../../devices/platform/
[Kernel-packages] [Bug 1837683] Re: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed
Thanks. Please ensure you don't have any external monitor plugged in while diagnosing this bug as it seems to have caused some confusion. Per comment #13, please test latest mainline kernel which is now: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc2/ ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1837683 Title: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: environment: - XPS-13-938 - connect 5G ac wifi - disabled suspend in power setting - disabled blank screen in power setting steps: - play 4k video by chrome on youtube[1] overnight symptom: - after about 8 hours, the screen is black and keyboard and mouse can not wake up screen. - the audio of 4K video is still playing, I can hear that when screen is black. - magic key still work, so I can reboot system by magic key. - a repeat error message in syslog: " Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW) modeset(0): Page flip failed: Invalid argument Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (EE) modeset(0): present flip failed " [1] https://www.youtube.com/watch?v=pkKBXH2qc_I&t=11701s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-1047.52-oem 4.15.18 Uname: Linux 4.15.0-1047-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 24 09:47:59 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08af] InstallationDate: Installed on 2019-07-20 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1047-oem root=UUID=77efb06b-1ce6-4749-a131-67f57aa8b21b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837683/+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 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
** Tags added: regression-update rls-bb-incoming ** Tags removed: rls-bb-incoming -- 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/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication control
[Kernel-packages] [Bug 1856370] Re: GPU has fallen off the bus
I don't think this bug should be used two track two different issues. This bug should be about the original problem: "Every time I suspend my laptop, after I resume it, a black screen shows with the error message - GPU has fallen off the bus" ** Summary changed: - GPU has fallen off the bus + Black screen with message "GPU has fallen off the bus" after resuming from suspend ** Summary changed: - Black screen with message "GPU has fallen off the bus" after resuming from suspend + [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend ** Tags added: nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1856370 Title: [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: Every time I suspend my laptop, after I resume it, a black screen shows with the error message - GPU has fallen off the bus It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590 with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5 Description: Ubuntu 19.10 Release: 19.10 nvidia driver 435 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 16:31:58 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905] Subsystem: Dell Device [1028:0905] InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856370/+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 1857040] Re: zfs: upstream support for hardware-accelerated encryption
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1857040 Title: zfs: upstream support for hardware-accelerated encryption Status in linux package in Ubuntu: Confirmed Bug description: I understand that in Linux 5.0+, certain encryption-related symbols have been marked GPL-only, making them unavailable for use by zfs. As a result, using encryption in zfs pools increases cpu load / decreases disk throughput. There are a pair of upstream pull requests that should improve the performance (with performance measurement done on x86-64). Can these be pulled into the Ubuntu kernel? https://github.com/zfsonlinux/zfs/pull/9515 https://github.com/zfsonlinux/zfs/pull/9296 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040/+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 1857257] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1857257 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: disco -- 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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Incomplete Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] [NEW] linux-image-5.0.0-35-generic breaks checkpointing of container
Public bug reported: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux- image-5.0.0-32-generic still works and linux-image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. ** 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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: New Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
I've been having the same problem, the workaround I have is to use older firmware. download: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/snapshot/linux-firmware- e58cbf78678fd872d0cf7ab858ba0030cd8695b0.tar.gz and install the ./iwlwifi-9260-th-b0-jf-b0-34.ucode blob to /lib/firmware I have also added an /etc/modprobe.d/wifi.conf with the following: options iwlmvm power_scheme=1 options iwlwifi swcrypto=0 bt_coex_active=0 power_save=0 11n_disable=1 However I know that none of them except the 11n_disable option actually fixed the problem -- disabling the 11n setting MIGHT be a workaround as well, however I haven't tested with the broken firmware to know. [the reason is because other bug reports have confirmed the older firmware alone fixes the issue]. -- 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/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 Kernel 5.3.0-18-generic Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card. Expected: Wifi connects, uploads/downloads as normal Symptom: Wifi connects, as soon as an upload/download (any heavy traffic) start, the system comes to a crawl, becomes barely usable, and I end up opening a prompt to reboot. The system is unusable. This happens even with the Live USB version. The only solution I found was to download a different (newer) firmware. Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz I then manually copy the contained firmware to /lib/firmware, remove all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode that the kernel expects to load. This completely resolves the issue. This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh installs): Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending SCAN_CFG_CMD: time out after 2000ms. Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue read_ptr 64 write_ptr 65 Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting before reading Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, count: 609870115 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 46.6bf1df06.0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | ADVANCED_SYSASSERT Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | trm_hw_status0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | trm_hw_status1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | interruptlink1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | interruptlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode revision type Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode version major Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode version minor Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration Oct 20 01:51:16 weywot kernel
[Kernel-packages] [Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
I've been having the same problem, the workaround I have is to use older firmware. download: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/snapshot/linux-firmware- e58cbf78678fd872d0cf7ab858ba0030cd8695b0.tar.gz and install the ./iwlwifi-9260-th-b0-jf-b0-34.ucode blob to /lib/firmware I have also added an /etc/modprobe.d/wifi.conf with the following: options iwlmvm power_scheme=1 options iwlwifi swcrypto=0 bt_coex_active=0 power_save=0 11n_disable=1 However I know that none of them except the 11n_disable option actually fixed the problem -- disabling the 11n setting MIGHT be a workaround as well, however I haven't tested with the broken firmware to know. [the reason is because other bug reports have confirmed the older firmware alone fixes the issue]. -- 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/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 Kernel 5.3.0-18-generic Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card. Expected: Wifi connects, uploads/downloads as normal Symptom: Wifi connects, as soon as an upload/download (any heavy traffic) start, the system comes to a crawl, becomes barely usable, and I end up opening a prompt to reboot. The system is unusable. This happens even with the Live USB version. The only solution I found was to download a different (newer) firmware. Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz I then manually copy the contained firmware to /lib/firmware, remove all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode that the kernel expects to load. This completely resolves the issue. This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh installs): Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending SCAN_CFG_CMD: time out after 2000ms. Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue read_ptr 64 write_ptr 65 Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting before reading Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, count: 609870115 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 46.6bf1df06.0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | ADVANCED_SYSASSERT Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | trm_hw_status0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | trm_hw_status1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | interruptlink1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | interruptlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode revision type Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode version major Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode version minor Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration Oct 20 01:51:16 weywot kernel
[Kernel-packages] [Bug 1835677] Re: Megal33t bug: touchpad with mousewheel is broken >:]
*** This bug is a duplicate of bug 1839716 *** https://bugs.launchpad.net/bugs/1839716 ** This bug is no longer a duplicate of bug 1838154 Something hinders XFCE performance. >:] ** This bug has been marked a duplicate of bug 1839716 There is infinite loop in address bar /\&/ -- 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/1835677 Title: Megal33t bug: touchpad with mousewheel is broken >:] Status in linux package in Ubuntu: Invalid Bug description: If you don't use mousewheel or touchpad (since reboot) everything will be fast and responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+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 1857235] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1857235 Title: touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: my touchpad is not working in ubuntu 18.04; however it works fine when I run the diagnostics from the boot menu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pratik 1509 F pulseaudio /dev/snd/controlC1: pratik 1509 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 22 20:44:41 2019 HibernationDevice: RESUME=UUID=cc034e3f-9499-474e-a0d8-089de59d3153 InstallationDate: Installed on 2016-12-11 (1106 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=706edc44-7e3d-4c83-82c4-d7ad2140392a ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-31 (570 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0G1TDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857235/+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 1857235] [NEW] touchpad not working
Public bug reported: my touchpad is not working in ubuntu 18.04; however it works fine when I run the diagnostics from the boot menu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pratik 1509 F pulseaudio /dev/snd/controlC1: pratik 1509 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 22 20:44:41 2019 HibernationDevice: RESUME=UUID=cc034e3f-9499-474e-a0d8-089de59d3153 InstallationDate: Installed on 2016-12-11 (1106 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=706edc44-7e3d-4c83-82c4-d7ad2140392a ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-31 (570 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0G1TDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1857235 Title: touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: my touchpad is not working in ubuntu 18.04; however it works fine when I run the diagnostics from the boot menu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pratik 1509 F pulseaudio /dev/snd/controlC1: pratik 1509 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 22 20:44:41 2019 HibernationDevice: RESUME=UUID=cc034e3f-9499-474e-a0d8-089de59d3153 InstallationDate: Installed on 2016-12-11 (1106 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=706edc44-7e3d-4c83-82c4-d7ad2140392a ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-31 (570 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0G1TDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857235/+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 1788623] Re: regression: IPv6 PMTU discovery fails with source-specific routing
This bug was fixed by upstream in v5.2 (commit 510e2ceda031eed97a7a0f9aad65d271a58b460d). It's also fixed in v5.0.19, i.e. the fix is available in Disco-updates/security since version 5.0.0-26.27 of the linux package, and in Eoan and Focal. -- 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/1788623 Title: regression: IPv6 PMTU discovery fails with source-specific routing Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: IPv6 PMTU discovery fails when using source-specific routing on Ubuntu 18.04. I have attached a test case called pmtu-sads.sh which is based on tools/testing/selftests/net/pmtu.sh in the linux source. I have verified that the test fails on: Ubuntu 18.04 with 4.15.0-30.32 Ubuntu 18.04 with 4.17.0-041700.201806041953 Ubuntu 18.04 with 4.18.3-041803.201808180530 The test succeeds on Ubuntu 16.04 with 4.4.0.131.137 which makes it a regression. System information: Ubuntu 4.15.0-30.32-generic 4.15.18 Description: Ubuntu 18.04.1 LTS Release: 18.04 See below for a patch which is working for me. I'm currently using linux kernel 4.15.0-32.35 built from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git with this patch. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-30-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=041f6e1e-4904-4760-8518-3a88dc288556 ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788623/+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 1857227] Re: PulseAudio sound disappears on hdmi via stereo output
When watching a video on YouTube and on VLC, if a stereo output is selected in pavucontrol, when switching to monaural sound goes without stuttering and problems -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1857227 Title: PulseAudio sound disappears on hdmi via stereo output Status in linux-raspi2 package in Ubuntu: Incomplete Bug description: Оn my Raspberry Pi 4 4GB version the sound constantly disappears when I connect the computer to my Samsung plasma TV using the hdmi output. This works great with an analog 3.5 jack and hdmi-vga adapter, but I can’t set up stable sound with a "clean" hdmi connection. I tried with different hdmi cables that work great with a desktop PC and other equipment and it seems like a software problem. Used operating system Ubuntu server 19.10.1 aarch64. I try removed pulseaudio and the sound works fine through alsa on hdmi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1857227/+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 1857227] Re: PulseAudio sound disappears on hdmi via stereo output
I enabled the audo in the config.txt: # Enable audio (loads snd_bcm2835) dtparam=audio=on disable_audio_dither=on Installed the pulseaudio based on the 19.10.1 aarch64, Then run paplay test.wav (about 30 seconds), no problem found. How did you test the audio? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1857227 Title: PulseAudio sound disappears on hdmi via stereo output Status in linux-raspi2 package in Ubuntu: Incomplete Bug description: Оn my Raspberry Pi 4 4GB version the sound constantly disappears when I connect the computer to my Samsung plasma TV using the hdmi output. This works great with an analog 3.5 jack and hdmi-vga adapter, but I can’t set up stable sound with a "clean" hdmi connection. I tried with different hdmi cables that work great with a desktop PC and other equipment and it seems like a software problem. Used operating system Ubuntu server 19.10.1 aarch64. I try removed pulseaudio and the sound works fine through alsa on hdmi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1857227/+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 1788623] Re: regression: IPv6 PMTU discovery fails with source-specific routing
** Patch removed: "net/ipv6/route: Fix PMTU for source-specific routes" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788623/+attachment/5179773/+files/0001-net-ipv6-route-Fix-PMTU-for-source-specific-routes.patch -- 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/1788623 Title: regression: IPv6 PMTU discovery fails with source-specific routing Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: IPv6 PMTU discovery fails when using source-specific routing on Ubuntu 18.04. I have attached a test case called pmtu-sads.sh which is based on tools/testing/selftests/net/pmtu.sh in the linux source. I have verified that the test fails on: Ubuntu 18.04 with 4.15.0-30.32 Ubuntu 18.04 with 4.17.0-041700.201806041953 Ubuntu 18.04 with 4.18.3-041803.201808180530 The test succeeds on Ubuntu 16.04 with 4.4.0.131.137 which makes it a regression. System information: Ubuntu 4.15.0-30.32-generic 4.15.18 Description: Ubuntu 18.04.1 LTS Release: 18.04 See below for a patch which is working for me. I'm currently using linux kernel 4.15.0-32.35 built from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git with this patch. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-30-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=041f6e1e-4904-4760-8518-3a88dc288556 ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788623/+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 1856161] Re: Thunderbolt dock fails to connect USB devices
Sorry, the joy was (relatively) short-lived: Even with `/etc/default/grub` `GRUB_CMDLINE_LINUX_DEFAULT` setting set to empty, I can still reproduce this problem with the lp1766076 kernel: it definitely happens less - maybe 1 in 3 times instead of almost always - but it still happens. Here's a boot dmesg log of a failing boot with no (additional) kernel command line flags - xhci_hcd assumes the controller died on timestamp 27, after which none of the USB things on the dock work. ** Attachment added: "lp1766076-boot-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5314569/+files/lp1766076-boot-dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Gui
[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
When the new patch/update will come up for this? -- 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/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HE
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
with the lp1766076 kernel, removing all the parameters after "quiet" (I'm thinking the ones before that are required for successful boot), the thunderbolt connects successfully on boot. Attached dmesg log. ** Attachment added: "lp1766076-boot-dmesg-tbconnected.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5314567/+files/lp1766076-boot-dmesg-tbconnected.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|reg
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
Also connect/disconnect succeeds. See attached logs. There are other problems now, which the kernel flags were supposed to solve. I'd need to reboot a few times to figure out which flag causes the problem. ** Attachment added: "lp1766076-tb-reconnect-success.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5314568/+files/lp1766076-tb-reconnect-success.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registe
[Kernel-packages] [Bug 1857227] [NEW] PulseAudio sound disappears on hdmi via stereo output
Public bug reported: Оn my Raspberry Pi 4 4GB version the sound constantly disappears when I connect the computer to my Samsung plasma TV using the hdmi output. This works great with an analog 3.5 jack and hdmi-vga adapter, but I can’t set up stable sound with a "clean" hdmi connection. I tried with different hdmi cables that work great with a desktop PC and other equipment and it seems like a software problem. Used operating system Ubuntu server 19.10.1 aarch64. I try removed pulseaudio and the sound works fine through alsa on hdmi ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Assignee: Rocinante (olevenets2) Status: Incomplete ** Tags: eoan ** Changed in: linux-raspi2 (Ubuntu) Assignee: (unassigned) => Rocinante (olevenets2) ** Changed in: linux-raspi2 (Ubuntu) Status: New => Incomplete ** Tags added: eoan ** Description changed: Оn my Raspberry Pi 4 4GB version the sound constantly disappears when I - connect the computer to my Samsung plasma TV using the hdmi output :? - This works great with an analog 3.5 jack and hdmi-vga adapter, but I - can’t set up stable sound with a "clean" hdmi connection. I tried with + connect the computer to my Samsung plasma TV using the hdmi output. This + works great with an analog 3.5 jack and hdmi-vga adapter, but I can’t + set up stable sound with a "clean" hdmi connection. I tried with different hdmi cables that work great with a desktop PC and other equipment and it seems like a software problem. Used operating system - Ubuntu server 19.10.1 aarch64. I removed pulseaudio and the sound works - fine through alsa on hdmi + Ubuntu server 19.10.1 aarch64. I try removed pulseaudio and the sound + works fine through alsa on hdmi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1857227 Title: PulseAudio sound disappears on hdmi via stereo output Status in linux-raspi2 package in Ubuntu: Incomplete Bug description: Оn my Raspberry Pi 4 4GB version the sound constantly disappears when I connect the computer to my Samsung plasma TV using the hdmi output. This works great with an analog 3.5 jack and hdmi-vga adapter, but I can’t set up stable sound with a "clean" hdmi connection. I tried with different hdmi cables that work great with a desktop PC and other equipment and it seems like a software problem. Used operating system Ubuntu server 19.10.1 aarch64. I try removed pulseaudio and the sound works fine through alsa on hdmi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1857227/+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 1856161] Re: Thunderbolt dock fails to connect USB devices
Please remove all the kernel parameters. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId: d83854e8c81f5d47b0b99c8a3b42ae5127c75eb8 ParentDeviceId: 84edf044a6b53037732
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
What I currently do, is to detach the USB cable from the dock, connect the thunderbolt cable to the computer, wait for everything to settle (either by looking at the dmesg log or just waiting for the dock audio device to be registered - which shows on the OSD), then connecting the USB cable. See attached dmesg log of this process. All of my devices are on the cable connected to the back of the dock - anything else listed in the log before timestamp 342 is internal to the dock (i.e. the built-in hub, audio device and NIC). ** Attachment added: "lp1766076-tb-reconnect-without-usb-chain.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5314557/+files/lp1766076-tb-reconnect-without-usb-chain.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
Additionaly, with the lp1766076 kernel, after disconnecting the thunderbolt cable, reconnecting it again fails - attached a short dmesg log of just that. ** Attachment added: "lp1766076-tb-reconnect-fail-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5314556/+files/lp1766076-tb-reconnect-fail-dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Ver
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
The current situation is that I can't use the thunderbolt dock's USB hub normally: it almost always fails to connect - with the generic Ubuntu kernel or with the "5.3.0-25-generic #27~lp1766076" kernel suggested in the comment above. Trying to boot with the lp1766076 kernel (which I'm currently running after the first boot), boot with the thunderbolt connected, xhci fails. I Attached dmesg log of that. ** Attachment added: "lp1766076-boot-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5314555/+files/lp1766076-boot-dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid:
[Kernel-packages] [Bug 1856077] Re: Fix latency issue on Realtek Bluetooth
Can you please share the bug number? -- 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/1856077 Title: Fix latency issue on Realtek Bluetooth Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Bug description: [Impact] When multiple Bluetooth devices are connected to Realtek Bluetooth controller, the BT latency becomes really high, e.g. audio stutters, mouse lags. [Fix] The new Realtek Bluetooth firmware can fix the issue. [Test] Cold boot the system to reload the new firmware, and the issue is gone. [Regression Potential] Low. The firmware is already in Eoan. We also tested it on Bionic and haven't found any regression so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1856077/+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 1851446] Re: Backport MPLS patches from 5.3 to 4.15
Hi Jeff. Unfortunately, was missing patch [1] that add the expose the support in the mlx5 driver. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.5-rc2&id=5dc9520bf04a6b95660a307d7654460d1463d91a could you please add it ? Yours, Talat -- 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/1851446 Title: Backport MPLS patches from 5.3 to 4.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Disco: New Bug description: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851446/+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