[Kernel-packages] [Bug 1876567] Re: ubuntu 20.04 nfs page fault since Kernel 5.3 (?)
Still happens with kernel 5.4.0-54, today my (nfs-)server crashed too. How can we help to fix this issue? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1876567 Title: ubuntu 20.04 nfs page fault since Kernel 5.3 (?) Status in linux-oem-5.6 package in Ubuntu: Confirmed Bug description: Kind of a follow up/extension to https://bugs.launchpad.net/ubuntu/disco/+source/linux/+bug/1858832 == Original Bug Report (for the most part, still holds true) == RELEASE=19.3 CODENAME=tricia EDITION="Cinnamon" DESCRIPTION="Linux Mint 19.3 Tricia" DESKTOP=Gnome TOOLKIT=GTK NEW_FEATURES_URL=https://www.linuxmint.com/rel_tricia_cinnamon_whatsnew.php RELEASE_NOTES_URL=https://www.linuxmint.com/rel_tricia_cinnamon.php USER_GUIDE_URL=https://www.linuxmint.com/documentation.php GRUB_TITLE=Linux Mint 19.3 Cinnamon My home dir is mounted through nfs on a local server via nfs4 and krb5i. When stressing the mounted directory or its sub-directories (sometimes starting firefox, sometimes starting thunderbird, nearly guaranteed when compiling, sometimes the login itself), it will eventually lead to the following stack-trace. The corresponding process is then stuck and accessing the mounted directory (like calling ls) easily yields further and similar stack trace and causing the process to also stuck. Currently I am running an AMD 3950x on a ASUS Crosshair VII Hero Wifi (chipset x470). I installed Ubuntu 20.04 LTS Desktop to check if the newer kernels (5.4 + 5.6) work without issues, but sadly, they **do not**. With a little compile-stress-test, I have tested the following kernels which seem to run fine: * 4.15.0-69 * 4.15.0-70 * 4.15.0-72 * 5.0.0-32 * 5.0.0-47 (current daily driver, runs without a hassle, max test length >7d - I am writing this bug report on it) * 5.4.0-32-generic #36-Ubuntu from the proposal https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/19306320 * 5.6.0-1010-oem #10-Ubuntu SMP * 5.7.0-050700rc6-generic #202005172030 But the following kernels do not run stable: * 5.3.0-51 (Linux Mint 19.3 HWE) * 5.4.0-28 (Ubuntu 20.04) * 5.4.0-31-generic #35-Ubuntu * 5.6.0-1008 (Ubuntu 20.04 OEM) $ lspci | grep -i ether 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03 $ mount | grep filer filer:/ on /share type nfs4 (rw,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.3.55,local_lock=none,addr=192.168.2.33) filer:/home/michael on /share/home/michael type nfs4 (rw,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.3.55,local_lock=none,addr=192.168.2.33) $ cat /etc/fstab | grep -i filer filer:/ /share/ nfs4 nfsvers=4,sec=krb5i,rw,x-systemd.automount,soft,intr,tcp,noatime 0 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rootmw 2299 F pulseaudio /dev/snd/controlC2: rootmw 2299 F pulseaudio /dev/snd/controlC1: rootmw 2299 F pulseaudio /dev/snd/controlC3: rootmw 2299 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1008-oem root=/dev/mapper/vgnvme-ubuntu2004 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4 RelatedPackageVersions: linux-restricted-modules-5.6.0-1008-oem N/A linux-backports-modules-5.6.0-1008-oem N/A linux-firmware 1.187 RfKill: Tags: focal Uname: Linux 5.6.0-1008-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3004 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string
[Kernel-packages] [Bug 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904848 Title: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: [Impact] unloading ib_ipoib causes a call trace to be logged in kernel buffer. bisecting the bionic kernel reveals that this issue was discovered by 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() in version 4.15.0-59.66 [test case] # modprobe ib_ipoib # modprobe ib_ipoib -r # dmesg [ 306.277717] [ cut here ] [ 306.277738] WARNING: CPU: 10 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.277739] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf [ 306.277790] serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core scsi_transport_sas ptp pps_core devlink [ 306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 4.15.0-124-generic #127-Ubuntu [ 306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [ 306.277823] RIP: 0010:__flush_work+0x1f8/0x210 [ 306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286 [ 306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 0006 [ 306.277829] RDX: RSI: 99429ef16498 RDI: 99429ef16490 [ 306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 0004 [ 306.277832] R10: e263a058c1c0 R11: 0001 R12: 993a5c3d8ec8 [ 306.277833] R13: 0001 R14: bdeb47ecfd78 R15: b00a9800 [ 306.277835] FS: 7fa1124a9540() GS:99429ef0() knlGS: [ 306.277837] CS: 0010 DS: ES: CR0: 80050033 [ 306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 001606e0 [ 306.277840] Call Trace: [ 306.277850] __cancel_work_timer+0x136/0x1b0 [ 306.277881] ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core] [ 306.277886] cancel_delayed_work_sync+0x13/0x20 [ 306.277909] mlx5e_detach_netdev+0x83/0x90 [mlx5_core] [ 306.277931] mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core] [ 306.277941] mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib] [ 306.277948] ipoib_remove_one+0xe4/0x180 [ib_ipoib] [ 306.277965] ib_unregister_client+0x171/0x1e0 [ib_core] [ 306.277972] ipoib_cleanup_module+0x15/0x2f [ib_ipoib] [ 306.277978] SyS_delete_module+0x1ab/0x2d0 [ 306.277983] do_syscall_64+0x73/0x130 [ 306.277989] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 306.277992] RIP: 0033:0x7fa111fc1047 [ 306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 00b0 [ 306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 7fa111fc1047 [ 306.277997] RDX: RSI: 0800 RDI: 5614be46cd08 [ 306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: [ 306.278000] R10: 7fa11203dc40 R11: 0206 R12: 5614be46cd08 [ 306.278002] R13: 0001 R14: 5614be46cd08 R15: 7ffc0db33680 [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 [ 306.278035] ---[ end trace 652f7759937172a2 ]--- [ 306.646061] [ cut here ] [ 306.646077] WARNING: CPU: 6 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.646078] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Expired Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+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 1904764] Re: failed boot mount, and systemd ordering cycle on zfs-import.target
BTW, I ran the following and that seems to have solved the missing bpool. zpool set cachefile=/etc/zfs/zpool.cache bpool zpool set cachefile=/etc/zfs/zpool.cache rpool update-initramfs -u -k all I have a hunch the zpool.cache file is getting out of sync with the initramfs one..? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1904764 Title: failed boot mount, and systemd ordering cycle on zfs-import.target Status in zfs-linux package in Ubuntu: New Bug description: On a new Ubuntu 20.10 ZoL root I frequently get boot failures, and I see these errors: [ 11.353930] systemd[1]: boot.mount: Mount process exited, code=exited, status=1/FAILURE [ 11.353934] systemd[1]: boot.mount: Failed with result 'exit-code'. [ 11.354267] systemd[1]: Failed to mount /boot. [ 11.354307] systemd[1]: Dependency failed for /boot/efi. [ 11.354327] systemd[1]: Dependency failed for /boot/grub. [ 11.354344] systemd[1]: Dependency failed for Local File Systems. [ 11.354365] systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. [ 11.354367] systemd[1]: local-fs.target: Triggering OnFailure= dependencies. [ 11.355088] systemd[1]: var-lib.mount: Found ordering cycle on zfs-import.target/start [ 11.355090] systemd[1]: var-lib.mount: Found dependency on zfs-import-cache.service/start [ 11.355091] systemd[1]: var-lib.mount: Found dependency on zfs-load-module.service/start [ 11.355093] systemd[1]: var-lib.mount: Found dependency on cryptsetup.target/start [ 11.355094] systemd[1]: var-lib.mount: Found dependency on systemd-cryptsetup@cryptoswap.service/start [ 11.355096] systemd[1]: var-lib.mount: Found dependency on systemd-random-seed.service/start [ 11.355097] systemd[1]: var-lib.mount: Found dependency on var-lib.mount/start [ 11.355099] systemd[1]: var-lib.mount: Job zfs-import.target/start deleted to break ordering cycle starting with var-lib.mount/start [ 11.355819] systemd[1]: boot-grub.mount: Job boot-grub.mount/start failed with result 'dependency'. [ 11.355823] systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed with result 'dependency'. Journalctl shows "filesystem 'bpool/BOOT/ubuntu_o9gk00' cannot be mounted, unable to open the dataset" for boot.mount I can manually start boot.mount from the console, which then lets the boot process complete. N.B. "zfs list" is NAME USED AVAIL REFER MOUNTPOINT bpool 402M 1.36G 96K /boot bpool/BOOT 401M 1.36G 96K none bpool/BOOT/ubuntu_o9gk00 401M 1.36G 201M /boot rpool 171G 720G 192K / rpool/ROOT9.26G 720G 192K none rpool/ROOT/ubuntu_1.57G 720G 5.16G / rpool/ROOT/ubuntu_o9gk00 7.69G 720G 4.24G / rpool/ROOT/ubuntu_o9gk00/srv 192K 720G 192K /srv rpool/ROOT/ubuntu_o9gk00/usr 1.02M 720G 192K /usr rpool/ROOT/ubuntu_o9gk00/usr/local 852K 720G 388K /usr/local rpool/ROOT/ubuntu_o9gk00/var 2.09G 720G 192K /var rpool/ROOT/ubuntu_o9gk00/var/games 192K 720G 192K /var/games rpool/ROOT/ubuntu_o9gk00/var/lib 1.85G 720G 1.42G /var/lib rpool/ROOT/ubuntu_o9gk00/var/lib/AccountsService 1.39M 720G 496K /var/lib/AccountsService rpool/ROOT/ubuntu_o9gk00/var/lib/NetworkManager 3.39M 720G 292K /var/lib/NetworkManager rpool/ROOT/ubuntu_o9gk00/var/lib/apt 87.2M 720G 78.0M /var/lib/apt rpool/ROOT/ubuntu_o9gk00/var/lib/dpkg 148M 720G 63.6M /var/lib/dpkg rpool/ROOT/ubuntu_o9gk00/var/log 223M 720G 94.2M /var/log rpool/ROOT/ubuntu_o9gk00/var/mail 1.19M 720G 224K /var/mail rpool/ROOT/ubuntu_o9gk00/var/snap 940K 720G 500K /var/snap rpool/ROOT/ubuntu_o9gk00/var/spool26.7M 720G 5.52M /var/spool rpool/ROOT/ubuntu_o9gk00/var/www 192K 720G 192K /var/www rpool/USERDATA 162G 720G 192K / rpool/USERDATA/chris_hwz0bd162G 720G 156G /home/chris rpool/USERDATA/root_hwz0bd2.91M 720G 804K /root rpool/keystore 518M 720G 48.1M - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904764/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1785207] Re: openat03 in ubuntu_ltp_syscall failed with Trusty
still visible on 4.4.0-1082.86 aws ** Tags added: 4.4 aws sru-20201109 -- 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/1785207 Title: openat03 in ubuntu_ltp_syscall failed with Trusty Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Triaged Bug description: <<>> tag=openat03 stime=1533289807 cmdline="openat03" contacts="" analysis=exit <<>> openat030 TINFO : creating a file with O_TMPFILE flag incrementing stop openat030 TINFO : writing data to the file openat030 TINFO : file size is '4096' openat030 TINFO : looking for the file in '.' openat030 TINFO : file not found, OK openat030 TINFO : renaming '/tmp/ltp-5saSOZV2Gx/opea7u155/#286254 (deleted)' -> 'tmpfile' openat030 TINFO : found a file: tmpfile openat031 TPASS : single file tests passed openat030 TINFO : create files in multiple directories openat030 TINFO : removing test directories openat030 TINFO : writing/reading temporary files openat030 TINFO : closing temporary files openat032 TPASS : multiple files tests passed openat030 TINFO : create multiple directories, link files into them openat030 TINFO : and check file permissions openat033 TFAIL : openat03.c:223: file mode read 0, but expected <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-153-generic 3.13.0-153.203 ProcVersionSignature: User Name 3.13.0-153.203-generic 3.13.11-ckt39 Uname: Linux 3.13.0-153-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 3 07:50 seq crw-rw 1 root audio 116, 33 Aug 3 07:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Aug 3 09:49:41 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro RelatedPackageVersions: linux-restricted-modules-3.13.0-153-generic N/A linux-backports-modules-3.13.0-153-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1785207/+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 1904953] 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/1904953 Title: USB2.0 HUB only works after an USB device is connected Status in linux package in Ubuntu: Confirmed Bug description: The USB hub identified as: "214b:7000 USB2.0 HUB" presents a problem on Linux where often it is only detected after another device (for example a mouse) is connected to it. On the computer's firmware screen and configuration, and on Windows, the hub works fine: once connected, it is detected and devices connected on it are detected. On Linux, most of the times nothing happens or only the hub is detected (not the devices connected to it). After one of the devices is disconnected and reconnected, or another USB device is connected in the hub, then the hub and all devices connected to it are detected at once. I believe this is a problem related to the Linux kernel because I never observed this behaviour on the computer's firmware or on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 19 23:54:44 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1255 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x10 nbd.nbds_max=2 nbd.max_part=127 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-22 (333 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904953/+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 1904953] [NEW] USB2.0 HUB only works after an USB device is connected
Public bug reported: The USB hub identified as: "214b:7000 USB2.0 HUB" presents a problem on Linux where often it is only detected after another device (for example a mouse) is connected to it. On the computer's firmware screen and configuration, and on Windows, the hub works fine: once connected, it is detected and devices connected on it are detected. On Linux, most of the times nothing happens or only the hub is detected (not the devices connected to it). After one of the devices is disconnected and reconnected, or another USB device is connected in the hub, then the hub and all devices connected to it are detected at once. I believe this is a problem related to the Linux kernel because I never observed this behaviour on the computer's firmware or on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 19 23:54:44 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1255 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x10 nbd.nbds_max=2 nbd.max_part=127 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-22 (333 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1904953 Title: USB2.0 HUB only works after an USB device is connected Status in linux package in Ubuntu: Confirmed Bug description: The USB hub identified as: "214b:7000 USB2.0 HUB" presents a problem on Linux where often it is only detected after another device (for example a mouse) is connected to it. On the computer's firmware screen and configuration, and on Windows, the hub works fine: once connected, it is detected and devices connected on it are detected. On Linux, most of the times nothing happens or only the hub is detected (not the devices connected to it). After one of the devices is disconnected and reconnected, or another USB device is connected in the hub, then the hub and all devices connected to it are detected at once. I believe this is a problem related to the Linux kernel because I never observed this behaviour on the computer's firmware or on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 19 23:54:44 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1255 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x10 nbd.nbds_max=2 nbd.max_part=127 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic
[Kernel-packages] [Bug 1904922] Re: External monitor undetected over hdmi
Does the monitor work before the udpate? What kind of monitor? -- 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/1904922 Title: External monitor undetected over hdmi Status in linux package in Ubuntu: Confirmed Bug description: After the latest updates when I plug in an external monitor over HDMI it doesn't pick it up. Unplugging and re-plugging the monitor seems to connect but immediately drops into power-saving mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rhys 6253 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 20:07:19 2020 InstallationDate: Installed on 2019-10-12 (404 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20KH007BUK ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-02 (78 days ago) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH007BUK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KH007BUK:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007BUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH007BUK dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904922/+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 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome
@Mike, sorry Im busy on others. Because can't find the kernel version in the last logs. Did you try the mainline kernel!? and is the issue triggered again!? -- 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/1895449 Title: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome Status in linux package in Ubuntu: In Progress Bug description: A few issues: 1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1, the system sometimes gets disconnected with the network and I get the following error in syslog: iwlwifi: BIOS contains WGDS but no WRDS It is unclear if this is the cause of the problem, but this is likely related to kernel. 2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will sometimes cause xorg freeze. The exact cause is unknown. (Mouse, control all freeze for 5-10 seconds) 3) After Wake up from sleep got the following error on screen sof-audio-pci error: no reply expected, received 0x0 iwlwifi: BIOS contains WGDS but no WRDS 4) After wake up from a long sleep session, sometimes chrome will not render web page correctly or even freeze. It is unclear if its a Chrome problem, or a Nvidia problem, or a Kernel Problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gao1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 09:14:36 2020 InstallationDate: Installed on 2020-08-25 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 7591 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+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 1889342] Re: Thunderbolt Dock Loses Monitors
@rhpot1991, ###Could you please help to try this!? https://kernel.ubuntu.com//~kernel-ppa/mainline/drm-tip/current/amd64/ ###And this 1. Please enable the proposed and sudo apt update. 2. sudo apt install linux-image-unsigned-5.6.0-1035-oem. -- 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/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+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 1889342] Re: Thunderbolt Dock Loses Monitors
And this 1. Please enable the proposed and sudo apt update. 2. sudo apt install linux-image-unsigned-5.6.0-1035-oem. -- 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/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+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 1889342] Re: Thunderbolt Dock Loses Monitors
@rhpot1991, Could you please help to try this!? https://kernel.ubuntu.com//~kernel-ppa/mainline/drm-tip/current/amd64/ -- 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/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+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 1903288] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-11-19 20:25 EDT--- Hi, I think that's the only feature patch required. There's not a lot because at this stage it's all based on static keys. So unlike the OpenPower secure boot, there's no code to interact with keys stored in firmware. There is one config change that we also need: because there are no keys advertised by firmware or early boot, and because lockdown requires that kexec kernels be signed, we need to get the kernel signing key into the .ima keyring somehow. One way to do this is at boot with IMA_X509_PATH, but it can also be done at runtime. In either case, however, the CA that signs the kernel signing key needs to be built in to the kernel's .builtin_trusted_keys keyring. I haven't attempted this because I don't know much about how the signing process works in your build infrastructure, but I'm happy to help. Of course, I expect there will also be bug fixes later! Kind regards, Daniel -- 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/1903288 Title: Power guest secure boot with static keys: kernel portion Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #2 - Daniel John Axtens - 2020-11-05 20:15:10 == This is the kernel side of changes needed for LPAR/guest secure boot. Because Ubuntu keeps its kernels so wonderfully up to date, I don't think there are any extra patches you need to pick up. (I'll double- check against the 21.04 tree once my git pulls finish!) However, we potentially need some configuration changes to make sure kexec-ing into a crashdump kernel still works. Because Lockdown requires that kexec kernels are signed by a key trusted by IMA, the public key for used for signing the kdump kernel needs to be in the IMA keyring or the platform keyring. For host secure boot (and in the UEFI case), it's loaded into the platform keyring. But in the case of guest secure boot with static keys, it's not loaded into the platform keyring so it needs to be loaded into the IMA keyring. This is easy enough to do. Firstly, load the Secure Boot CA into the .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS property. We assume the key used to sign the kernel is signed by this CA. Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the .primary_trusted_keys keyring to be loaded into the IMA keyring. Then set IMA_X509_PATH to provide a path to the signing key on installed file system. (It may also be possible to do this step in userspace, so long as the CA is trusted by the kernel.) Then that key will be loaded into the .ima keyring at boot and be used to appraise the kexec kernel for crashdumps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+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 1896482] Re: acpi event detection crashes
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: = SRU Justification = [Impact] The bug causes the EC driver to fail and ACPI events are no longer handled by Linux kernel, i.e lid close no longer triggers suspends. [Fix] Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid initialisation failures. The other three patches are prerequisite to apply 03e9a0e05739cf on focal kernel. [Test] Tested with Lenovo ThinkPad X1 Carbon Gen 8 [Regression Potential] Low. The patches were cherry-picked from mainline kernel (two since 5.5 and two since 5.7) = Original Bug Report = Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: Sep 20 11:35:33 laxmi kernel: [232492.303654] ? acpi_os_release_lock+0xe/0x10 Sep 20 11:35:33 laxmi kernel:
[Kernel-packages] [Bug 1904941] [NEW] Groovy update: v5.8.18 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.8.18 upstream stable release
from git://git.kernel.org/
netfilter: nftables_offload: KASAN slab-out-of-bounds Read in
nft_flow_rule_create
io_uring: don't run task work on an exiting task
io_uring: allow timeout/poll/files killing to take task into account
io_uring: move dropping of files into separate helper
io_uring: stash ctx task reference for SQPOLL
io_uring: unconditionally grab req->task
io_uring: return cancelation status from poll/timeout/files handlers
io_uring: enable task/files specific overflow flushing
io_uring: don't rely on weak ->files references
io_uring: reference ->nsproxy for file table commands
io_wq: Make io_wqe::lock a raw_spinlock_t
io-wq: fix use-after-free in io_wq_worker_running
io_uring: no need to call xa_destroy() on empty xarray
io_uring: Fix use of XArray in __io_uring_files_cancel
io_uring: Fix XArray usage in io_uring_add_task_file
io_uring: Convert advanced XArray uses to the normal API
scripts/setlocalversion: make git describe output more reliable
efi/arm64: libstub: Deal gracefully with EFI_RNG_PROTOCOL failure
fs/kernel_read_file: Remove FIRMWARE_EFI_EMBEDDED enum
arm64: Run ARCH_WORKAROUND_1 enabling code on all CPUs
arm64: Run ARCH_WORKAROUND_2 enabling code on all CPUs
arm64: link with -z norelro regardless of CONFIG_RELOCATABLE
x86/PCI: Fix intel_mid_pci.c build error when ACPI is not enabled
x86, powerpc: Rename memcpy_mcsafe() to copy_mc_to_{user, kernel}()
UBUNTU: [Config] update config for ARCH_HAS_COPY_MC
x86/copy_mc: Introduce copy_mc_enhanced_fast_string()
bnxt_en: Check abort error state in bnxt_open_nic().
bnxt_en: Fix regression in workqueue cleanup logic in bnxt_remove_one().
bnxt_en: Invoke cancel_delayed_work_sync() for PFs also.
bnxt_en: Re-write PCI BARs after PCI fatal error.
bnxt_en: Send HWRM_FUNC_RESET fw command unconditionally.
chelsio/chtls: fix deadlock issue
chelsio/chtls: fix memory leaks in CPL handlers
chelsio/chtls: fix tls record info to user
cxgb4: set up filter action after rewrites
gtp: fix an use-before-init in gtp_newlink()
ibmveth: Fix use of ibmveth in a bridge.
ibmvnic: fix ibmvnic_set_mac
mlxsw: core: Fix memory leak on module removal
netem: fix zero division in tabledist
net: hns3: Clear the CMDQ registers before unmapping BAR region
net: ipa: command payloads already mapped
net/sched: act_mpls: Add softdep on mpls_gso.ko
r8169: fix issue with forced threading in combination with shared interrupts
ravb: Fix bit fields checking in ravb_hwtstamp_get()
tcp: Prevent low rmem stalls with SO_RCVLOWAT.
tipc: fix memory leak caused by tipc_buf_append()
net: protect tcf_block_unbind with block lock
erofs: avoid duplicated permission check for "trusted." xattrs
arch/x86/amd/ibs: Fix re-arming IBS Fetch
x86/traps: Fix #DE Oops message regression
x86/xen: disable Firmware First mode for correctable memory errors
PCI: aardvark: Fix initialization with old Marvell's Arm Trusted Firmware
ata: ahci: mvebu: Make SATA PHY optional for Armada 3720
fuse: fix page dereference after free
bpf: Fix comment for helper bpf_current_task_under_cgroup()
evm: Check size of security.evm before using it
p54: avoid accessing the data mapped to streaming DMA
cxl: Rework error message for incompatible slots
RDMA/addr: Fix race with netevent_callback()/rdma_addr_cancel()
mtd: lpddr: Fix bad logic in print_drs_error
drm/i915/gem: Serialise debugfs i915_gem_objects with ctx->mutex
serial: qcom_geni_serial: To correct QUP Version detection logic
serial: pl011: Fix lockdep splat when handling magic-sysrq interrupt
PM: runtime: Fix timer_expires data type on 32-bit arches
ata: sata_rcar: Fix DMA boundary mask
xen/gntdev.c: Mark pages as dirty
openrisc: Fix issue with get_user for 64-bit values
misc: rtsx: do not setting OC_POWER_DOWN reg in rtsx_pci_init_ocp()
phy: marvell: comphy: Convert internal SMCC firmware return codes to errno
Linux 5.8.18
UBUNTU: upstream stable to v5.8.18
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Groovy)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
[Kernel-packages] [Bug 1904912] Re: linux-riscv 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu
** Also affects: linux-riscv (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux-riscv (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: linux-riscv (Ubuntu Groovy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-riscv (Ubuntu Groovy) Importance: Undecided => High ** Changed in: linux-riscv (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1904912 Title: linux-riscv 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in linux-riscv source package in Groovy: Fix Committed Bug description: [Impact] linux-riscv won't boot on some memory configurations. [Test case] linux-riscv boots with the qemu line below. [Potential Regression] We might see some stack traces, and memory use (for init data) will slightly increase. = 5.8.0-9.11 and other v5.8 kernels all fail to boot in qemu with opensbi and qemu. I'm booting a cloud-image with kenrel install like this: qemu-system-riscv64 -machine virt -m 2048 -smp 4 -kernel /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -device loader,file=/usr/lib/u-boot/qemu- riscv64_smode/uboot.elf,addr=0x8020 -device virtio-blk- device,drive=vda -drive file=focal-riscv64-20200422.qcow2,id=vda -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 on groovy host. v5.4 kernels from focal-updates boots; upgrading to groovy/-upstead/-proposed kernel the boot fails. The image has linux-generic installed with u-boot-menu for the extlinux.conf based boot menu kernel just panics. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1904912/+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 1881322] Re: Touchpad not detected in 'Lenovo V15-IIL model 82C5' after installing Ubuntu 20.04
I'm facing the same problem. I just finished installing 20.04, and not only wireless (which is a more common issue), even my touchpad does not work. In fact, it has not been detected as I followed this: https://wiki.ubuntu.com/DebuggingTouchpadDetection and `cat /proc/bus/input/devices` does not list anything containing `touchpad`. Hope there is a workaround for this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881322 Title: Touchpad not detected in 'Lenovo V15-IIL model 82C5' after installing Ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 is installed in a brand new Lenovo V15-IIL alongside Windows 10. According to lenovo's support page, the driver for windows is Synaptics 19.5.10.149_Elan 22.4.18.1. In windows the touchpad works fine. This model has two options in BIOS regarding Fn Keys, a "Smart Fn key" that toogles the Fn key on/off each time you press it and a "Foolproof Fn Key" that maps the Fn key to Ctrl when you press a combinations of keys that does not have a Fn assigned. When I enable the "foolproof fn key" in the BIOS, the Fn + F1...F12 and the sound driver stop working (i dont have sound, i can't change the volume and the volume icon in the GUI does not show). Fn+F6 (to enable/disable touchpad) can't enable it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fdadam 1434 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 29 13:08:24 2020 InstallationDate: Installed on 2020-05-28 (1 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 002: ID 0458:0186 KYE Systems Corp. (Mouse Systems) Genius DX-120 Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82C5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=fd0c8ed1-6032-467c-9902-3094e6740be8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW 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: Lenovo V15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL: dmi.product.family: V15-IIL dmi.product.name: 82C5 dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL dmi.product.version: Lenovo V15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881322/+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 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
I also note that you are testing with 5.10.0-0, which was based on 5.10-rc1. We have 5.10.0-4 in the ppa now based on -rc4, it is built for hirsute and not groovy though. I'd recommend trying that version to see if there was an upstream bug which has already been fixed. -- 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/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+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 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
I've attached our configs for the Ubuntu 5.8 and 5.10 kernels along with a diff between these configs. I didn't see anything in the diff which looked like an obvious candidate for causing the boot problems. Please let me know if you see something there which should be changed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+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 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
** Patch added: "Diff between Ubuntu 5.8 and 5.10 ppc64el kernel configs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904906/+attachment/5436111/+files/ppc64el-config.flavour.generic.diff -- 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/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+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 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
** Attachment added: "Ubuntu ppc64el kernel config for 5.10" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904906/+attachment/5436110/+files/ppc64el-config.flavour.generic-5.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+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 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
** Attachment added: "Ubuntu ppc64el kernel config for 5.8" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904906/+attachment/5436109/+files/ppc64el-config.flavour.generic-5.8 -- 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/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+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 1904922] 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/1904922 Title: External monitor undetected over hdmi Status in linux package in Ubuntu: Confirmed Bug description: After the latest updates when I plug in an external monitor over HDMI it doesn't pick it up. Unplugging and re-plugging the monitor seems to connect but immediately drops into power-saving mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rhys 6253 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 20:07:19 2020 InstallationDate: Installed on 2019-10-12 (404 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20KH007BUK ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-02 (78 days ago) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH007BUK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KH007BUK:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007BUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH007BUK dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904922/+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 1904912] Re: linux-riscv 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu
** Summary changed: - linux 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu + linux-riscv 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu ** Description changed: - 5.8.0-9.11 and other v5.8 kernels all fail to boot in qemu with opensbi - and qemu. + [Impact] + linux-riscv won't boot on some memory configurations. + + [Test case] + linux-riscv boots with the qemu line below. + + [Potential Regression] + We might see some stack traces, and memory use (for init data) will slightly increase. + + + = + + + 5.8.0-9.11 and other v5.8 kernels all fail to boot in qemu with opensbi and qemu. I'm booting a cloud-image with kenrel install like this: qemu-system-riscv64 -machine virt -m 2048 -smp 4 -kernel /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -device loader,file=/usr/lib/u-boot/qemu-riscv64_smode/uboot.elf,addr=0x8020 -device virtio-blk-device,drive=vda -drive file=focal- riscv64-20200422.qcow2,id=vda -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 on groovy host. v5.4 kernels from focal-updates boots; upgrading to groovy/-upstead/-proposed kernel the boot fails. The image has linux-generic installed with u-boot-menu for the extlinux.conf based boot menu kernel just panics. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1904912 Title: linux-riscv 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu Status in linux-riscv package in Ubuntu: New Bug description: [Impact] linux-riscv won't boot on some memory configurations. [Test case] linux-riscv boots with the qemu line below. [Potential Regression] We might see some stack traces, and memory use (for init data) will slightly increase. = 5.8.0-9.11 and other v5.8 kernels all fail to boot in qemu with opensbi and qemu. I'm booting a cloud-image with kenrel install like this: qemu-system-riscv64 -machine virt -m 2048 -smp 4 -kernel /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -device loader,file=/usr/lib/u-boot/qemu- riscv64_smode/uboot.elf,addr=0x8020 -device virtio-blk- device,drive=vda -drive file=focal-riscv64-20200422.qcow2,id=vda -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 on groovy host. v5.4 kernels from focal-updates boots; upgrading to groovy/-upstead/-proposed kernel the boot fails. The image has linux-generic installed with u-boot-menu for the extlinux.conf based boot menu kernel just panics. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1904912/+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 1904922] [NEW] External monitor undetected over hdmi
Public bug reported: After the latest updates when I plug in an external monitor over HDMI it doesn't pick it up. Unplugging and re-plugging the monitor seems to connect but immediately drops into power-saving mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rhys 6253 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 20:07:19 2020 InstallationDate: Installed on 2019-10-12 (404 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20KH007BUK ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-02 (78 days ago) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH007BUK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KH007BUK:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007BUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH007BUK dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th 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/1904922 Title: External monitor undetected over hdmi Status in linux package in Ubuntu: New Bug description: After the latest updates when I plug in an external monitor over HDMI it doesn't pick it up. Unplugging and re-plugging the monitor seems to connect but immediately drops into power-saving mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rhys 6253 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 20:07:19 2020 InstallationDate: Installed on 2019-10-12 (404 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20KH007BUK ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-02 (78 days ago) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH007BUK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KH007BUK:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007BUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH007BUK dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904922/+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 1904860] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1904860 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904860 Title: QCA9377 802.11ac Wireless Network Adapter-Network unclaimed on every ubuntu os Status in linux package in Ubuntu: Incomplete Bug description: 4 months ago,I installed ubuntu on my lenovo E41-25 notebook. Working damn fine going good. recently i updated my system via `sudo apt update && sudo apt upgrade`. Thats all i do. Now,my wifi adapter not working properly. harish@harish$ sudo dmesg | grep ath10k [ 12.347183] ath10k_pci :02:00.0: failed to iomap BAR0 [ 12.347239] ath10k_pci :02:00.0: failed to claim device: -5 [ 12.347355] ath10k_pci: probe of :02:00.0 failed with error -5 harish@harish$ lshw -c network WARNING: you should run this program as super-user. *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:01:00.0 logical name: enp1s0 version: 15 serial: 9c:5a:44:44:f4:41 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:30 ioport:3000(size=256) memory:f0404000-f0404fff memory:f040-f0403fff *-network UNCLAIMED description: Network controller product: QCA9377 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:02:00.0 version: 31 width: 64 bits clock: 33MHz capabilities: cap_list configuration: latency=0 *-network description: Ethernet interface physical id: 1 bus info: usb@2:3 logical name: usb0 serial: ca:74:69:53:09:2a capabilities: ethernet physical configuration: broadcast=yes driver=rndis_host driverversion=22-Aug-2005 firmware=RNDIS device ip=192.168.42.225 link=yes multicast=yes harish@harish$ lsmod Module Size Used by rndis_host 20480 0 cdc_ether 20480 1 rndis_host usbnet 45056 2 rndis_host,cdc_ether mii20480 1 usbnet cdc_acm40960 0 rfcomm 81920 4 cmac 16384 2 algif_hash 16384 1 algif_skcipher 16384 1 af_alg 24576 6 algif_hash,algif_skcipher bnep 24576 2 nls_iso8859_1 16384 1 edac_mce_amd 32768 0 kvm_amd98304 0 ccp86016 1 kvm_amd kvm 663552 1 kvm_amd crct10dif_pclmul 16384 1 ghash_clmulni_intel16384 0 snd_hda_codec_conexant28672 1 uvcvideo 98304 0 snd_hda_codec_generic81920 1 snd_hda_codec_conexant aesni_intel 372736 3 amdgpu 4579328 21 ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_conexant videobuf2_vmalloc 20480 1 uvcvideo videobuf2_memops 20480 1 videobuf2_vmalloc snd_hda_codec_hdmi 61440 1 crypto_simd16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel snd_hda_intel 53248 4 snd_intel_dspcfg 24576 1 snd_hda_intel snd_hda_codec 135168 4 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel videobuf2_v4l2 24576 1 uvcvideo snd_hda_core 90112 5 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec videobuf2_common 49152 2 videobuf2_v4l2,uvcvideo videodev 225280 3 videobuf2_v4l2,uvcvideo,videobuf2_common glue_helper16384 1 aesni_intel amd_iommu_v2 20480 1 amdgpu snd_hwdep 20480 1 snd_hda_codec mc 53248 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
[Kernel-packages] [Bug 1904914] [NEW] Xenial update: v4.4.244 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v4.4.244 upstream stable release
from git://git.kernel.org/
ring-buffer: Fix recursion protection transitions between interrupt context
gfs2: Wake up when sd_glock_disposal becomes zero
mm: mempolicy: fix potential pte_unmap_unlock pte error
time: Prevent undefined behaviour in timespec64_to_ns()
btrfs: reschedule when cloning lots of extents
net: xfrm: fix a race condition during allocing spi
perf tools: Add missing swap for ino_generation
ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context
can: dev: __can_get_echo_skb(): fix real payload length return value for RTR
frames
can: can_create_echo_skb(): fix echo skb generation: always use skb_clone()
can: peak_usb: add range checking in decode operations
can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
Btrfs: fix missing error return if writeback for extent buffer never started
i40e: Wrong truncation from u16 to u8
i40e: Fix of memory leak and integer truncation in i40e_virtchnl.c
ath9k_htc: Use appropriate rs_datalen type
usb: gadget: goku_udc: fix potential crashes in probe
gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
gfs2: check for live vs. read-only file system in gfs2_fitrim
drm/amdgpu: perform srbm soft reset always on SDMA resume
mac80211: fix use of skb payload instead of header
cfg80211: regulatory: Fix inconsistent format argument
iommu/amd: Increase interrupt remapping table limit to 512 entries
xfs: fix a missing unlock on error in xfs_fs_map_blocks
of/address: Fix of_node memory leak in of_dma_is_coherent
cosa: Add missing kfree in error path of cosa_write
perf: Fix get_recursion_context()
ext4: correctly report "not supported" for {usr,grp}jquota when !CONFIG_QUOTA
ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
mei: protect mei_cl_mtu from null dereference
ocfs2: initialize ip_next_orphan
don't dump the threads that had been already exiting when zapped.
drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
pinctrl: amd: use higher precision for 512 RtcClk
pinctrl: amd: fix incorrect way to disable debounce filter
swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
IPv6: Set SIT tunnel hard_header_len to zero
net/af_iucv: fix null pointer dereference on shutdown
net/x25: Fix null-ptr-deref in x25_connect
net: Update window_clamp if SOCK_RCVBUF is set
random32: make prandom_u32() output unpredictable
x86/speculation: Allow IBPB to be conditionally enabled on CPUs with always-on
STIBP
xen/events: avoid removing an event channel while handling it
xen/events: add a proper barrier to 2-level uevent unmasking
xen/events: fix race in evtchn_fifo_unmask()
xen/events: add a new "late EOI" evtchn framework
xen/blkback: use lateeoi irq binding
xen/netback: use lateeoi irq binding
xen/scsiback: use lateeoi irq binding
xen/pciback: use lateeoi irq binding
xen/events: switch user event channels to lateeoi model
xen/events: use a common cpu hotplug hook for event channels
xen/events: defer eoi in case of excessive number of events
xen/events: block rogue events for some time
Revert "kernel/reboot.c: convert simple_strtoul to kstrtoint"
reboot: fix overflow parsing reboot cpu number
ext4: fix leaking sysfs kobject after failed mount
Convert trailing spaces and periods in path components
Linux 4.4.244
UBUNTU: upstream stable to v4.4.244
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
I also tried this on my pi400 and confirmed I can see and connect to bluetooth devices after updating to bluez 5.55-0ubuntu1.1 from groovy- proposed ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Committed Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1904860] Re: QCA9377 802.11ac Wireless Network Adapter-Network unclaimed on every ubuntu os
** Package changed: ubuntu => linux (Ubuntu) -- 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/1904860 Title: QCA9377 802.11ac Wireless Network Adapter-Network unclaimed on every ubuntu os Status in linux package in Ubuntu: New Bug description: 4 months ago,I installed ubuntu on my lenovo E41-25 notebook. Working damn fine going good. recently i updated my system via `sudo apt update && sudo apt upgrade`. Thats all i do. Now,my wifi adapter not working properly. harish@harish$ sudo dmesg | grep ath10k [ 12.347183] ath10k_pci :02:00.0: failed to iomap BAR0 [ 12.347239] ath10k_pci :02:00.0: failed to claim device: -5 [ 12.347355] ath10k_pci: probe of :02:00.0 failed with error -5 harish@harish$ lshw -c network WARNING: you should run this program as super-user. *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:01:00.0 logical name: enp1s0 version: 15 serial: 9c:5a:44:44:f4:41 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:30 ioport:3000(size=256) memory:f0404000-f0404fff memory:f040-f0403fff *-network UNCLAIMED description: Network controller product: QCA9377 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:02:00.0 version: 31 width: 64 bits clock: 33MHz capabilities: cap_list configuration: latency=0 *-network description: Ethernet interface physical id: 1 bus info: usb@2:3 logical name: usb0 serial: ca:74:69:53:09:2a capabilities: ethernet physical configuration: broadcast=yes driver=rndis_host driverversion=22-Aug-2005 firmware=RNDIS device ip=192.168.42.225 link=yes multicast=yes harish@harish$ lsmod Module Size Used by rndis_host 20480 0 cdc_ether 20480 1 rndis_host usbnet 45056 2 rndis_host,cdc_ether mii20480 1 usbnet cdc_acm40960 0 rfcomm 81920 4 cmac 16384 2 algif_hash 16384 1 algif_skcipher 16384 1 af_alg 24576 6 algif_hash,algif_skcipher bnep 24576 2 nls_iso8859_1 16384 1 edac_mce_amd 32768 0 kvm_amd98304 0 ccp86016 1 kvm_amd kvm 663552 1 kvm_amd crct10dif_pclmul 16384 1 ghash_clmulni_intel16384 0 snd_hda_codec_conexant28672 1 uvcvideo 98304 0 snd_hda_codec_generic81920 1 snd_hda_codec_conexant aesni_intel 372736 3 amdgpu 4579328 21 ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_conexant videobuf2_vmalloc 20480 1 uvcvideo videobuf2_memops 20480 1 videobuf2_vmalloc snd_hda_codec_hdmi 61440 1 crypto_simd16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel snd_hda_intel 53248 4 snd_intel_dspcfg 24576 1 snd_hda_intel snd_hda_codec 135168 4 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel videobuf2_v4l2 24576 1 uvcvideo snd_hda_core 90112 5 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec videobuf2_common 49152 2 videobuf2_v4l2,uvcvideo videodev 225280 3 videobuf2_v4l2,uvcvideo,videobuf2_common glue_helper16384 1 aesni_intel amd_iommu_v2 20480 1 amdgpu snd_hwdep 20480 1 snd_hda_codec mc 53248 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common snd_pcm 106496 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core btusb 57344 0 btrtl 24576 1 btusb ath10k_pci 49152 0 btbcm 16384 1 btusb btintel24576 1 btusb snd_seq_midi 20480 0 snd_seq_midi_event 16384 1 snd_seq_midi ath10k_core 475136 1 ath10k_pci bluetooth 548864 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm ath36864 1 ath10k_core ecdh_generic 16384 1 bluetooth
[Kernel-packages] [Bug 1904912] [NEW] linux 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu
Public bug reported: 5.8.0-9.11 and other v5.8 kernels all fail to boot in qemu with opensbi and qemu. I'm booting a cloud-image with kenrel install like this: qemu-system-riscv64 -machine virt -m 2048 -smp 4 -kernel /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -device loader,file=/usr/lib/u-boot/qemu-riscv64_smode/uboot.elf,addr=0x8020 -device virtio-blk-device,drive=vda -drive file=focal- riscv64-20200422.qcow2,id=vda -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 on groovy host. v5.4 kernels from focal-updates boots; upgrading to groovy/-upstead/-proposed kernel the boot fails. The image has linux-generic installed with u-boot-menu for the extlinux.conf based boot menu kernel just panics. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: riscv64 ** Attachment added: "riscv-panic.txt" https://bugs.launchpad.net/bugs/1904912/+attachment/5436059/+files/riscv-panic.txt ** Tags added: riscv64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1904912 Title: linux 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu Status in linux-riscv package in Ubuntu: New Bug description: 5.8.0-9.11 and other v5.8 kernels all fail to boot in qemu with opensbi and qemu. I'm booting a cloud-image with kenrel install like this: qemu-system-riscv64 -machine virt -m 2048 -smp 4 -kernel /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -device loader,file=/usr/lib/u-boot/qemu- riscv64_smode/uboot.elf,addr=0x8020 -device virtio-blk- device,drive=vda -drive file=focal-riscv64-20200422.qcow2,id=vda -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 on groovy host. v5.4 kernels from focal-updates boots; upgrading to groovy/-upstead/-proposed kernel the boot fails. The image has linux-generic installed with u-boot-menu for the extlinux.conf based boot menu kernel just panics. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1904912/+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 1904860] [NEW] QCA9377 802.11ac Wireless Network Adapter-Network unclaimed on every ubuntu os
You have been subscribed to a public bug: 4 months ago,I installed ubuntu on my lenovo E41-25 notebook. Working damn fine going good. recently i updated my system via `sudo apt update && sudo apt upgrade`. Thats all i do. Now,my wifi adapter not working properly. harish@harish$ sudo dmesg | grep ath10k [ 12.347183] ath10k_pci :02:00.0: failed to iomap BAR0 [ 12.347239] ath10k_pci :02:00.0: failed to claim device: -5 [ 12.347355] ath10k_pci: probe of :02:00.0 failed with error -5 harish@harish$ lshw -c network WARNING: you should run this program as super-user. *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:01:00.0 logical name: enp1s0 version: 15 serial: 9c:5a:44:44:f4:41 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:30 ioport:3000(size=256) memory:f0404000-f0404fff memory:f040-f0403fff *-network UNCLAIMED description: Network controller product: QCA9377 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:02:00.0 version: 31 width: 64 bits clock: 33MHz capabilities: cap_list configuration: latency=0 *-network description: Ethernet interface physical id: 1 bus info: usb@2:3 logical name: usb0 serial: ca:74:69:53:09:2a capabilities: ethernet physical configuration: broadcast=yes driver=rndis_host driverversion=22-Aug-2005 firmware=RNDIS device ip=192.168.42.225 link=yes multicast=yes harish@harish$ lsmod Module Size Used by rndis_host 20480 0 cdc_ether 20480 1 rndis_host usbnet 45056 2 rndis_host,cdc_ether mii20480 1 usbnet cdc_acm40960 0 rfcomm 81920 4 cmac 16384 2 algif_hash 16384 1 algif_skcipher 16384 1 af_alg 24576 6 algif_hash,algif_skcipher bnep 24576 2 nls_iso8859_1 16384 1 edac_mce_amd 32768 0 kvm_amd98304 0 ccp86016 1 kvm_amd kvm 663552 1 kvm_amd crct10dif_pclmul 16384 1 ghash_clmulni_intel16384 0 snd_hda_codec_conexant28672 1 uvcvideo 98304 0 snd_hda_codec_generic81920 1 snd_hda_codec_conexant aesni_intel 372736 3 amdgpu 4579328 21 ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_conexant videobuf2_vmalloc 20480 1 uvcvideo videobuf2_memops 20480 1 videobuf2_vmalloc snd_hda_codec_hdmi 61440 1 crypto_simd16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel snd_hda_intel 53248 4 snd_intel_dspcfg 24576 1 snd_hda_intel snd_hda_codec 135168 4 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel videobuf2_v4l2 24576 1 uvcvideo snd_hda_core 90112 5 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec videobuf2_common 49152 2 videobuf2_v4l2,uvcvideo videodev 225280 3 videobuf2_v4l2,uvcvideo,videobuf2_common glue_helper16384 1 aesni_intel amd_iommu_v2 20480 1 amdgpu snd_hwdep 20480 1 snd_hda_codec mc 53248 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common snd_pcm 106496 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core btusb 57344 0 btrtl 24576 1 btusb ath10k_pci 49152 0 btbcm 16384 1 btusb btintel24576 1 btusb snd_seq_midi 20480 0 snd_seq_midi_event 16384 1 snd_seq_midi ath10k_core 475136 1 ath10k_pci bluetooth 548864 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm ath36864 1 ath10k_core ecdh_generic 16384 1 bluetooth ecc28672 1 ecdh_generic mac80211 843776 1 ath10k_core gpu_sched 32768 1 amdgpu snd_rawmidi36864 1 snd_seq_midi cfg80211 704512 3 ath,mac80211,ath10k_core ttm 106496 1 amdgpu drm_kms_helper184320 1 amdgpu snd_seq69632 2 snd_seq_midi,snd_seq_midi_event snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi i2c_algo_bit 16384 1 amdgpu snd_timer 36864 2
[Kernel-packages] [Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+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 1904906] [NEW] 5.10 kernel fails to boot with secure boot disabled
Public bug reported: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? ** Affects: ubuntu-power-systems Importance: Undecided Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-189504 severity-medium targetmilestone-inin2010 ** Tags added: architecture-ppc64le bugnameltc-189504 severity-medium targetmilestone-inin2010 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- 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/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+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 1904904] [NEW] Xenial update: v4.4.243 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.243 upstream stable release from git://git.kernel.org/ Note: This patch set is empty for xenial because v4.4.243 contained only one patch: ed3691aa7e4a powercap: restrict energy meter to root access The contents of which are already present here via: 7a1c0417c5111 powercap: make attributes only readable by root ^^^ (note also that this should have been "UBUNTU: SAUCE:") Linux 4.4.243 UBUNTU: upstream stable to v4.4.243 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v4.4.243 upstream stable release + from git://git.kernel.org/ -v4.4.243 upstream stable release -from git://git.kernel.org/ + Note: This patch set is empty for xenial because v4.4.243 contained + only one patch: + + ed3691aa7e4a powercap: restrict energy meter to root access + + The contents of which are already present here via: + + 7a1c0417c5111 powercap: make attributes only readable by root + ^^^ (note also that this should have been "UBUNTU: SAUCE:") + + + Linux 4.4.243 + UBUNTU: upstream stable to v4.4.243 -- 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/1904904 Title: Xenial update: v4.4.243 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.243 upstream stable release from git://git.kernel.org/ Note: This patch set is empty for xenial because v4.4.243 contained only one patch: ed3691aa7e4a powercap: restrict energy meter to root access The contents of which are already present here via: 7a1c0417c5111 powercap: make attributes only readable by root ^^^ (note also that this should have been "UBUNTU: SAUCE:") Linux 4.4.243 UBUNTU: upstream stable to v4.4.243 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904904/+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 1904906] [NEW] 5.10 kernel fails to boot with secure boot disabled
You have been subscribed to a public bug: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-189504 severity-medium targetmilestone-inin2010 -- 5.10 kernel fails to boot with secure boot disabled https://bugs.launchpad.net/bugs/1904906 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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 1902701] Re: zfs-linux 0.8.3-1ubuntu12.4 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1
I can confirm that zfs-linux 0.8.3-1ubuntu12.5 fixes the dkms installation error with linux 5.8 on Focal while still working with linux 5.4. Setting up zfs-dkms (0.8.3-1ubuntu12.5) ... Loading new zfs-0.8.3 DKMS files... Building for 5.8.0-30-generic Building initial module for 5.8.0-30-generic Error! The /var/lib/dkms/zfs/0.8.3/5.8.0-30-generic/x86_64/dkms.conf for module zfs includes a BUIL D_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. Skipped. The smoke tests were also successful with the 5.8 kernel: $ sudo ./debian/tests/kernel-smoke-test Removing existing zfs modules Unloading zfs Unloading icp Unloading zcommon Unloading znvpair Unloading zavl Unloading spl Loading new zfs modules kernel smoke test, create and destroy pool, 2x2 mirror: PASSED kernel smoke test, create and destroy pool, 4x1 mirror: PASSED kernel smoke test, create and destroy pool, nested raidz3: PASSED kernel smoke test, create and destroy pool, raidz1: PASSED kernel smoke test, create and destroy pool, raidz2: PASSED kernel smoke test, create and destroy pool, raidz3: PASSED kernel smoke test, create and destroy pool, striped: PASSED kernel smoke test, create and destroy ZFS Intent Log: PASSED kernel smoke test, create and destroy ZFS filesystems: PASSED kernel smoke test, ZFS snapshot: PASSED kernel smoke test, ZFS clone: PASSED kernel smoke test, ZFS send and receive: PASSED kernel smoke test, corrupt data and clean with a scrub: PASSED kernel smoke test, encrypted ZFS filesystems, load/unload keys: PASSED ADT also completed successfully for both linux-generic 5.4 and linux-hwe 5.8: * linux 5.4: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/z/zfs-linux/20201119_163205_07089@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/z/zfs-linux/20201119_165530_b73f7@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/z/zfs-linux/20201119_164146_76812@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/z/zfs-linux/20201119_162758_07089@/log.gz * linux-hwe 5.8: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/z/zfs-linux/20201119_162748_82a89@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/z/zfs-linux/20201119_163654_cf222@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/z/zfs-linux/20201119_163259_90ac9@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/z/zfs-linux/20201119_162409_cf222@/log.gz ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1902701 Title: zfs-linux 0.8.3-1ubuntu12.4 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1 Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Focal: Fix Committed Bug description: [SRU Justification] Impact: When attempting to compile the zfs-dkms module on a 5.8 kernel the module fails to properly configure the build. The kernel driver part of zfs-linux is only prepared to handle the kernels it released with. For Ubuntu kernels the zfs module is build based on the zfs-dkms that is current for the series the kernel originates from (so Groovy for 5.8). And this should be the encouraged way to do this. Fix: Add a limitation to the dkms package to only build for supported kernels. This causes the whole build/install to be skipped on 5.8 rather than to fail. Testcase: dkms install runs for 5.4 and 5.8 in Focal. For the 5.8 kernel this should result in: Building initial module for 5.8.0-25-generic Error! The /var/lib/dkms/zfs/0.8.3/5.8.0-25-generic/x86_64/dkms.conf for module zfs includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. Skipped. Regression Potential: Since the module fails to compile for the newer kernel there should be nothing that can regress. --- Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/z/zfs-linux/20201016_104632_e52aa@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/z/zfs-linux/20201016_144759_7735c@/log.gz ppc64el:
[Kernel-packages] [Bug 1904895] 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/1904895 Title: Network does not work after restart from Windows 10 Status in linux package in Ubuntu: Confirmed Bug description: I got a Intel I217-V integrated on the motherboard, it is an Ethernet NIC. $ lspci 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) Before this worked good, but yesterday it stopped working after restarting the computer from Windows 10. I suspect there might have been some Windows update maybe. It seems to work again after I went into the Device Manager in Windows and turned off power management settings. Under the "Power Management" tab, I unchecked the checkbox option "Allow the computer to turn off this device to save power". Under the "Advanced" tab, I selected the "Enable PME" option and changed it from "Enabled" to "Disabled". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.29.34 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shockzor 1889 F pulseaudio /dev/snd/controlC0: shockzor 1889 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:23:08 2020 HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9 InstallationDate: Installed on 2013-12-26 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904895/+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 1904895] [NEW] Network does not work after restart from Windows 10
Public bug reported: I got a Intel I217-V integrated on the motherboard, it is an Ethernet NIC. $ lspci 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) Before this worked good, but yesterday it stopped working after restarting the computer from Windows 10. I suspect there might have been some Windows update maybe. It seems to work again after I went into the Device Manager in Windows and turned off power management settings. Under the "Power Management" tab, I unchecked the checkbox option "Allow the computer to turn off this device to save power". Under the "Advanced" tab, I selected the "Enable PME" option and changed it from "Enabled" to "Disabled". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.29.34 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shockzor 1889 F pulseaudio /dev/snd/controlC0: shockzor 1889 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:23:08 2020 HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9 InstallationDate: Installed on 2013-12-26 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1904895 Title: Network does not work after restart from Windows 10 Status in linux package in Ubuntu: New Bug description: I got a Intel I217-V integrated on the motherboard, it is an Ethernet NIC. $ lspci 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) Before this worked good, but yesterday it stopped working after restarting the computer from Windows 10. I suspect there might have been some Windows update maybe. It seems to work again after I went into the Device Manager in Windows and turned off power management settings. Under the "Power Management" tab, I unchecked the checkbox option "Allow the computer to turn off this device to save power". Under the "Advanced" tab, I selected the "Enable PME" option and changed it from "Enabled" to "Disabled". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.29.34 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shockzor 1889 F pulseaudio /dev/snd/controlC0: shockzor 1889 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:23:08 2020 HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9 InstallationDate: Installed on 2013-12-26 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1904884] Re: [UBUNUT 20.04] s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap
The commit 92fb1db26eef "mm/page_idle.c: skip offline pages" is upstream with
5.8 (rc-1) (also tagged with next-20200820).
Hence it's in groovy (since Ubuntu-5.8.0-13.14) and in hirsute
(Ubuntu-5.8.0-30.32+21.04.1).
It's not in focal (also not via upstream stable updates).
Hence updating only G and H to Fix Released.
** Changed in: linux (Ubuntu Hirsute)
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
** Changed in: linux (Ubuntu Hirsute)
Status: New => Fix Released
** Changed in: linux (Ubuntu Groovy)
Status: New => Fix Released
** Changed in: ubuntu-z-systems
Status: New => Triaged
** Summary changed:
- [UBUNUT 20.04] s390: dbginfo.sh triggers kernel panic, reading from
/sys/kernel/mm/page_idle/bitmap
+ s390: dbginfo.sh triggers kernel panic, reading from
/sys/kernel/mm/page_idle/bitmap
--
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/1904884
Title:
s390: dbginfo.sh triggers kernel panic, reading from
/sys/kernel/mm/page_idle/bitmap
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
New
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Bug description:
System hangs on dbginfo.sh script execution.
Solution:
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages")
Included upstream since kernel v5.8, so it is already included in
Ubuntu 20.10, but not in 20.04 and earlier.
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") applies cleanly on
ubuntu-focal, but not on ubuntu-bionic.
Adjustment / backport for bionic should be trivial, but it is not IBM
code and therefore the backport will be requested here by Canonical.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904884/+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 1904884] Re: [UBUNUT 20.04] s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap
--- Comment From heinz-werner_se...@de.ibm.com 2020-11-19 10:17 EDT---
Reduced importance from "ship issue" to "high", not a real ship issue, but is
mandatory to be fixed within the service stream
** Tags removed: severity-critical
** Tags added: severity-high
--
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/1904884
Title:
[UBUNUT 20.04] s390: dbginfo.sh triggers kernel panic, reading from
/sys/kernel/mm/page_idle/bitmap
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
New
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
New
Bug description:
System hangs on dbginfo.sh script execution.
Solution:
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages")
Included upstream since kernel v5.8, so it is already included in
Ubuntu 20.10, but not in 20.04 and earlier.
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") applies cleanly on
ubuntu-focal, but not on ubuntu-bionic.
Adjustment / backport for bionic should be trivial, but it is not IBM
code and therefore the backport will be requested here by Canonical.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904884/+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 1904884] Re: [UBUNUT 20.04] s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904884
Title:
[UBUNUT 20.04] s390: dbginfo.sh triggers kernel panic, reading from
/sys/kernel/mm/page_idle/bitmap
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
New
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
New
Bug description:
System hangs on dbginfo.sh script execution.
Solution:
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages")
Included upstream since kernel v5.8, so it is already included in
Ubuntu 20.10, but not in 20.04 and earlier.
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") applies cleanly on
ubuntu-focal, but not on ubuntu-bionic.
Adjustment / backport for bionic should be trivial, but it is not IBM
code and therefore the backport will be requested here by Canonical.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904884/+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 1904884] [NEW] [UBUNUT 20.04] s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap
Public bug reported:
System hangs on dbginfo.sh script execution.
Solution:
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages")
Included upstream since kernel v5.8, so it is already included in Ubuntu
20.10, but not in 20.04 and earlier.
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") applies cleanly on
ubuntu-focal, but not on ubuntu-bionic.
Adjustment / backport for bionic should be trivial, but it is not IBM
code and therefore the backport will be requested here by Canonical.
** Affects: ubuntu-z-systems
Importance: High
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-189321 severity-critical
targetmilestone-inin20041
** Tags added: architecture-s39064 bugnameltc-189321 severity-critical
targetmilestone-inin20041
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
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/1904884
Title:
[UBUNUT 20.04] s390: dbginfo.sh triggers kernel panic, reading from
/sys/kernel/mm/page_idle/bitmap
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
New
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
New
Bug description:
System hangs on dbginfo.sh script execution.
Solution:
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages")
Included upstream since kernel v5.8, so it is already included in
Ubuntu 20.10, but not in 20.04 and earlier.
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") applies cleanly on
ubuntu-focal, but not on ubuntu-bionic.
Adjustment / backport for bionic should be trivial, but it is not IBM
code and therefore the backport will be requested here by Canonical.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904884/+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 1904884] [NEW] [UBUNUT 20.04] s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap
You have been subscribed to a public bug:
System hangs on dbginfo.sh script execution.
Solution:
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages")
Included upstream since kernel v5.8, so it is already included in Ubuntu
20.10, but not in 20.04 and earlier.
Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") applies cleanly on
ubuntu-focal, but not on ubuntu-bionic.
Adjustment / backport for bionic should be trivial, but it is not IBM
code and therefore the backport will be requested here by Canonical.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-189321 severity-critical
targetmilestone-inin20041
--
[UBUNUT 20.04] s390: dbginfo.sh triggers kernel panic, reading from
/sys/kernel/mm/page_idle/bitmap
https://bugs.launchpad.net/bugs/1904884
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux 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 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
** 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/1904848 Title: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module Status in linux package in Ubuntu: Confirmed Bug description: [Impact] unloading ib_ipoib causes a call trace to be logged in kernel buffer. bisecting the bionic kernel reveals that this issue was discovered by 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() in version 4.15.0-59.66 [test case] # modprobe ib_ipoib # modprobe ib_ipoib -r # dmesg [ 306.277717] [ cut here ] [ 306.277738] WARNING: CPU: 10 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.277739] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf [ 306.277790] serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core scsi_transport_sas ptp pps_core devlink [ 306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 4.15.0-124-generic #127-Ubuntu [ 306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [ 306.277823] RIP: 0010:__flush_work+0x1f8/0x210 [ 306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286 [ 306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 0006 [ 306.277829] RDX: RSI: 99429ef16498 RDI: 99429ef16490 [ 306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 0004 [ 306.277832] R10: e263a058c1c0 R11: 0001 R12: 993a5c3d8ec8 [ 306.277833] R13: 0001 R14: bdeb47ecfd78 R15: b00a9800 [ 306.277835] FS: 7fa1124a9540() GS:99429ef0() knlGS: [ 306.277837] CS: 0010 DS: ES: CR0: 80050033 [ 306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 001606e0 [ 306.277840] Call Trace: [ 306.277850] __cancel_work_timer+0x136/0x1b0 [ 306.277881] ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core] [ 306.277886] cancel_delayed_work_sync+0x13/0x20 [ 306.277909] mlx5e_detach_netdev+0x83/0x90 [mlx5_core] [ 306.277931] mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core] [ 306.277941] mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib] [ 306.277948] ipoib_remove_one+0xe4/0x180 [ib_ipoib] [ 306.277965] ib_unregister_client+0x171/0x1e0 [ib_core] [ 306.277972] ipoib_cleanup_module+0x15/0x2f [ib_ipoib] [ 306.277978] SyS_delete_module+0x1ab/0x2d0 [ 306.277983] do_syscall_64+0x73/0x130 [ 306.277989] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 306.277992] RIP: 0033:0x7fa111fc1047 [ 306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 00b0 [ 306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 7fa111fc1047 [ 306.277997] RDX: RSI: 0800 RDI: 5614be46cd08 [ 306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: [ 306.278000] R10: 7fa11203dc40 R11: 0206 R12: 5614be46cd08 [ 306.278002] R13: 0001 R14: 5614be46cd08 R15: 7ffc0db33680 [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 [ 306.278035] ---[ end trace 652f7759937172a2 ]--- [ 306.646061] [ cut here ] [ 306.646077] WARNING: CPU: 6 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.646078] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp
[Kernel-packages] [Bug 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904848 Title: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module Status in linux package in Ubuntu: Incomplete Bug description: [Impact] unloading ib_ipoib causes a call trace to be logged in kernel buffer. bisecting the bionic kernel reveals that this issue was discovered by 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() in version 4.15.0-59.66 [test case] # modprobe ib_ipoib # modprobe ib_ipoib -r # dmesg [ 306.277717] [ cut here ] [ 306.277738] WARNING: CPU: 10 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.277739] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf [ 306.277790] serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core scsi_transport_sas ptp pps_core devlink [ 306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 4.15.0-124-generic #127-Ubuntu [ 306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [ 306.277823] RIP: 0010:__flush_work+0x1f8/0x210 [ 306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286 [ 306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 0006 [ 306.277829] RDX: RSI: 99429ef16498 RDI: 99429ef16490 [ 306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 0004 [ 306.277832] R10: e263a058c1c0 R11: 0001 R12: 993a5c3d8ec8 [ 306.277833] R13: 0001 R14: bdeb47ecfd78 R15: b00a9800 [ 306.277835] FS: 7fa1124a9540() GS:99429ef0() knlGS: [ 306.277837] CS: 0010 DS: ES: CR0: 80050033 [ 306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 001606e0 [ 306.277840] Call Trace: [ 306.277850] __cancel_work_timer+0x136/0x1b0 [ 306.277881] ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core] [ 306.277886] cancel_delayed_work_sync+0x13/0x20 [ 306.277909] mlx5e_detach_netdev+0x83/0x90 [mlx5_core] [ 306.277931] mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core] [ 306.277941] mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib] [ 306.277948] ipoib_remove_one+0xe4/0x180 [ib_ipoib] [ 306.277965] ib_unregister_client+0x171/0x1e0 [ib_core] [ 306.277972] ipoib_cleanup_module+0x15/0x2f [ib_ipoib] [ 306.277978] SyS_delete_module+0x1ab/0x2d0 [ 306.277983] do_syscall_64+0x73/0x130 [ 306.277989] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 306.277992] RIP: 0033:0x7fa111fc1047 [ 306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 00b0 [ 306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 7fa111fc1047 [ 306.277997] RDX: RSI: 0800 RDI: 5614be46cd08 [ 306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: [ 306.278000] R10: 7fa11203dc40 R11: 0206 R12: 5614be46cd08 [ 306.278002] R13: 0001 R14: 5614be46cd08 R15: 7ffc0db33680 [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 [ 306.278035] ---[ end trace 652f7759937172a2 ]--- [ 306.646061] [ cut here ] [ 306.646077] WARNING: CPU: 6 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.646078] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables
[Kernel-packages] [Bug 1890612] Re: [Source NEW SRU FOCAL] ITP: Please support loading microcode early, whilst otherwise booting without initrd
linux-meta-aws patch is submitted at https://lists.ubuntu.com/archives /kernel-team/2020-November/114920.html ** Also affects: linux-meta-aws (Ubuntu) Importance: Undecided Status: New ** Description changed: + Now that micorocode-initrd is in focal, linux-meta-aws should start + depending on it in focal too. + + -- + [Impact] - * New package to provide micorocode-only initrd for application of + * New package to provide micorocode-only initrd for application of microcode on boot, when otherwise no initrd is in use. [Test Case] - * install microcode-initrd in AWS cloud x86 metal instance - * reboot, observe that microcode has been applied, and yet the boot was without initrd (observe journalctl -b -k to see that initrd was not used for boot) + * install microcode-initrd in AWS cloud x86 metal instance + * reboot, observe that microcode has been applied, and yet the boot was without initrd (observe journalctl -b -k to see that initrd was not used for boot) [Regression Potential] - * This is a brand new package, that will be used by AWS images. + * This is a brand new package, that will be used by AWS images. Otherwise this package will not be automatically installed anywhere. Re spinning & promoting AWS images are tested and gated by the CPC team. [Other Info] - - * Original bug report for groovy: + + * Original bug report for groovy: Normally Ubuntu boots using initrd that has three archives: early amd64 microcode, early intel microcode, and compressed main initrd. When booting without initrd, simply kernel is loaded without any initrd and thus without microcode. However, grub supports booting with multiple initrds and one can specify a standalone early initrd which contains microcode only, and separate main initrd. As an added bonus one can also specify just eary microcode initrd without a main one, to allow kernel to load microcode early, but otherwise boot without an initrd. To achieve that I need to introduce a microcode-initrd package will will only provide early initrd which only has microcode. The intention is to seed microcode-initrd to targets that boot on baremental without initrd. ** Changed in: linux-meta-aws (Ubuntu) Status: New => Fix Released ** Changed in: linux-meta-aws (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws in Ubuntu. https://bugs.launchpad.net/bugs/1890612 Title: [Source NEW SRU FOCAL] ITP: Please support loading microcode early, whilst otherwise booting without initrd Status in cloud-images: Fix Committed Status in linux-meta-aws package in Ubuntu: Fix Released Status in microcode-initrd package in Ubuntu: Fix Released Status in linux-meta-aws source package in Focal: Triaged Status in microcode-initrd source package in Focal: Fix Released Bug description: Now that micorocode-initrd is in focal, linux-meta-aws should start depending on it in focal too. -- [Impact] * New package to provide micorocode-only initrd for application of microcode on boot, when otherwise no initrd is in use. [Test Case] * install microcode-initrd in AWS cloud x86 metal instance * reboot, observe that microcode has been applied, and yet the boot was without initrd (observe journalctl -b -k to see that initrd was not used for boot) [Regression Potential] * This is a brand new package, that will be used by AWS images. Otherwise this package will not be automatically installed anywhere. Re spinning & promoting AWS images are tested and gated by the CPC team. [Other Info] * Original bug report for groovy: Normally Ubuntu boots using initrd that has three archives: early amd64 microcode, early intel microcode, and compressed main initrd. When booting without initrd, simply kernel is loaded without any initrd and thus without microcode. However, grub supports booting with multiple initrds and one can specify a standalone early initrd which contains microcode only, and separate main initrd. As an added bonus one can also specify just eary microcode initrd without a main one, to allow kernel to load microcode early, but otherwise boot without an initrd. To achieve that I need to introduce a microcode-initrd package will will only provide early initrd which only has microcode. The intention is to seed microcode-initrd to targets that boot on baremental without initrd. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1890612/+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 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing
I'm using the 5.10-rc4 and the problem still occurs. Seems (but I'm probably wrong) the controoler is using another MAC address. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+attachment/5435972/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1904638 Title: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have Xbox Series X|S controller and the Xbox icon still blinks after the successful pairing. I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm following this bug closely and I can provide any information you need and do any tests you want. mhalano@glados:~$ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 mhalano@glados:~$ apt policy bluez bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-23 (25 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 5590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17 Tags: groovy package-from-proposed Uname: Linux 5.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/13/2020 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0XRXN9 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5590 dmi.product.sku: 0957 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:F6:D8:6A:A3:F0 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0 TX bytes:18701 acl:357 sco:0 commands:841 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1879547] Re: wl driver 6.30.223.271 (r587334) failed with code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- 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/1879547 Title: wl driver 6.30.223.271 (r587334) failed with code 1 Status in bcmwl package in Ubuntu: Confirmed Bug description: After upgrade from 18.04 to focal 20.04 it was working. The additional broadcom driver was listed in the proprietary "Additional Drivers" tab of Software & Update manager. After reboot, wifi stopped working and the driver no more was listed in the Additional Drivers" tab. Drivers broadcom-sta* also not working. Purge and reinstall bcmwl not work. rfkill not work. secure boot is disabled. dmesg [ 244.329685] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 244.335290] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 244.351067] wl driver 6.30.223.271 (r587334) failed with code 1 [ 244.351069] ERROR @wl_cfg80211_detach : [ 244.351070] NULL ndev->ieee80211ptr, unable to deref wl sudo lspci -v 01:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03) Subsystem: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f610 (64-bit, non-prefetchable) [size=32K] Capabilities: [48] Power Management version 3 Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [68] Vendor Specific Information: Len=44 Capabilities: [ac] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Device Serial Number 00-00-00-ff-ff-00-00-00 Capabilities: [150] Power Budgeting Capabilities: [160] Virtual Channel Capabilities: [1b0] Latency Tolerance Reporting Kernel modules: bcma, wl cat /etc/modprobe.d/blacklist.conf blacklist b43 blacklist b43legacy blacklist b44 blacklist brcm80211 blacklist brcmsmac blacklist ssb blacklist bcm43 blacklist bcm43xx blacklist ndiswrapper blacklist bcma sudo lshw -C network *-network DISPONÍVEL descrição: Network controller produto: BCM4360 802.11ac Wireless Network Adapter fabricante: Broadcom Inc. and subsidiaries ID físico: 0 informações do barramento: pci@:01:00.0 versão: 03 largura: 64 bits clock: 33MHz capacidades: pm msi pciexpress bus_master cap_list configuração: latency=0 recursos: memória:f610-f6107fff sudo hwinfo --netcard 15: PCI 100.0: 0280 Network controller [Created at pci.386] Unique ID: VCu0.FmxE7Ki8dh2 Parent ID: vSkL.OXv6hi5TXAE SysFS ID: /devices/pci:00/:00:01.0/:01:00.0 SysFS BusID: :01:00.0 Hardware Class: network Model: "Broadcom BCM4360 802.11ac Wireless Network Adapter" Vendor: pci 0x14e4 "Broadcom" Device: pci 0x4360 "BCM4360 802.11ac Wireless Network Adapter" SubVendor: pci 0x14e4 "Broadcom" SubDevice: pci 0x4360 Revision: 0x03 Memory Range: 0xf610-0xf6107fff (rw,non-prefetchable) IRQ: 16 (no events) Module Alias: "pci:v14E4d4360sv14E4sd4360bc02sc80i00" Driver Info #0: Driver Status: bcma is not active Driver Activation Cmd: "modprobe bcma" Driver Info #1: Driver Status: wl is active Driver Activation Cmd: "modprobe wl" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #13 (PCI bridge) sudo modinfo wl filename: /lib/modules/5.4.0-31-generic/updates/dkms/wl.ko license:MIXED/Proprietary srcversion: 00D38A27B7E3C7B97C238FC alias: pci:v*d*sv*sd*bc02sc80i* depends:cfg80211 retpoline: Y name: wl vermagic: 5.4.0-31-generic SMP mod_unload parm: passivemode:int parm: wl_txq_thresh:int parm: oneonly:int parm: piomode:int parm: instance_base:int parm: nompc:int parm: intf_name:string iwconfig lono wireless extensions. enp3s0no wireless extensions. bootctl Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi. Alternatively, use --esp-path= to specify path to mount point. System: Not booted with EFI sudo systemctl list-unit-files --state=enabled UNIT FILE STATE VENDOR PRESET snap-canonical\x2dlivepatch-94.mount enabled enabled snap-canonical\x2dlivepatch-95.mount enabled enabled snap-chromium\x2dffmpeg-13.mount
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 Same bug, Acer Aspire V-Nitro vn7-792G-79LX intel + Nvidia Graphics -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
I've just used a fresh image of Mate 20.10 and used -proposed and done a full update and reboot. My bluetooth mouse, headphones and external keyboard are working fine now with this build so this bug has been fixed for me. Thank you all for your efforts in getting it sorted Kind regards Tony -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Committed Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1882136] Re: Intel Corporation Wireless 8265 / 8275 [8086:24fd] Subsystem [8086:0050] unable to connect to 5GHz wifi
Dear You-Sheng Yang, I tried the 5.9.8-050908-generic kernel based on the description, but unfortunately the 5GHz connection still doesn't work. What might be a useful information that I got this message during kernel installation: update-initramfs: Generating /boot/initrd.img-5.9.3-050903-generic W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.12.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.12.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_06.bin for module i915 W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_01.bin for module i915 I: The initramfs will attempt to resume from /dev/dm-2 -- 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/1882136 Title: Intel Corporation Wireless 8265 / 8275 [8086:24fd] Subsystem [8086:0050] unable to connect to 5GHz wifi Status in linux package in Ubuntu: Incomplete Bug description: After updating the NetworkManager I can't connect to 5GHz wifi. The router is a mikrotik hap ac2.The notebook is a Dell Latitude 5580. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 22:20:15 2020 InstallationDate: Installed on 2020-05-15 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: szili 1443 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2020-11-17 (0 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Dell Inc. Latitude 5590 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/elementary--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0MM81M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
** Description changed: [Impact] - unloading ib_ipoib causes a call trace to be logged in kernel buffer. + unloading ib_ipoib causes a call trace to be logged in kernel buffer. - bisecting the bionic kernel reveals that this issue was introduced by - 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() - in version 4.15.0-59.66 - + bisecting the bionic kernel reveals that this issue was discovered by + 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() + in version 4.15.0-59.66 [test case] # modprobe ib_ipoib # modprobe ib_ipoib -r # dmesg [ 306.277717] [ cut here ] [ 306.277738] WARNING: CPU: 10 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.277739] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf [ 306.277790] serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core scsi_transport_sas ptp pps_core devlink [ 306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 4.15.0-124-generic #127-Ubuntu [ 306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [ 306.277823] RIP: 0010:__flush_work+0x1f8/0x210 [ 306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286 [ 306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 0006 [ 306.277829] RDX: RSI: 99429ef16498 RDI: 99429ef16490 [ 306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 0004 [ 306.277832] R10: e263a058c1c0 R11: 0001 R12: 993a5c3d8ec8 [ 306.277833] R13: 0001 R14: bdeb47ecfd78 R15: b00a9800 [ 306.277835] FS: 7fa1124a9540() GS:99429ef0() knlGS: [ 306.277837] CS: 0010 DS: ES: CR0: 80050033 [ 306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 001606e0 [ 306.277840] Call Trace: [ 306.277850] __cancel_work_timer+0x136/0x1b0 [ 306.277881] ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core] [ 306.277886] cancel_delayed_work_sync+0x13/0x20 [ 306.277909] mlx5e_detach_netdev+0x83/0x90 [mlx5_core] [ 306.277931] mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core] [ 306.277941] mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib] [ 306.277948] ipoib_remove_one+0xe4/0x180 [ib_ipoib] [ 306.277965] ib_unregister_client+0x171/0x1e0 [ib_core] [ 306.277972] ipoib_cleanup_module+0x15/0x2f [ib_ipoib] [ 306.277978] SyS_delete_module+0x1ab/0x2d0 [ 306.277983] do_syscall_64+0x73/0x130 [ 306.277989] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 306.277992] RIP: 0033:0x7fa111fc1047 [ 306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 00b0 [ 306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 7fa111fc1047 [ 306.277997] RDX: RSI: 0800 RDI: 5614be46cd08 [ 306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: [ 306.278000] R10: 7fa11203dc40 R11: 0206 R12: 5614be46cd08 [ 306.278002] R13: 0001 R14: 5614be46cd08 R15: 7ffc0db33680 - [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 + [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 [ 306.278035] ---[ end trace 652f7759937172a2 ]--- [ 306.646061] [ cut here ] [ 306.646077] WARNING: CPU: 6 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.646078] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat
[Kernel-packages] [Bug 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
** Patch added: "0001-net-mlx5e-IPoIB-initialize-update_stat_work-for-ipoi.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904848/+attachment/5435933/+files/0001-net-mlx5e-IPoIB-initialize-update_stat_work-for-ipoi.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904848 Title: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module Status in linux package in Ubuntu: Incomplete Bug description: [Impact] unloading ib_ipoib causes a call trace to be logged in kernel buffer. bisecting the bionic kernel reveals that this issue was introduced by 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() in version 4.15.0-59.66 [test case] # modprobe ib_ipoib # modprobe ib_ipoib -r # dmesg [ 306.277717] [ cut here ] [ 306.277738] WARNING: CPU: 10 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.277739] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf [ 306.277790] serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core scsi_transport_sas ptp pps_core devlink [ 306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 4.15.0-124-generic #127-Ubuntu [ 306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [ 306.277823] RIP: 0010:__flush_work+0x1f8/0x210 [ 306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286 [ 306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 0006 [ 306.277829] RDX: RSI: 99429ef16498 RDI: 99429ef16490 [ 306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 0004 [ 306.277832] R10: e263a058c1c0 R11: 0001 R12: 993a5c3d8ec8 [ 306.277833] R13: 0001 R14: bdeb47ecfd78 R15: b00a9800 [ 306.277835] FS: 7fa1124a9540() GS:99429ef0() knlGS: [ 306.277837] CS: 0010 DS: ES: CR0: 80050033 [ 306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 001606e0 [ 306.277840] Call Trace: [ 306.277850] __cancel_work_timer+0x136/0x1b0 [ 306.277881] ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core] [ 306.277886] cancel_delayed_work_sync+0x13/0x20 [ 306.277909] mlx5e_detach_netdev+0x83/0x90 [mlx5_core] [ 306.277931] mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core] [ 306.277941] mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib] [ 306.277948] ipoib_remove_one+0xe4/0x180 [ib_ipoib] [ 306.277965] ib_unregister_client+0x171/0x1e0 [ib_core] [ 306.277972] ipoib_cleanup_module+0x15/0x2f [ib_ipoib] [ 306.277978] SyS_delete_module+0x1ab/0x2d0 [ 306.277983] do_syscall_64+0x73/0x130 [ 306.277989] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 306.277992] RIP: 0033:0x7fa111fc1047 [ 306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 00b0 [ 306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 7fa111fc1047 [ 306.277997] RDX: RSI: 0800 RDI: 5614be46cd08 [ 306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: [ 306.278000] R10: 7fa11203dc40 R11: 0206 R12: 5614be46cd08 [ 306.278002] R13: 0001 R14: 5614be46cd08 R15: 7ffc0db33680 [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 [ 306.278035] ---[ end trace 652f7759937172a2 ]--- [ 306.646061] [ cut here ] [ 306.646077] WARNING: CPU: 6 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.646078] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle
[Kernel-packages] [Bug 1904848] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1904848 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904848 Title: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module Status in linux package in Ubuntu: Incomplete Bug description: [Impact] unloading ib_ipoib causes a call trace to be logged in kernel buffer. bisecting the bionic kernel reveals that this issue was introduced by 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() in version 4.15.0-59.66 [test case] # modprobe ib_ipoib # modprobe ib_ipoib -r # dmesg [ 306.277717] [ cut here ] [ 306.277738] WARNING: CPU: 10 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.277739] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf [ 306.277790] serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core scsi_transport_sas ptp pps_core devlink [ 306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 4.15.0-124-generic #127-Ubuntu [ 306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [ 306.277823] RIP: 0010:__flush_work+0x1f8/0x210 [ 306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286 [ 306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 0006 [ 306.277829] RDX: RSI: 99429ef16498 RDI: 99429ef16490 [ 306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 0004 [ 306.277832] R10: e263a058c1c0 R11: 0001 R12: 993a5c3d8ec8 [ 306.277833] R13: 0001 R14: bdeb47ecfd78 R15: b00a9800 [ 306.277835] FS: 7fa1124a9540() GS:99429ef0() knlGS: [ 306.277837] CS: 0010 DS: ES: CR0: 80050033 [ 306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 001606e0 [ 306.277840] Call Trace: [ 306.277850] __cancel_work_timer+0x136/0x1b0 [ 306.277881] ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core] [ 306.277886] cancel_delayed_work_sync+0x13/0x20 [ 306.277909] mlx5e_detach_netdev+0x83/0x90 [mlx5_core] [ 306.277931] mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core] [ 306.277941] mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib] [ 306.277948] ipoib_remove_one+0xe4/0x180 [ib_ipoib] [ 306.277965] ib_unregister_client+0x171/0x1e0 [ib_core] [ 306.277972] ipoib_cleanup_module+0x15/0x2f [ib_ipoib] [ 306.277978] SyS_delete_module+0x1ab/0x2d0 [ 306.277983] do_syscall_64+0x73/0x130 [ 306.277989] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 306.277992] RIP: 0033:0x7fa111fc1047 [ 306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 00b0 [ 306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 7fa111fc1047 [ 306.277997] RDX: RSI: 0800 RDI: 5614be46cd08 [ 306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: [ 306.278000] R10: 7fa11203dc40 R11: 0206 R12: 5614be46cd08 [ 306.278002] R13: 0001 R14: 5614be46cd08 R15: 7ffc0db33680 [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f>
[Kernel-packages] [Bug 1904848] [NEW] Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
Public bug reported: [Impact] unloading ib_ipoib causes a call trace to be logged in kernel buffer. bisecting the bionic kernel reveals that this issue was introduced by 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() in version 4.15.0-59.66 [test case] # modprobe ib_ipoib # modprobe ib_ipoib -r # dmesg [ 306.277717] [ cut here ] [ 306.277738] WARNING: CPU: 10 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.277739] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf [ 306.277790] serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core scsi_transport_sas ptp pps_core devlink [ 306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 4.15.0-124-generic #127-Ubuntu [ 306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [ 306.277823] RIP: 0010:__flush_work+0x1f8/0x210 [ 306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286 [ 306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 0006 [ 306.277829] RDX: RSI: 99429ef16498 RDI: 99429ef16490 [ 306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 0004 [ 306.277832] R10: e263a058c1c0 R11: 0001 R12: 993a5c3d8ec8 [ 306.277833] R13: 0001 R14: bdeb47ecfd78 R15: b00a9800 [ 306.277835] FS: 7fa1124a9540() GS:99429ef0() knlGS: [ 306.277837] CS: 0010 DS: ES: CR0: 80050033 [ 306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 001606e0 [ 306.277840] Call Trace: [ 306.277850] __cancel_work_timer+0x136/0x1b0 [ 306.277881] ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core] [ 306.277886] cancel_delayed_work_sync+0x13/0x20 [ 306.277909] mlx5e_detach_netdev+0x83/0x90 [mlx5_core] [ 306.277931] mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core] [ 306.277941] mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib] [ 306.277948] ipoib_remove_one+0xe4/0x180 [ib_ipoib] [ 306.277965] ib_unregister_client+0x171/0x1e0 [ib_core] [ 306.277972] ipoib_cleanup_module+0x15/0x2f [ib_ipoib] [ 306.277978] SyS_delete_module+0x1ab/0x2d0 [ 306.277983] do_syscall_64+0x73/0x130 [ 306.277989] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 306.277992] RIP: 0033:0x7fa111fc1047 [ 306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 00b0 [ 306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 7fa111fc1047 [ 306.277997] RDX: RSI: 0800 RDI: 5614be46cd08 [ 306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: [ 306.278000] R10: 7fa11203dc40 R11: 0206 R12: 5614be46cd08 [ 306.278002] R13: 0001 R14: 5614be46cd08 R15: 7ffc0db33680 [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 [ 306.278035] ---[ end trace 652f7759937172a2 ]--- [ 306.646061] [ cut here ] [ 306.646077] WARNING: CPU: 6 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.646078] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt
