[Kernel-packages] [Bug 1993532] Re: [i915] Unable to see second monitor in 5.15.0-52 (but 5.15.0-50 works)
I don't know what changed, but I've had no issues for a while now. I've been using HDMI via a USB-C/thunderbolt dongle. -- 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/1993532 Title: [i915] Unable to see second monitor in 5.15.0-52 (but 5.15.0-50 works) Status in linux package in Ubuntu: Expired Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+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 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
I would gladly answer #20 @kaihengfeng but I don't have nor want Windows on this professional machine used for sysadmin work. Since this appears to be a global kernel issue and I didn't find it on the Linux kernel Bugzilla, I have forwarded the issue: https://bugzilla.kernel.org/show_bug.cgi?id=217076 I'm unsure if this is necessary, but if not, there isn't much harm, and if necessary, well now it's done. All the best ** Bug watch added: Linux Kernel Bug Tracker #217076 https://bugzilla.kernel.org/show_bug.cgi?id=217076 -- 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/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: LG Gram laptop 17Z90Q with a Core i7-1260P CPU. Whenever an external monitor is connected to USB-C/Thunderbolt 4, average load goes above 3.0 and the machine is getting very hot. Output from top -H shows a lot of kworker CPU usage: top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 buff/cache MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ WCHAN COMMAND 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 worker_th+ kworker/0:2-events 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 ec_guard kworker/u32:2+USBC000:00-con0 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 worker_th+ kworker/0:0-events 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 worker_th+ kworker/1:3-events 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 worker_th+ kworker/15:0-events 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 worker_th+ kworker/11:1-events 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 worker_th+ kworker/9:3-events Perf shows a lot of time spent inside handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. Additionally, kernel log is getting spammed with these lines every 4 seconds (but also without any USB-C device attached): [ 223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20210730/exfldio-261) [ 223.514337] Initialized Local Variables for Method [_TMP]: [ 223.514339] Local0: 21495082Integer 0034 [ 223.514349] No Arguments are initialized for method [_TMP] [ 223.514354] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1678 F pulseaudio /dev/snd/controlC1: me 1678 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Aug 26 11:57:05 2022 InstallationDate: Installed on 2022-08-25 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LG Electronics 17Z90Q-G.AA78N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: A1ZG0380 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17Z90Q dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.ec.firmware.release: 33.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrA1ZG0380X64:bd07/06/2022:br0.1:efr33.0:svnLGElectronics:pn17Z90Q-G.AA78N:pvr0.1:rvnLGElectronics:rn
[Kernel-packages] [Bug 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
@kaihengfeng I gave latest mainline a try on my Fedora, installed through copr according to this doc: https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories It's kernel 6.3 instead of 6.2, but I would assume it contains changes from 6.2. No luck, still same symptoms. # uname -a Linux lrob.local 6.3.0-0.rc0.20230222gt5b7c4cab.201.vanilla.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Feb 22 05:16:05 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux At idle: # cat /proc/loadavg 2.66 3.05 2.87 3/2147 27819 Processes on top of CPU utilization: 1044 root 20 0 0 0 0 D 18.2 0.0 0:07.52 [kworker/u32:8+USBC000:00-con0] 19136 root 20 0 0 0 0 D 17.5 0.0 0:02.22 [kworker/0:0+events] 230 root 20 0 0 0 0 R 15.2 0.0 1:04.60 [kworker/0:3+kacpi_notify] Also the issue is now occurring even when the laptop's battery is 100% charged as it is currently. On a side note, a Thunderbolt docking station from Dell, which also charges the laptop, shows the exact same symptoms as the embedded charger. All the best. -- 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/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: LG Gram laptop 17Z90Q with a Core i7-1260P CPU. Whenever an external monitor is connected to USB-C/Thunderbolt 4, average load goes above 3.0 and the machine is getting very hot. Output from top -H shows a lot of kworker CPU usage: top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 buff/cache MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ WCHAN COMMAND 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 worker_th+ kworker/0:2-events 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 ec_guard kworker/u32:2+USBC000:00-con0 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 worker_th+ kworker/0:0-events 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 worker_th+ kworker/1:3-events 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 worker_th+ kworker/15:0-events 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 worker_th+ kworker/11:1-events 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 worker_th+ kworker/9:3-events Perf shows a lot of time spent inside handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. Additionally, kernel log is getting spammed with these lines every 4 seconds (but also without any USB-C device attached): [ 223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20210730/exfldio-261) [ 223.514337] Initialized Local Variables for Method [_TMP]: [ 223.514339] Local0: 21495082Integer 0034 [ 223.514349] No Arguments are initialized for method [_TMP] [ 223.514354] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1678 F pulseaudio /dev/snd/controlC1: me 1678 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Aug 26 11:57:05 2022 InstallationDate: Installed on 2022-08-25 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LG Electronics 17Z90Q-G.AA78N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7 PulseList: Error: comm
[Kernel-packages] [Bug 2003857] [NEW] nvidia module keeps going missing
Public bug reported: I have nvidia drivers to use the secondary GPU. I've notice that, probably due to kernel upgrades, the module doesn't get rebuilt for the new kernel. The "additional drivers" tool shows it as being installed (see screenshot.) $ lsmod | grep nvi $ $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. If I use the additional drivers tool to go to an old version and back to a new one, it starts working again for a while. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-515 515.76+really.515.65.01-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 25 12:15:07 2023 InstallationDate: Installed on 2022-03-23 (307 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: nvidia-graphics-drivers-515 UpgradeStatus: Upgraded to kinetic on 2022-10-22 (95 days ago) ** Affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "additional drivers" https://bugs.launchpad.net/bugs/2003857/+attachment/5643319/+files/Screenshot%20from%202023-01-25%2012-14-46.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/2003857 Title: nvidia module keeps going missing Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: I have nvidia drivers to use the secondary GPU. I've notice that, probably due to kernel upgrades, the module doesn't get rebuilt for the new kernel. The "additional drivers" tool shows it as being installed (see screenshot.) $ lsmod | grep nvi $ $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. If I use the additional drivers tool to go to an old version and back to a new one, it starts working again for a while. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-515 515.76+really.515.65.01-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 25 12:15:07 2023 InstallationDate: Installed on 2022-03-23 (307 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: nvidia-graphics-drivers-515 UpgradeStatus: Upgraded to kinetic on 2022-10-22 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/2003857/+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 1882968] Re: ath10k_pci failed to wake target for write32
Thanks. So I installed 18 LTS again. A major PITA, but I used 18 LTS on this laptop for 2 full years without a problem. Always fully upgraded, so with all the standard permutations of kernel, modules and firmware, on lots of different wifi networks. There was never a single issue. Nor under 16.10 or 20 LTS for the first year. This time it crashed within 2 hours. I take this as final confirmation that this bug is not all it seems. There is clearly an arbitrary hardware component. The laptop is on its last legs. It's on its second power block, one USB port is gone. Apparently this is way the wifi chip goes out. Thanks for the ideas and feedback. -- 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/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] Re: ath10k_pci failed to wake target for write32
But how would the live CD change anything? I'm on exactly the same version as the live CD right now (20.4.5). What I *know* is that my system was stable on 20.4.1 from two years ago, i.e. that version of the kernel, modules, and firmware. So how would I go about reverting to it (and blocking upgrades)? Then, if the crashes *still* continue, I can conclude that I must have a hardware fault. After all, it seems the software problem is fixed for everybody except me. Or am I not understanding something fundamental? -- 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/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] Re: ath10k_pci failed to wake target for write32
Ideas, anyone? (Driving me crazy - 5 crashes this morning.) This is basically a virgin Ubuntu 20 LTS. My laptop had no problems with 20 LTS until about a year ago. To exclude hardware failure as the cause, my idea is to get the software back to the state it was in a year ago. Is that reasonable? How can it be done? I just did `apt install linux-generic` to get the 5.4 kernel. But how should I revert whatever changes `apt full-upgrade` and `unattended- upgrade` have made? At this point I don't care about security holes, I just want to know if this is a hardware or software issue, since apparently it got solved for everyone else but not me (or maybe the others gave up and junked their computers). -- 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/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] Re: ath10k_pci failed to wake target for write32
@kaihengfeng I try to use only the most vanilla setup, so yes, it has happened with all the mainline Ubuntu kernels coming from 20 LTS upgrades over the last year and also 22.10. Suspend is disabled, I guess by kernel parameter `pcie_aspm=off`, by `HandleLidSwitch=ignore` in `/etc/systemd/logind.conf`, and by the fact that I'm using a tiling window manager without any screen timeout. When suspend was enabled with Gnome, the issue did NOT specially affect waking from suspend. It seems to arise randomly. Occasionally the crash is quite hard and freezes the system for 30 seconds. I believe this scenario is when even a reboot is not enough - the card "fails to wake" even on boot. Only a second reboot will fix it (see #18 above for dmesg). Crazy. It's probably unrelated, but here's some dmesg output from very early in boot: [0.040179] Kernel command line: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro text pcie_aspm=off pcie_port_pm=off [0.040374] PCIe ASPM is disabled [0.040432] Unknown kernel command line parameters "text BOOT_IMAGE=/vmlinuz-5.15.0-56-generic", will be passed to user space. Is this last line expected? More generally, how would I exclude the possibility of hardware failure? -- 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/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] Re: ath10k_pci failed to wake target for write32
Crashed. :( $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro text pcie_aspm=off pcie_port_pm=off -- 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/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] Re: ath10k_pci failed to wake target for write32
Interesting. Yes `pcie_aspm=off` is already in the grub parameters but not `pcie_port_pm=off`. I will add that now, wait for the daily crash and then report back in due course. Thanks. -- 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/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] Re: ath10k_pci failed to wake target for write32
$ sudo lshw -C Network *-network description: Wireless interface product: QCA9377 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:01:00.0 logical name: wlp1s0 version: 31 serial: f9:03:2c:14:50:91 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.15.0-56-generic firmware=WLAN.TF.2.1-00021-QCARMSWP-1 ip=192.168.1.66 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:9120-913f Yes yes, disabling power management was the first thing I tried. $ iwconfig wlp1s0 wlp1s0IEEE 802.11 ESSID:"XXX" Mode:Managed Frequency:5.52 GHz Access Point: 22:8D:36:8F:62:3B Bit Rate=6 Mb/s Tx-Power=30 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=39/70 Signal level=-71 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:550 Missed beacon:0 I've seen every single forum discussion about this issue (lots of them) and tried everything short of compiling custom software. The Fedora discussion (https://bugzilla.redhat.com/show_bug.cgi?id=1846802) is particularly dense. It ends with "Won't fix". ** Bug watch added: Red Hat Bugzilla #1846802 https://bugzilla.redhat.com/show_bug.cgi?id=1846802 -- 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/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] Re: ath10k_pci failed to wake target for write32
Just the usual "failed to wake target", sometimes accompanied by "firmware crashed!", but always requiring a full reboot to fix. BUT occasionally it even "sleeps through" the reboot and requires a second reboot! In fact this was what happened last time, yesterday. Here's the dmesg: [ 41.752713] wlp1s0: authenticate with 44:8d:36:8f:62:41 [ 41.752783] wlp1s0: bad VHT capabilities, disabling VHT [ 41.752796] wlp1s0: 80 MHz not supported, disabling VHT [ 41.799985] wlp1s0: send auth to 44:8d:36:8f:62:41 (try 1/3) [ 41.801945] wlp1s0: authenticated [ 41.805210] wlp1s0: associate with 44:8d:36:8f:62:41 (try 1/3) [ 41.809491] wlp1s0: RX AssocResp from 44:8d:36:8f:62:41 (capab=0x1411 status=0 aid=2) [ 41.816358] wlp1s0: associated [ 41.816957] ath: EEPROM regdomain: 0x82d4 [ 41.816980] ath: EEPROM indicates we should expect a country code [ 41.817133] ath: doing EEPROM country->regdmn map search [ 41.817154] ath: country maps to regdmn code: 0x37 [ 41.817166] ath: Country alpha2 being used: ES [ 41.817176] ath: Regpair used: 0x37 [ 41.817186] ath: regdomain 0x82d4 dynamically updated by country element [ 41.950556] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready [ 41.950542] wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 44:8d:36:8f:62:41 [ 44.774289] ath10k_pci :01:00.0: failed to wake target for write32 of 0x0041 at 0x0003543c: -110 Could it be a clue? -- 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/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] Re: ath10k_pci failed to wake target for write32
Hello thedoctar. As mentioned, I had 22.10 installed with latest repo-provided firmware. That's pretty recent isn't it? I also tried a surgical downgrade of the ath10k firmware to a version corresponding to 20 LTS. Crashes continued. I tried removing the firmware6.bin file which forced "API5" mode. Crashes continued. Then I completely reinstalled 20 LTS, refusing the non-security upgrades. Crashes go on. This seems like quite a lot of software permutations over quite a time period - is there reason to think that the very latest firmware update will have magically fixed something people have been complaining about on various other distros for 7 years? What I don't get is that I had zero problems with this same laptop under Ubuntu 18 for 3 years. That suggests a regression does it not? - or could the wifi card be physically failing? I'm reluctant to junk it because of a problem that has been so widely reported as a software bug. Very frustrating. -- 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/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] Re: ath10k_pci failed to wake target for write32
This bug is still very much a thing. A quick search will show plenty of recentish talk on forums of other distros. On my laptop it affects both 20 LTS and the latest 22.10. Have tried everything. Disabling wifi power management. Limiting the band to 2.4khz (supposedly more stable). Upgrading the linux-firmware package (obviously). Switching the firmware files with versions from previous releases. Switching kernels. Once or twice I have managed a month or so of stability (perhaps something special about the LAN). Other times it crashes multiple times per day. Nothing fixes it. Before Ubuntu 20 wifi on my machine worked perfectly. Since then it has not. Very frustrating indeed. -- 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/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
Issue re-reproduced on Ubuntu 22.04 as well, same laptop model (LG Gram 16Z90Q). -- 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/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: LG Gram laptop 17Z90Q with a Core i7-1260P CPU. Whenever an external monitor is connected to USB-C/Thunderbolt 4, average load goes above 3.0 and the machine is getting very hot. Output from top -H shows a lot of kworker CPU usage: top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 buff/cache MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ WCHAN COMMAND 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 worker_th+ kworker/0:2-events 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 ec_guard kworker/u32:2+USBC000:00-con0 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 worker_th+ kworker/0:0-events 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 worker_th+ kworker/1:3-events 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 worker_th+ kworker/15:0-events 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 worker_th+ kworker/11:1-events 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 worker_th+ kworker/9:3-events Perf shows a lot of time spent inside handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. Additionally, kernel log is getting spammed with these lines every 4 seconds (but also without any USB-C device attached): [ 223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20210730/exfldio-261) [ 223.514337] Initialized Local Variables for Method [_TMP]: [ 223.514339] Local0: 21495082Integer 0034 [ 223.514349] No Arguments are initialized for method [_TMP] [ 223.514354] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1678 F pulseaudio /dev/snd/controlC1: me 1678 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Aug 26 11:57:05 2022 InstallationDate: Installed on 2022-08-25 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LG Electronics 17Z90Q-G.AA78N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: A1ZG0380 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17Z90Q dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.ec.firmware.release: 33.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrA1ZG0380X64:bd07/06/2022:br0.1:efr33.0:svnLGElectronics:pn17Z90Q-G.AA78N:pvr0.1:rvnLGElectronics:rn17Z90Q:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:skuEVO: dmi.product.family: LG gram PC dmi.product.name: 17Z90Q-G.AA78N dmi.product.sku: EVO dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : http
[Kernel-packages] [Bug 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
Not only an Ubuntu bug, it also affects Fedora with similar symptoms. Also, this happens when the device connected to USBC is a charger; and it appears to stop once fully charged. -- 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/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in linux package in Ubuntu: Confirmed Bug description: LG Gram laptop 17Z90Q with a Core i7-1260P CPU. Whenever an external monitor is connected to USB-C/Thunderbolt 4, average load goes above 3.0 and the machine is getting very hot. Output from top -H shows a lot of kworker CPU usage: top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 buff/cache MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ WCHAN COMMAND 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 worker_th+ kworker/0:2-events 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 ec_guard kworker/u32:2+USBC000:00-con0 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 worker_th+ kworker/0:0-events 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 worker_th+ kworker/1:3-events 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 worker_th+ kworker/15:0-events 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 worker_th+ kworker/11:1-events 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 worker_th+ kworker/9:3-events Perf shows a lot of time spent inside handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. Additionally, kernel log is getting spammed with these lines every 4 seconds (but also without any USB-C device attached): [ 223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20210730/exfldio-261) [ 223.514337] Initialized Local Variables for Method [_TMP]: [ 223.514339] Local0: 21495082Integer 0034 [ 223.514349] No Arguments are initialized for method [_TMP] [ 223.514354] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1678 F pulseaudio /dev/snd/controlC1: me 1678 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Aug 26 11:57:05 2022 InstallationDate: Installed on 2022-08-25 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LG Electronics 17Z90Q-G.AA78N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: A1ZG0380 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17Z90Q dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.ec.firmware.release: 33.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrA1ZG0380X64:bd07/06/2022:br0.1:efr33.0:svnLGElectronics:pn17Z90Q-G.AA78N:pvr0.1:rvnLGElectronics:rn17Z90Q:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:skuEVO: dmi.product.family: LG gram PC dmi.product.name: 17Z90Q-G.AA78N dmi.product.sku: EVO dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1993532] Re: Unable to see second monitor
...but unlike last time it works when I plug HDMI directly in. -- 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/1993532 Title: Unable to see second monitor Status in linux package in Ubuntu: Incomplete Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+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 1993532] Re: Unable to see second monitor
This has resurfaced again: $ grep connect /sys/class/drm/*/status /sys/class/drm/card0-DP-1/status:disconnected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-eDP-1/status:connected /sys/class/drm/card0-HDMI-A-1/status:disconnected /sys/class/drm/card0-HDMI-A-2/status:disconnected /sys/class/drm/card0-HDMI-A-3/status:disconnected /sys/class/drm/card1-DVI-I-1/status:disconnected /sys/class/drm/card2-DVI-I-2/status:disconnected /sys/class/drm/card3-DVI-I-3/status:disconnected /sys/class/drm/card4-DVI-I-4/status:disconnected Despite it working fine before the reboot. -- 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/1993532 Title: Unable to see second monitor Status in linux package in Ubuntu: Incomplete Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+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 1995238] Re: snaps randomly crash after some time
I'm on kernel 6.0.7, all appears well so far. -- 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/1995238 Title: snaps randomly crash after some time Status in snapd: Invalid Status in linux package in Ubuntu: Confirmed Bug description: This is https://forum.snapcraft.io/t/unsupported-version-0-of-verneed- record-linux-6-0/32160. When I load the web interfaces to these two services, firefox will immediately crash. Attempting to run from the command-line produces an error message as follows: Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: /snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed record Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ /snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verdef record] The only way to restart firefox is to restart the computer! Logging out and in again, then running firefox, produces the same errors. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 Uname: Linux 6.0.6-060006-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 31 19:41:21 2022 InstallationDate: Installed on 2019-05-26 (1253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1995238/+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 1995238] Re: snaps randomly crash after some time
I think it's likely that firefox crashing on bumble/whatsapp is a red herring, a coincidence. As Donald reports, his setup crashes on any new tabs. -- 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/1995238 Title: snaps randomly crash after some time Status in snapd: New Status in linux package in Ubuntu: Confirmed Bug description: This is https://forum.snapcraft.io/t/unsupported-version-0-of-verneed- record-linux-6-0/32160. When I load the web interfaces to these two services, firefox will immediately crash. Attempting to run from the command-line produces an error message as follows: Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: /snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed record Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ /snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verdef record] The only way to restart firefox is to restart the computer! Logging out and in again, then running firefox, produces the same errors. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 Uname: Linux 6.0.6-060006-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 31 19:41:21 2022 InstallationDate: Installed on 2019-05-26 (1253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1995238/+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 1993532] Re: Unable to see second monitor
$ uname -a Linux tangaroa 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ grep connect /sys/class/drm/*/status /sys/class/drm/card0-DP-1/status:connected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-eDP-1/status:connected /sys/class/drm/card0-HDMI-A-1/status:disconnected /sys/class/drm/card0-HDMI-A-2/status:disconnected /sys/class/drm/card0-HDMI-A-3/status:disconnected /sys/class/drm/card1-DVI-I-1/status:disconnected /sys/class/drm/card2-DVI-I-2/status:disconnected /sys/class/drm/card3-DVI-I-3/status:disconnected /sys/class/drm/card4-DVI-I-4/status:disconnected ... and it's still working. That's quite odd as I did multiple reboots/tests yesterday and it was consistently the new kernel that was causing it to not work, today it's worked no matter what. I guess perhaps there was some coincidental thing happening that made it look like a pattern. -- 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/1993532 Title: Unable to see second monitor Status in linux package in Ubuntu: Incomplete Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+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 1993532] Re: Unable to see second monitor
oh, this is interesting. I booted with the HDMI directly connected into -52, and it worked. $ grep connect /sys/class/drm/*/status /sys/class/drm/card0-DP-1/status:disconnected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-eDP-1/status:connected /sys/class/drm/card0-HDMI-A-1/status:connected /sys/class/drm/card0-HDMI-A-2/status:disconnected /sys/class/drm/card0-HDMI-A-3/status:disconnected /sys/class/drm/card1-DVI-I-1/status:disconnected /sys/class/drm/card2-DVI-I-2/status:disconnected /sys/class/drm/card3-DVI-I-3/status:disconnected /sys/class/drm/card4-DVI-I-4/status:disconnected Replugged it into the dongle, and it works again: $ grep connect /sys/class/drm/*/status /sys/class/drm/card0-DP-1/status:connected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-eDP-1/status:connected /sys/class/drm/card0-HDMI-A-1/status:disconnected /sys/class/drm/card0-HDMI-A-2/status:disconnected /sys/class/drm/card0-HDMI-A-3/status:disconnected /sys/class/drm/card1-DVI-I-1/status:disconnected /sys/class/drm/card2-DVI-I-2/status:disconnected /sys/class/drm/card3-DVI-I-3/status:disconnected /sys/class/drm/card4-DVI-I-4/status:disconnected Trying a power off/reboot with it plugged into the dongle now. -- 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/1993532 Title: Unable to see second monitor Status in linux package in Ubuntu: Incomplete Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+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 1993532] Re: Unable to see second monitor
Ah, the displaylink stuff is perhaps a red herring. Some of our office configurations use that so I have the drivers installed to work with it, however it's not in use in this case. Note that the monitor detection also fails when plugged directly into the laptop's HDMI port. These are the connected devices in a working configuration, via the USB-C dongle: $ grep connect /sys/class/drm/*/status /sys/class/drm/card0-DP-1/status:connected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-eDP-1/status:connected /sys/class/drm/card0-HDMI-A-1/status:disconnected /sys/class/drm/card0-HDMI-A-2/status:disconnected /sys/class/drm/card0-HDMI-A-3/status:disconnected /sys/class/drm/card1-DVI-I-1/status:disconnected /sys/class/drm/card2-DVI-I-2/status:disconnected /sys/class/drm/card3-DVI-I-3/status:disconnected /sys/class/drm/card4-DVI-I-4/status:disconnected via the HDMI port directly: $ grep connect /sys/class/drm/*/status /sys/class/drm/card0-DP-1/status:disconnected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-eDP-1/status:connected /sys/class/drm/card0-HDMI-A-1/status:connected /sys/class/drm/card0-HDMI-A-2/status:disconnected /sys/class/drm/card0-HDMI-A-3/status:disconnected /sys/class/drm/card1-DVI-I-1/status:disconnected /sys/class/drm/card2-DVI-I-2/status:disconnected /sys/class/drm/card3-DVI-I-3/status:disconnected /sys/class/drm/card4-DVI-I-4/status:disconnected and I'll reboot into the newer kernel to collect that also. -- 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/1993532 Title: Unable to see second monitor Status in linux package in Ubuntu: Incomplete Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+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 1993532] [NEW] Unable to see second monitor
Public bug reported: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-session -- 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/1993532 Title: Unable to see second monitor Status in linux package in Ubuntu: Confirmed Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+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 1973463] Re: ZFS kernel null pointer dereference
Sorry, this is not a reliably reproducible bug so I won't be able to provide any more logs. Feel free to close if this this report is not useful -- 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/1973463 Title: ZFS kernel null pointer dereference Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 LTS Linux server 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux zfs-2.1.2-1ubuntu3 zfs-kmod-2.1.2-1ubuntu3 [ 1249.508427] BUG: kernel NULL pointer dereference, address: 002a [ 1249.508435] #PF: supervisor read access in kernel mode [ 1249.508438] #PF: error_code(0x) - not-present page [ 1249.508440] PGD 0 P4D 0 [ 1249.508444] Oops: [#1] SMP NOPTI [ 1249.508447] CPU: 3 PID: 2119 Comm: txg_sync Tainted: PW O 5.15.0-30-generic #31-Ubuntu [ 1249.508452] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P5.90 07/03/2019 [ 1249.508455] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1249.508564] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1249.508571] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1249.508576] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1249.508580] RDX: RSI: c1494df0 RDI: 0002 [ 1249.508583] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1249.508587] R10: 8cc62bfa4a80 R11: R12: 8cca7b162280 [ 1249.508590] R13: 0009 R14: 8cca70f1ea30 R15: 8cc62bfa4a80 [ 1249.508594] FS: () GS:8ccdfeac() knlGS: [ 1249.508598] CS: 0010 DS: ES: CR0: 80050033 [ 1249.508601] CR2: 002a CR3: 0004c2b7e000 CR4: 003506e0 [ 1249.508607] Call Trace: [ 1249.508610] [ 1249.508613] ? RW_WRITE_HELD+0x9/0x20 [zfs] [ 1249.508689] dmu_buf_will_dirty_impl+0x87/0x110 [zfs] [ 1249.508786] dmu_buf_will_dirty+0x16/0x20 [zfs] [ 1249.508869] space_map_write+0x3f/0x1a0 [zfs] [ 1249.508970] metaslab_sync+0x60a/0x8b0 [zfs] [ 1249.509066] ? __raw_spin_unlock+0x9/0x10 [zfs] [ 1249.509182] vdev_sync+0x72/0x190 [zfs] [ 1249.509281] spa_sync_iterate_to_convergence+0x14f/0x1e0 [zfs] [ 1249.509388] spa_sync+0x2dc/0x5b0 [zfs] [ 1249.509483] txg_sync_thread+0x266/0x2f0 [zfs] [ 1249.509582] ? txg_dispatch_callbacks+0x100/0x100 [zfs] [ 1249.509683] thread_generic_wrapper+0x64/0x70 [spl] [ 1249.509695] ? __thread_exit+0x20/0x20 [spl] [ 1249.509704] kthread+0x12a/0x150 [ 1249.509708] ? set_kthread_struct+0x50/0x50 [ 1249.509712] ret_from_fork+0x22/0x30 [ 1249.509717] [ 1249.509718] Modules linked in: wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 libcurve25519_generic libchacha libblake2s_generic sctp ip6_udp_tunnel udp_tunnel macvtap macvlan vhost_net vhost vhost_iotlb tap xt_nat veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables libcrc32c nfnetlink bridge stp llc overlay intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd zfs(PO) zunicode(PO) snd_hda_codec_realtek kvm_amd zzstd(O) snd_hda_codec_generic zlua(O) snd_hda_codec_hdmi ledtrig_audio kvm crct10dif_pclmul ghash_clmulni_intel zcommon(PO) snd_usb_audio aesni_intel crypto_simd znvpair(PO) cryptd snd_usbmidi_lib zavl(PO) snd_hda_codec wmi_bmof snd_rawmidi rapl k10temp efi_pstore nls_iso8859_1 snd_hda_core snd_seq_device snd_hwdep icp(PO) mc snd_pcm spl(O) [ 1249.509765] input_leds snd_timer snd joydev soundcore ccp mac_hid sch_fq_codel nct6775 hwmon_vid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid mpt3sas hid nvme uas raid_class usb_storage gpio_amdpt r8169 crc32_pclmul xhci_pci scsi_transport_sas ahci i2c_piix4 realtek e1000e nvme_core libahci xhci_pci_renesas wmi gpio_generic [last unloaded: snd_intel_sdw_acpi] [ 1249.509806] CR2: 002a [ 1249.509808] ---[ end trace 09588539e96f5ea2 ]--- [ 1250.063053] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1250.063198] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1250.063206] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1250.063211] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1250.063215] RDX: RSI: c1494df0 RDI: 0002 [ 1250.0
[Kernel-packages] [Bug 1973463] Re: ZFS kernel null pointer dereference
** Package changed: ubuntu => zfs-linux (Ubuntu) -- 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/1973463 Title: ZFS kernel null pointer dereference Status in zfs-linux package in Ubuntu: New Bug description: Ubuntu 22.04 LTS Linux server 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux zfs-2.1.2-1ubuntu3 zfs-kmod-2.1.2-1ubuntu3 [ 1249.508427] BUG: kernel NULL pointer dereference, address: 002a [ 1249.508435] #PF: supervisor read access in kernel mode [ 1249.508438] #PF: error_code(0x) - not-present page [ 1249.508440] PGD 0 P4D 0 [ 1249.508444] Oops: [#1] SMP NOPTI [ 1249.508447] CPU: 3 PID: 2119 Comm: txg_sync Tainted: PW O 5.15.0-30-generic #31-Ubuntu [ 1249.508452] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P5.90 07/03/2019 [ 1249.508455] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1249.508564] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1249.508571] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1249.508576] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1249.508580] RDX: RSI: c1494df0 RDI: 0002 [ 1249.508583] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1249.508587] R10: 8cc62bfa4a80 R11: R12: 8cca7b162280 [ 1249.508590] R13: 0009 R14: 8cca70f1ea30 R15: 8cc62bfa4a80 [ 1249.508594] FS: () GS:8ccdfeac() knlGS: [ 1249.508598] CS: 0010 DS: ES: CR0: 80050033 [ 1249.508601] CR2: 002a CR3: 0004c2b7e000 CR4: 003506e0 [ 1249.508607] Call Trace: [ 1249.508610] [ 1249.508613] ? RW_WRITE_HELD+0x9/0x20 [zfs] [ 1249.508689] dmu_buf_will_dirty_impl+0x87/0x110 [zfs] [ 1249.508786] dmu_buf_will_dirty+0x16/0x20 [zfs] [ 1249.508869] space_map_write+0x3f/0x1a0 [zfs] [ 1249.508970] metaslab_sync+0x60a/0x8b0 [zfs] [ 1249.509066] ? __raw_spin_unlock+0x9/0x10 [zfs] [ 1249.509182] vdev_sync+0x72/0x190 [zfs] [ 1249.509281] spa_sync_iterate_to_convergence+0x14f/0x1e0 [zfs] [ 1249.509388] spa_sync+0x2dc/0x5b0 [zfs] [ 1249.509483] txg_sync_thread+0x266/0x2f0 [zfs] [ 1249.509582] ? txg_dispatch_callbacks+0x100/0x100 [zfs] [ 1249.509683] thread_generic_wrapper+0x64/0x70 [spl] [ 1249.509695] ? __thread_exit+0x20/0x20 [spl] [ 1249.509704] kthread+0x12a/0x150 [ 1249.509708] ? set_kthread_struct+0x50/0x50 [ 1249.509712] ret_from_fork+0x22/0x30 [ 1249.509717] [ 1249.509718] Modules linked in: wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 libcurve25519_generic libchacha libblake2s_generic sctp ip6_udp_tunnel udp_tunnel macvtap macvlan vhost_net vhost vhost_iotlb tap xt_nat veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables libcrc32c nfnetlink bridge stp llc overlay intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd zfs(PO) zunicode(PO) snd_hda_codec_realtek kvm_amd zzstd(O) snd_hda_codec_generic zlua(O) snd_hda_codec_hdmi ledtrig_audio kvm crct10dif_pclmul ghash_clmulni_intel zcommon(PO) snd_usb_audio aesni_intel crypto_simd znvpair(PO) cryptd snd_usbmidi_lib zavl(PO) snd_hda_codec wmi_bmof snd_rawmidi rapl k10temp efi_pstore nls_iso8859_1 snd_hda_core snd_seq_device snd_hwdep icp(PO) mc snd_pcm spl(O) [ 1249.509765] input_leds snd_timer snd joydev soundcore ccp mac_hid sch_fq_codel nct6775 hwmon_vid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid mpt3sas hid nvme uas raid_class usb_storage gpio_amdpt r8169 crc32_pclmul xhci_pci scsi_transport_sas ahci i2c_piix4 realtek e1000e nvme_core libahci xhci_pci_renesas wmi gpio_generic [last unloaded: snd_intel_sdw_acpi] [ 1249.509806] CR2: 002a [ 1249.509808] ---[ end trace 09588539e96f5ea2 ]--- [ 1250.063053] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1250.063198] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1250.063206] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1250.063211] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1250.063215] RDX: RSI: c1494df0 RDI: 0002 [ 1250.063218] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1250.063222] R10:
[Kernel-packages] [Bug 1954746] Re: ASIX AX88179 compatible USB adapter not working
I had similar problems with this too. The .ko that is delivered with 21.10 gives me the same output as above. I downloaded the firmware from ASIX and tried to compile it. That didn't work because 'usbnet_get_stats64' (line 1030) no longer exist in kernel 5.11 and up. I had to change it out for 'dev_get_tstats64' as this replaced a whole lot of statements. After this change it compiled perfectly and the USB3 adapter works just fine without error. I am running it right now and i got 0 drops in the last 4 hours. If needed i can add a .gz with my working files and compiled stuff. -- 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/1954746 Title: ASIX AX88179 compatible USB adapter not working Status in linux package in Ubuntu: Confirmed Bug description: Upon inserting the USB device errors can be found in dmesg. (see below) The current result: USB adapter is no longer working The expected result: USB adapter should work properly Please also note that this is my first bug report here. [ 5667.499655] ax88179_178a 2-1.3:2.0 eth0: unregister 'ax88179_178a' usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet [ 5667.541257] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.541264] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0001: -19 [ 5667.541268] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.541445] ax88179_178a 2-1.3:2.1 eth1: unregister 'ax88179_178a' usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet [ 5667.585338] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.585345] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write reg index 0x0001: -19 [ 5667.585350] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write reg index 0x0002: -19 [ 5668.066721] usb 2-1.3: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd [ 5668.237190] usb 2-1.3: New USB device found, idVendor=0b95, idProduct=1790, bcdDevice= 2.00 [ 5668.237196] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 5668.237199] usb 2-1.3: Product: AX88179A [ 5668.237203] usb 2-1.3: Manufacturer: ASIX [ 5668.237205] usb 2-1.3: SerialNumber: 000CFBDD [ 5668.915280] ax88179_178a 2-1.3:1.0 (unnamed net_device) (uninitialized): Failed to read reg index 0x0040: -32 [ 5669.227298] ax88179_178a 2-1.3:1.0 eth0: register 'ax88179_178a' at usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, f8:e4:3b:0c:fb:dd [ 5669.285419] ax88179_178a 2-1.3:1.0 enxf8e43b0cfbdd: renamed from eth0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arno 1964 F pulseaudio /dev/snd/controlC1: arno 1964 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 08:14:34 2021 HibernationDevice: RESUME=UUID=67bde916-af41-4b15-bcb4-599116d67df7 InstallationDate: Installed on 2018-05-18 (1306 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-21 (387 days ago) dmi.bios.date: 05/25/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.1:bd05/25/2021:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954746/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
Will new media be available w/ this fix in place? I ask because running "dkms status" or any dkms command presently triggers this bug for me, and the only way forward I can see to being able to fix that system is new media w/ a patched kernel. -- 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/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: Fix Committed Status in zfs-linux source package in Impish: Fix Committed Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+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 1912916] [NEW] package libnvidia-compute-418-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in
Public bug reported: sudo dpkg --configure -a Setting up libaccinj64-10.1:amd64 (10.1.243-3) ... dpkg: dependency problems prevent configuration of libcuinj64-10.1:amd64: libcuinj64-10.1:amd64 depends on libcuda1 (>= 418.39) | libnvidia-tesla-cuda1 (>= 418.39) | libcuda.so.1 (>= 418.39) | libcuda-10.1-1; however: Package libcuda1 is not installed. Package libnvidia-compute-460:amd64 which provides libcuda1 is not installed. Package libnvidia-compute-455:amd64 which provides libcuda1 is not installed. Package libnvidia-tesla-cuda1 is not installed. Package libcuda.so.1 is not installed. Package libcuda-10.1-1 is not installed. Package libnvidia-compute-460:amd64 which provides libcuda-10.1-1 is not installed. Package libnvidia-compute-455:amd64 which provides libcuda-10.1-1 is not installed. dpkg: error processing package libcuinj64-10.1:amd64 (--configure): dependency problems - leaving unconfigured Setting up libthrust-dev (1.9.5-1) ... dpkg: dependency problems prevent configuration of libnvidia-ml-dev: libnvidia-ml-dev depends on libnvidia-ml1 (>= 418.39) | libnvidia-tesla-440-ml1 (>= 418.39) | libnvidia-tesla-418-ml1 (>= 418.39) | libnvidia-ml.so.1 (>= 418.39); however: Package libnvidia-ml1 is not installed. Package libnvidia-compute-460:amd64 which provides libnvidia-ml1 is not installed. Package libnvidia-compute-455:amd64 which provides libnvidia-ml1 is not installed. Package libnvidia-tesla-440-ml1 is not installed. Package libnvidia-tesla-418-ml1 is not installed. Package libnvidia-ml.so.1 is not installed. dpkg: error processing package libnvidia-ml-dev (--configure): dependency problems - leaving unconfigured Setting up libnppc10:amd64 (10.1.243-3) ... Setting up libnppial10:amd64 (10.1.243-3) ... Setting up libnvvm3:amd64 (10.1.243-3) ... Setting up libcusparse10:amd64 (10.1.243-3) ... Setting up libnvrtc10.1:amd64 (10.1.243-3) ... dpkg: dependency problems prevent configuration of nvidia-cuda-dev: nvidia-cuda-dev depends on libcuinj64-10.1 (= 10.1.243-3); however: Package libcuinj64-10.1:amd64 is not configured yet. nvidia-cuda-dev depends on libnvidia-ml-dev (= 10.1.243-3); however: Package libnvidia-ml-dev is not configured yet. dpkg: error processing package nvidia-cuda-dev (--configure): dependency problems - leaving unconfigured Setting up node-html5shiv (3.7.3+dfsg-3) ... Setting up libcupti-doc (10.1.243-3) ... Setting up libcupti10.1:amd64 (10.1.243-3) ... Setting up libnppisu10:amd64 (10.1.243-3) ... Setting up libnppicc10:amd64 (10.1.243-3) ... Setting up libncurses5:amd64 (6.2-0ubuntu2) ... Setting up libnppicom10:amd64 (10.1.243-3) ... dpkg: dependency problems prevent configuration of nvidia-profiler: nvidia-profiler depends on libcuinj64-10.1; however: Package libcuinj64-10.1:amd64 is not configured yet. dpkg: error processing package nvidia-profiler (--configure): dependency problems - leaving unconfigured Setting up libcusolver10:amd64 (10.1.243-3) ... Setting up libnvjpeg10:amd64 (10.1.243-3) ... dpkg: dependency problems prevent configuration of nvidia-cuda-toolkit: nvidia-cuda-toolkit depends on nvidia-profiler (= 10.1.243-3); however: Package nvidia-profiler is not configured yet. nvidia-cuda-toolkit depends on nvidia-cuda-dev (= 10.1.243-3); however: Package nvidia-cuda-dev is not configured yet. dpkg: error processing package nvidia-cuda-toolkit (--configure): dependency problems - leaving unconfigured Setting up libcublaslt10:amd64 (10.1.243-3) ... Setting up libcusolvermg10:amd64 (10.1.243-3) ... Setting up libnpps10:amd64 (10.1.243-3) ... Setting up nvidia-cuda-doc (10.1.243-3) ... Setting up opencl-c-headers (2.2~2019.08.06-g0d5f18c-1) ... Setting up ocl-icd-opencl-dev:amd64 (2.2.11-1ubuntu1) ... Setting up libcudart10.1:amd64 (10.1.243-3) ... Setting up libcufft10:amd64 (10.1.243-3) ... Setting up libnppim10:amd64 (10.1.243-3) ... Setting up libnppitc10:amd64 (10.1.243-3) ... Setting up libnppist10:amd64 (10.1.243-3) ... Setting up libvdpau-dev:amd64 (1.3-1ubuntu2) ... Setting up libnvtoolsext1:amd64 (10.1.243-3) ... Setting up libcurand10:amd64 (10.1.243-3) ... Setting up libnvgraph10:amd64 (10.1.243-3) ... Setting up libstdc++-8-dev:amd64 (8.4.0-3ubuntu2) ... Setting up libnppig10:amd64 (10.1.243-3) ... Setting up libnppidei10:amd64 (10.1.243-3) ... Setting up libnppif10:amd64 (10.1.243-3) ... Setting up libcufftw10:amd64 (10.1.243-3) ... Setting up nvidia-cuda-gdb (10.1.243-3) ... Setting up libcublas10:amd64 (10.1.243-3) ... Setting up libcupti-dev:amd64 (10.1.243-3) ... dpkg: dependency problems prevent configuration of nvidia-visual-profiler: nvidia-visual-profiler depends on nvidia-profiler (= 10.1.243-3); however: Package nvidia-profiler is not configured yet. dpkg: error processing package nvidia-visual-profiler (--configure): dependency problems - leaving unconfigured Setting up libnvblas10:amd64 (10.1.243-3) ... Setting up nvidia-opencl-dev:amd64 (10.1.243-3) ... Setting up g++-8 (8.4.0-3
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
I'm also on 20.04 and my network connection stopped working after an update today. I have a Broadcom BCM4360. I got things working again by following the steps shared by rafae-s (thank you!), but I expect that other 20.04 users will come across the same problem in the next couple of days. Does a fix for 20.04 also need to be released? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
If you like you can dowload the patched 5.10.3 kernel from the link i
posted in #332. Just download the two files and install them via dpkg -i
*.deb
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (#296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work. Before the
release of v5.11, you are suggested to use #189 to save your touchpad.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@wangjun (biggerchina) i can confirm that #311 is working without any
workarounds when applied on 5.10.3 with touchpad MSFT0001:00 04F3:3140
and Ubuntu 20.04, thanks!
If anyone on a Debian based system is interested: i've uploaded the
patched version as .deb-packages here
https://drive.google.com/drive/folders/1ICZmuBx3ecwxtwufhSHbYmfnv9Prw-
kc?usp=sharing
@Coiby Xu (coiby) Phan Thanh Long (phanlong2811) any chance to get #311
backported to 5.10?
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (#296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work. Before the
release of v5.11, you are suggested to use #189 to save your touchpad.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Had access to another Ideapad with touchpad MSFT0001:00 04F3:3140
installed. Kernel 5.10.2-051002-generic #202012210832 did not work out
of the box but in combination with #322 it worked so i can confirm, too.
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (#296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work. Before the
release of v5.11, you are suggested to use #189 to save your touchpad.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
root=UUID=d88
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Piotr Tomaszewski (nfm886) according to #109 it seems like you have the "Elan" touchpad (mine is the "Synaptic" one) so it might behave a little different? -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.ve
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Piotr Tomaszewski (nfm886) can confirm my touchpad is the MSFT0001:00 06CB:7F28. I booted kernel 5.10.1 into recovery and then resumed regular boot and my touchpad works. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Could you try to boot in recovery mode and then resume the normal boot process? I think i have the MSFT0001:00 06CB:7F28 touchpad installed but i'll check these days. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Piotr Tomaszewski (nfm886) i just installed headers (all), image (generic) and modules (generic) from https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.10.1/amd64/ via 'dpkg -i *.deb', rebooted with new kernel 5.10.1 and everything worked. So no special config or parameter tweaking was necessary for me. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion51
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I'm on Ubuntu 20.04 with kernel 5.10.1 (https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.10.1/) and the touchpad is working on my Lenovo Legion 5. Thanks for that guys :-) -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
[Kernel-packages] [Bug 1903473] Re: Bluetooth does not work
For me it's a dongle (https://www.amazon.de/Mpow-Bluetooth-Empf%C3 %A4nger-Lautsprecher- kompatibel/dp/B087JRFGV7?pd_rd_w=YmEc6&pf_rd_p=8d2a1a06-f0ba-4603-bd06-75edf607bd62&pf_rd_r=7PQ125F33S6FJFDZX9SK&pd_rd_r =4484adca-29c6-4c15-b00d- b94cc61893bb&pd_rd_wg=rSu7g&pd_rd_i=B087JRFGV7&ref_=pd_bap_m_rp_1_sc) and it's always plugged in pre-boot. Also removing and plugging it in again doesn't help. -- 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/1903473 Title: Bluetooth does not work Status in linux package in Ubuntu: Incomplete Bug description: [625347.017671] usb 1-1.4: Product: Bluetooth Radio [625347.039793] Bluetooth: Core ver 2.22 [625347.039819] Bluetooth: HCI device and connection manager initialized [625347.039822] Bluetooth: HCI socket layer initialized [625347.039824] Bluetooth: L2CAP socket layer initialized [625347.039829] Bluetooth: SCO socket layer initialized [625347.047141] Bluetooth: hci0: rtl: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [625347.047142] Bluetooth: hci0: rtl: loading rtl_bt/rtl8761a_config.bin [625347.047360] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761a_config.bin failed with error -2 [625347.047362] Bluetooth: hci0: rtl: loading rtl_bt/rtl8761a_fw.bin [625347.049134] Bluetooth: hci0: rom_version status=0 version=1 [625347.049140] Bluetooth: hci0: cfg_sz 0, total size 20204 [625347.147059] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [625347.147060] Bluetooth: BNEP filters: protocol multicast [625347.147062] Bluetooth: BNEP socket layer initialized [625349.156276] Bluetooth: hci0: command 0xfc20 tx timeout [625357.380082] Bluetooth: hci0: download fw command failed (-110) [625562.330711] Bluetooth: RFCOMM TTY layer initialized [625562.330717] Bluetooth: RFCOMM socket layer initialized [625562.330722] Bluetooth: RFCOMM ver 1.11 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-122-generic 4.15.0-122.124 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel 2276 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 18:56:36 2020 InstallationDate: Installed on 2018-12-08 (702 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Z220 SFF Workstation ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=7af66fb9-8488-4a45-a134-214f705e35d5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-122-generic N/A linux-backports-modules-4.15.0-122-generic N/A linux-firmware 1.173.19 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K51 v01.80 dmi.board.name: 1791 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK51v01.80:bd10/21/2014:svnHewlett-Packard:pnHPZ220SFFWorkstation:pvr:rvnHewlett-Packard:rn1791:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z220 SFF Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903473/+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 1870451] Re: I accepted SW update and now doesnt exit sleep
Additional note The main screen with a TIME clock on it appears but it dosent respond to any key presses or the mouse so dont get logon prompt etc -- 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/1870451 Title: I accepted SW update and now doesnt exit sleep Status in linux package in Ubuntu: Confirmed Bug description: I very recently accepted a SW update from Ubuntu after that when my laptop goes to sleep i cant wake it , i have to power cycle.. This was working before the update. HP ELiteBook 8440p Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-91-generic 4.15.0-91.92 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robin 1736 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:01:25 2020 InstallationDate: Installed on 2018-10-11 (539 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=ac0d7bbe-3453-4b2e-ad03-06d82cda4739 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-91-generic N/A linux-backports-modules-4.15.0-91-generic N/A linux-firmware 1.173.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.11 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.31 dmi.chassis.asset.tag: AG021536 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870451/+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 1870451] [NEW] I accepted SW update and now doesnt exit sleep
Public bug reported: I very recently accepted a SW update from Ubuntu after that when my laptop goes to sleep i cant wake it , i have to power cycle.. This was working before the update. HP ELiteBook 8440p Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-91-generic 4.15.0-91.92 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robin 1736 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:01:25 2020 InstallationDate: Installed on 2018-10-11 (539 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=ac0d7bbe-3453-4b2e-ad03-06d82cda4739 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-91-generic N/A linux-backports-modules-4.15.0-91-generic N/A linux-firmware 1.173.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.11 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.31 dmi.chassis.asset.tag: AG021536 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard ** 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/1870451 Title: I accepted SW update and now doesnt exit sleep Status in linux package in Ubuntu: New Bug description: I very recently accepted a SW update from Ubuntu after that when my laptop goes to sleep i cant wake it , i have to power cycle.. This was working before the update. HP ELiteBook 8440p Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-91-generic 4.15.0-91.92 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robin 1736 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:01:25 2020 InstallationDate: Installed on 2018-10-11 (539 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=ac0d7bbe-3453-4b2e-ad03-06d82cda4739 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-91-generic N/A linux-backports-modules-4.15.0-91-generic N/A linux-firmware 1.173.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.11 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.31 dmi.chassis.asset.tag: AG021536 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://
[Kernel-packages] [Bug 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty, but not 5.0.1)
I installed your kernel and commented out the previous manual configuration. All is working fine and the speakers are working after suspend, too. So the bug can't be reproduced. Thanks! -- 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/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty, but not 5.0.1) Status in linux package in Ubuntu: Incomplete Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829621/+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 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty, but not 5.0.1)
Thanks for your comments @Hui Wang: The additional line worked. Following your steps the bug could no longer be reproduced with kernel 5.1.5-050105. Thanks a lot. Would it be suitable to apply these changes as default or to propose them commented out in the config file? @Kai-Heng Feng: Your kernel worked, too. I tested it with the additional line and without: The bug could not be reproduced in both cases. -- 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/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty, but not 5.0.1) Status in linux package in Ubuntu: Incomplete Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829621/+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 132002] Re: libportaudio packaging very confusing
As suggested in #3 above, this solution may work: The clean solution to this issue is to install libjack-jackd2-dev *before* installing portaudio19-dev. I have a note on this, available on request. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to portaudio19 in Ubuntu. https://bugs.launchpad.net/bugs/132002 Title: libportaudio packaging very confusing Status in portaudio19 package in Ubuntu: Opinion Bug description: Installing portaudio 19 is very confusing. I am trying to compile an application which uses it, as well as the CPP bindings which are contained in libportaudiocpp0. 1) Previously, PortAudio 18 dev files were installed using the package libportaudio-dev. So far so good. 2) So libportaudio0 goes with libportaudio-dev and libportaudio-doc, for V18. 3) To install V19 and the cpp bindings, first I tried installing libportaudiocpp0. 4) Apparently libportaudiocpp0 is not intended for libportaudio0, but for portaudio19-dev. 5) portaudio19-dev is the development files for libportaudio2. 2? Why couldn't this be 19? 6) The dev files for libportaudiocpp0 are contained in portaudio19-dev. I spent some time looking for a package called libportaudiocpp0-dev, but was very confused for a while. So anyways, it finally become apparent that all I had to do was install portaudio19-dev and libportaudiocpp0. I just wanted to state my general confusion here at the package naming scheme... At the very least, why not put the cpp binding dev files in libportaudiocpp0-dev? And if I install libportaudiocpp0, it should detect the dependancy on libportaudio2, instead of allowing me to compile programs with an incompatible version of the library. It is very non-obvious which package to install for V18 or V19. I had to issue several "apt-cache show" commands before figuring it out. Lastly, V18 for some reason is mutually exclusive with V19. This is a bad thing, because some older applications may require V18. There is a perfectly good way to deal with this problem, by using version numbers in the file names. (For example, I currently have both libglib-1.2 and libglib-2.0 installed at the same time.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portaudio19/+bug/132002/+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 1726299]
@whitequark I was struggling to get stuff to work with the Apple Thunderbolt 3 to 2 adapter, but when I replaced it with the Startech Thunderbolt 3 to 2 I got it working. Read about other's recommending it online 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/1726299 Title: Apple Thunderbolt 2 to FireWire adapter not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt 2 adapter. Ubuntu seems not to recognize the Firewire adapter. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty uname -r 4.10.0-19-generic sudo lshw -short H/W-Pfad Gerät Klasse Beschreibung === system Z170N-Gaming 5 (Default string) /0 busZ170N-Gaming 5 /0/0memory 64KiB BIOS /0/3d memory 16GiB Systemspeicher /0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/1 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/3 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/43 memory 128KiB L1 Cache /0/44 memory 512KiB L2 Cache /0/45 memory 3MiB L3 Cache /0/46 processor Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz /0/100 bridge Skylake Host Bridge/DRAM Registers /0/100/1bridge Skylake PCIe Controller (x16) /0/100/1/0 displayOland GL [FirePro W2100] /0/100/1/0.1multimedia Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] /0/100/14 busSunrise Point-H USB 3.0 xHCI Controller /0/100/14/0 usb1 busxHCI Host Controller /0/100/14/0/6 input USB Gaming Keyboard /0/100/14/0/d communication Bluetooth-Schnittstelle /0/100/14/1 usb2 busxHCI Host Controller /0/100/14/1/5scsi6 storageStorage Media /0/100/14/1/5/0.0.0 /dev/sdb disk 15GB Storage Media /0/100/14/1/5/0.0.0/0/dev/sdb disk 15GB /0/100/14/1/5/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT Laufwerk /0/100/16 communication Sunrise Point-H CSME HECI #1 /0/100/17 storageSunrise Point-H SATA controller [AHCI mode] /0/100/1b bridge Sunrise Point-H PCI Root Port #17 /0/100/1b.2 bridge Sunrise Point-H PCI Root Port #19 /0/100/1b.3 bridge Sunrise Point-H PCI Root Port #20 /0/100/1c bridge Sunrise Point-H PCI Express Root Port #1 /0/100/1c/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/1 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2/0 busDSL6540 USB 3.1 Controller [Alpine Ridge] /0/100/1c/0/2/0/0usb3 busxHCI Host Controller /0/100/1c/0/2/0/0/1 genericThunderbolt 3 (USB-C) to Thunderbolt 2 Adapter /0/100/1c/0/2/0/0/2 input USB Optical Mouse /0/100/1c/0/2/0/1usb4 busxHCI Host Controller /0/100/1c/0/4 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c.2 bridge Sunrise Point-H PCI Express Root Port #3 /0/100/1c.3 bridge Sunrise Point-H PCI Express Root Port #4 /0/100/1c.4 bridge Sunrise Point-H PCI Express Root Port #5 /0/100/1c.4/0enp13s0networkKiller E2400 Gigabit Ethernet Controller /0/100/1c.5 bridge Sunris
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Commenting out blacklist i2c_i801 did end with mouse not working at all after wakeup but adding psmouse.synaptics_intertouch=0 to grub did solve the issue. I got an L440. Ubuntu 18.04 4.19rc1 -- 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/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+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 1752772] Re: r8169 ethernet card don't work after returning from suspension
Peter Smith - I had the same experience of trying the 4.15.0-33 and it not working for me. ** Try 4.15.0.23 if you would like to be on the 4.15 kernel ** Background: In my case I am running Mint, but same Ubuntu kernels. It is a desktop PC which is not often suspended so I noticed the problem only a couple of days ago, when already on 4.15.0-30, so tried the 4.15.0-33 which Mint's update manager was offering.. no improvement. The modprobe trick worked and I have a Realtec NIC. I had seen references to 4.13.0-31 working and also 4.15.0-20, both of which worked for me. I worked my way up through the following:- 4.15.0-20 resumes 4.15.0-22 resumes 4.15.0-23 resumes 4.15.0-24 does not resume 4.15.0-30 does not resume 4.15.0-33 does not resume The modprobe treatment worked for the recent -30 and -33, but curiously not on -24. That's probably a symptom of progress. I thought I experienced a surprising result of going to -24 then back to -23 and the problem reappearing in -23. After a power-off restart all was well again. I had a theory that maybe since all I was doing were OS "restarts" without the PC shutting down the hardware might be holding some state. I've tried recreating that problem (because it seemed such a dodgy assertion) - but without luck. On the one hand it might be a valid thought that it is very easy to just do restarts between kernels and actually still be holding some unfortunate state in the hardware - OR my bad in accidentally booting the wrong kernel (I've mostly done a uname -a check straight after the boot) There do seem to have been some inconsistencies in people's experiences, so I wonder if hardware state can be a factor, after all, we are in the area of suspended motherboard h/w People who know more about Linux initial initialisation of hardware may say I'm talking bo***cks! Anyway, I'm happy with suspend/resume with 4.15.0-23-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/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mi
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I have also coruppted bios on Lenovo y50-70. I cant do any chnages. Do you think that will be a software solution ? I hope i wont to change MB. -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (20/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Dell XPS 13 9350 I7. Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
TL;DR: pass '-vga none' with -nographic, or redirect the screen somewhere! I ended up digging into this after it was mentioned by smoser. The bug is invalid because of a bad assumption in the QEMU inputs. smoser's workaround of usb=off removes USB as a workaround. The kernel, OpenFirmware, and QEMU are behaving correctly, but the original command-line hides the screen output. If you have both a supported* keyboard AND screen, then OpenFirmware/SLOF sets OF stdout to be the screen. This causes the OF output of 'No console specified using screen & keyboard' If you are missing either a keyboard OR screen, then OF sets stdout to be hvterm (serial). This causes the OF output of 'No console specified using hvterm' https://git.qemu.org/?p=SLOF.git;a=blob;f=board- qemu/slof/OF.fs;h=4e04b840d5e6ff6c39191939e1a4f70f3d169d5d;hb=HEAD#l215 Which devices are available depends on the QEMU commandline... Base QEMU defaults to '-vga std'. QEMU '-machine pseries' defaults to enabling USB. Re supported keyboards: The OpenFirmware/SLOF only seems to support USB keyboards at this time (virtio keyboard not supported). -- 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/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le Status in QEMU: Invalid Status in linux package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Bug description: qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image as part of the certification process. This on an IBM ppc64le in PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no error output. ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio WARNING: Image format was not specified for 'seed.iso' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. SLOF ** QEMU Starting Build Date = Jan 29 2016 18:58:37 FW Version = buildd@ release 20151103 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/vty@7100 Populating /vdevice/nvram@7101 Populating /vdevice/l-lan@7102 Populating /vdevice/v-scsi@7103 SCSI: Looking for devices 8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+" Populating /pci@8002000 00 1800 (D) : 1af4 1001virtio [ block ] 00 1000 (D) : 1af4 1001virtio [ block ] 00 0800 (D) : 106b 003fserial bus [ usb-ohci ] 00 (D) : 1234 qemu vga No NVRAM common partition, re-initializing... Installing QEMU fb Scanning USB OHCI: initializing USB Keyboard USB mouse No console specified using screen & keyboard Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... E3404: Not a bootable device! Trying to load: from: /pci@8002000/scsi@2 ... Successfully loaded Linux ppc64le #31-Ubuntu SMP F ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic ppc64le ApportVersion: 2.20-0ubuntu3 Architecture: ppc64el Date: Wed Mar 30 14:10:01 2016 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 1172 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 13467 1 0.0 qemu-nbd -c /dev/nbd0 xenial-server-cloudimg-ppc64el-disk1.img qemu-system-ppc Sl+ 1000 1000 18973 18896 101 qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro ProcLoadAvg: 1.08 0.94 0.58 2/616 19571 ProcLocks: 1: POSIX ADVISORY WRITE 886 00:13:381 0 EOF 2: POSIX
[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
This is ubuntu desktop. I found that if I did: sudo hciconfig hci0 lp HOLD,SNIFF while everything was disconnected, then the audio started working properly. Now I'm back here because after a reboot it wouldn't connect at all, so I guess I need to fix the pairing or something. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1620636] Re: Fails to pair with Bose QC35 headphones
Following the instructions here: http://askubuntu.com/questions/833322 /pair-bose-quietcomfort-35-with-ubuntu-16-04-over-bluetooth I managed to make it pair and appear as an audio device. While playback technically worked, it wasn't useable as it came across as though there wasn't enough bandwidth - the audio was choppy and got delayed. It seemed that pulse gave up sending to it after a point, and nothing would play back then. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1637346] Re: HP printer no longer working after upgrade.
'kernel-fixed-upstream' After I tried reinstalling the kernel and performing a restart, everything worked perfectly. Thanks for the help. -- 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/1637346 Title: HP printer no longer working after upgrade. Status in linux package in Ubuntu: Incomplete Bug description: My HP-Deskjet-F2100-series printer stopped working after upgrade from 16.04 to 16.10. It worked fine in 16.04. I've tried several different printing jobs, and it's the same for every one, it prints half of a page and then stops. I have a laptop with 16.04 on it, and when I tried the printer there it worked fine. Thank you for your time. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-26-generic 4.8.0-26.28 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robin 2394 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 27 18:46:42 2016 HibernationDevice: RESUME=UUID=ad90ea5b-2c52-473c-8431-7a785290e6d4 InstallationDate: Installed on 2016-10-25 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp0s10 no wireless extensions. MachineType: Acer Aspire X3400G ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=6166bf8f-97c2-4915-8e8d-3b3e57c10816 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-26-generic N/A linux-backports-modules-4.8.0-26-generic N/A linux-firmware1.161 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-27 (0 days ago) dmi.bios.date: 06/01/2010 dmi.bios.vendor: AMI dmi.bios.version: P01-B2 dmi.board.name: Aspire X3400G dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAMI:bvrP01-B2:bd06/01/2010:svnAcer:pnAspireX3400G:pvr:rvnAcer:rnAspireX3400G:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire X3400G dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637346/+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 1637346] Re: HP printer no longer working after upgrade.
'kernel-bug-exists-upstream' -- 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/1637346 Title: HP printer no longer working after upgrade. Status in linux package in Ubuntu: Incomplete Bug description: My HP-Deskjet-F2100-series printer stopped working after upgrade from 16.04 to 16.10. It worked fine in 16.04. I've tried several different printing jobs, and it's the same for every one, it prints half of a page and then stops. I have a laptop with 16.04 on it, and when I tried the printer there it worked fine. Thank you for your time. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-26-generic 4.8.0-26.28 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robin 2394 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 27 18:46:42 2016 HibernationDevice: RESUME=UUID=ad90ea5b-2c52-473c-8431-7a785290e6d4 InstallationDate: Installed on 2016-10-25 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp0s10 no wireless extensions. MachineType: Acer Aspire X3400G ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=6166bf8f-97c2-4915-8e8d-3b3e57c10816 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-26-generic N/A linux-backports-modules-4.8.0-26-generic N/A linux-firmware1.161 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-27 (0 days ago) dmi.bios.date: 06/01/2010 dmi.bios.vendor: AMI dmi.bios.version: P01-B2 dmi.board.name: Aspire X3400G dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAMI:bvrP01-B2:bd06/01/2010:svnAcer:pnAspireX3400G:pvr:rvnAcer:rnAspireX3400G:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire X3400G dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637346/+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 1637346] [NEW] HP printer no longer working after upgrade.
Public bug reported: My HP-Deskjet-F2100-series printer stopped working after upgrade from 16.04 to 16.10. It worked fine in 16.04. I've tried several different printing jobs, and it's the same for every one, it prints half of a page and then stops. I have a laptop with 16.04 on it, and when I tried the printer there it worked fine. Thank you for your time. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-26-generic 4.8.0-26.28 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robin 2394 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 27 18:46:42 2016 HibernationDevice: RESUME=UUID=ad90ea5b-2c52-473c-8431-7a785290e6d4 InstallationDate: Installed on 2016-10-25 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp0s10 no wireless extensions. MachineType: Acer Aspire X3400G ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=6166bf8f-97c2-4915-8e8d-3b3e57c10816 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-26-generic N/A linux-backports-modules-4.8.0-26-generic N/A linux-firmware1.161 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-27 (0 days ago) dmi.bios.date: 06/01/2010 dmi.bios.vendor: AMI dmi.bios.version: P01-B2 dmi.board.name: Aspire X3400G dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAMI:bvrP01-B2:bd06/01/2010:svnAcer:pnAspireX3400G:pvr:rvnAcer:rnAspireX3400G:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire X3400G dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1637346 Title: HP printer no longer working after upgrade. Status in linux package in Ubuntu: New Bug description: My HP-Deskjet-F2100-series printer stopped working after upgrade from 16.04 to 16.10. It worked fine in 16.04. I've tried several different printing jobs, and it's the same for every one, it prints half of a page and then stops. I have a laptop with 16.04 on it, and when I tried the printer there it worked fine. Thank you for your time. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-26-generic 4.8.0-26.28 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robin 2394 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 27 18:46:42 2016 HibernationDevice: RESUME=UUID=ad90ea5b-2c52-473c-8431-7a785290e6d4 InstallationDate: Installed on 2016-10-25 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp0s10 no wireless extensions. MachineType: Acer Aspire X3400G ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=6166bf8f-97c2-4915-8e8d-3b3e57c10816 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-26-generic N/A linux-backports-modules-4.8.0-26-generic N/A linux-firmware1.161 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-27 (0 days ago) dmi.bios.date: 06/01/2010 dmi.bios.vendor: AMI dmi.bios.version: P01-B2 dmi.board.name: Aspire X3400G dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAMI:bvrP01-B2:bd06/01/2010:svnAcer:pnAspireX3400G:pvr:rvnAcer:rnAspireX3400G:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire X3400G dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637346/+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 1518457] Re: kswapd0 100% CPU usage
To add - these servers are all built on the official Ubuntu Amazon EC2 AMIs of the 'ebs-ssd' variety. -- 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/1518457 Title: kswapd0 100% CPU usage Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' 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: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1518457/+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 1518457] Re: kswapd0 100% CPU usage
We have been seeing this issue intermittently on a set of servers that were running Ubuntu 15.10 and then 16.04. After overriding that udev vm hotadd rule as suggested above a couple weeks ago, the issue has yet to return (not a conclusive result, but so far so good). -- 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/1518457 Title: kswapd0 100% CPU usage Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' 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: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1518457/+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 1546603] Re: Bluetooth mouse connects but doesn't work
I took a different approach to getting my mouse working: I installed blueman and used that to configure it. I guess it enables experimental features itself. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546603 Title: Bluetooth mouse connects but doesn't work Status in bluez package in Ubuntu: Confirmed Bug description: I have a bluetooth mouse that I can get to connect via the gnome bluetooth settings panel, but even after it's connected it doesn't move the pointer or register any clicks. the following shows up in the journal : $ $ journalctl -b 0 |grep bluetooth Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36 Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 initialized Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service Changed" characteristic Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be registered Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error (5) Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed. Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted (1) Feb 17 07:18:22 spiny NetworkManager[1062]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSource Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSource Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher language-selector (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 'str != NULL' failed Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x000c for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x001b for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x003f for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_a
[Kernel-packages] [Bug 1328595] Re: lvcreate -s hangs when overlayfs is in use
I can confirm that this is still an issue in Ubuntu 14.04.4. I ran into this problem trying to backup a server hosting lxc containers, some of them using overlayfs as the root fs. When the containers are running (and therefore overlayfs is mounted) lvcreate -s hangs forever. The debug output is: root@host:~# lvcreate -n foobar -L 5G -s -d -v /dev/vg0/var Setting logging type to disk Setting chunksize to 8 sectors. Finding volume group "vg0" Archiving volume group "vg0" metadata (seqno 5091). Creating logical volume foobar Creating volume group backup "/etc/lvm/backup/vg0" (seqno 5092). Found volume group "vg0" activation/volume_list configuration setting not defined: Checking only host tags for vg0/foobar Creating vg0-foobar Loading vg0-foobar table (252:5) Resuming vg0-foobar (252:5) Clearing start of logical volume "foobar" Creating logical volume snapshot0 Found volume group "vg0" Found volume group "vg0" Executing: /sbin/modprobe dm-snapshot Creating vg0-var-real Loading vg0-var-real table (252:6) Loading vg0-var table (252:3) Creating vg0-foobar-cow Loading vg0-foobar-cow table (252:7) Resuming vg0-foobar-cow (252:7) Loading vg0-foobar table (252:5) Suspending vg0-var (252:3) with filesystem sync with device flush When the containers are stopped (and therefore overlayfs is no longer mounted), the snapshot is created without issues. -- 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/1328595 Title: lvcreate -s hangs when overlayfs is in use Status in linux package in Ubuntu: Confirmed Bug description: I am using xbuntu 14.04 LTS in combination with KVM, lxc, logical volumes and overlayfs. After I started using overlayfs i realized that my backup based on LVM snapshots made the system "go mad". As described in the manual I tried the kernel from 13.10 (3.11.0-xx) with the same result. A test against main line does not help, since it does not include the overlayfs support. I tested the behaviour on a server as well as in a VirtualBox environment with the same result: lvcreate -s -n backup -L512M /dev/VG/NAME hangs and does not come back. This issue is easy reproducable: sudo mkdir /mnt/test /mnt/delta sudo mount -t overlayfs -o lowerdir=/usr,upperdir=/mnt/delta overlayfs /mnt/test sudo lvcreate -s -n backup -L512M /dev/xubuntu-vg/root -> Hang df@feretti-virt:~$ uname -r 3.13.0-29-generic df@feretti-virt:~$ cat /proc/version_signature Ubuntu 3.13.0-29.53-generic 3.13.11.2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jun 10 18:02:13 2014 HibernationDevice: RESUME=UUID=6e68761a-6768-4e19-9c4e-f188538d6068 InstallationDate: Installed on 2014-02-18 (112 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-22 (49 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://
[Kernel-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode
Did something change with this? Because I can't reproduce this any more on my bq Aquaris E4.5 phone with OTA-11. With OTA-10.1 this happened every time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1488170 Title: Bluetooth initiated after quitting airplane mode Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in urfkill package in Ubuntu: Confirmed Bug description: This happens despite bluetooth not being enabled when entering airplane mode. On Aquaris E5 OTA-5. Boot with bluetooth disabled Turn on flight mode turn off flight mode Bluetooth gets enabled See bug #1421249 for related symptoms To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+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 1536249] Re: XPS 13 9350: reboot fails with "Transaction is destructive" after resume from suspend
It says "not installed" 'cos I'm using a kernel from here: http://askubuntu.com/questions/709794/dell-xps-13-9350-compatibility - to get my wifi to work. Does this make this bug invalid? Maybe I should file a bug about wireless not working with the ubuntu kernel? ** Description changed: With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical "reboot" and "shut down" buttons don't do anything, and from the CLI I get: $ reboot Failed to execute operation: Transaction is destructive. - I imagine it's associated with closing the lid to suspend because when I - first start the system it reboots fine. It resumes fine when I open the - lid in the sense that I can enter my password and continue to use - Ubuntu, but it would make sense if there's something hanging about in - the background. I don't know how to check this. + This only happens after resuming from suspend after the lid was closed. + Also, the touch screen no longer works after resuming. (I initially found this "wontfix" bug which describes the same problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253) - --- + --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-18 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: linux (not installed) Tags: wily Uname: Linux 4.3.0-wifitest-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- 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/1536249 Title: XPS 13 9350: reboot fails with "Transaction is destructive" after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical "reboot" and "shut down" buttons don't do anything, and from the CLI I get: $ reboot Failed to execute operation: Transaction is destructive. This only happens after resuming from suspend after the lid was closed. Also, the touch screen no longer works after resuming. (I initially found this "wontfix" bug which describes the same problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253) --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-18 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: linux (not installed) Tags: wily Uname: Linux 4.3.0-wifitest-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536249/+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 1536249] Re: XPS 13 9350: reboot fails with "Transaction is destructive" after resume from suspend
apport information ** Tags added: apport-collected wily ** Description changed: With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical "reboot" and "shut down" buttons don't do anything, and from the CLI I get: $ reboot Failed to execute operation: Transaction is destructive. I imagine it's associated with closing the lid to suspend because when I first start the system it reboots fine. It resumes fine when I open the lid in the sense that I can enter my password and continue to use Ubuntu, but it would make sense if there's something hanging about in the background. I don't know how to check this. - (I initially found this "wontfix" bug which describes the same problem: - https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253) + (I initially found this "wontfix" bug which describes the same problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253) + --- + ApportVersion: 2.19.1-0ubuntu5 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.10 + EcryptfsInUse: Yes + InstallationDate: Installed on 2016-01-18 (1 days ago) + InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) + Package: linux (not installed) + Tags: wily + Uname: Linux 4.3.0-wifitest-custom x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1536249/+attachment/4553473/+files/JournalErrors.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/1536249 Title: XPS 13 9350: reboot fails with "Transaction is destructive" after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical "reboot" and "shut down" buttons don't do anything, and from the CLI I get: $ reboot Failed to execute operation: Transaction is destructive. This only happens after resuming from suspend after the lid was closed. Also, the touch screen no longer works after resuming. (I initially found this "wontfix" bug which describes the same problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253) --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-18 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: linux (not installed) Tags: wily Uname: Linux 4.3.0-wifitest-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536249/+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 1536249] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1536249/+attachment/4553474/+files/ProcEnviron.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/1536249 Title: XPS 13 9350: reboot fails with "Transaction is destructive" after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical "reboot" and "shut down" buttons don't do anything, and from the CLI I get: $ reboot Failed to execute operation: Transaction is destructive. This only happens after resuming from suspend after the lid was closed. Also, the touch screen no longer works after resuming. (I initially found this "wontfix" bug which describes the same problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253) --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-18 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: linux (not installed) Tags: wily Uname: Linux 4.3.0-wifitest-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536249/+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 1536249] [NEW] XPS 13 9350: reboot fails with "Transaction is destructive" after resume from suspend
Public bug reported: With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical "reboot" and "shut down" buttons don't do anything, and from the CLI I get: $ reboot Failed to execute operation: Transaction is destructive. I imagine it's associated with closing the lid to suspend because when I first start the system it reboots fine. It resumes fine when I open the lid in the sense that I can enter my password and continue to use Ubuntu, but it would make sense if there's something hanging about in the background. I don't know how to check this. (I initially found this "wontfix" bug which describes the same problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253) ** 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/1536249 Title: XPS 13 9350: reboot fails with "Transaction is destructive" after resume from suspend Status in linux package in Ubuntu: New Bug description: With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical "reboot" and "shut down" buttons don't do anything, and from the CLI I get: $ reboot Failed to execute operation: Transaction is destructive. I imagine it's associated with closing the lid to suspend because when I first start the system it reboots fine. It resumes fine when I open the lid in the sense that I can enter my password and continue to use Ubuntu, but it would make sense if there's something hanging about in the background. I don't know how to check this. (I initially found this "wontfix" bug which describes the same problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536249/+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 1488170] Re: Bluetooth initiated after quitting airplane mode
I can reproduce this on BQ Aquaris E4.5 - krillin - rc-proposed r277 (released today) and this bug is really annoying. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1488170 Title: Bluetooth initiated after quitting airplane mode Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in urfkill package in Ubuntu: Confirmed Bug description: This happens despite bluetooth not being enabled when entering airplane mode. On Aquaris E5 OTA-5. Boot with bluetooth disabled Turn on flight mode turn off flight mode Bluetooth gets enabled See bug #1421249 for related symptoms To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+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 1520519] Re: ASUS ROG GL552 TouchPad not detected
I got a similiar model, the ASUS ROG GL552VW, and I have exactly the same problem. The touchpad does not work when I boot Xubuntu, but my gaming mouse that I got with this laptop does seem to work. I will gladly help you with giving detailed information about this bug, but I do not know what kind of information is actually needed. -- 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/1520519 Title: ASUS ROG GL552 TouchPad not detected Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Laptop Model : ASUS ROG GL552 DH71 First Appearance : Got laptop yesterday. dual booted with ubuntu 14.04. Touchpad never detected. Manufacturer : ASUS ( as listed under windows 10 ) * xinput list * ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=10 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Power Buttonid=7[slave keyboard (3)] ↳ Logitech USB Keyboard id=8[slave keyboard (3)] ↳ Logitech USB Keyboard id=9[slave keyboard (3)] * List of devices * : Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=c05a Version=0111 N: Name="Logitech USB Optical Mouse" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C05A.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=100013 B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0 B: MSC=10 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04f2 Product=b424 Version=6969 N: Name="USB2.0 HD UVC WebCam" P: Phys=usb-:00:14.0-4/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input8 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 please find
[Kernel-packages] [Bug 1515513] [NEW] /boot/initrd.img-*.old-dkms files left behind
Public bug reported: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Affects: dkms (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug vivid ** Bug watch added: Debian Bug tracker #717584 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717584 ** Also affects: dkms (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717584 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: New Status in dkms package in Debian: Unknown Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1467867] Re: USB devices found but not working
Which upstream commit actually fixed this 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/1467867 Title: USB devices found but not working Status in linux package in Ubuntu: Triaged Bug description: USB devices don't work properly for me in Linux 3.13.0-54-generic and *-55-generic, i can see them with lsusb but the devices are not created. For instance there is no input device for the keyboard. The mother board is an Intel S1200BTS. [rikard|eclipse|0|~] lsusb Bus 002 Device 005: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 002 Device 004: ID 2304:0208 Pinnacle Systems, Inc. Studio PCTV USB2 Bus 002 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [rikard|eclipse|0|~] sudo lsinput /dev/input/event0 bustype : BUS_HOST vendor : 0x0 product : 0x3 version : 0 name: "Sleep Button" phys: "PNP0C0E/button/input0" bits ev : EV_SYN EV_KEY /dev/input/event1 bustype : BUS_HOST vendor : 0x0 product : 0x1 version : 0 name: "Power Button" phys: "LNXPWRBN/button/input0" bits ev : EV_SYN EV_KEY Devices work fine on earlier kernels: [rikard|eclipse|0|~] uname -a Linux eclipse 3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [rikard|eclipse|0|~] sudo lsinput /dev/input/event0 bustype : BUS_HOST vendor : 0x0 product : 0x3 version : 0 name: "Sleep Button" phys: "PNP0C0E/button/input0" bits ev : EV_SYN EV_KEY /dev/input/event1 bustype : BUS_HOST vendor : 0x0 product : 0x1 version : 0 name: "Power Button" phys: "LNXPWRBN/button/input0" bits ev : EV_SYN EV_KEY /dev/input/event2 bustype : BUS_USB vendor : 0x4b3 product : 0x3025 version : 272 name: "CHICONY USB NetVista Full Width " phys: "usb-:00:1d.0-1.2/input0" uniq: "" bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP /dev/input/event3 bustype : BUS_USB vendor : 0x2304 product : 0x208 version : 1 name: "em28xx IR (em2710/2820 #0)" phys: "usb-:00:1d.0-1.3/input0" bits ev : EV_SYN EV_KEY EV_MSC EV_REP ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-54-generic 3.13.0-54.91 ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20 Uname: Linux 3.13.0-54-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 jun 23 11:28 seq crw-rw 1 root audio 116, 33 jun 23 11:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Jun 23 11:29:04 2015 InstallationDate: Installed on 2012-05-03 (1145 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) MachineType: Intel Corporation SandyBridge Platform PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-54-generic root=UUID=da4fb901-3020-4610-8599-4857f891c200 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-54-generic N/A linux-backports-modules-3.13.0-54-generic N/A linux-firmware 1.127.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2015-04-05 (78 days ago) dmi.bios.date: 05/08/2014 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200BT.86B.02.00.0042.050820141549 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: Intel Corporation dmi.board.version: E98683-307 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200BT.86B.02.00.0042.050820141549:bd05/08/2014:svnIntelCorporation:pnSandyBridgePlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnTobefilledbyO.E.M.:rvrE98683-307:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.: dmi.product.nam
[Kernel-packages] [Bug 1297049] Re: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]
I'm now running 15.04, so the bug no longer applies. I've marked it as invalid. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1297049 Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia] Status in linux package in Ubuntu: Invalid Bug description: apport detected this error on a fresh boot. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.40 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rgarner2756 F pulseaudio /dev/snd/pcmC1D0c: rgarner2756 F...m pulseaudio /dev/snd/controlC2: rgarner2756 F pulseaudio /dev/snd/controlC0: rgarner2756 F pulseaudio Date: Tue Mar 25 10:20:28 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=c7ef60d1-697d-4495-bb69-10665128efd3 InstallationDate: Installed on 2014-01-27 (55 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E6420 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=e960e3c7-aa3d-43d3-9178-7719d9023e08 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/01/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 032T9K dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd01/01/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1297049/+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 1502944] [NEW] Laptop built-in keyboard is not working after kernel upgrade
Public bug reported: I cannot enter my encryption password to unlock the hard drive because the keyboard does not work. Old working kernel: 3.19.0-28-generic Non-working kernel: 3.19.0-30-generic ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robin 1800 F pulseaudio /dev/snd/controlC1: robin 1800 F pulseaudio CurrentDesktop: KDE Date: Mon Oct 5 16:37:40 2015 HibernationDevice: RESUME=UUID=805a7dda-9be7-4a44-aaed-bbd91cc56268 InstallationDate: Installed on 2015-05-05 (152 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. tun0 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216c Broadcom Corp. Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 RfKill: 0: hci0: Bluetooth 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: 11/28/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2293 dmi.board.vendor: Hewlett-Packard dmi.board.version: 78.15 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn2293:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 097312405F1620180 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1502944 Title: Laptop built-in keyboard is not working after kernel upgrade Status in linux package in Ubuntu: New Bug description: I cannot enter my encryption password to unlock the hard drive because the keyboard does not work. Old working kernel: 3.19.0-28-generic Non-working kernel: 3.19.0-30-generic ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robin 1800 F pulseaudio /dev/snd/controlC1: robin 1800 F pulseaudio CurrentDesktop: KDE Date: Mon Oct 5 16:37:40 2015 HibernationDevice: RESUME=UUID=805a7dda-9be7-4a44-aaed-bbd91cc56268 InstallationDate: Installed on 2015-05-05 (152 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. tun0 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216c Broadcom Corp. Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 RfKill: 0: hci0: Bluetooth 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: 11/28/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name:
[Kernel-packages] [Bug 1484980] [NEW] AVRCP support for Ubuntu Phone
Public bug reported: Hey! I bought a bluetooth headphone, but the volume, next and previous track buttons don't work with my Ubuntu Phone, because it doesn't support AVRCP. So please implement this feature. :) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1484980 Title: AVRCP support for Ubuntu Phone Status in bluez package in Ubuntu: New Bug description: Hey! I bought a bluetooth headphone, but the volume, next and previous track buttons don't work with my Ubuntu Phone, because it doesn't support AVRCP. So please implement this feature. :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1484980/+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 1473105] [NEW] In AMD 64 14.04 dmesg shows xHCI drop endpoint and other repeating problems
Public bug reported: dmesg | tail -n 35 |less Extract: [ 337.978401] xhci_hcd :00:10.0: xHCI xhci_drop_endpoint called with disabled ep 880414902d90 [ 337.978405] xhci_hcd :00:10.0: xHCI xhci_drop_endpoint called with disabled ep 880416e56b40 [ 337.979961] cdc_acm 6-2.3:1.1: This device cannot do calls on its own. It is not a modem. [ 337.980023] cdc_acm 6-2.3:1.1: ttyACM0: USB ACM device [ 893.965035] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use) [ 906.135939] usblp1: removed [ 906.140645] device eth0 entered promiscuous mode [ 1121.936646] usb 6-2.3: reset high-speed USB device number 6 using xhci_hcd [ 1122.040414] xhci_hcd :00:10.0: xHCI xhci_drop_endpoint called with disabled ep 880414902d48 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-43-generic 3.16.0-43.58~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13 Uname: Linux 3.16.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jul 9 16:02:37 2015 InstallationDate: Installed on 2015-07-07 (2 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1473105 Title: In AMD 64 14.04 dmesg shows xHCI drop endpoint and other repeating problems Status in linux-lts-utopic package in Ubuntu: New Bug description: dmesg | tail -n 35 |less Extract: [ 337.978401] xhci_hcd :00:10.0: xHCI xhci_drop_endpoint called with disabled ep 880414902d90 [ 337.978405] xhci_hcd :00:10.0: xHCI xhci_drop_endpoint called with disabled ep 880416e56b40 [ 337.979961] cdc_acm 6-2.3:1.1: This device cannot do calls on its own. It is not a modem. [ 337.980023] cdc_acm 6-2.3:1.1: ttyACM0: USB ACM device [ 893.965035] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use) [ 906.135939] usblp1: removed [ 906.140645] device eth0 entered promiscuous mode [ 1121.936646] usb 6-2.3: reset high-speed USB device number 6 using xhci_hcd [ 1122.040414] xhci_hcd :00:10.0: xHCI xhci_drop_endpoint called with disabled ep 880414902d48 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-43-generic 3.16.0-43.58~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13 Uname: Linux 3.16.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jul 9 16:02:37 2015 InstallationDate: Installed on 2015-07-07 (2 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1473105/+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 1382302] Re: Broadcom Corporation BCM4352 bluetooth adapter not finding any bluetooth devices
The description in #5 is not a fix, but rather a hack, which will have to be repeated for every kernel update. A true fix would involve: a) amending the btusb file b) including the fully BT capable firmware in a package If only a) is done, that would be a big improvement! Please note that 14.04 LTS will be using the 3.13.0 kernel until 2019, so this bug needs a robust fix! Thanks to redfox for getting to the bottom of it! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1382302 Title: Broadcom Corporation BCM4352 bluetooth adapter not finding any bluetooth devices Status in bluez package in Ubuntu: Fix Released Bug description: Broadcom Corporation BCM4352 wi-fi/bluetooth adapter is unable to find/detect Bluetooth devices, and Bluetooth devices can not see the Ubuntu PC, even when in pairing mode. (Here is a similar bug, but for a different Broadcom device: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311) MOTHERBOARD INFO $ sudo dmidecode -t baseboard # dmidecode 2.12 SMBIOS 2.7 present. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASRock Product Name: Z87E-ITX Version: Serial Number: E80-34027900563 Asset Tag: Features: Board is a hosting board Board is replaceable Location In Chassis: Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 UBUNTU INFO $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty $ uname -a Linux Computer 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux WI-FI DEVICE INFO $ lspci | grep Broadcom 03:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03) Note, the BCM4352 802.11ac device is a combination Wi-Fi + Bluetooth adapter. BLUETOOTH DEVICE INFO $ lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 13d3:3404 IMC Networks Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 1b1c:0c04 Corsair Bus 003 Device 003: ID 046d:0826 Logitech, Inc. Bus 003 Device 002: ID 09da:024f A4 Tech Co., Ltd RF Receiver and G6-20D Wireless Optical Mouse Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The system log does not show any errors when the btusb module is loaded... kernel: [36245.996355] usbcore: registered new interface driver btusb bluetoothd[833]: Unknown command complete for opcode 19 bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPAG bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPHS bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/A2DPSource bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/A2DPSink bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPAG bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPHS bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSource bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSink bluetoothd[833]: Adapter /org/bluez/833/hci0 has been enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1382302/+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 1309578] Re: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k
Mint 17.1 does not solve the problem. It is extremely disapointing that this issue has not been solved. Why does 16 work and 17 does not? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309578 Title: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k Status in linux package in Ubuntu: Incomplete Bug description: I have a custom built AMD System with the following hardware currently running on Linux Mint 16 : AMD A8 6600k with Integrated graphics | MSI-FM2-A55M-E33 Motherboard | Kingston Hyperx Blu 4GB RAM | Corsair VS450 PSU Today when I tried to install 14.04 amd64 iso using a bootable USB, then the system rebooted. Any further attempts in installing it resulted in the same bug. As soon as I open the "Ubuntu installer" application and click "Continue" button then the system restarts after 2-3 seconds. I asked the same on AskUbuntu and some more guys reported the same problem with AMD APU, so I believe it to be a genuine bug and not just with me. The BIOS version is the latest one downloaded from MSI official website which is version 11.5. Also an Interesting thing is that this bug is common with the latest iso of Arch Linux too, but when booting older distros like Linux Mint 16 from USB, then everything works like it should, so it might have something to do with the newer 3.13 Kernel version. I am not an expert, but I can surely tell that only the newer distros are affected by this bug as reported by some other guys at AskUbuntu and the fact that Arch which is running the newer Kernel is having the same bug, so it probably has something to do with the newer Kernel, but I could be wrong. This bug is not letting me install Ubuntu 14.04 on my hardware and it is affecting a few more users too. Here is the AskUbuntu thread : http://askubuntu.com/questions/449391/unable-to-install-ubuntu-14-04 -pc-restarts-after-i-click-continue-button-in I hope this gets fixed soon or with the 14.04.1 upcoming July release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309578/+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 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver
Ravi, intriguingly, those systems are certified for Ubuntu 12.04 LTS, not for Ubuntu 14.04 LTS. My recollection is that the driver from the manufacturer was specifically directed at 12.04 (or it may have been a corresponding kernel version). The kernel has changed sufficiently from 12.04 to 14.04 for the driver no longer to be effective, as one understands it. Had the manufacturer updated the driver, or someone else taken over maintenance (with or without manufacturer's sponsorship), then this frustrating problem would not have arisen. Cheers, Robin PS: It wasn't really necessary to quote all the certified machines (36 in total) in glorious detail! On 23/12/14 15:29, Ravi Karki wrote: > There are many Ubuntu certified laptops using the same RT3290 chip. > List is below : > > The RaLink RT3290 Bluetooth is under the Bluetooth category and is contained > in the ubuntu certified systems below. > Why can't it be included in Standard Ubuntu release which can help many > others too. ? > ><<34 HP & 2 Asus systems' detail DELETED.>> -- 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/1189721 Title: Ralink RT3290 doesn't have a bluetooth driver Status in The Linux Kernel: Unknown Status in The Linux Mint Distribution: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: As of Raring Ubuntu has a wifi driver for the RT3290 that works out of the box. It still does not have bluetooth support. This thread in the Ubuntu forums links to a driver that is claimed to work: http://ubuntuforums.org/showthread.php?t=2115570 --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graeme 2412 F pulseaudio CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70 InstallationDate: Installed on 2013-05-17 (144 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/06/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.32 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1189721/+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 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver
Ravi, intriguingly, those systems are certified for Ubuntu *12.04 LTS*, *not* for Ubuntu *14.04 LTS*. My recollection is that the driver from the manufacturer was specifically directed at 12.04 (or it may have been a corresponding kernel version). The kernel has changed sufficiently from 12.04 to 14.04 for the driver no longer to be effective, as one understands it. Had the manufacturer updated the driver, or someone else taken over maintenance (with or without manufacturer's sponsorship), then this frustrating problem would not have arisen. Cheers, Robin PS: It wasn't really necessary to quote all the certified machines (36 in total) in glorious detail! On 23/12/14 15:29, Ravi Karki wrote: > There are many Ubuntu certified laptops using the same RT3290 chip. > List is below : > > The RaLink RT3290 Bluetooth is under the Bluetooth category and is contained > in the ubuntu certified systems below. > Why can't it be included in Standard Ubuntu release which can help many > others too. ? > > <<34 HP & 2 Asus systems' detail DELETED.>> -- 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/1189721 Title: Ralink RT3290 doesn't have a bluetooth driver Status in The Linux Kernel: Unknown Status in The Linux Mint Distribution: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: As of Raring Ubuntu has a wifi driver for the RT3290 that works out of the box. It still does not have bluetooth support. This thread in the Ubuntu forums links to a driver that is claimed to work: http://ubuntuforums.org/showthread.php?t=2115570 --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graeme 2412 F pulseaudio CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70 InstallationDate: Installed on 2013-05-17 (144 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/06/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.32 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1189721/+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 1234541] Re: 1814:3290 Ralink corp. RT3290 Bluetooth not toggling on
*** This bug is a duplicate of bug 1189721 *** https://bugs.launchpad.net/bugs/1189721 For the avoidance of anyone's doubt, this bug is functionally a duplicate of bug #1189721. The reason for the problem as reported on bug 1234541 is that there is *no* driver to enable the bluetooth functionality of the RT3290 combined Wi-Fi & Bluetooth device. The focus—and bug reports—should transfer to the 1189721 bug, whose resolution should also deal with 1234541. Cheers -- 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/1234541 Title: 1814:3290 Ralink corp. RT3290 Bluetooth not toggling on Status in “linux” package in Ubuntu: Triaged Bug description: When I try to toggle my Novatech nfinity laptop bluetooth via Fn+F11 nothing happens. geoff@geoff-laptop:~$ lspci|grep Bluetooth 01:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth geoff@geoff-laptop:~$ ps aux| grep bluetooth geoff 2090 0.0 0.1 490248 6648 ?Sl 09:02 0:00 /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service root 3328 0.0 0.0 19240 1752 ?Ss 09:41 0:00 /usr/sbin/bluetoothd geoff 3371 0.0 0.0 14984 1004 pts/3R+ 09:52 0:00 grep --color=auto bluetooth ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geoff 1957 F pulseaudio Date: Thu Oct 3 09:58:04 2013 HibernationDevice: RESUME=UUID=75bcd0bb-68ec-4ee2-a80d-e6cd4aa1d39d InstallationDate: Installed on 2013-10-03 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=286ca2cc-f79e-446b-9746-3865b1bfc022 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ChiefRiver dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. 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.:bvr4.6.5:bd06/11/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnChiefRiver:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234541/+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 1234541] Re: 1814:3290 Ralink corp. RT3290 Bluetooth not toggling on
*** This bug is a duplicate of bug 1189721 *** https://bugs.launchpad.net/bugs/1189721 ** This bug has been marked a duplicate of bug 1189721 Ralink RT3290 needs bluetooth driver -- 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/1234541 Title: 1814:3290 Ralink corp. RT3290 Bluetooth not toggling on Status in “linux” package in Ubuntu: Triaged Bug description: When I try to toggle my Novatech nfinity laptop bluetooth via Fn+F11 nothing happens. geoff@geoff-laptop:~$ lspci|grep Bluetooth 01:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth geoff@geoff-laptop:~$ ps aux| grep bluetooth geoff 2090 0.0 0.1 490248 6648 ?Sl 09:02 0:00 /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service root 3328 0.0 0.0 19240 1752 ?Ss 09:41 0:00 /usr/sbin/bluetoothd geoff 3371 0.0 0.0 14984 1004 pts/3R+ 09:52 0:00 grep --color=auto bluetooth ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geoff 1957 F pulseaudio Date: Thu Oct 3 09:58:04 2013 HibernationDevice: RESUME=UUID=75bcd0bb-68ec-4ee2-a80d-e6cd4aa1d39d InstallationDate: Installed on 2013-10-03 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=286ca2cc-f79e-446b-9746-3865b1bfc022 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ChiefRiver dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. 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.:bvr4.6.5:bd06/11/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnChiefRiver:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234541/+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 1307794] Re: [HP Compaq nx6320 Notebook PC] CPU frequency scaling not available
Yes, that's working great. Thanks for taking the time to look it up, appreciated. -- 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/1307794 Title: [HP Compaq nx6320 Notebook PC] CPU frequency scaling not available Status in “linux” package in Ubuntu: Incomplete Bug description: On login, I am presented with a dialogue stating that frequency scaling is not available for my hardware. Also, the frequency scaling applet informs me of the same. This contradicts the physical characteristics of the CPU, which does support frequency scaling. This page informs me that Intel SpeedStep technology is available for the CPU I am using: http://ark.intel.com/products/27253 At boot, i get the following messages: * Loading cpufreq kernel modules... [fail] * Starting CPU Frequency daemon cpufreqd [fail] $ lshw provides the following output for the CPU: *-cpu product: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 version: 6.15.6 serial: -06F6---- size: 1650MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx x86-64 constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm configuration: id=0 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-19-generic 3.11.0-19.33~precise1 ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-19-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robin 2411 F pulseaudio /dev/snd/controlC1: robin 2411 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xe858 irq 44' Mixer name : 'Analog Devices AD1981' Components : 'HDA:11d41981,103c30aa,00100200 HDA:11c13026,103c30aa,00100700' Controls : 18 Simple ctrls : 12 Card1.Amixer.info: Card hw:1 'Loopback'/'Loopback 1' Mixer name : 'Loopback Mixer' Components : '' Controls : 96 Simple ctrls : 0 Card1.Amixer.values: Date: Tue Apr 15 14:57:24 2014 HibernationDevice: RESUME=UUID=afe22c34-b1b0-4e32-9f54-319b48e34d51 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MachineType: Hewlett-Packard HP Compaq nx6320 (RM709PA#ABG) MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-generic root=UUID=55141efa-fd44-4842-9b7b-9c6cef1635aa ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-19-generic N/A linux-backports-modules-3.11.0-19-generic N/A linux-firmware 1.106~precise1~ppa1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-lts-saucy UpgradeStatus: Upgraded to precise on 2012-05-03 (711 days ago) dmi.bios.date: 07/27/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68YDU Ver. F.08 dmi.board.name: 30AA dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.11 dmi.chassis.asset.tag: CNU6360FH8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68YDUVer.F.08:bd07/27/2006:svnHewlett-Packard:pnHPCompaqnx6320(RM709PA#ABG):pvrF.08:rvnHewlett-Packard:rn30AA:rvrKBCVersion58.11:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx6320 (RM709PA#ABG) dmi.product.version: F.08 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307794/+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 1297049] [NEW] [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]
Public bug reported: apport detected this error on a fresh boot. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.40 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rgarner2756 F pulseaudio /dev/snd/pcmC1D0c: rgarner2756 F...m pulseaudio /dev/snd/controlC2: rgarner2756 F pulseaudio /dev/snd/controlC0: rgarner2756 F pulseaudio Date: Tue Mar 25 10:20:28 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=c7ef60d1-697d-4495-bb69-10665128efd3 InstallationDate: Installed on 2014-01-27 (55 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E6420 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=e960e3c7-aa3d-43d3-9178-7719d9023e08 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/01/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 032T9K dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd01/01/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops resume suspend trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1297049 Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: Confirmed Bug description: apport detected this error on a fresh boot. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.40 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rgarner2756 F pulseaudio /dev/snd/pcmC1D0c: rgarner2756 F...m pulseaudio /dev/snd/controlC2: rgarner2756 F pulseaudio /dev/snd/controlC0: rgarner2756 F pulseaudio Date: Tue Mar 25 10:20:28 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=c7ef60d1-697d-4495-bb69-10665128efd3 InstallationDate: Installed on 2014-01-27 (55 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E6420 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=e960e3c7-aa3d-43d3-9178-7719d9023e08 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/01/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 032T9K dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd01/01/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor
