[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Confirmed, 1018 boots fine here under Secure Boot, all good! ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FBEEA98 0047, LDTR - IDTR - 3F2D8018 0FFF, TR -
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
@smb what's the state of groovy, did you push the config update there too? For the cloud images, we'll want to switch over to those using linux-kvm in groovy first, then focal, so just want to make sure we'll get a working kernel on there too! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3
[Kernel-packages] [Bug 1690085]
As a last resort, I've tried `idle=halt` on this machine. And yet my system just crashed after 3 weeks of uptime. I'm done with AMD. I will RMA this processor to try things out, but overall, if that doesn't work, this thing is headed to the junkyard and I'm going to live with Intel. At least in the 13 or so odd Intel systems I've tried, I've not had exhasperating issues like these where the company is positively trying to ignore this ongoing issue. This is disgusting from AMD. On 6/11/20 6:03 PM, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=196683 > > --- Comment #689 from raulvior@gmail.com --- > (In reply to raulvior.bcn from comment #653) >> (In reply to txrx from comment #651) >> >> Typical Current Idle might not be working. Read the sensor output. If >> voltage is not higher than without enabling it, try to increase the core >> voltage. >> >> My Ryzen 7 1800X seems to not produce hangs since I upgraded to 1003ABB with >> an ASUS Crosshair VI Hero and enabled Typical current idle. >> >> >>> I was able to update my BIOS to version 18, but my system still locks up. >>> I tried the following with the new BIOS: >>> - use factory defaults >>> - disable SMT >>> - disable SMT with Typical Current Idle >>> - all of the above with SVM disabled/enabled >>> Right now I set the power supply idle control to "Low ..." and will report >>> back. >>> > The motherboard kept hanging. I had to remove the Vitals GNOME Extension. It > seems that polling voltage values hangs the motherboard... Still, there are > times that the computer does not come back from suspend. There's something > wrong with the BIOS/UEFI. > -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 M
[Kernel-packages] [Bug 1690085]
Before you discard the CPU if your BIOS has PBO option turn it off, with latest BIOS on my B350 motherboard version 5406 PBO is on by default and apart from causing high temperature it would lead to this kind of crashes and reboots with my Ryzen7. Turning off PBO fixed it and now I am running a Ryzen9 with the same board and all works fine with PBO 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The
[Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
As per commeent #32, thermald helps here. But it is better to avoid kernel shutdown for one bad temperarure sample instead of some running average. We should have "mode" attribute so that we can avoid this by disabling the zone. I will see what can be done to add "mode" attribute for these zones. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Confirmed Status in Gentoo Linux: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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 1878045] Re: doing dist-upgrade got error related do Broadcom
There seems to be a bug in /usr/src/bcmwl-6.30.223.271+bdcom/patches/0028-add-support-for- linux-5.6.patch -- all the paths have the 'src' component doubled. Changed all 'src/src' to just 'src' and it compiles and works for me. -- 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: Confirmed 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 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
What ucode version are you using? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 Kernel 5.3.0-18-generic Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card. Expected: Wifi connects, uploads/downloads as normal Symptom: Wifi connects, as soon as an upload/download (any heavy traffic) start, the system comes to a crawl, becomes barely usable, and I end up opening a prompt to reboot. The system is unusable. This happens even with the Live USB version. The only solution I found was to download a different (newer) firmware. Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz I then manually copy the contained firmware to /lib/firmware, remove all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode that the kernel expects to load. This completely resolves the issue. This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh installs): Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending SCAN_CFG_CMD: time out after 2000ms. Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue read_ptr 64 write_ptr 65 Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting before reading Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, count: 609870115 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 46.6bf1df06.0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | ADVANCED_SYSASSERT Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | trm_hw_status0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | trm_hw_status1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | interruptlink1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | interruptlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode revision type Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode version major Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode version minor Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7BDF6F9E | l2p_mhvalid Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x190AF41B | l2p_addr_match Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7FF297FF | lmpm_pmg_sel Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5248C715 | timestamp Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xBBB939AF | flow_handler Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, count: -4391457 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5350C91F | ADVANCED_SYSASSERT Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1FFE5437 | umac branchlink1 Oct 20 01:51:16 weywot kernel: iwlwifi :03
[Kernel-packages] [Bug 1885368] Re: Installed by ubuntu-drivers for unsupported GPU (GTS 450)
Probably a duplicate of or related to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1874874 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1885368 Title: Installed by ubuntu-drivers for unsupported GPU (GTS 450) Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: Clean install of Kubuntu 20.04, with the "install proprietary drivers" option checked. System didn't go past boot screen. Further checks suggested that there is no working graphics driver compatible with SDDM/KDE (XDM would start using VESA). $ lspci -nn 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF116 [GeForce GTS 450 Rev. 2] [10de:1245] (rev a1) $ ubuntu-drivers devices == /sys/devices/pci:00/:00:02.0/:01:00.0 == modalias : pci:v10DEd1245sv1458sd3523bc03sc00i00 vendor : NVIDIA Corporation model: GF116 [GeForce GTS 450 Rev. 2] driver : nvidia-driver-435 - distro non-free driver : nvidia-driver-390 - distro non-free driver : nvidia-340 - distro non-free driver : nvidia-driver-440 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin The modalias appears in apt show nvidia-driver-440. This is incorrect, this GPU is not supported by the 440 driver. I manually switched to 390 (which is listed as supported by Nvidia) and that works. This is also seen in the support list (/usr/share/doc/nvidia- driver-440/README.txt.gz). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 (not installed) ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jun 27 13:19:14 2020 InstallationDate: Installed on 2020-06-25 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1885368/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
This issue is fixed with kernel version 5.4.49 (current longterm kernel). I was having the exact same issue for almost 3 months. My Wifi speed used to get throttled whenever I download something or just consume more bandwidth continuously. More importantly whenever the throttling happens, the laptop also freezes for a few seconds. During these 3 months I tried several iwlwifi configurations, changed its driver versions... etc. Nothing worked. But then updating the kernel from version 5.3.0 to 5.4.49 manually fixed the issue. Now the wifi works perfectly without any issues. I haven't faced any other issue with this kernel yet(I am on Ubuntu 18.04). Also, now I couldn't see any iwlwifi error messages getting reported in dmesg logs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 Kernel 5.3.0-18-generic Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card. Expected: Wifi connects, uploads/downloads as normal Symptom: Wifi connects, as soon as an upload/download (any heavy traffic) start, the system comes to a crawl, becomes barely usable, and I end up opening a prompt to reboot. The system is unusable. This happens even with the Live USB version. The only solution I found was to download a different (newer) firmware. Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz I then manually copy the contained firmware to /lib/firmware, remove all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode that the kernel expects to load. This completely resolves the issue. This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh installs): Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending SCAN_CFG_CMD: time out after 2000ms. Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue read_ptr 64 write_ptr 65 Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting before reading Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, count: 609870115 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 46.6bf1df06.0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | ADVANCED_SYSASSERT Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | trm_hw_status0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | trm_hw_status1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | interruptlink1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | interruptlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode revision type Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode version major Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode version minor Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7BDF6F9E | l2p_mhvalid Oct 20 01:
[Kernel-packages] [Bug 1885397] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885397 Title: Touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Touchpad (with microsoft precision drivers) can't recognize by linux. No touchpad manufacture can't be identified Laptop: Lenovo IdeaPad 5 15IIL05. Occurence: Direct after installing ubuntu. Thank you for your support. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 27 23:29:48 2020 InstallationDate: Installed on 2020-06-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=6673529c-7bec-4811-99fa-d7f1f6492f6b ro i8042.reset quit splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN41WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN41WW:bd04/10/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885397/+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 1885397] [NEW] Touchpad not detected
Public bug reported: Touchpad (with microsoft precision drivers) can't recognize by linux. No touchpad manufacture can't be identified Laptop: Lenovo IdeaPad 5 15IIL05. Occurence: Direct after installing ubuntu. Thank you for your support. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 27 23:29:48 2020 InstallationDate: Installed on 2020-06-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=6673529c-7bec-4811-99fa-d7f1f6492f6b ro i8042.reset quit splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN41WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN41WW:bd04/10/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885397 Title: Touchpad not detected Status in linux package in Ubuntu: New Bug description: Touchpad (with microsoft precision drivers) can't recognize by linux. No touchpad manufacture can't be identified Laptop: Lenovo IdeaPad 5 15IIL05. Occurence: Direct after installing ubuntu. Thank you for your support. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 27 23:29:48 2020 InstallationDate: Installed on 2020-06-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=6673529c-7bec-4811-99fa-d7f1f6492f6b ro i8042.reset quit splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN41WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN41WW:bd04/10/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885397/+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 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend
Also seeing the same behavior on 20.04 -- 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 and click-and-drag no longer works after resuming from suspend Status in Linux: Confirmed Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid 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 1870014] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870014 Title: task blocked too long Status in linux package in Ubuntu: Confirmed Bug description: I plugged in the EasyCap device, then started VLC to read from it. Nothing worked, and I saw the following call traces from the kernel: Mar 31 23:48:30 cerberus kernel: [49598.934870] usb 3-6: new full-speed USB device number 41 using xhci_hcd Mar 31 23:48:30 cerberus kernel: [49599.062914] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:30 cerberus kernel: [49599.574905] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:31 cerberus kernel: [49599.682966] usb usb3-port6: attempt power cycle Mar 31 23:48:32 cerberus kernel: [49600.974908] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946905] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946975] usb usb3-port6: unable to enumerate USB device Mar 31 23:48:45 cerberus kernel: [49614.418840] usb 3-6: new high-speed USB device number 44 using xhci_hcd Mar 31 23:48:45 cerberus kernel: [49614.570267] usb 3-6: config 1 interface 0 altsetting 1 bulk endpoint 0x83 has invalid maxpa cket 256 Mar 31 23:48:45 cerberus kernel: [49614.573126] usb 3-6: New USB device found, idVendor=1b71, idProduct=3002 Mar 31 23:48:45 cerberus kernel: [49614.573130] usb 3-6: New USB device strings: Mfr=3, Product=4, SerialNumber=2 Mar 31 23:48:45 cerberus kernel: [49614.573132] usb 3-6: Product: usbtv007 Mar 31 23:48:45 cerberus kernel: [49614.573135] usb 3-6: Manufacturer: fushicai Mar 31 23:48:45 cerberus kernel: [49614.573136] usb 3-6: SerialNumber: 3002 Mar 31 23:48:45 cerberus kernel: [49614.574491] usbtv 3-6:1.0: Fushicai USBTV007 Audio-Video Grabber Mar 31 23:52:29 cerberus kernel: [49838.118469] usb 3-6: USB disconnect, device number 44 Mar 31 23:52:44 cerberus kernel: [49853.203903] perf: interrupt took too long (3978 > 3967), lowering kernel.perf_event_max_sam ple_rate to 50250 Mar 31 23:55:36 cerberus kernel: [50024.968505] INFO: task VideoCapture:11251 blocked for more than 120 seconds. Mar 31 23:55:36 cerberus kernel: [50024.968512] Tainted: G IOE 4.15.0-94-generic #95-Ubuntu Mar 31 23:55:36 cerberus kernel: [50024.968514] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 31 23:55:36 cerberus kernel: [50024.968517] VideoCaptureD0 11251 1 0x Mar 31 23:55:36 cerberus kernel: [50024.968521] Call Trace: Mar 31 23:55:36 cerberus kernel: [50024.968535] __schedule+0x24e/0x880 Mar 31 23:55:36 cerberus kernel: [50024.968539] schedule+0x2c/0x80 Mar 31 23:55:36 cerberus kernel: [50024.968542] schedule_preempt_disabled+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968547] __mutex_lock.isra.5+0x276/0x4e0 Mar 31 23:55:36 cerberus kernel: [50024.968551] __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968554] ? __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968557] mutex_lock+0x2f/0x40 Mar 31 23:55:36 cerberus kernel: [50024.968569] _vb2_fop_release+0x29/0xa0 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968573] vb2_fop_release+0x31/0x40 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968593] v4l2_release+0x38/0x80 [videodev] Mar 31 23:55:36 cerberus kernel: [50024.968600] __fput+0xea/0x220 Mar 31 23:55:36 cerberus kernel: [50024.968604] fput+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968611] task_work_run+0x9d/0xc0 Mar 31 23:55:36 cerberus kernel: [50024.968620] exit_to_usermode_loop+0xc0/0xd0 Mar 31 23:55:36 cerberus kernel: [50024.968623] do_syscall_64+0x121/0x130 Mar 31 23:55:36 cerberus kernel: [50024.968630] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Mar 31 23:55:36 cerberus kernel: [50024.968633] RIP: 0033:0x7f6411c26447 Mar 31 23:55:36 cerberus kernel: [50024.968635] RSP: 002b:7f63da9bd900 EFLAGS: 0293 ORIG_RAX: 0003 Mar 31 23:55:36 cerberus kernel: [50024.968638] RAX: RBX: 0064 RCX: 7f6411c26447 Mar 31 23:55:36 cerberus kernel: [50024.968639] RDX: RSI: 7f63da9bd930 RDI: 0064 Mar 31 23:55:36 cerberus kernel: [50024.968641] RBP: R08: R09: Mar 31 23:55:36 cerberus kernel: [50024.968642] R10: R11: 0293 R12: 7f628d4c5fa0 Mar 31 23:55:36 cerberus kernel: [50024.968644] R13: R14: 7f640422d381 R15: 7f63da9bd930 Mar 31 23:55:36 cerberus kernel: [50024.968915] INFO: task kworker/5:1:25898 blocked for more than 120 seconds.
[Kernel-packages] [Bug 1870014] Re: task blocked too long
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1870014 Title: task blocked too long Status in linux package in Ubuntu: Confirmed Bug description: I plugged in the EasyCap device, then started VLC to read from it. Nothing worked, and I saw the following call traces from the kernel: Mar 31 23:48:30 cerberus kernel: [49598.934870] usb 3-6: new full-speed USB device number 41 using xhci_hcd Mar 31 23:48:30 cerberus kernel: [49599.062914] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:30 cerberus kernel: [49599.574905] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:31 cerberus kernel: [49599.682966] usb usb3-port6: attempt power cycle Mar 31 23:48:32 cerberus kernel: [49600.974908] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946905] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946975] usb usb3-port6: unable to enumerate USB device Mar 31 23:48:45 cerberus kernel: [49614.418840] usb 3-6: new high-speed USB device number 44 using xhci_hcd Mar 31 23:48:45 cerberus kernel: [49614.570267] usb 3-6: config 1 interface 0 altsetting 1 bulk endpoint 0x83 has invalid maxpa cket 256 Mar 31 23:48:45 cerberus kernel: [49614.573126] usb 3-6: New USB device found, idVendor=1b71, idProduct=3002 Mar 31 23:48:45 cerberus kernel: [49614.573130] usb 3-6: New USB device strings: Mfr=3, Product=4, SerialNumber=2 Mar 31 23:48:45 cerberus kernel: [49614.573132] usb 3-6: Product: usbtv007 Mar 31 23:48:45 cerberus kernel: [49614.573135] usb 3-6: Manufacturer: fushicai Mar 31 23:48:45 cerberus kernel: [49614.573136] usb 3-6: SerialNumber: 3002 Mar 31 23:48:45 cerberus kernel: [49614.574491] usbtv 3-6:1.0: Fushicai USBTV007 Audio-Video Grabber Mar 31 23:52:29 cerberus kernel: [49838.118469] usb 3-6: USB disconnect, device number 44 Mar 31 23:52:44 cerberus kernel: [49853.203903] perf: interrupt took too long (3978 > 3967), lowering kernel.perf_event_max_sam ple_rate to 50250 Mar 31 23:55:36 cerberus kernel: [50024.968505] INFO: task VideoCapture:11251 blocked for more than 120 seconds. Mar 31 23:55:36 cerberus kernel: [50024.968512] Tainted: G IOE 4.15.0-94-generic #95-Ubuntu Mar 31 23:55:36 cerberus kernel: [50024.968514] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 31 23:55:36 cerberus kernel: [50024.968517] VideoCaptureD0 11251 1 0x Mar 31 23:55:36 cerberus kernel: [50024.968521] Call Trace: Mar 31 23:55:36 cerberus kernel: [50024.968535] __schedule+0x24e/0x880 Mar 31 23:55:36 cerberus kernel: [50024.968539] schedule+0x2c/0x80 Mar 31 23:55:36 cerberus kernel: [50024.968542] schedule_preempt_disabled+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968547] __mutex_lock.isra.5+0x276/0x4e0 Mar 31 23:55:36 cerberus kernel: [50024.968551] __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968554] ? __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968557] mutex_lock+0x2f/0x40 Mar 31 23:55:36 cerberus kernel: [50024.968569] _vb2_fop_release+0x29/0xa0 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968573] vb2_fop_release+0x31/0x40 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968593] v4l2_release+0x38/0x80 [videodev] Mar 31 23:55:36 cerberus kernel: [50024.968600] __fput+0xea/0x220 Mar 31 23:55:36 cerberus kernel: [50024.968604] fput+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968611] task_work_run+0x9d/0xc0 Mar 31 23:55:36 cerberus kernel: [50024.968620] exit_to_usermode_loop+0xc0/0xd0 Mar 31 23:55:36 cerberus kernel: [50024.968623] do_syscall_64+0x121/0x130 Mar 31 23:55:36 cerberus kernel: [50024.968630] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Mar 31 23:55:36 cerberus kernel: [50024.968633] RIP: 0033:0x7f6411c26447 Mar 31 23:55:36 cerberus kernel: [50024.968635] RSP: 002b:7f63da9bd900 EFLAGS: 0293 ORIG_RAX: 0003 Mar 31 23:55:36 cerberus kernel: [50024.968638] RAX: RBX: 0064 RCX: 7f6411c26447 Mar 31 23:55:36 cerberus kernel: [50024.968639] RDX: RSI: 7f63da9bd930 RDI: 0064 Mar 31 23:55:36 cerberus kernel: [50024.968641] RBP: R08: R09: Mar 31 23:55:36 cerberus kernel: [50024.968642] R10: R11: 0293 R12: 7f628d4c5fa0 Mar 31 23:55:36 cerberus kernel: [50024.968644] R13: R14: 7f640422d381 R15: 7f63da9bd930 Mar 31 23:55:36 cerberus kernel: [50024.968915] INFO: task kworker/5:1:25898 blocked for more than 120 seconds. Mar 31 23:55:36 cerberus ker
[Kernel-packages] [Bug 1885380] Re: ejecting mp3-CD doesn't leave tray open
btw, Audio CDs and DVDs work fine, the problem is limited to mp3-CDs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to eject in Ubuntu. https://bugs.launchpad.net/bugs/1885380 Title: ejecting mp3-CD doesn't leave tray open Status in eject package in Ubuntu: New Bug description: When I load an mp3-CD in either of my DVD drives (DVDrom and BlueRay Burner from LG), when I try to eject the CD, the tray doesn't stay open long enough to retrieve it, but closes again right away. This happens, no matter if I eject from KDE apps or from the terminal. Same problem on a second computer installed and configured the same way. OS is Kubuntu 20.04 LTS Linux ... 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux on both machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/1885380/+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 1885380] Re: ejecting mp3-CD doesn't leave tray open
/bin/eject ** Package changed: ubuntu => eject (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to eject in Ubuntu. https://bugs.launchpad.net/bugs/1885380 Title: ejecting mp3-CD doesn't leave tray open Status in eject package in Ubuntu: New Bug description: When I load an mp3-CD in either of my DVD drives (DVDrom and BlueRay Burner from LG), when I try to eject the CD, the tray doesn't stay open long enough to retrieve it, but closes again right away. This happens, no matter if I eject from KDE apps or from the terminal. Same problem on a second computer installed and configured the same way. OS is Kubuntu 20.04 LTS Linux ... 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux on both machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/1885380/+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 1885380] [NEW] ejecting mp3-CD doesn't leave tray open
You have been subscribed to a public bug: When I load an mp3-CD in either of my DVD drives (DVDrom and BlueRay Burner from LG), when I try to eject the CD, the tray doesn't stay open long enough to retrieve it, but closes again right away. This happens, no matter if I eject from KDE apps or from the terminal. Same problem on a second computer installed and configured the same way. OS is Kubuntu 20.04 LTS Linux ... 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux on both machines. ** Affects: eject (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- ejecting mp3-CD doesn't leave tray open https://bugs.launchpad.net/bugs/1885380 You received this bug notification because you are a member of Kernel Packages, which is subscribed to eject in Ubuntu. -- 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 1883472] Re: linux-image-5.4.0-37-generic freezes on idle. linux-image-5.4.0-33-generic works fine.
** Description changed: + UPDATE: + linux-image-5.4.0-39-generic Works OK + == + Original report: linux-image-5.4.0-33-generic Works OK linux-image-5.4.0-37-generic Freezes when leaving idle for some time. Ubuntu 20.04LTS 64 bits. Fully updated. Hardware: AMD Ryzen 7 1800X 32GB RAM (two sticks: Part number KHX2666C16/16G) Asus PRIME A320M-K - latest BIOS installed AMD Radeon R9 390X 8GB NVMe SSD 512GB (I don't recall the brand) Tried AMDGPU and RADEON drivers for the video card. The issue persists. I was not able to find any logs nor kernel panics on the usual log files. Booting the older kernel makes the machine work perfectly stable as before. Most of the time I come back to a black screen. Other times is partially dimmed, like when entering into power save mode, when the screensaver kicks in to shut down the monitor. WORKAROUND: Disabling the ability to shut down the monitor "fixes" the problem. In the xscreensaver settings I disabled quick power-off and also disabled power management, so it never tries to power off the monitor. Now the system is stable again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1883472 Title: linux-image-5.4.0-37-generic freezes on idle. linux- image-5.4.0-33-generic works fine. Status in linux-signed package in Ubuntu: New Bug description: UPDATE: linux-image-5.4.0-39-generic Works OK == Original report: linux-image-5.4.0-33-generic Works OK linux-image-5.4.0-37-generic Freezes when leaving idle for some time. Ubuntu 20.04LTS 64 bits. Fully updated. Hardware: AMD Ryzen 7 1800X 32GB RAM (two sticks: Part number KHX2666C16/16G) Asus PRIME A320M-K - latest BIOS installed AMD Radeon R9 390X 8GB NVMe SSD 512GB (I don't recall the brand) Tried AMDGPU and RADEON drivers for the video card. The issue persists. I was not able to find any logs nor kernel panics on the usual log files. Booting the older kernel makes the machine work perfectly stable as before. Most of the time I come back to a black screen. Other times is partially dimmed, like when entering into power save mode, when the screensaver kicks in to shut down the monitor. WORKAROUND: Disabling the ability to shut down the monitor "fixes" the problem. In the xscreensaver settings I disabled quick power-off and also disabled power management, so it never tries to power off the monitor. Now the system is stable again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1883472/+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 1883472] Re: linux-image-5.4.0-37-generic freezes on idle. linux-image-5.4.0-33-generic works fine.
This bug no longer happens on 5.4.0-39. I turned on power management again and the screen is correctly turned off by xscreensaver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1883472 Title: linux-image-5.4.0-37-generic freezes on idle. linux- image-5.4.0-33-generic works fine. Status in linux-signed package in Ubuntu: New Bug description: linux-image-5.4.0-33-generic Works OK linux-image-5.4.0-37-generic Freezes when leaving idle for some time. Ubuntu 20.04LTS 64 bits. Fully updated. Hardware: AMD Ryzen 7 1800X 32GB RAM (two sticks: Part number KHX2666C16/16G) Asus PRIME A320M-K - latest BIOS installed AMD Radeon R9 390X 8GB NVMe SSD 512GB (I don't recall the brand) Tried AMDGPU and RADEON drivers for the video card. The issue persists. I was not able to find any logs nor kernel panics on the usual log files. Booting the older kernel makes the machine work perfectly stable as before. Most of the time I come back to a black screen. Other times is partially dimmed, like when entering into power save mode, when the screensaver kicks in to shut down the monitor. WORKAROUND: Disabling the ability to shut down the monitor "fixes" the problem. In the xscreensaver settings I disabled quick power-off and also disabled power management, so it never tries to power off the monitor. Now the system is stable again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1883472/+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 1880835] Re: pulse audio hangs in kernel call
Taking after csita I unplugged/replugged all my external audio devices and restarted pulseaudio and alsa-mixer. I found the below error in journalctl: Jun 27 09:15:37 hostname pulseaudio[3735]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="usb-N-SIA_KJ- USB_HEASET-00" card_name="alsa_card.usb-N-SIA_KJ-USB_HEASET-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties ="module-udev-detect.discovered=1""): initialization failed. This is a usb headset. When unplugging and leaving unplugged after reboot everything works. The failure to load the the module for the USB headset was for some reason leaving pulseaudio blocked on IO in a D state. I use audio via HDMI output from my Nvidia card. I have Nvidia driver 440 installed on my system, but I do not use the Nvidia driver. I still use nouveau. -- 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/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Incomplete Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib] [ 364.150674] pcr_modify+0x65/0x100 [snd_firewire_lib] [ 364.150675] cmp_connection_break+0x37/0x50 [snd_firewire_lib] [ 364.150677] snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw] [ 364.150678] ? wait_woken+0x80/0x80 [ 364.150679] pcm_capture_prepare+0x26/0x50 [snd_oxfw] [ 364.150682] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [ 364.150684] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [ 364.150686] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [ 364.150687] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [ 364.150689] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [ 364.150691] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [ 364.150692] do_vfs_ioctl+0x407/0x670 [ 364.150694] ? __secure_computing+0x42/0xe0 [ 364.150694] ksys_ioctl+0x67/0x90 [ 364.150695] __x64_sys_ioctl+0x1a/0x20 [ 364.150697] do_syscall_64+0x57/0x190 [ 364.150698] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 364.150699] RIP: 0033:0x7f0bbfa1a37b [ 364.150701] Code: Bad RIP value. [ 364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 0010 [ 364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 7f0bbfa1a37b [ 364.150703] RDX: RSI: 4140 RDI: 006e [ 364.150703] RBP: 5607c7b63bb0 R08: R09: 1000 [ 364.150703] R10: 0004 R11: 0202 R12: 5607c7b63de0 [ 364.150704] R13: 7ffed915d6f0 R14: R15: 7ffed915d480 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 10:07:13 2020 InstallationDate: Installed on 2020-02-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) MachineType: Dell Inc. Precision 7540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-r
[Kernel-packages] [Bug 1880835] Re: pulse audio hangs in kernel call
My system has hit the same bug and I do not use firewire. I have not upgraded to mainline kernel. The power cycling work arounds above do not mitigate the issue for me. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" $ uname -a Linux hostname 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ pactl info Connection failure: Connection refused pa_context_connect() failed: Connection refused $ ps aux | grep pulse | grep -v grep username12895 17.0 0.0 100788 10908 ?D] usb_start_wait_urb+0x8f/0x180 [<0>] usb_control_msg+0xe3/0x140 [<0>] snd_usb_ctl_msg+0xe3/0x190 [snd_usb_audio] [<0>] snd_usb_init_sample_rate+0x235/0x320 [snd_usb_audio] [<0>] snd_usb_pcm_prepare+0x159/0x460 [snd_usb_audio] [<0>] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [<0>] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [<0>] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [<0>] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [<0>] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [<0>] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [<0>] do_vfs_ioctl+0x407/0x670 [<0>] ksys_ioctl+0x67/0x90 [<0>] __x64_sys_ioctl+0x1a/0x20 [<0>] do_syscall_64+0x57/0x190 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 The stack frames line up w/ the above. $ journalctl -f | grep pulse # a selection of the output Jun 27 09:38:50 hostname systemd[2373]: pulseaudio.service: State 'stop-sigterm' timed out. Killing. Jun 27 09:38:50 hostname systemd[2373]: pulseaudio.service: Killing process 12140 (pulseaudio) with signal SIGKILL. Jun 27 09:38:56 hostname systemd[2373]: pulseaudio.service: Main process exited, code=killed, status=9/KILL Jun 27 09:38:56 hostname systemd[2373]: pulseaudio.service: Failed with result 'timeout'. Jun 27 09:38:56 hostname systemd[2373]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jun 27 09:38:56 hostname pulseaudio[12895]: Stale PID file, overwriting. Jun 27 09:40:26 hostname systemd[2373]: pulseaudio.service: start operation timed out. Terminating. Jun 27 09:41:56 hostname systemd[2373]: pulseaudio.service: State 'stop-sigterm' timed out. Killing. Jun 27 09:41:56 hostname systemd[2373]: pulseaudio.service: Killing process 12895 (pulseaudio) with signal SIGKILL. Jun 27 09:42:02 hostname systemd[2373]: pulseaudio.service: Main process exited, code=killed, status=9/KILL Jun 27 09:42:02 hostname systemd[2373]: pulseaudio.service: Failed with result 'timeout'. Jun 27 09:42:02 hostname systemd[2373]: pulseaudio.service: Scheduled restart job, restart counter is at 6. Jun 27 09:42:03 hostname pulseaudio[13050]: Stale PID file, overwriting. Jun 27 09:43:33 hostname systemd[2373]: pulseaudio.service: start operation timed out. Terminating. Jun 27 09:45:03 hostname systemd[2373]: pulseaudio.service: State 'stop-sigterm' timed out. Killing. Jun 27 09:45:03 hostname systemd[2373]: pulseaudio.service: Killing process 13050 (pulseaudio) with signal SIGKILL. Jun 27 09:45:10 hostname systemd[2373]: pulseaudio.service: Main process exited, code=killed, status=9/KILL Jun 27 09:45:10 hostname systemd[2373]: pulseaudio.service: Failed with result 'timeout'. Jun 27 09:45:10 hostname systemd[2373]: pulseaudio.service: Scheduled restart job, restart counter is at 7. -- 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/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Incomplete Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info
[Kernel-packages] [Bug 1884505] Re: Libreoffice crashes gnome session
Issue prevails with 440.100. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1884505 Title: Libreoffice crashes gnome session Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: After while (1-5 min) using Libreoffice Cals/Writer the program crashes the running gnome session. And login screen pops up. After new login there are issues with audio playback so restart is required. I tested both libreoffice snap and dep packages. Problem occurs with both. My suspicion is that it is related to graphics card or driver. Notebook Dell 7559, GeForce 960M rev a2, driver 440.62, Ububtu 20.04 After each crash I found something like below in dmesg log: [14564.930179] NVRM: Xid (PCI::02:00): 32, pid=30138, Channel ID 0018 intr 0004 [14564.930629] NVRM: Xid (PCI::02:00): 32, pid=30138, Channel ID 0018 intr 0004 full output in attachment. This bug is very annoying and makes the whole system useless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 22 10:47:12 2020 InstallationDate: Installed on 2020-05-11 (41 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1884505/+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 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
Hi! I have C940-14IIL, running under Fedora 32 and I am very pleased by this laptop. Everything is OK, except shutdown/reboot (workaround i915.enable_psr=0 kernel option), fingerprint reader (do not care) and overheating shutdown. I have resolved my overheating problem by installing the last version 2.2 of thermald from Github and automatically creating config bydptfxtract (https://github.com/intel/dptfxtract). The bydptfxtract create 10 different thermal-conf.xml. I have tested all of them and I am attaching the most successful of them. I did a stress test with full load for 10 minutes. Following is the uptime output: 14:47:46 up 18:57, 1 user, load average: 8.49, 9.10, 7.25 During the test temperature vary around 75-80 degree - something that I could not imagine before installing the thermald. One virtual machine and a minute of compilation or R calculations would certainly cause overheating shutdown. Actually, as far as can explain the results, the thermald do a CPU scaling of the CPU speed in range 2.5-2.8 GHz - about 1 GHz below the maximum speed - something that I definitely agree. Scaling is done after the rise of the temperature and I do not experience any inconvenience, troubles or interruptions with the lower speed. ** Attachment added: "Thermald conf file" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+attachment/5387703/+files/thermal-conf.xml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Confirmed Status in Gentoo Linux: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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 1885267] Re: Amd64 ppa kernel mainline build failing self test.
This is not a bug with the kernel, but with the build process for kernels in the mainline ppa. As such, logs from my machine are not relevant, and the original report links to the relevant build logs, and has relevant extracts from those logs. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885267 Title: Amd64 ppa kernel mainline build failing self test. Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.6.18 / 5.7.2 and onwards, the amd64 kernel builds (and the s390x builds) in the kernel ppa at https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D are failing self tests "Test amd64/self-tests failed (rc=2, on=amd64, time=0:00:57, log=amd64 /self-tests/log)" The log shows: ++ INSTALL headers CC test_stub.o BINARY test_verifier test_verifier.c:25:10: fatal error: sys/capability.h: No such file or directory 25 | #include | ^~ compilation terminated. make[2]: *** [Makefile:398: /home/kernel/COD/linux/tools/testing/selftests/bpf/test_verifier] Error 1 make[2]: Leaving directory '/home/kernel/COD/linux/tools/testing/selftests/bpf' make[1]: *** [Makefile:157: all] Error 2 make[1]: Leaving directory '/home/kernel/COD/linux/tools/testing/selftests' make: *** [debian/rules.d/1-maintainer.mk:170: compileselftests] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885267/+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 1885368] [NEW] Installed by ubuntu-drivers for unsupported GPU (GTS 450)
Public bug reported: Clean install of Kubuntu 20.04, with the "install proprietary drivers" option checked. System didn't go past boot screen. Further checks suggested that there is no working graphics driver compatible with SDDM/KDE (XDM would start using VESA). $ lspci -nn 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF116 [GeForce GTS 450 Rev. 2] [10de:1245] (rev a1) $ ubuntu-drivers devices == /sys/devices/pci:00/:00:02.0/:01:00.0 == modalias : pci:v10DEd1245sv1458sd3523bc03sc00i00 vendor : NVIDIA Corporation model: GF116 [GeForce GTS 450 Rev. 2] driver : nvidia-driver-435 - distro non-free driver : nvidia-driver-390 - distro non-free driver : nvidia-340 - distro non-free driver : nvidia-driver-440 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin The modalias appears in apt show nvidia-driver-440. This is incorrect, this GPU is not supported by the 440 driver. I manually switched to 390 (which is listed as supported by Nvidia) and that works. This is also seen in the support list (/usr/share/doc/nvidia- driver-440/README.txt.gz). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 (not installed) ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jun 27 13:19:14 2020 InstallationDate: Installed on 2020-06-25 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1885368 Title: Installed by ubuntu-drivers for unsupported GPU (GTS 450) Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: Clean install of Kubuntu 20.04, with the "install proprietary drivers" option checked. System didn't go past boot screen. Further checks suggested that there is no working graphics driver compatible with SDDM/KDE (XDM would start using VESA). $ lspci -nn 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF116 [GeForce GTS 450 Rev. 2] [10de:1245] (rev a1) $ ubuntu-drivers devices == /sys/devices/pci:00/:00:02.0/:01:00.0 == modalias : pci:v10DEd1245sv1458sd3523bc03sc00i00 vendor : NVIDIA Corporation model: GF116 [GeForce GTS 450 Rev. 2] driver : nvidia-driver-435 - distro non-free driver : nvidia-driver-390 - distro non-free driver : nvidia-340 - distro non-free driver : nvidia-driver-440 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin The modalias appears in apt show nvidia-driver-440. This is incorrect, this GPU is not supported by the 440 driver. I manually switched to 390 (which is listed as supported by Nvidia) and that works. This is also seen in the support list (/usr/share/doc/nvidia- driver-440/README.txt.gz). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 (not installed) ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jun 27 13:19:14 2020 InstallationDate: Installed on 2020-06-25 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1885368/+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 1881338] Autopkgtest regression report (linux-base/4.5ubuntu1.2)
All autopkgtests for the newly accepted linux-base (4.5ubuntu1.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.0/5.0.0-53.57~18.04.1 (armhf) makedumpfile/1:1.6.5-1ubuntu1~18.04.5 (ppc64el) linux-hwe-5.4/5.4.0-40.44~18.04.1 (armhf) linux-raspi2-5.3/5.3.0-1028.30~18.04.2 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-base [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1881338 Title: linux-azure: Update SGX version to version LD_1.33 Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-4.15 package in Ubuntu: New Status in linux-base package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Invalid Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-base source package in Xenial: Fix Committed Status in linux-azure source package in Bionic: Fix Committed Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux-base source package in Bionic: Fix Committed Status in linux-azure source package in Eoan: Fix Committed Status in linux-azure-4.15 source package in Eoan: Invalid Status in linux-base source package in Eoan: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-base source package in Focal: Fix Committed Bug description: [Impact] We have included the DCAP version of SGX into the linux-azure kernels in order to provide a signed version of this driver that can be used with secure boot in Azure instances. Since a new version of this driver was released, we should update the embedded driver: https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.33/driver/linux [Test Case] - Install the new kernel on an ACC azure instance. - Ensure the module loads properly. - Check if ECL (provided on the azure images) is working properly. [Regression Potential] The changes are extensive, but both Canonical and Microsoft perform validation tests on SGX. Besides that, the change is restricted to linux-azure running on specific instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881338/+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 1885365] Re: package linux-modules-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new'
*** This bug is a duplicate of bug 1883976 *** https://bugs.launchpad.net/bugs/1883976 Please stop Sophos Antivirus while upgrading/installing kernel related packages: $ sudo systemctl stop sav-protect.service ** This bug has been marked a duplicate of bug 1883976 package linux-modules-extra-5.4.0-37-generic (not installed) failed to install/upgrade: impossible de créer le fichier « /var/lib/dpkg/info/linux-modules-extra-5.4.0-37-generic.list-new »: Opération non permise -- 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/1885365 Title: package linux-modules-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-5.4.0-39-generic.list-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: I don't know if it's related but my sound drivers are often missing on boot and running `sudo alsa force-reload` either fixes it or crashes the computer. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sat Jun 27 10:50:30 2020 Dependencies: DuplicateSignature: package:linux-modules-5.4.0-39-generic:5.4.0-39.43 Unpacking linux-modules-5.4.0-39-generic (5.4.0-39.43) ... dpkg: error processing archive /tmp/apt-dpkg-install-xaNEUW/10-linux-modules-5.4.0-39-generic_5.4.0-39.43_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted InstallationDate: Installed on 2020-06-19 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81RS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=19dbbb0b-690b-4e17-a31e-5755e1b3d8cd ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-modules-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BYCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL: dmi.product.family: Yoga S740-14IIL dmi.product.name: 81RS dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL dmi.product.version: Lenovo Yoga S740-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885365/+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 1885365] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885365 Title: package linux-modules-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-5.4.0-39-generic.list-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: I don't know if it's related but my sound drivers are often missing on boot and running `sudo alsa force-reload` either fixes it or crashes the computer. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sat Jun 27 10:50:30 2020 Dependencies: DuplicateSignature: package:linux-modules-5.4.0-39-generic:5.4.0-39.43 Unpacking linux-modules-5.4.0-39-generic (5.4.0-39.43) ... dpkg: error processing archive /tmp/apt-dpkg-install-xaNEUW/10-linux-modules-5.4.0-39-generic_5.4.0-39.43_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted InstallationDate: Installed on 2020-06-19 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81RS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=19dbbb0b-690b-4e17-a31e-5755e1b3d8cd ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-modules-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BYCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL: dmi.product.family: Yoga S740-14IIL dmi.product.name: 81RS dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL dmi.product.version: Lenovo Yoga S740-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885365/+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 1885365] Re: package linux-modules-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new'
** Tags removed: need-duplicate-check -- 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/1885365 Title: package linux-modules-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-5.4.0-39-generic.list-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: I don't know if it's related but my sound drivers are often missing on boot and running `sudo alsa force-reload` either fixes it or crashes the computer. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sat Jun 27 10:50:30 2020 Dependencies: DuplicateSignature: package:linux-modules-5.4.0-39-generic:5.4.0-39.43 Unpacking linux-modules-5.4.0-39-generic (5.4.0-39.43) ... dpkg: error processing archive /tmp/apt-dpkg-install-xaNEUW/10-linux-modules-5.4.0-39-generic_5.4.0-39.43_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted InstallationDate: Installed on 2020-06-19 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81RS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=19dbbb0b-690b-4e17-a31e-5755e1b3d8cd ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-modules-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BYCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL: dmi.product.family: Yoga S740-14IIL dmi.product.name: 81RS dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL dmi.product.version: Lenovo Yoga S740-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885365/+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 1885365] [NEW] package linux-modules-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-ne
Public bug reported: I don't know if it's related but my sound drivers are often missing on boot and running `sudo alsa force-reload` either fixes it or crashes the computer. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sat Jun 27 10:50:30 2020 Dependencies: DuplicateSignature: package:linux-modules-5.4.0-39-generic:5.4.0-39.43 Unpacking linux-modules-5.4.0-39-generic (5.4.0-39.43) ... dpkg: error processing archive /tmp/apt-dpkg-install-xaNEUW/10-linux-modules-5.4.0-39-generic_5.4.0-39.43_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted InstallationDate: Installed on 2020-06-19 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81RS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=19dbbb0b-690b-4e17-a31e-5755e1b3d8cd ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-modules-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BYCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL: dmi.product.family: Yoga S740-14IIL dmi.product.name: 81RS dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL dmi.product.version: Lenovo Yoga S740-14IIL dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885365 Title: package linux-modules-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-5.4.0-39-generic.list-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: I don't know if it's related but my sound drivers are often missing on boot and running `sudo alsa force-reload` either fixes it or crashes the computer. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sat Jun 27 10:50:30 2020 Dependencies: DuplicateSignature: package:linux-modules-5.4.0-39-generic:5.4.0-39.43 Unpacking linux-modules-5.4.0-39-generic (5.4.0-39.43) ... dpkg: error processing archive /tmp/apt-dpkg-install-xaNEUW/10-linux-modules-5.4.0-39-generic_5.4.0-39.43_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-39-generic.list-new': Operation not permitted InstallationDate: Installed on 2020-06-19 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81RS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=19dbbb0b-690b-4e17-a31e-5755e1b3d8cd ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, P
[Kernel-packages] [Bug 1874465] Re: dummy output ubuntu 20.04 LTS dell inspiron 3420
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065
This bug is flagged as duplicate of bug #1876065. However:
1. The bug description of #1876065 does not match the issue I have, which is
the one described here.
2. Even if #1876065 is now fixed, and my system is up-to-date (pulseaudio
13.99.1), I'm still having the issue: no device is shown upon each reboot, only
dummy output.
The only way around for me is to `alsa force-reload` until I get the devices
listed ("speakers","HDMI","Headset").
How should I proceed? Should I open a new bug? This is quite urgent, as
nowadays most of my work activity relies on conversations through my laptop.
--
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/1874465
Title:
dummy output ubuntu 20.04 LTS dell inspiron 3420
Status in linux package in Ubuntu:
Confirmed
Bug description:
in sound settings there is only dummy output, everything worked until
April, 21 2020 when updated 18.04 LTS to 20.04 LTS via terminal.
Description: Ubuntu 20.04 LTS
Release: 20.04
alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
*** 1.0.25+dfsg-0ubuntu5 500
500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://br.archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status
pavucontrol:
Installed: 4.0-1build1
Candidate: 4.0-1build1
Version table:
*** 4.0-1build1 500
500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ploosh 1949 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 23 11:35:40 2020
InstallationDate: Installed on 2019-10-06 (199 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
MachineType: Dell Inc. Inspiron 3420
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic
root=UUID=ec870298-2798-4d1b-a6d2-6118c2078d5e ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-04-22 (1 days ago)
dmi.bios.date: 11/04/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 04XGDT
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd11/04/2013:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3420
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874465/+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 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
In response to my own #56 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/comments/56) comment. I have downgraded the BIOS to CJCN26WW, but nothing seems working. For more information Please check devices log I have also attached the dmesg log, please check. #devices I: 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=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 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=ab83 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 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 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/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=13d3 Product=5415 Version=1906 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 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/input7 U: Uniq= H: Handlers=event7 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/input8 U: Uniq= H: Handlers=event8 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/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" 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=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" 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 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=046d Product=c077 Version=0111 N: Name="Logitech USB Optical Mouse" P: Phys=usb-:00:14.0-4/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:046D:C077.0003/input/input16 U: Uniq= H: Handlers=mouse0 event14 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=903 B: MSC=10 ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+attachment/5387644/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
This only started for me yesterday. I'm on 20.04 and don't remember running any updates. Tried most of the above and nothing works for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+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 1884981] Re: The touchpad soesn't work at all
I have the same touchpad issues with the same laptop IdeaPad 5 14ARE05 As requested by You-Sheng, I have added the kernel boot parameters and got some interesting logs. Although, I am running arch linux, it looks like the journalctl logs are as relevant Some boot, the touchpad is detected but not fully working (tab click fails, two fingers motion fails, etc) Otherwise, it is not detected at all. On kernel 5.7.6: (no touchpad at all) i2c_hid i2c-MSFT0004:00: HID over i2c has not been provided an Int IRQ i2c_hid: probe of i2c-MSFT0004:00 failed with error -22 On kernel 5.8.2-rc2 mainline: (touchpad acting limited) i2c_hid i2c-MSFT0004:00: supply vdd not found, using dummy regulator i2c_hid i2c-MSFT0004:00: supply vddl not found, using dummy regulator i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input13 input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input14 hid-generic 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00 i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input16 input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input17 hid-multitouch 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00 If needed I can attached the full logs, but does not look like there is anything else relevant to this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884981 Title: The touchpad soesn't work at all Status in linux package in Ubuntu: Incomplete Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+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 1885352] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885352 Title: touchpad not working at all Status in linux package in Ubuntu: Confirmed Bug description: Just bought a brand new lenovo IdeaPad S145-15IIL and switched it to linux. The touchpad was working before swapping os. Can't find the manufacturer of the touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: draal 1458 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 27 08:14:20 2020 InstallationDate: Installed on 2020-06-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=88c27fbd-2ac5-47e8-9181-d8307885944c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN21WW 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 IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN21WW:bd10/09/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885352/+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
