[Kernel-packages] [Bug 1857418] [NEW] KDE Panel disappears after screen lock
Public bug reported: Hello! I use ubuntu 18.04. Kernel Ubuntu 4.15.0-73.82+lp1854798+2-generic 4.15.18 (problem exists on previous kernels too) KDE from the repo Screen is extended to external monitor laptop Lenovo Carbon 6x Monitor attached with HDMI Monitor model: Acer H236HL When the screen is locked by timeout, after unlocking by entering password, KDE panel disappears on external monitor. I can not add a panel to it, e.g. I add it to screen but the panel does not appear. After reboot panel is in place. If I have added panels to screen they are also exist. It is interesting that this problem exists with only my monitor. Other monitors attached to my laptop work OK. The problem also does not exist if I turn my monitor off before screen lock. ** 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/1857418 Title: KDE Panel disappears after screen lock Status in linux package in Ubuntu: New Bug description: Hello! I use ubuntu 18.04. Kernel Ubuntu 4.15.0-73.82+lp1854798+2-generic 4.15.18 (problem exists on previous kernels too) KDE from the repo Screen is extended to external monitor laptop Lenovo Carbon 6x Monitor attached with HDMI Monitor model: Acer H236HL When the screen is locked by timeout, after unlocking by entering password, KDE panel disappears on external monitor. I can not add a panel to it, e.g. I add it to screen but the panel does not appear. After reboot panel is in place. If I have added panels to screen they are also exist. It is interesting that this problem exists with only my monitor. Other monitors attached to my laptop work OK. The problem also does not exist if I turn my monitor off before screen lock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857418/+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 1857413] 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 1857413 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 -- 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/1857413 Title: mce: ras: When inject 1bit ecc error, there is no mce log recorded in the dmesg Status in linux package in Ubuntu: Incomplete Bug description: Using Linux kernel, When inject 1bit ecc error, there are some mce log recorded in the dmesg.like: [ 1561.511210] mce: [Hardware Error]: Machine check events logged [ 1561.511221] [Hardware Error]: Corrected error, no action required. [ 1561.511311] [Hardware Error]: CPU:0 (18:0:2) MC16_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-|CECC]: 0xdc20411b [ 1561.511388] [Hardware Error]: Error Addr: 0x00077cd66940 [ 1561.511439] [Hardware Error]: IPID: 0x009600150f00, Syndrome: 0x10ce0a400d01 [ 1561.511499] [Hardware Error]: Unified Memory Controller Extended Error Code: 0 [ 1561.511556] [Hardware Error]: Unified Memory Controller Error: DRAM ECC error. [ 1561.511646] EDAC MC0: 1 CE on mc#0csrow#1channel#1 (csrow:1 channel:1 page:0x7fcd66 offset:0x940 grain:0 syndrome:0x10ce) [ 1561.511648] [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD *But, there are no the log when Using "Ubuntu 18.04.3 LTS"* The upstream related commit is de0e0624d86ff9fc512dedb297f8978698abf21a . After merged this commit, Ubuntu kernel's dmesg can record the mce log as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857413/+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 1857413] Re: mce: ras: When inject 1bit ecc error, there is no mce log recorded in the dmesg
** Description changed: Using Linux kernel, When inject 1bit ecc error, there are some mce log recorded in the dmesg.like: [ 1561.511210] mce: [Hardware Error]: Machine check events logged [ 1561.511221] [Hardware Error]: Corrected error, no action required. [ 1561.511311] [Hardware Error]: CPU:0 (18:0:2) MC16_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-|CECC]: 0xdc20411b [ 1561.511388] [Hardware Error]: Error Addr: 0x00077cd66940 [ 1561.511439] [Hardware Error]: IPID: 0x009600150f00, Syndrome: 0x10ce0a400d01 [ 1561.511499] [Hardware Error]: Unified Memory Controller Extended Error Code: 0 [ 1561.511556] [Hardware Error]: Unified Memory Controller Error: DRAM ECC error. [ 1561.511646] EDAC MC0: 1 CE on mc#0csrow#1channel#1 (csrow:1 channel:1 page:0x7fcd66 offset:0x940 grain:0 syndrome:0x10ce) [ 1561.511648] [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD *But, there are no the log when Using "Ubuntu 18.04.3 LTS"* The upstream related commit is de0e0624d86ff9fc512dedb297f8978698abf21a . - After merged this commit, dmesg can record the mce log. + After merged this commit, Ubuntu kernel's dmesg can record the mce log + as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857413 Title: mce: ras: When inject 1bit ecc error, there is no mce log recorded in the dmesg Status in linux package in Ubuntu: New Bug description: Using Linux kernel, When inject 1bit ecc error, there are some mce log recorded in the dmesg.like: [ 1561.511210] mce: [Hardware Error]: Machine check events logged [ 1561.511221] [Hardware Error]: Corrected error, no action required. [ 1561.511311] [Hardware Error]: CPU:0 (18:0:2) MC16_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-|CECC]: 0xdc20411b [ 1561.511388] [Hardware Error]: Error Addr: 0x00077cd66940 [ 1561.511439] [Hardware Error]: IPID: 0x009600150f00, Syndrome: 0x10ce0a400d01 [ 1561.511499] [Hardware Error]: Unified Memory Controller Extended Error Code: 0 [ 1561.511556] [Hardware Error]: Unified Memory Controller Error: DRAM ECC error. [ 1561.511646] EDAC MC0: 1 CE on mc#0csrow#1channel#1 (csrow:1 channel:1 page:0x7fcd66 offset:0x940 grain:0 syndrome:0x10ce) [ 1561.511648] [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD *But, there are no the log when Using "Ubuntu 18.04.3 LTS"* The upstream related commit is de0e0624d86ff9fc512dedb297f8978698abf21a . After merged this commit, Ubuntu kernel's dmesg can record the mce log as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857413/+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 1857409] Re: alsa/sof: load different firmware on different platforms
** Description changed: - Need SOF f/w support for CML-H in Selek G3/MLK and G5 + [Impact] + In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware) + on all platforms, but mainline kernel already supported the multi + firmwares on differnt platforms, and OEM project needs us to + support the mutli-firmware names in the ubuntu kernel + + [Fix] + cherry-pick 3 upstream patches, then on cnl platforms, it will + load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl + platforms, it will load sof-cfl.ri + + + [Test Case] + Prepare the firmware from https://github.com/thesofproject/linux-firmware + master branch, then boot the kernel with these patches. + + [Regression Risk] + Low, just let different platforms load differnt firmware, and these + patches are in the upstream kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857409 Title: alsa/sof: load different firmware on different platforms Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware) on all platforms, but mainline kernel already supported the multi firmwares on differnt platforms, and OEM project needs us to support the mutli-firmware names in the ubuntu kernel [Fix] cherry-pick 3 upstream patches, then on cnl platforms, it will load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl platforms, it will load sof-cfl.ri [Test Case] Prepare the firmware from https://github.com/thesofproject/linux-firmware master branch, then boot the kernel with these patches. [Regression Risk] Low, just let different platforms load differnt firmware, and these patches are in the upstream kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857409/+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 1857413] [NEW] mce: ras: When inject 1bit ecc error, there is no mce log recorded in the dmesg
Public bug reported: Using Linux kernel, When inject 1bit ecc error, there are some mce log recorded in the dmesg.like: [ 1561.511210] mce: [Hardware Error]: Machine check events logged [ 1561.511221] [Hardware Error]: Corrected error, no action required. [ 1561.511311] [Hardware Error]: CPU:0 (18:0:2) MC16_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-|CECC]: 0xdc20411b [ 1561.511388] [Hardware Error]: Error Addr: 0x00077cd66940 [ 1561.511439] [Hardware Error]: IPID: 0x009600150f00, Syndrome: 0x10ce0a400d01 [ 1561.511499] [Hardware Error]: Unified Memory Controller Extended Error Code: 0 [ 1561.511556] [Hardware Error]: Unified Memory Controller Error: DRAM ECC error. [ 1561.511646] EDAC MC0: 1 CE on mc#0csrow#1channel#1 (csrow:1 channel:1 page:0x7fcd66 offset:0x940 grain:0 syndrome:0x10ce) [ 1561.511648] [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD *But, there are no the log when Using "Ubuntu 18.04.3 LTS"* The upstream related commit is de0e0624d86ff9fc512dedb297f8978698abf21a . After merged this commit, dmesg can record the mce log. ** 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/1857413 Title: mce: ras: When inject 1bit ecc error, there is no mce log recorded in the dmesg Status in linux package in Ubuntu: New Bug description: Using Linux kernel, When inject 1bit ecc error, there are some mce log recorded in the dmesg.like: [ 1561.511210] mce: [Hardware Error]: Machine check events logged [ 1561.511221] [Hardware Error]: Corrected error, no action required. [ 1561.511311] [Hardware Error]: CPU:0 (18:0:2) MC16_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-|CECC]: 0xdc20411b [ 1561.511388] [Hardware Error]: Error Addr: 0x00077cd66940 [ 1561.511439] [Hardware Error]: IPID: 0x009600150f00, Syndrome: 0x10ce0a400d01 [ 1561.511499] [Hardware Error]: Unified Memory Controller Extended Error Code: 0 [ 1561.511556] [Hardware Error]: Unified Memory Controller Error: DRAM ECC error. [ 1561.511646] EDAC MC0: 1 CE on mc#0csrow#1channel#1 (csrow:1 channel:1 page:0x7fcd66 offset:0x940 grain:0 syndrome:0x10ce) [ 1561.511648] [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD *But, there are no the log when Using "Ubuntu 18.04.3 LTS"* The upstream related commit is de0e0624d86ff9fc512dedb297f8978698abf21a . After merged this commit, dmesg can record the mce log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857413/+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] Re: Wireless wouldn't turn on.
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1857409] 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 1857409 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 -- 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/1857409 Title: alsa/sof: load different firmware on different platforms Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Need SOF f/w support for CML-H in Selek G3/MLK and G5 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857409/+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 1857178] Re: GPU hang
Please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ -- 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/1857178 Title: GPU hang Status in linux package in Ubuntu: Confirmed Bug description: System randomly hangs for 5-15 seconds. It has been occurring for about a week. Please let me know if there is any further information that can be of use. Thank you in advance for your help. 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: sebjr 1357 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 20 17:40:03 2019 InstallationDate: Installed on 2019-12-05 (15 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q0002EUS ProcEnviron: TERM=xterm-256color 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=dc41f3d8-af4c-4d77-965f-c77f918ac63e 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET73W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q0002EUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0002EUS:pvrThinkPadX390:rvnLENOVO:rn20Q0002EUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X390 dmi.product.name: 20Q0002EUS dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857178/+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
Re: [Kernel-packages] [Bug 1857307] Re: Wireless wouldn't turn on.
Hello, Thank you for getting back to me. I am reporting on 19.10, PCI wireless. 1. Here the rfkill output: $ sudo rfkill unblock all $ sudo rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes 2. There is no any special switch but F8 key which I suppose works when pressed F8+Fn but i doesn't get wireless on still. If F8 pressed alone -- no difference either. 3. I checked the BIOS-> Security: Wireless LAN [Enabled] On 12/23/19 9:01 PM, Po-Hsu Lin wrote: > Hello, > let's focus on 19.10, you're reporting an issue for the PCI wireless card > (Wireless-AC 9260) in your system or the USB D-Link card? > > Can you try the following steps to see if it helps: >1. run command "rfkill unblock all" >2. or to flip the wifi switch (if any) >3. check you BIOS setting to ensure this device is enabled > > ** 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/1857307 Title: Wireless wouldn't turn on. Status in linux package in Ubuntu: Incomplete 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 1857409] [NEW] alsa/sof: load different firmware on different platforms
Public bug reported: Need SOF f/w support for CML-H in Selek G3/MLK and G5 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1856130 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: originate-from-1856130 somerville -- 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/1857409 Title: alsa/sof: load different firmware on different platforms Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: Need SOF f/w support for CML-H in Selek G3/MLK and G5 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857409/+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 1854401] Re: headphone has noise as not mute on dell machines with alc236/256
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- 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/1854401 Title: headphone has noise as not mute on dell machines with alc236/256 Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] There is noise in the headphone on some dell machines with the codec alc256 or alc236 [Fix] Realtek provide a patch to disable PCBEEP_IN to heapdhone. [Test Case] tested the kernel with this patch, the noise disappeared. [Regression Risk] Low, Realtek provided the patch, and it is limited to apply to alc236 and 256, and just disable the PCBEEP_IN to headphone.. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1854401/+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] Re: Wireless wouldn't turn on.
Hello, let's focus on 19.10, you're reporting an issue for the PCI wireless card (Wireless-AC 9260) in your system or the USB D-Link card? Can you try the following steps to see if it helps: 1. run command "rfkill unblock all" 2. or to flip the wifi switch (if any) 3. check you BIOS setting to ensure this device is enabled ** 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/1857307 Title: Wireless wouldn't turn on. Status in linux package in Ubuntu: Incomplete 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 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
Can you please attach dmesg with kernel parameter `usbcore.dyndbg=+p`? -- 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/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Triaged Status in linux source package in Disco: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. Kernel emits messages like: usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+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 1741381] Re: [Feature] Crystal Ridge - dynamic filesystem DAX based on HMAT info
[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/1741381 Title: [Feature] Crystal Ridge - dynamic filesystem DAX based on HMAT info Status in intel: Invalid Status in linux package in Ubuntu: Expired Bug description: Description: Have the kernel automatically choose whether or not to use filesystem DAX based on information in the HMAT. This depends on the outcome of the "mount option and inode flag" discussion in the community. Target Release: 19.10 Target Kernel:TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1741381/+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 1849273] Re: network connection fails to re-establish on resume from suspend
[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/1849273 Title: network connection fails to re-establish on resume from suspend Status in linux package in Ubuntu: Expired Bug description: The network connection doesn't reestablish on resume from suspend and the laptop has to be restarted. Restarting networking or network-manager doesn't make it reconnect either. However, unloading iwlwifi and reloading it, then restarting the network stack makes it work again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 09:28:30 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-03 (2239 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2018-01-26 (633 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connecting started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849273/+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 1849540] Re: "PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)" causing boot delays
[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/1849540 Title: "PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)" causing boot delays Status in linux package in Ubuntu: Expired Bug description: ubuntu shows pci bus error severity=corrected when shutting down takes time for login page to pop up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-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 23 13:32:16 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5921] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13d1] InstallationDate: Installed on 2019-10-09 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b721 Realtek Semiconductor Corp. Bus 001 Device 003: ID 13d3:5a11 IMC Networks Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook 14_ASUS Laptop X441UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=18fd12ef-f3d1-4d80-b60a-a8111a2dd43d ro quiet splash i915.alpha_support=1 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441UAR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX441UAR.308:bd06/11/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook14_ASUSLaptopX441UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook 14_ASUS Laptop X441UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git1910190630.fc9336~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1910200730.7ceafa~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1910200730.7ceafa~oibaf~b 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/1849540/+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 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1857398 Title: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install Status in ubiquity package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: zfs supports built-in encryption support, but the decision of whether a pool is encrypted or not must be made at pool creation time; it is possible to add encrypted datasets on top of an unencrypted pool but it is not possible to do an online change of a dataset (or a whole pool) to toggle encryption. We should therefore always install with encryption enabled on zfs systems, with a non-secret key by default, and allow the user to use 'zfs change-key -o keylocation=prompt' after install to take ownership of the encryption and upgrade the security. This is also the simplest way to allow users to avoid having to choose between the security of full-disk encryption, and the advanced filesystem features of zfs since it requires no additional UX work in ubiquity. We should make sure that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed first in the kernel so that enabling zfs encryption does not impose an unreasonable performance penalty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+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] Re: touchpad not working
Hello, this might be a duplicate of bug 1854798, can you try to boot with an older kernel to see if this issue still exist? Thanks ** 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/1857235 Title: touchpad not working Status in linux package in Ubuntu: Incomplete 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 1857181] Re: Kernel driver updates caused BlueTooth to not start
Marked as incomplete as per request in comment #4, please feel free to change it back after replying on that request. ** 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/1857181 Title: Kernel driver updates caused BlueTooth to not start Status in linux package in Ubuntu: Incomplete 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 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install
This is an interesting approach. I figured the installer should prompt for encryption, and it probably still should, but if the performance impact is minimal, this does have the nice property of allowing for enabling encryption post-install. It might be worthwhile (after merging the SIMD fixes) to benchmark aes256-ccm (the default) vs encryption=aes-256-gcm. I think GCM seems to be preferred, security wise, in various places (though I don't immediately have references) and may be faster. There's also an upstream PR in progress that significantly improves AES-GCM: https://github.com/zfsonlinux/zfs/pull/9749 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1857398 Title: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install Status in ubiquity package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: zfs supports built-in encryption support, but the decision of whether a pool is encrypted or not must be made at pool creation time; it is possible to add encrypted datasets on top of an unencrypted pool but it is not possible to do an online change of a dataset (or a whole pool) to toggle encryption. We should therefore always install with encryption enabled on zfs systems, with a non-secret key by default, and allow the user to use 'zfs change-key -o keylocation=prompt' after install to take ownership of the encryption and upgrade the security. This is also the simplest way to allow users to avoid having to choose between the security of full-disk encryption, and the advanced filesystem features of zfs since it requires no additional UX work in ubiquity. We should make sure that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed first in the kernel so that enabling zfs encryption does not impose an unreasonable performance penalty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+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 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install
** Merge proposal linked: https://code.launchpad.net/~vorlon/ubiquity/+git/ubiquity/+merge/377100 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1857398 Title: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install Status in ubiquity package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: zfs supports built-in encryption support, but the decision of whether a pool is encrypted or not must be made at pool creation time; it is possible to add encrypted datasets on top of an unencrypted pool but it is not possible to do an online change of a dataset (or a whole pool) to toggle encryption. We should therefore always install with encryption enabled on zfs systems, with a non-secret key by default, and allow the user to use 'zfs change-key -o keylocation=prompt' after install to take ownership of the encryption and upgrade the security. This is also the simplest way to allow users to avoid having to choose between the security of full-disk encryption, and the advanced filesystem features of zfs since it requires no additional UX work in ubiquity. We should make sure that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed first in the kernel so that enabling zfs encryption does not impose an unreasonable performance penalty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+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 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install
ubiquity side of the equation: https://code.launchpad.net/~vorlon/ubiquity/+git/ubiquity/+ref/lp.1857398 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1857398 Title: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install Status in ubiquity package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: zfs supports built-in encryption support, but the decision of whether a pool is encrypted or not must be made at pool creation time; it is possible to add encrypted datasets on top of an unencrypted pool but it is not possible to do an online change of a dataset (or a whole pool) to toggle encryption. We should therefore always install with encryption enabled on zfs systems, with a non-secret key by default, and allow the user to use 'zfs change-key -o keylocation=prompt' after install to take ownership of the encryption and upgrade the security. This is also the simplest way to allow users to avoid having to choose between the security of full-disk encryption, and the advanced filesystem features of zfs since it requires no additional UX work in ubiquity. We should make sure that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed first in the kernel so that enabling zfs encryption does not impose an unreasonable performance penalty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+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 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install
Here is a proof-of-concept patch for the zfs-initramfs side of such a feature. ** Patch added: "zfs-linux-1857398.debdiff" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1857398/+attachment/5314923/+files/zfs-linux-1857398.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1857398 Title: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install Status in ubiquity package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: zfs supports built-in encryption support, but the decision of whether a pool is encrypted or not must be made at pool creation time; it is possible to add encrypted datasets on top of an unencrypted pool but it is not possible to do an online change of a dataset (or a whole pool) to toggle encryption. We should therefore always install with encryption enabled on zfs systems, with a non-secret key by default, and allow the user to use 'zfs change-key -o keylocation=prompt' after install to take ownership of the encryption and upgrade the security. This is also the simplest way to allow users to avoid having to choose between the security of full-disk encryption, and the advanced filesystem features of zfs since it requires no additional UX work in ubiquity. We should make sure that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed first in the kernel so that enabling zfs encryption does not impose an unreasonable performance penalty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+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 1857398] [NEW] ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install
Public bug reported: zfs supports built-in encryption support, but the decision of whether a pool is encrypted or not must be made at pool creation time; it is possible to add encrypted datasets on top of an unencrypted pool but it is not possible to do an online change of a dataset (or a whole pool) to toggle encryption. We should therefore always install with encryption enabled on zfs systems, with a non-secret key by default, and allow the user to use 'zfs change-key -o keylocation=prompt' after install to take ownership of the encryption and upgrade the security. This is also the simplest way to allow users to avoid having to choose between the security of full-disk encryption, and the advanced filesystem features of zfs since it requires no additional UX work in ubiquity. We should make sure that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed first in the kernel so that enabling zfs encryption does not impose an unreasonable performance penalty. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1857398 Title: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install Status in ubiquity package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: zfs supports built-in encryption support, but the decision of whether a pool is encrypted or not must be made at pool creation time; it is possible to add encrypted datasets on top of an unencrypted pool but it is not possible to do an online change of a dataset (or a whole pool) to toggle encryption. We should therefore always install with encryption enabled on zfs systems, with a non-secret key by default, and allow the user to use 'zfs change-key -o keylocation=prompt' after install to take ownership of the encryption and upgrade the security. This is also the simplest way to allow users to avoid having to choose between the security of full-disk encryption, and the advanced filesystem features of zfs since it requires no additional UX work in ubiquity. We should make sure that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed first in the kernel so that enabling zfs encryption does not impose an unreasonable performance penalty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+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 1857394] 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 1857394 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 -- 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/1857394 Title: [Firmware Bug]: reg 0x1c: invalid BAR (can't size) Status in linux package in Ubuntu: Incomplete Bug description: 1) Ubuntu 19.10 2) kernel 5.3.0-23-generic 3) No error. 4) Error in Ubuntu Logs App. Message: 4:47:59 PM kernel: pci :00:14.4: bridge window [mem 0xd000-0xfebf window] (subtractive decode) 4:47:59 PM kernel: pci_bus :04: extended config space not accessible 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfdd0-0xfddf 64bit pref] 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfdd0-0xfddf 64bit pref] 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfde0-0xfdef] 4:47:59 PM kernel: pci :00:0a.0: bridge window [io 0xc000-0xcfff] 4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03] 4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot D3cold 4:47:59 PM kernel: pci :03:00.0: supports D1 D2 4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 64bit pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 64bit pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io 0xce00-0xceff] 4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02 4:47:59 PM kernel: pci :00:06.0: bridge window [mem 0xfa00-0xfbff 64bit pref] 4:47:59 PM kernel: pci :00:06.0: bridge window [mem 0xfdf0-0xfdff] 4:47:59 PM kernel: pci :00:06.0: bridge window [io 0xd000-0xdfff] 4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02] 4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' 4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags 4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 64bit pref] 4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 64bit] 4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000 4:47:59 PM kernel: pci :00:02.0: bridge window [mem 0xd000-0xdfff 64bit pref] 4:47:59 PM kernel: pci :00:02.0: bridge window [mem 0xfda0-0xfdaf] 4:47:59 PM kernel: pci :00:02.0: bridge window [io 0xe000-0xefff] 4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01] 4:47:59 PM kernel: pci :01:00.1: supports D1 D2 4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags 4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 64bit] 4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300 4:47:59 PM kernel: pci :01:00.0: supports D1 D2 4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags 4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 pref] 4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io 0xee00-0xeeff] 4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 64bit] 4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 64bit pref] 4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03 4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06 4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff] 4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310 4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401 4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100 4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold 4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 64bit] 4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io 0x0376] 4:47:59 PM kernel: pci :00:14.1: legacy
[Kernel-packages] [Bug 1857394] [NEW] [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
Public bug reported: 1) Ubuntu 19.10 2) kernel 5.3.0-23-generic 3) No error. 4) Error in Ubuntu Logs App. Message: 4:47:59 PM kernel: pci :00:14.4: bridge window [mem 0xd000-0xfebf window] (subtractive decode) 4:47:59 PM kernel: pci_bus :04: extended config space not accessible 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfdd0-0xfddf 64bit pref] 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfdd0-0xfddf 64bit pref] 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfde0-0xfdef] 4:47:59 PM kernel: pci :00:0a.0: bridge window [io 0xc000-0xcfff] 4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03] 4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot D3cold 4:47:59 PM kernel: pci :03:00.0: supports D1 D2 4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 64bit pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 64bit pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io 0xce00-0xceff] 4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02 4:47:59 PM kernel: pci :00:06.0: bridge window [mem 0xfa00-0xfbff 64bit pref] 4:47:59 PM kernel: pci :00:06.0: bridge window [mem 0xfdf0-0xfdff] 4:47:59 PM kernel: pci :00:06.0: bridge window [io 0xd000-0xdfff] 4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02] 4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' 4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags 4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 64bit pref] 4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 64bit] 4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000 4:47:59 PM kernel: pci :00:02.0: bridge window [mem 0xd000-0xdfff 64bit pref] 4:47:59 PM kernel: pci :00:02.0: bridge window [mem 0xfda0-0xfdaf] 4:47:59 PM kernel: pci :00:02.0: bridge window [io 0xe000-0xefff] 4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01] 4:47:59 PM kernel: pci :01:00.1: supports D1 D2 4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags 4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 64bit] 4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300 4:47:59 PM kernel: pci :01:00.0: supports D1 D2 4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags 4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 pref] 4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io 0xee00-0xeeff] 4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 64bit] 4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 64bit pref] 4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03 4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06 4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff] 4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310 4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401 4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100 4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold 4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 64bit] 4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io 0x0376] 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177] 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io 0x03f6] 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7] 4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io 0xfa00-0xfa0f] 4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io 0x-0x0003] 4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io 0x-0x0007] 4:47:59 PM kernel: pci :00:14.1: reg 0x14: [io 0x-0x0003] 4:47:59 PM kernel: pci :00:14.1: reg 0x10: [io 0x-0x0007] 4:47:59 PM kernel: pci :00:14.1: [1002:439c] type 00 class 0x01018a 4:47:59 PM kernel: pci :00:14.0: [1002:4385] type 00 class 0x0c0500 4:47:59 PM kernel: pci :00:13.2: PME# supported from D0 D1 D2 D3hot 4:47:59 PM kernel: pci :00:13.2: supports D1 D2 4:47:59 PM kernel: pci :00:13.2: reg 0x10: [mem 0xfe029000-0xfe0290ff] 4:47:59 PM kernel: pci :00:13.2: [1002:4396] type 00 class 0x0c0320 4:47:59 PM kernel: pci
[Kernel-packages] [Bug 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station
just for info : I tried also the kernel provided by https://launchpad.net/~kaihengfeng on post 90 ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/90) but nothing changed -- 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/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: Confirmed Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
[Kernel-packages] [Bug 1857385] 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/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: Confirmed Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.3 PCI
[Kernel-packages] [Bug 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station
** Description changed: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. - The bios and firmware of the docking station are updated at the last one + The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] - Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:08.0 Host bridge:
[Kernel-packages] [Bug 1857385] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314920/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD]
[Kernel-packages] [Bug 1857385] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314919/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2
[Kernel-packages] [Bug 1857385] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314918/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2
[Kernel-packages] [Bug 1857385] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314917/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD]
[Kernel-packages] [Bug 1857385] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314913/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe
[Kernel-packages] [Bug 1857385] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314912/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe
[Kernel-packages] [Bug 1857385] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314907/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD]
[Kernel-packages] [Bug 1857385] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314909/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe
[Kernel-packages] [Bug 1857385] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314910/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD]
[Kernel-packages] [Bug 1857385] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314911/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD]
[Kernel-packages] [Bug 1857385] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314914/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD]
[Kernel-packages] [Bug 1857385] [NEW] xHCI host controller not responding, assume dead via USB-C docking station
Public bug reported: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A 00:14.0 SMBus: Advanced Micro
[Kernel-packages] [Bug 1857385] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314915/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices,
[Kernel-packages] [Bug 1857385] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314916/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD]
[Kernel-packages] [Bug 1857385] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1857385/+attachment/5314908/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: New Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc.
[Kernel-packages] [Bug 1575071] 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/1575071 Title: Graphics corruption (framebuffer offset) in i915 on 4.4.0 Status in linux package in Ubuntu: Confirmed Bug description: Appeared after upgrading to 16.04 LTS. Mostly happens with switching channels in a full-screen irssi window by using Alt and the number keys (or the top row of the keyboard). Entire screen flickers between normal view, and a semi-arbitary offset view (with the entire screen offset by about 50-100 pixel, wrapping to the other side). Minor irritation to begin with. Eventually lead to the entire screen blanking save for a solid yellow/green line (about 5-10 px wide) on the left, occasionally (~1s) flicking back to the correct contents. Rebooting into 4.2.0 (left over from before the upgrade) appears to have fixed the issue. Hardware: Toshiba Portege z20t - "VGA compatible controller [0300]: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) (prog-if 00 [VGA controller])" Relevant packages (assuming that they weren't captured): - linux-image-4.4.0-21-generic - linux-image-extra-4.4.0-21-generic - (working version is 4.2.0-35) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tpg2401 F pulseaudio /dev/snd/controlC0: tpg2401 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 17:08:04 2016 HibernationDevice: RESUME=UUID=ab95a533-52f3-4458-96dc-9119684b0ed6 InstallationDate: Installed on 2015-06-19 (312 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: TOSHIBA PORTEGE Z20t-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=b6cc139d-95e4-48f1-a3a8-284dbdb3b6fa ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-25 (1 days ago) dmi.bios.date: 01/06/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z20t-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd01/06/2015:svnTOSHIBA:pnPORTEGEZ20t-B:pvrPT15BA-00500Y:rvnTOSHIBA:rnPORTEGEZ20t-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z20t-B dmi.product.version: PT15BA-00500Y dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575071/+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 1575071] Re: Graphics corruption (framebuffer offset) in i915 on 4.4.0
Hmm this issue still exists on Ubuntu 19.10 for me :-( ** Changed in: linux (Ubuntu) Status: Expired => 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/1575071 Title: Graphics corruption (framebuffer offset) in i915 on 4.4.0 Status in linux package in Ubuntu: Confirmed Bug description: Appeared after upgrading to 16.04 LTS. Mostly happens with switching channels in a full-screen irssi window by using Alt and the number keys (or the top row of the keyboard). Entire screen flickers between normal view, and a semi-arbitary offset view (with the entire screen offset by about 50-100 pixel, wrapping to the other side). Minor irritation to begin with. Eventually lead to the entire screen blanking save for a solid yellow/green line (about 5-10 px wide) on the left, occasionally (~1s) flicking back to the correct contents. Rebooting into 4.2.0 (left over from before the upgrade) appears to have fixed the issue. Hardware: Toshiba Portege z20t - "VGA compatible controller [0300]: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) (prog-if 00 [VGA controller])" Relevant packages (assuming that they weren't captured): - linux-image-4.4.0-21-generic - linux-image-extra-4.4.0-21-generic - (working version is 4.2.0-35) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tpg2401 F pulseaudio /dev/snd/controlC0: tpg2401 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 17:08:04 2016 HibernationDevice: RESUME=UUID=ab95a533-52f3-4458-96dc-9119684b0ed6 InstallationDate: Installed on 2015-06-19 (312 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: TOSHIBA PORTEGE Z20t-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=b6cc139d-95e4-48f1-a3a8-284dbdb3b6fa ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-25 (1 days ago) dmi.bios.date: 01/06/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z20t-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd01/06/2015:svnTOSHIBA:pnPORTEGEZ20t-B:pvrPT15BA-00500Y:rvnTOSHIBA:rnPORTEGEZ20t-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z20t-B dmi.product.version: PT15BA-00500Y dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575071/+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 1857378] [NEW] Please drop i386 dkms package, as there are no i386 kernel
Public bug reported: Please drop i386 dkms package, as there are no i386 kernel Systems should enable amd64 archive and install amd64 kernel & the amd64 dkms package. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1857378 Title: Please drop i386 dkms package, as there are no i386 kernel Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Please drop i386 dkms package, as there are no i386 kernel Systems should enable amd64 archive and install amd64 kernel & the amd64 dkms package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1857378/+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 1856807] Re: eoan/linux: 5.3.0-26.28 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Signoff phase-changed: Friday, 20. December 2019 02:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-hwe: bug 1856849 + eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1856988 + eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 eoan/linux/unknown: bug 1856806, bug 1856805 variant: debs -- 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/1856807 Title: eoan/linux: 5.3.0-26.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Signoff phase-changed: Friday, 20. December 2019 02:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-hwe: bug 1856849 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1856988 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 eoan/linux/unknown: bug 1856806, bug 1856805 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856807/+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 1856985] Re: disco/linux-gcp: 5.0.0-1028.29 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854788 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Friday, 20. December 2019 02:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-gcp: bug 1856983 + bionic/linux-gke-5.0: bug 1854776 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1856985 Title: disco/linux-gcp: 5.0.0-1028.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854788 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Friday, 20. December 2019 02:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-gcp: bug 1856983 bionic/linux-gke-5.0: bug 1854776 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856985/+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 1856988] Re: eoan/linux-gcp: 5.3.0-1011.12 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1856807 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Friday, 20. December 2019 22:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff + trackers: + bionic/linux-gcp-5.3: bug 1854750 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1856988 Title: eoan/linux-gcp: 5.3.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1856807 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Friday, 20. December 2019 22:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-gcp-5.3: bug 1854750 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856988/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
This has been tested with live ubuntu 19.10 as suggested by Daniel and the mouse problem persists for intel braswell. xdotool reveals that X reports a vertical position of zero, even when the mouse is painted with an offset to the right, which seems to indicate this is could be a compositor problem, a mouse driver problem (not providing proper movement info to the left), or a 915 driver problem -- 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/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1443924]
GTA 5 Cheats PS4 https://learncybers.com/gta-5-cheats-ps4/ -- 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/1443924 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity after installing 15.04 Beta. The system did work correctly with older Ubuntu versions (like 12.04) and had this problem show up after upgrading to Trusty (as I already reported in bug #1318837). Using Trusty the problem went away when switching from the stock 3.13.0-XX-generic kernel to builds of newer kernels (like 3.14.1-031401). Now the same problem shows up again after installing Vivid Beta. It seems to be the same problem reported for other Ubuntu releases (see bugs #1318837 and #1383555) and also the same problem of this upstream kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=61621 Someone on kernel's bug mentions turning off MSI interrupts and I can confirm it did change the situation: - normally the system looses WiFi connectivity mere seconds after boot (eg. can't ping anything after boot) - if I boot with "pci=nomsi" the system will remain connected to the WiFi for a much longer period (eg. I am able to apt-get install something after boot) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic i686 ApportVersion: 2.17-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1997 F pulseaudio CurrentDesktop: LXDE Date: Tue Apr 14 14:19:19 2015 HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132 MachineType: Freeline Freeline Series ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 pci=nomsi RelatedPackageVersions: linux-restricted-modules-3.19.0-13-generic N/A linux-backports-modules-3.19.0-13-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: Freeline Series dmi.board.vendor: Freeline dmi.board.version: Ver1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr: dmi.product.name: Freeline Series dmi.product.version: Ver1.0 dmi.sys.vendor: Freeline To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1443924/+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] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed 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 1854746] Re: eoan/linux-aws: 5.3.0-1009.10 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1854762 + kernel-stable-master-bug: '1856807' packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 05. December 2019 11:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1854745 variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1856807' packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Testing - phase-changed: Thursday, 05. December 2019 11:36 UTC + phase: Signoff + phase-changed: Monday, 23. December 2019 16:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1854745 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1854746 Title: eoan/linux-aws: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1856807' packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Monday, 23. December 2019 16:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-aws-5.3: bug 1854745 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854746/+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 1854752] Re: eoan/linux-kvm: 5.3.0-1009.10 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1854762 + kernel-stable-master-bug: '1856807' packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 05. December 2019 10:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1856807' packages: main: linux-kvm meta: linux-meta-kvm - phase: Testing - phase-changed: Thursday, 05. December 2019 10:41 UTC + phase: Signoff + phase-changed: Monday, 23. December 2019 16:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1854752 Title: eoan/linux-kvm: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1856807' packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Monday, 23. December 2019 16:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854752/+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 1854746] Re: eoan/linux-aws: 5.3.0-1009.10 -proposed tracker
Verification is done for master kernel but this hasn't transitioned automatically. Manually setting VT to "Fix released" ** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1854746 Title: eoan/linux-aws: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 05. December 2019 11:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1854745 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854746/+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 1854752] Re: eoan/linux-kvm: 5.3.0-1009.10 -proposed tracker
Verification is done for master kernel but this hasn't transitioned automatically. Manually setting VT to "Fix released" ** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1854752 Title: eoan/linux-kvm: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 05. December 2019 10:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854752/+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 1857348] 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/1857348 Title: amdgpu crashes badly Status in linux package in Ubuntu: Confirmed Bug description: I'm running current ubuntu 19.10 with kernel "Ubuntu 5.3.0-24.26-generic 5.3.10" on a ThinkPad T495 laptop, which is confirmed to be certified here: https://certification.ubuntu.com/hardware/201905-27049 Unfortunately, the experience is really bad: `amdgpu` driver in the kernel crashes sometimes. I managed to get the `dmesg` output, please see atachemnt. This is confirmed at least on linux-image-5.3.0-18 and linux-image-5.3.0-24 "linux-image-X-generic ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-generic 5.3.0.24.28 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 Date: Mon Dec 23 14:50:14 2019 InstallationDate: Installed on 2019-12-07 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20NJ0010PB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET46W(1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NJ0010PB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NJ0010PB dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+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 1857348] Re: amdgpu crashes badly
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+attachment/5314874/+files/lspci-vnvn.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/1857348 Title: amdgpu crashes badly Status in linux package in Ubuntu: Confirmed Bug description: I'm running current ubuntu 19.10 with kernel "Ubuntu 5.3.0-24.26-generic 5.3.10" on a ThinkPad T495 laptop, which is confirmed to be certified here: https://certification.ubuntu.com/hardware/201905-27049 Unfortunately, the experience is really bad: `amdgpu` driver in the kernel crashes sometimes. I managed to get the `dmesg` output, please see atachemnt. This is confirmed at least on linux-image-5.3.0-18 and linux-image-5.3.0-24 "linux-image-X-generic ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-generic 5.3.0.24.28 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 Date: Mon Dec 23 14:50:14 2019 InstallationDate: Installed on 2019-12-07 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20NJ0010PB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET46W(1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NJ0010PB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NJ0010PB dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+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 1857348] Re: amdgpu crashes badly
** Attachment added: "dmesg-smdgpu.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+attachment/5314875/+files/dmesg-smdgpu.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/1857348 Title: amdgpu crashes badly Status in linux package in Ubuntu: Confirmed Bug description: I'm running current ubuntu 19.10 with kernel "Ubuntu 5.3.0-24.26-generic 5.3.10" on a ThinkPad T495 laptop, which is confirmed to be certified here: https://certification.ubuntu.com/hardware/201905-27049 Unfortunately, the experience is really bad: `amdgpu` driver in the kernel crashes sometimes. I managed to get the `dmesg` output, please see atachemnt. This is confirmed at least on linux-image-5.3.0-18 and linux-image-5.3.0-24 "linux-image-X-generic ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-generic 5.3.0.24.28 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 Date: Mon Dec 23 14:50:14 2019 InstallationDate: Installed on 2019-12-07 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20NJ0010PB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET46W(1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NJ0010PB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NJ0010PB dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+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 1857348] Re: amdgpu crashes badly
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+attachment/5314873/+files/version.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/1857348 Title: amdgpu crashes badly Status in linux package in Ubuntu: Confirmed Bug description: I'm running current ubuntu 19.10 with kernel "Ubuntu 5.3.0-24.26-generic 5.3.10" on a ThinkPad T495 laptop, which is confirmed to be certified here: https://certification.ubuntu.com/hardware/201905-27049 Unfortunately, the experience is really bad: `amdgpu` driver in the kernel crashes sometimes. I managed to get the `dmesg` output, please see atachemnt. This is confirmed at least on linux-image-5.3.0-18 and linux-image-5.3.0-24 "linux-image-X-generic ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-generic 5.3.0.24.28 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 Date: Mon Dec 23 14:50:14 2019 InstallationDate: Installed on 2019-12-07 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20NJ0010PB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET46W(1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NJ0010PB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NJ0010PB dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+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 1857348] [NEW] amdgpu crashes badly
Public bug reported: I'm running current ubuntu 19.10 with kernel "Ubuntu 5.3.0-24.26-generic 5.3.10" on a ThinkPad T495 laptop, which is confirmed to be certified here: https://certification.ubuntu.com/hardware/201905-27049 Unfortunately, the experience is really bad: `amdgpu` driver in the kernel crashes sometimes. I managed to get the `dmesg` output, please see atachemnt. This is confirmed at least on linux-image-5.3.0-18 and linux-image-5.3.0-24 "linux-image-X-generic ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-generic 5.3.0.24.28 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 Date: Mon Dec 23 14:50:14 2019 InstallationDate: Installed on 2019-12-07 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20NJ0010PB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET46W(1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NJ0010PB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NJ0010PB dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 amdgpu apport-bug eoan kernel-bug -- 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/1857348 Title: amdgpu crashes badly Status in linux package in Ubuntu: Confirmed Bug description: I'm running current ubuntu 19.10 with kernel "Ubuntu 5.3.0-24.26-generic 5.3.10" on a ThinkPad T495 laptop, which is confirmed to be certified here: https://certification.ubuntu.com/hardware/201905-27049 Unfortunately, the experience is really bad: `amdgpu` driver in the kernel crashes sometimes. I managed to get the `dmesg` output, please see atachemnt. This is confirmed at least on linux-image-5.3.0-18 and linux-image-5.3.0-24 "linux-image-X-generic ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-generic 5.3.0.24.28 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 Date: Mon Dec 23 14:50:14 2019 InstallationDate: Installed on 2019-12-07 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20NJ0010PB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET46W(1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NJ0010PB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NJ0010PB dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1857348] Re: amdgpu crashes badly
** Attachment added: "output of lsmod" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+attachment/5314876/+files/lsmod.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/1857348 Title: amdgpu crashes badly Status in linux package in Ubuntu: Confirmed Bug description: I'm running current ubuntu 19.10 with kernel "Ubuntu 5.3.0-24.26-generic 5.3.10" on a ThinkPad T495 laptop, which is confirmed to be certified here: https://certification.ubuntu.com/hardware/201905-27049 Unfortunately, the experience is really bad: `amdgpu` driver in the kernel crashes sometimes. I managed to get the `dmesg` output, please see atachemnt. This is confirmed at least on linux-image-5.3.0-18 and linux-image-5.3.0-24 "linux-image-X-generic ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-generic 5.3.0.24.28 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 Date: Mon Dec 23 14:50:14 2019 InstallationDate: Installed on 2019-12-07 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20NJ0010PB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET46W(1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NJ0010PB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NJ0010PB dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+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 1776563]
Where did you find information about the positive site, this post? I just read some articles on your website, and I really like your style. Thank you for the millions and keep working effectively.and also found some interesting topi roblox asset downloader here https://www.giantbomb.com/profile/emmaro/blog/roblox-free-robux- generator-2020/142230/ -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+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 1239459]
GTA 5 Cheats PS4 https://learncybers.com/gta-5-cheats-ps4/ -- 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/1239459 Title: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: With the new 3.11.0-12-generic kernel, wifi has problems to connect with many errors like these: Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0 Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 1791 F pulseaudio Date: Sun Oct 13 23:45:04 2013 HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15 InstallationDate: Installed on 2013-10-12 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X200CA MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago) dmi.bios.date: 09/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200CA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X200CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1239459/+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 1857336] Re: Touchpad not Working
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 ** This bug has been marked a duplicate of bug 1854798 Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic -- 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/1857336 Title: Touchpad not Working Status in linux package in Ubuntu: Confirmed Bug description: I am using BIOS with Windows and Ubuntu 18.04. Laptop's touchpad is working in windows but not in Ubuntu. Please help... 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: saurabh2383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 17:00:50 2019 InstallationDate: Installed on 2019-03-30 (267 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:241a Syntek Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 004: ID :0538 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=046d4d12-a05e-4ff4-b64e-35eddc269873 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: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857336/+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 1857336] 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/1857336 Title: Touchpad not Working Status in linux package in Ubuntu: Confirmed Bug description: I am using BIOS with Windows and Ubuntu 18.04. Laptop's touchpad is working in windows but not in Ubuntu. Please help... 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: saurabh2383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 17:00:50 2019 InstallationDate: Installed on 2019-03-30 (267 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:241a Syntek Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 004: ID :0538 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=046d4d12-a05e-4ff4-b64e-35eddc269873 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: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857336/+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 1857336] [NEW] Touchpad not Working
Public bug reported: I am using BIOS with Windows and Ubuntu 18.04. Laptop's touchpad is working in windows but not in Ubuntu. Please help... 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: saurabh2383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 17:00:50 2019 InstallationDate: Installed on 2019-03-30 (267 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:241a Syntek Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 004: ID :0538 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=046d4d12-a05e-4ff4-b64e-35eddc269873 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: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1857336 Title: Touchpad not Working Status in linux package in Ubuntu: New Bug description: I am using BIOS with Windows and Ubuntu 18.04. Laptop's touchpad is working in windows but not in Ubuntu. Please help... 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: saurabh2383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 17:00:50 2019 InstallationDate: Installed on 2019-03-30 (267 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:241a Syntek Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 004: ID :0538 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=046d4d12-a05e-4ff4-b64e-35eddc269873 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: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857336/+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 made a log with heart rate audio while playing video on vlc when there is no sound. Hope this helps https://paste.ee/p/q8dIz ** Changed in: linux-raspi2 (Ubuntu) Status: New => In Progress -- 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: In Progress 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 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
It looks the same bug on my Linux Mint 19.2 Cinnamon, Linux Kernel: 4.15.0-72-generic Using second second monitor with NVIDIA Corporation GF108M [GeForce GT 525M] graphics. The error log is on tty1 console: [drm:intel_set_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A -- 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/1550779 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this
[Kernel-packages] [Bug 1856701] Re: focal/linux: 5.4.0-9.12 -proposed tracker
** Tags added: update-excuse-focal ** Branch linked: lp:~xnox/britney/release-v5.4 -- 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/1856701 Title: focal/linux: 5.4.0-9.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Release phase-changed: Sunday, 22. December 2019 01:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856701/+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
any ideas? -- 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: New 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
Re: [Kernel-packages] [Bug 1850681] Re: TREKSTOR Primebook C11B touchpad and touchscreen not working
> thanks a lot ! touchpad active after restart, no touchscreen, but that would be of lesser importance. Thx again - Frank Lettau - $ sudo apt install linux-generic-hwe-18.04-edge > > -- > You received this bug notification because you are subscribed to the bug > report. > 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 > -- 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.
[Kernel-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
Well well, I change my mind. It may bug a xfce bug see that everything is Ok with 5.3.0-24-generic kernel and gnome, mate and cinnamon interfaces. No more bug display -- 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/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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 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 xserver.bootTime: Sat Oct 19 23:52:52 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config
[Kernel-packages] [Bug 1857227] Re: PulseAudio sound disappears on hdmi via stereo output
** Changed in: linux-raspi2 (Ubuntu) Status: Incomplete => New -- 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: New 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
