[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)
I tested the new kernel in artful-proposed on a system which failed with the newest kernel + intel-microcode in normal artful repository. Thus I confirm that the kernel in artful-proposed fixes this issue for me. $ apt policy linux-image-4.13.0-39-generic linux-image-4.13.0-39-generic: Installed: 4.13.0-39.44 Candidate: 4.13.0-39.44 Version table: *** 4.13.0-39.44 400 400 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy intel-microcode intel-microcode: Installed: 3.20180312.0~ubuntu17.10.1 Candidate: 3.20180312.0~ubuntu17.10.1 Version table: *** 3.20180312.0~ubuntu17.10.1 500 500 http://fi.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 3.20170707.1 500 500 http://fi.archive.ubuntu.com/ubuntu artful/restricted amd64 Packages ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- 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/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in intel-microcode source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in intel-microcode source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in intel-microcode source package in Artful: Invalid Status in linux source package in Artful: Fix Committed Bug description: [Impact] * Some systems experience kernel lockups after updating to the latest intel-microcode package or when receiving updated microcode from a BIOS update. * In many cases, the lockups occur before users can reach the login screen which makes it very difficult to debug/workaround. [Test Case] * The most reliable test case currently known is to install the sssd package. Lockups may occur during package installation (disable IBPB by writing 0 to /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup will most likely occur just after booting the system up as the lock screen is displayed. [Regression Potential] * The fix is in the task switching code of the kernel so complexity of the change is relatively high. [Original Report] I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. ## Workaround ## 1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary avoid the problem: https://wiki.ubuntu.com/Kernel/KernelBootParameters 2. Install the previous version of package from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb 3. (Optional) Hold the package so that it won't be upgraded accidentally sudo apt-mark hold intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+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 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)
I may have experienced this issue also on bionic (18.04) with the current kernel version as of today (4.15.0-13.14). I upgraded one affected system with "do-release-upgrade -d". After completing the upgrade and rebooting, the system froze the same way as with the affected 17.10 kernel and microcode combination. After adding "apparmor=0" to the kernel command line the boot was successful. The system has sssd. I was not able to perform further testing today. I will try to confirm tomorrow. Or maybe someone else with an affected system is able to try bionic as well? ISOs available at http://releases.ubuntu.com/18.04/ if needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in intel-microcode source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in intel-microcode source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in intel-microcode source package in Artful: Invalid Status in linux source package in Artful: Fix Committed Bug description: [Impact] * Some systems experience kernel lockups after updating to the latest intel-microcode package or when receiving updated microcode from a BIOS update. * In many cases, the lockups occur before users can reach the login screen which makes it very difficult to debug/workaround. [Test Case] * The most reliable test case currently known is to install the sssd package. Lockups may occur during package installation (disable IBPB by writing 0 to /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup will most likely occur just after booting the system up as the lock screen is displayed. [Regression Potential] * The fix is in the task switching code of the kernel so complexity of the change is relatively high. [Original Report] I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. ## Workaround ## 1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary avoid the problem: https://wiki.ubuntu.com/Kernel/KernelBootParameters 2. Install the previous version of package from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb 3. (Optional) Hold the package so that it won't be upgraded accidentally sudo apt-mark hold intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+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 1450442] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at (null); Call Trace: [] ? audit_compare_dname_path+0x2b/0xa0
I encountered this issue on a Hetzner VPS. It is a KVM based virtual server, not VMware. After rebooting I was unable to login through ssh. Accessing the system from console was possible thugh running many commands resulted in "Killed". The kernel stack trace was the same as in the original bug report. There is no quick and dirty workaround documented yet on this bug report, so I add it. Do the following to get your system quickly back to usable state while waiting for the patched kernel: 1) disable starting "auditd" at boot (for example "chmod 000 /etc/init.d/auditd" is an easy and ugly way to do it) 2) reboot the system (in my case the "reboot" command did not work, I had to hard-reset the system) Done. -- 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/1450442 Title: Kernel Oops - unable to handle kernel NULL pointer dereference at (null); Call Trace: [] ? audit_compare_dname_path+0x2b/0xa0 Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Bug description: [Impact] Ubuntu VMWare instances running 3.13.0-51 will crash with the following backtrace: [ 12.357276] BUG: unable to handle kernel NULL pointer dereference at (null) [ 12.357886] IP: [] strlen+0x0/0x30 [ 12.358457] PGD 230fe9067 PUD 230d5c067 PMD 0 [ 12.359034] Oops: [#1] SMP [ 12.359590] Modules linked in: tcp_diag inet_diag vmw_vsock_vmci_transport vsock ip6t_REJECT xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack crct10dif_pclmul iptable_filter crc32_pclmul ip_tables ghash_clmulni_intel aesni_intel aes_x86_64 ppdev lrw x_tables gf128mul vmwgfx glue_helper ablk_helper cryptd ttm drm vmw_balloon serio_raw shpchp parport_pc lp i2c_piix4 parport mac_hid vmw_vmci psmouse mptspi vmw_pvscsi e1000 mptscsih floppy vmxnet3 mptbase [ 12.364773] CPU: 2 PID: 1718 Comm: fail2ban-server Not tainted 3.13.0-51-generic #84-Ubuntu [ 12.365587] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 04/14/2014 [ 12.367276] task: 880230fc3000 ti: 8802308c4000 task.ti: 8802308c4000 [ 12.368159] RIP: 0010:[] [] strlen+0x0/0x30 [ 12.369073] RSP: 0018:8802308c5d60 EFLAGS: 00010212 [ 12.369963] RAX: 000d RBX: 000d RCX: 2df0 [ 12.370973] RDX: 0012 RSI: RDI: [ 12.372005] RBP: 8802308c5d90 R08: 8800b9218648 R09: 8802308c5d60 [ 12.372988] R10: 0002 R11: 88023082e180 R12: 0012 [ 12.373901] R13: R14: 880231f1b3f8 R15: 8800b9218460 [ 12.374827] FS: 7f196f84c740() GS:88023fd0() knlGS: [ 12.375752] CS: 0010 DS: ES: CR0: 80050033 [ 12.376667] CR2: CR3: 000230872000 CR4: 000407e0 [ 12.377684] Stack: [ 12.378612] 810fb39b 0004 88022ff74838 [ 12.379559] 8800b9218400 8800b9218460 8802308c5df8 810fdb36 [ 12.380516] 811d56e0 00042ff74838 880231f1b3c0 88022febecf8 [ 12.381506] Call Trace: [ 12.382630] [] ? audit_compare_dname_path+0x2b/0xa0 [ 12.383784] [] __audit_inode_child+0xb6/0x330 [ 12.384912] [] ? d_instantiate+0x50/0x70 [ 12.386013] [] vfs_mknod+0x110/0x160 [ 12.387145] [] unix_bind+0x2a5/0x360 [ 12.388207] [] ? __audit_sockaddr+0x42/0x80 [ 12.389250] [] SYSC_bind+0xe0/0x120 [ 12.390297] [] ? do_page_fault+0x1a/0x70 [ 12.391303] [] SyS_bind+0xe/0x10 [ 12.392426] [] system_call_fastpath+0x1a/0x1f [ 12.393581] Code: 89 f8 48 89 e5 f6 82 40 c7 84 81 20 74 15 0f 1f 44 00 00 48 83 c0 01 0f b6 10 f6 82 40 c7 84 81 20 75 f0 5d c3 66 0f 1f 44 00 00 <80> 3f 00 55 48 89 e5 74 15 48 89 f8 0f 1f 40 00 48 83 c0 01 80 [ 12.396831] RIP [] strlen+0x0/0x30 [ 12.397812] RSP [ 12.398769] CR2: [ 12.399743] ---[ end trace 2c5a33d31a03347e ]--- We've also seen this on our precise machines that are running the backported trusty kernel. When reverting to kernel 3.13.0-49 this no longer occurs. [Test Case] 1) Run an Ubuntu VMWare instance with the affected kernel. apt-get install auditd echo "-w /etc/test" >>/etc/audit/audit.rules /etc/init.d/auditd restart apt-get install linux-headers-3.13.0-51 linux-headers-3.13.0-51-generic linux-image-3.13.0-51-generic reboot attempt to login or ssh into the host - you'll get a similar stacktrace. [Fix]
[Kernel-packages] [Bug 1930783] Re: integrity: Problem loading X.509 certificate
Also affects: Computer: Lenovo Yoga Slim 7 Pro 14ACH5 (82MS008AMX) Ubuntu version: Ubuntu 22.04.2 LTS Kernel: linux-image-5.19.0-35-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930783 Title: integrity: Problem loading X.509 certificate Status in linux package in Ubuntu: Confirmed Bug description: Following error shows on Acer machines while booting when UEFI boot is enabled. integrity: Problem loading X.509 certificate -65 The issue is discussed at https://bugzilla.opensuse.org/show_bug.cgi?id=1129471 and a patch is available at https://lkml.org/lkml/2019/7/16/23. Seems like this patch is not included in Ubuntu as I'm still getting this error. I'm using Linux Mint 20, which is based on Ubuntu 20.04. This error comes while live booting Ubuntu 20.04 and Ubuntu 18.04 also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930783/+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 2072612] Re: Lenovo touchpad intermittently stops working with i2c_designware errors
I am facing exactly same symptoms as described on my Lenovo Yoga Slim Pro 7 14ACH5. However I don't see messages containing "i2c_designware" in system 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/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors Status in Linux: Incomplete Status in linux package in Ubuntu: Opinion Bug description: Hi. When using my laptop, I frequently experience the touchpad suddenly cease working. Sometimes there's a few seconds' warning with reduced responsiveness, and sometimes it's completely sudden. I experienced this in Kubuntu 22.04, and I still experience it after upgrading to 24.04. Output from kern.log when it happens often looks like this: 2024-07-09T21:31:51.573862-04:00 machinename kernel: i2c_designware AMDI0010:00: controller timed out 2024-07-09T21:31:51.577113-04:00 machinename kernel: i2c_designware AMDI0010:00: timeout in disabling adapter 2024-07-09T21:31:51.596828-04:00 machinename kernel: i2c_designware AMDI0010:00: timeout waiting for bus ready 2024-07-09T21:32:45.928870-04:00 machinename kernel: message repeated 2652 times: [ i2c_designware AMDI0010:00: timeout waiting for bus ready] The only workaround I've found is to sleep/hibernate or shut down the laptop; it always works again on reboot. Since I upgraded to 24.04, I sometimes have the additional problem that I can't sleep the laptop when this is happening. I get errors that say "kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" when I try. Note that the problem did not happen between my most recent boot and the generation of the attached files via "ubuntu-bug linux". ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-36-generic 6.8.0-36.36 ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jul 9 22:02:03 2024 InstallationDate: Installed on 2021-11-28 (954 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82ND ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=1ae6eb8d-78a6-4fdd-affc-4d1e32c995d6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-36-generic N/A linux-backports-modules-6.8.0-36-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-06-27 (12 days ago) dmi.bios.date: 03/26/2024 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: H6CN22WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 6 13ALC6 dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrH6CN22WW(V1.15):bd03/26/2024:br1.22:efr1.22:svnLENOVO:pn82ND:pvrYoga613ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga613ALC6:skuLENOVO_MT_82ND_BU_idea_FM_Yoga613ALC6: dmi.product.family: Yoga 6 13ALC6 dmi.product.name: 82ND dmi.product.sku: LENOVO_MT_82ND_BU_idea_FM_Yoga 6 13ALC6 dmi.product.version: Yoga 6 13ALC6 dmi.sys.vendor: LENOVO modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-04-23T07:30:10 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2072612/+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
