[Kernel-packages] [Bug 2062562] Re: Keyboard not working after resume from suspend on Dell XPS 13 laptop
That previous comment was false-positive, I was probably still booted to 6.5.0-26 and on 6.5.0-28 this bug is still present. After resume from suspend in 6.5.0-28 keyboard is not-responsive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2062562 Title: Keyboard not working after resume from suspend on Dell XPS 13 laptop Status in linux-signed package in Ubuntu: New Bug description: After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes back to life after suspend. When booted with 6.5.0-26-generic everything is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2062562/+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 2062562] Re: Keyboard not working after resume from suspend on Dell XPS 13 laptop
It seems that this is already fixed with 6.5.0-28-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2062562 Title: Keyboard not working after resume from suspend on Dell XPS 13 laptop Status in linux-signed package in Ubuntu: New Bug description: After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes back to life after suspend. When booted with 6.5.0-26-generic everything is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2062562/+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 2062562] Re: Keyboard not working after resume from suspend on Dell XPS 13 laptop
Maybe this is related with this: https://lore.kernel.org/linux- input/20240126160724.13278-1-hdego...@redhat.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2062562 Title: Keyboard not working after resume from suspend on Dell XPS 13 laptop Status in linux-signed package in Ubuntu: New Bug description: After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes back to life after suspend. When booted with 6.5.0-26-generic everything is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2062562/+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 2062562] [NEW] Keyboard not working after resume from suspend on Dell XPS 13 laptop
Public bug reported: After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes back to life after suspend. When booted with 6.5.0-26-generic everything is fine. ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2062562 Title: Keyboard not working after resume from suspend on Dell XPS 13 laptop Status in linux-signed package in Ubuntu: New Bug description: After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes back to life after suspend. When booted with 6.5.0-26-generic everything is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2062562/+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 2026358] [NEW] can not umount cifs share
Public bug reported: Hello, I can not umount a cifs share with umount /media/share. I alwas have to use umount -f -l /media/share. We have round about 260 installations with Automatic software distribution which need to unmount the share or it get stuck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-154-generic 5.4.0-154.171 ProcVersionSignature: Ubuntu 5.4.0-154.171-generic 5.4.240 Uname: Linux 5.4.0-154-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 7 10:50 seq crw-rw 1 root audio 116, 33 Jul 7 10:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 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: CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Fri Jul 7 10:57:48 2023 InstallationDate: Installed on 2021-12-15 (569 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-154-generic root=/dev/mapper/vg0--ubuntu-lv0--system ro maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-154-generic N/A linux-backports-modules-5.4.0-154-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed uec-images -- 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/2026358 Title: can not umount cifs share Status in linux package in Ubuntu: New Bug description: Hello, I can not umount a cifs share with umount /media/share. I alwas have to use umount -f -l /media/share. We have round about 260 installations with Automatic software distribution which need to unmount the share or it get stuck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-154-generic 5.4.0-154.171 ProcVersionSignature: Ubuntu 5.4.0-154.171-generic 5.4.240 Uname: Linux 5.4.0-154-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 7 10:50 seq crw-rw 1 root audio 116, 33 Jul 7 10:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 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: CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Fri Jul 7 10:57:48 2023 InstallationDate: Installed on 2021-12-15 (569 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-154-generic root=/dev/mapper/vg0--ubuntu-lv0--system ro maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-154-generic N/A linux-backports-modules-5.4.0-154-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
[Kernel-packages] [Bug 2009275] Re: HDMI audio doesn't work for AMD RX6700 XT
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009275 Title: HDMI audio doesn't work for AMD RX6700 XT Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After the recent update to the 5.19.35 kernel (installed on 4th March 2023), the HDMI audio (out) of my AMD RX6700 XT doesn't work anymore. I don't see any devices in Gnome or when listing the devices with `aplay -a` In the ACPI error message on startup I see: kernel: snd_hda_intel :01:00.1: no codecs initialized kernel: hdaudio hdaudioC1D0: no AFG or MFG node found When I boot with the old 5.19.0.32 kernel version HDMI audio works perfectly. Ubuntu 22.04.2 LTS linux-image-5.19.0-35-generic: 5.19.0-35.36~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:49:59 2023 InstallationDate: Installed on 2022-04-24 (314 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009275/+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 2009275] [NEW] HDMI audio doesn't work for AMD RX6700 XT
Public bug reported: After the recent update to the 5.19.35 kernel (installed on 4th March 2023), the HDMI audio (out) of my AMD RX6700 XT doesn't work anymore. I don't see any devices in Gnome or when listing the devices with `aplay -a` In the ACPI error message on startup I see: kernel: snd_hda_intel :01:00.1: no codecs initialized kernel: hdaudio hdaudioC1D0: no AFG or MFG node found When I boot with the old 5.19.0.32 kernel version HDMI audio works perfectly. Ubuntu 22.04.2 LTS linux-image-5.19.0-35-generic: 5.19.0-35.36~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:49:59 2023 InstallationDate: Installed on 2022-04-24 (314 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009275 Title: HDMI audio doesn't work for AMD RX6700 XT Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After the recent update to the 5.19.35 kernel (installed on 4th March 2023), the HDMI audio (out) of my AMD RX6700 XT doesn't work anymore. I don't see any devices in Gnome or when listing the devices with `aplay -a` In the ACPI error message on startup I see: kernel: snd_hda_intel :01:00.1: no codecs initialized kernel: hdaudio hdaudioC1D0: no AFG or MFG node found When I boot with the old 5.19.0.32 kernel version HDMI audio works perfectly. Ubuntu 22.04.2 LTS linux-image-5.19.0-35-generic: 5.19.0-35.36~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:49:59 2023 InstallationDate: Installed on 2022-04-24 (314 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009275/+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 2007788] [NEW] Exporting a logical volume via NBD leads to kernel crashes
Public bug reported: I'm exporting a logical volume via nbd-server to a raspberry pi which uses the nbd device as a physical volume for its own LVM stack. Some operations such as running mkfs.ext2 on a logical volume inside the raspberry pi crash the exporting server. I have seen various messages from the kernel in the syslog & dmesg and experienced lock-ups etc. The operations that cause this cause the issues consistently. For instance the mkfs.ext2 on the RPI cause this to appear in dmesg on the server exporting the NBD: [ 1188.468279] [ cut here ] [ 1188.468282] kernel BUG at include/linux/highmem.h:279! [ 1188.468289] invalid opcode: [#1] PREEMPT SMP NOPTI [ 1188.468292] CPU: 2 PID: 4944 Comm: pool Not tainted 5.19.0-32-generic #33~22.04.1-Ubuntu [ 1188.468295] Hardware name: Gigabyte Technology Co., Ltd. X570 GAMING X/X570 GAMING X, BIOS F37 12/26/2022 [ 1188.468296] RIP: 0010:zero_user_segments.constprop.0+0x15c/0x1a0 [ 1188.468303] Code: ff 48 8b 57 48 f6 c2 01 0f 84 00 ff ff ff 48 83 ea 01 48 39 d7 0f 84 f3 fe ff ff 41 be 00 10 00 00 4c 39 f0 0f 86 03 ff ff ff <0f> 0b f7 c3 ff 0f 00 00 0f 85 04 ff ff ff 48 8b 03 a9 00 00 01 00 [ 1188.468305] RSP: 0018:be5984817be8 EFLAGS: 00010206 [ 1188.468308] RAX: fae0 RBX: f46887f2f800 RCX: [ 1188.468309] RDX: 0017c0020037 RSI: RDI: f46887f2f800 [ 1188.468311] RBP: be5984817c20 R08: f4688000 R09: [ 1188.468312] R10: R11: R12: fae0 [ 1188.468314] R13: R14: 1000 R15: 977ac000 [ 1188.468315] FS: 7fd36bfff640() GS:9782dea8() knlGS: [ 1188.468317] CS: 0010 DS: ES: CR0: 80050033 [ 1188.468319] CR2: 04c500e89000 CR3: 000114472000 CR4: 00350ee0 [ 1188.468321] Call Trace: [ 1188.468323] [ 1188.468325] truncate_inode_partial_folio+0xce/0x240 [ 1188.468329] truncate_inode_pages_range+0x237/0x650 [ 1188.468332] ? hrtimer_cancel+0x21/0x50 [ 1188.468335] ? futex_wait+0x238/0x260 [ 1188.468339] ? __hrtimer_init+0x120/0x120 [ 1188.468342] ? rseq_get_rseq_cs.isra.0+0x1b/0x270 [ 1188.468345] ? bd_prepare_to_claim+0x131/0x150 [ 1188.468349] ? rseq_ip_fixup+0x72/0x1b0 [ 1188.468351] truncate_bdev_range+0x4f/0x120 [ 1188.468354] blkdev_common_ioctl+0x479/0x980 [ 1188.468358] blkdev_ioctl+0x133/0x2a0 [ 1188.468360] __x64_sys_ioctl+0x9a/0xe0 [ 1188.468363] do_syscall_64+0x59/0x90 [ 1188.468367] ? syscall_exit_to_user_mode+0x2a/0x50 [ 1188.468370] ? do_syscall_64+0x69/0x90 [ 1188.468372] ? do_syscall_64+0x69/0x90 [ 1188.468375] ? syscall_exit_to_user_mode+0x2a/0x50 [ 1188.468377] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 1188.468380] RIP: 0033:0x7fd371d1aaff [ 1188.468383] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 [ 1188.468385] RSP: 002b:7fd36bffeb00 EFLAGS: 0246 ORIG_RAX: 0010 [ 1188.468387] RAX: ffda RBX: 7fd36bffebb0 RCX: 7fd371d1aaff [ 1188.468389] RDX: 7fd36bffebb0 RSI: 1277 RDI: 0007 [ 1188.468390] RBP: 7fd36bffec00 R08: R09: 0001 [ 1188.468391] R10: fffbfae0 R11: 0246 R12: 557743114ea0 [ 1188.468393] R13: 557743114e40 R14: 5577431117d0 R15: 0007 [ 1188.468395] [ 1188.468396] Modules linked in: rfcomm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi bridge stp snd_hda_intel llc snd_intel_dspcfg cmac snd_intel_sdw_acpi algif_hash snd_hda_codec algif_skcipher snd_hda_core af_alg snd_hwdep intel_rapl_msr snd_pcm intel_rapl_common bnep snd_seq_midi btusb snd_seq_midi_event btrtl snd_rawmidi edac_mce_amd btbcm sch_fq_codel snd_seq kvm_amd btintel btmtk msr snd_seq_device binfmt_misc kvm bluetooth snd_timer parport_pc ftdi_sio nls_iso8859_1 snd ecdh_generic rapl ppdev serio_raw gigabyte_wmi wmi_bmof usbserial joydev input_leds k10temp ccp ecc soundcore lp ramoops mac_hid pstore_blk parport reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 amdgpu iommu_v2 gpu_sched i2c_algo_bit dm_thin_pool drm_ttm_helper hid_generic dm_persistent_data ttm usbhid dm_bio_prison drm_display_helper hid dm_bufio cec libcrc32c rc_core drm_kms_helper syscopyarea sysfillrect crct10dif_pclmul sysimgblt crc32_pclmul ghash_clmulni_in tel [ 1188.468452] aesni_intel crypto_simd fb_sys_fops nvme ahci xhci_pci r8169 cryptd psmouse drm i2c_piix4 nvme_core libahci xhci_pci_renesas realtek wmi [ 1188.468463] ---[ end trace ]--- [ 1188.614812] RIP: 0010:zero_user_segments.constprop.0+0x15c/0x1a0 [ 1188.614818] Code: ff 48 8b 57 48 f6 c2 01 0f 84 00 ff ff ff 48 83 ea 01 48 39 d7 0f 84 f3 fe ff ff 41 be 00 10 00 00 4c 39 f0 0f 86 03 ff ff ff <0f>
[Kernel-packages] [Bug 1994025] Re: Suspend or hibernate fails when using Arc Alchemist (DG2) graphics
Seems like this issue was caused by nvidia driver remainders, which caused an instant wake-up after suspend or hibernate. ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Incomplete ** Changed in: linux-oem-6.0 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1994025 Title: Suspend or hibernate fails when using Arc Alchemist (DG2) graphics Status in linux-oem-6.0 package in Ubuntu: Invalid Bug description: The computer is unable to suspend or hibernate, when a DG2 graphics card is installed and in-use in the system. When attempting to suspend or hibernate the system will turn off its screens for a few seconds after which they will light up again. I am using the latest linux-oem-6.0 kernel and the mesa 22.2 packages from the canonical-x/x-staging ppa. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04b 6.0.0.1005.5 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 12:07:27 2022 InstallationDate: Installed on 2022-02-23 (242 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-oem-6.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1994025/+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 1971712] Re: Add support for Intel DG2
It seems like there is no more force-probe required for oem-6.1, works fine out-of-the-box now. When is the 22.2 mesa from ppa:canonical-x/x-staging going to be released, currently using the linux-oem-6.1 kernel together with the 23.0 mesa from the Intel Arc package sources. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1971712] Re: Add support for Intel DG2
Is this not going to happen? > kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Confirmed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1971712] Re: Add support for Intel DG2
The new firmware package works fine with the 6.0 kernel, it loads the GuC and HuC Firmware, as seen below: [4.691687] i915 :03:00.0: [drm] Finished loading DMC firmware i915/dg2_dmc_ver2_06.bin (v2.6) [4.702309] i915 :03:00.0: [drm] GuC firmware i915/dg2_guc_70.1.2.bin version 70. I presume the firmware updates are a preparation for the i915/drm backports to the 6.0-oem kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Confirmed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1994157] [NEW] Chromium and Firefox snap won't launch with Linux 6.0.0-1006-oem Kernel
Private bug reported: When using the latest Linux 6.0.0-1006-oem Kernel, Firefox and Chromium won't open anymore. ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Invalid ** Information type changed from Public to Private -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1994157 Title: Chromium and Firefox snap won't launch with Linux 6.0.0-1006-oem Kernel Status in linux-oem-6.0 package in Ubuntu: Invalid Bug description: When using the latest Linux 6.0.0-1006-oem Kernel, Firefox and Chromium won't open anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1994157/+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 1994025] [NEW] Suspend or hibernate fails when using Arc Alchemist (DG2) graphics
Public bug reported: The computer is unable to suspend or hibernate, when a DG2 graphics card is installed and in-use in the system. When attempting to suspend or hibernate the system will turn off its screens for a few seconds after which they will light up again. I am using the latest linux-oem-6.0 kernel and the mesa 22.2 packages from the canonical-x/x-staging ppa. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04b 6.0.0.1005.5 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 12:07:27 2022 InstallationDate: Installed on 2022-02-23 (242 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-oem-6.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Package changed: linux-meta-oem-6.0 (Ubuntu) => linux-oem-6.0 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1994025 Title: Suspend or hibernate fails when using Arc Alchemist (DG2) graphics Status in linux-oem-6.0 package in Ubuntu: New Bug description: The computer is unable to suspend or hibernate, when a DG2 graphics card is installed and in-use in the system. When attempting to suspend or hibernate the system will turn off its screens for a few seconds after which they will light up again. I am using the latest linux-oem-6.0 kernel and the mesa 22.2 packages from the canonical-x/x-staging ppa. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04b 6.0.0.1005.5 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 12:07:27 2022 InstallationDate: Installed on 2022-02-23 (242 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-oem-6.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1994025/+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 1992667] Re: Application windows invisible (on DG2 graphics)
Hi Timo, Upgrading to Mesa 22.2 seems to resolve this issue. Using the packages from the intel repository (https://dgpu-docs.intel.com/installation- guides/ubuntu/ubuntu-jammy-arc.html) works as well. Is it planned to release the updated mesa 22.2 packages to Ubuntu 22.04? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992667 Title: Application windows invisible (on DG2 graphics) Status in linux-oem-6.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in linux-oem-6.0 source package in Jammy: New Status in mesa source package in Jammy: New Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+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 1992667] Re: Application windows invisible (on DG2 graphics)
I've managed to reproduce this bug on an Arc A380 and Arc A770 GPU. I've attached the requested lspci output for the A770. Ubuntu 22.04 has already received a mesa update with backported patches for DG2 support: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1971712 I haven't tried 22.10 yet, but I will do so in the coming days. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+attachment/5623860/+files/lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992667 Title: Application windows invisible (on DG2 graphics) Status in linux-oem-6.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+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 1971712] Re: Add support for Intel DG2
Looking forward to linux-oem-6.0 support. Got an A380 and A770 here for testing purposes. It seems like the current proposed build of the linux-oem-6.0 kernel still has some issues in this regard. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: In Progress Status in mesa source package in Jammy: Fix Released Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1992667] [NEW] Application windows invisible (on DG2 graphics)
Public bug reported: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot of the described bug" https://bugs.launchpad.net/bugs/1992667/+attachment/5623541/+files/gnome_shell_invisible_windows.png ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992667 Title: Application windows invisible (on DG2 graphics) Status in gnome-shell package in Ubuntu: New Status in linux-oem-6.0 package in Ubuntu: New Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992667/+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 1992532] [NEW] Enable DG2 graphics support
Public bug reported: DG2 graphics support should be enabled by default, dmesg outputs the following: i915 :67:00.0: Your graphics device 56a5 is not properly supported by the driver in this kernel version. To force driver probe anyway, use i915.force_probe=56a5 module parameter or CONFIG_DRM_I915_FORCE_PROBE=56a5 configuration option, or (recommended) check for kernel updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04b 6.0.0.1005.5 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 01:29:02 2022 InstallationDate: Installed on 2022-10-11 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-oem-6.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy package-from-proposed ** Package changed: linux-meta-oem-6.0 (Ubuntu) => linux-oem-6.0 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992532 Title: Enable DG2 graphics support Status in linux-oem-6.0 package in Ubuntu: New Bug description: DG2 graphics support should be enabled by default, dmesg outputs the following: i915 :67:00.0: Your graphics device 56a5 is not properly supported by the driver in this kernel version. To force driver probe anyway, use i915.force_probe=56a5 module parameter or CONFIG_DRM_I915_FORCE_PROBE=56a5 configuration option, or (recommended) check for kernel updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04b 6.0.0.1005.5 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 01:29:02 2022 InstallationDate: Installed on 2022-10-11 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-oem-6.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992532/+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 1971712] Re: Add support for Intel DG2
Are there any plans for providing an i915 DKMS Module with DG2 Support for oem-5.17? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1990595] [NEW] Kernel Module usbserial not available on Jammy 22.04 (Raspi 4)
Public bug reported: After installing a USB to Serial Adapter on a Raspberry Pi 4 running Ubuntu Server 22.04 LTS, no tty device is created under /dev/ttyUSB... dmesg: [3.793123] usb 1-1.2.1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 [3.793142] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.793149] usb 1-1.2.1: Product: FT232R USB UART [3.793155] usb 1-1.2.1: Manufacturer: FTDI [3.793160] usb 1-1.2.1: SerialNumber: A504D2PO The usbserial and ftdi_sio kernel modules are not included in the linux- modules-extra-5.15.0-1015-raspi package. dpkg-query -L linux-modules-extra-5.15.0-1015-raspi |grep -E 'usbserial|ftdio_sio' => NO OUTPUT lsb_release -rd: Description:Ubuntu 22.04.1 LTS Release:22.04 uname -a: Linux Host 5.15.0-1014-raspi #16-Ubuntu SMP PREEMPT Thu Aug 25 09:50:55 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux For Reference: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947723 Configuration from /boot/config-5.15.0-1014-raspi: grep USB_SERIAL /boot/config-5.15.0-1014-raspi CONFIG_USB_SERIAL=m <= set CONFIG_USB_SERIAL_GENERIC=y <= set CONFIG_USB_SERIAL_FTDI_SIO=m <= set Fix: According to the configuration, the modules should be built. Include the modules in the package. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: - After installing a USB to Serial Adapter on a Raspberry PI 4 running + After installing a USB to Serial Adapter on a Raspberry Pi 4 running Ubuntu Server 22.04 LTS, no tty device is created under /dev/ttyUSB... dmesg: [3.793123] usb 1-1.2.1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 [3.793142] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.793149] usb 1-1.2.1: Product: FT232R USB UART [3.793155] usb 1-1.2.1: Manufacturer: FTDI [3.793160] usb 1-1.2.1: SerialNumber: A504D2PO The usbserial and ftdi_sio kernel modules are not included in the linux- modules-extra-5.15.0-1015-raspi package. dpkg-query -L linux-modules-extra-5.15.0-1015-raspi |grep -E 'usbserial|ftdio_sio' => NO OUTPUT lsb_release -rd: Description:Ubuntu 22.04.1 LTS Release:22.04 uname -a: Linux Host 5.15.0-1014-raspi #16-Ubuntu SMP PREEMPT Thu Aug 25 09:50:55 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux For Reference: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947723 - Configuration from /boot/config-5.15.0-1014-raspi: grep USB_SERIAL /boot/config-5.15.0-1014-raspi CONFIG_USB_SERIAL=m <= set CONFIG_USB_SERIAL_GENERIC=y <= set CONFIG_USB_SERIAL_FTDI_SIO=m <= set - Fix: + Fix: According to the configuration, the modules should be built. Include the modules in the package. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1990595 Title: Kernel Module usbserial not available on Jammy 22.04 (Raspi 4) Status in linux-raspi package in Ubuntu: New Bug description: After installing a USB to Serial Adapter on a Raspberry Pi 4 running Ubuntu Server 22.04 LTS, no tty device is created under /dev/ttyUSB... dmesg: [3.793123] usb 1-1.2.1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 [3.793142] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.793149] usb 1-1.2.1: Product: FT232R USB UART [3.793155] usb 1-1.2.1: Manufacturer: FTDI [3.793160] usb 1-1.2.1: SerialNumber: A504D2PO The usbserial and ftdi_sio kernel modules are not included in the linux-modules-extra-5.15.0-1015-raspi package. dpkg-query -L linux-modules-extra-5.15.0-1015-raspi |grep -E 'usbserial|ftdio_sio' => NO OUTPUT lsb_release -rd: Description:Ubuntu 22.04.1 LTS Release:22.04 uname -a: Linux Host 5.15.0-1014-raspi #16-Ubuntu SMP PREEMPT Thu Aug 25 09:50:55 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux For Reference: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947723 Configuration from /boot/config-5.15.0-1014-raspi: grep USB_SERIAL /boot/config-5.15.0-1014-raspi CONFIG_USB_SERIAL=m <= set CONFIG_USB_SERIAL_GENERIC=y <= set CONFIG_USB_SERIAL_FTDI_SIO=m <= set Fix: According to the configuration, the modules should be built. Include the modules in the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1990595/+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 1978475] Re: Docker container ports cannot be allocated
Okay, I updated to the latest kernel 5.13.0-1031-aws and the problem doesn't seem to be present anymore: sudo apt update apt list --upgradable apt-transport-https/focal-updates 2.0.9 all [upgradable from: 2.0.8] apt-utils/focal-updates 2.0.9 amd64 [upgradable from: 2.0.8] apt/focal-updates 2.0.9 amd64 [upgradable from: 2.0.8] cloud-init/focal-updates 22.2-0ubuntu1~20.04.2 all [upgradable from: 22.2-0ubuntu1~20.04.1] intel-microcode/focal-updates 3.20220510.0ubuntu0.20.04.1 amd64 [upgradable from: 3.20210608.0ubuntu0.20.04.1] libapt-pkg6.0/focal-updates 2.0.9 amd64 [upgradable from: 2.0.8] linux-aws/focal-updates,focal-security 5.13.0.1031.35~20.04.25 amd64 [upgradable from: 5.13.0.1029.32~20.04.24] linux-headers-aws/focal-updates,focal-security 5.13.0.1031.35~20.04.25 amd64 [upgradable from: 5.13.0.1029.32~20.04.24] linux-image-aws/focal-updates,focal-security 5.13.0.1031.35~20.04.25 amd64 [upgradable from: 5.13.0.1029.32~20.04.24] linux-libc-dev/focal-updates,focal-security 5.4.0-120.136 amd64 [upgradable from: 5.4.0-117.132] # uname -a Linux ip-10-0-69-193 5.13.0-1031-aws #35~20.04.1-Ubuntu SMP Mon Jun 13 22:30:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux I was able to confirm this on two affected hosts. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1978475 Title: Docker container ports cannot be allocated Status in linux-aws-5.13 package in Ubuntu: Confirmed Bug description: This is a follow-up bug to https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.13/+bug/1977919 I can confirm that the problem is indeed not fully fixed. @electricdaemon said: > Test kernel posted fixes crash but has another bug with unkillable stuck defunct docker-proxy service causing more issues. Bug is not solved. Tested on Linux AWS Lightsail instance. What I'm seeing is that docker-compose stacks either don't start at all or only start partially. In both cases the affected containers cannot start due to their host port being already allocated. I can say with absolute certainty that the ports on the host are dedicated to container applications and no other service is actually bound to the affected port numbers. # uname -a Linux ip-10-0-69-193 5.13.0-1029-aws #32~20.04.1-Ubuntu SMP Thu Jun 9 13:03:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # apt-cache policy docker containerd docker: Installed: (none) Candidate: 1.5-2 Version table: 1.5-2 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal/universe amd64 Packages containerd: Installed: (none) Candidate: 1.5.9-0ubuntu1~20.04.4 Version table: 1.5.9-0ubuntu1~20.04.4 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1.3.3-0ubuntu2 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages # docker-compose --version docker-compose version 1.29.2, build 5becea4c root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose up -d Creating network "myappserv-int_default" with the default driver Creating myapp-migrator-int ... done Creating myapp-dealer-int ... Creating myapp-offer-int... Creating myapp-customer-int ... Creating myapp-customer-int ... error Creating myapp-dealer-int ... done Creating myapp-offer-int... done : port is already allocated ERROR: for customer Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (fe4112364528b0e7d192c793929c579e8a81af715118c8f83ad7e65e7397f3be): Bind for 0.0.0.0:9001 failed: port is already allocated ERROR: Encountered errors while bringing up the project. root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose down Stopping myapp8-offer-int ... done Stopping myapp8-dealer-int ... done Removing myapp8-customer-int ... done Removing myapp8-offer-int... done Removing myapp8-dealer-int ... done Removing myapp8-migrator-int ... done Removing network myappserv-int_default root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose up -d Creating network "myappserv-int_default" with the default driver Creating myapp8-migrator-int ... done Creating myapp8-offer-int... Creating myapp8-customer-int ... Creating myapp8-customer-int ... error WARNING: Host is already in use by another container Creating myapp8-offer-int... done ERROR: for myapp8-customer-int Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (72fc08854cd278e63cd3234e7fb03c08cb045efdcfb9e42075a1250d893645d5): Bind for 0.0.0.0:9001 failed Creating myapp8-dealer-int ... done ERROR: for customer Cannot start service customer: driver failed
[Kernel-packages] [Bug 1978475] Re: Docker container ports cannot be allocated
I'm currently on a conference so I won't be able to look into this further until Thursday. I should be able to provide more information by the end of the week. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1978475 Title: Docker container ports cannot be allocated Status in linux-aws-5.13 package in Ubuntu: Confirmed Bug description: This is a follow-up bug to https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.13/+bug/1977919 I can confirm that the problem is indeed not fully fixed. @electricdaemon said: > Test kernel posted fixes crash but has another bug with unkillable stuck defunct docker-proxy service causing more issues. Bug is not solved. Tested on Linux AWS Lightsail instance. What I'm seeing is that docker-compose stacks either don't start at all or only start partially. In both cases the affected containers cannot start due to their host port being already allocated. I can say with absolute certainty that the ports on the host are dedicated to container applications and no other service is actually bound to the affected port numbers. # uname -a Linux ip-10-0-69-193 5.13.0-1029-aws #32~20.04.1-Ubuntu SMP Thu Jun 9 13:03:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # apt-cache policy docker containerd docker: Installed: (none) Candidate: 1.5-2 Version table: 1.5-2 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal/universe amd64 Packages containerd: Installed: (none) Candidate: 1.5.9-0ubuntu1~20.04.4 Version table: 1.5.9-0ubuntu1~20.04.4 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1.3.3-0ubuntu2 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages # docker-compose --version docker-compose version 1.29.2, build 5becea4c root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose up -d Creating network "myappserv-int_default" with the default driver Creating myapp-migrator-int ... done Creating myapp-dealer-int ... Creating myapp-offer-int... Creating myapp-customer-int ... Creating myapp-customer-int ... error Creating myapp-dealer-int ... done Creating myapp-offer-int... done : port is already allocated ERROR: for customer Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (fe4112364528b0e7d192c793929c579e8a81af715118c8f83ad7e65e7397f3be): Bind for 0.0.0.0:9001 failed: port is already allocated ERROR: Encountered errors while bringing up the project. root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose down Stopping myapp8-offer-int ... done Stopping myapp8-dealer-int ... done Removing myapp8-customer-int ... done Removing myapp8-offer-int... done Removing myapp8-dealer-int ... done Removing myapp8-migrator-int ... done Removing network myappserv-int_default root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose up -d Creating network "myappserv-int_default" with the default driver Creating myapp8-migrator-int ... done Creating myapp8-offer-int... Creating myapp8-customer-int ... Creating myapp8-customer-int ... error WARNING: Host is already in use by another container Creating myapp8-offer-int... done ERROR: for myapp8-customer-int Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (72fc08854cd278e63cd3234e7fb03c08cb045efdcfb9e42075a1250d893645d5): Bind for 0.0.0.0:9001 failed Creating myapp8-dealer-int ... done ERROR: for customer Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (72fc08854cd278e63cd3234e7fb03c08cb045efdcfb9e42075a1250d893645d5): Bind for 0.0.0.0:9001 failed: port is already allocated ERROR: Encountered errors while bringing up the project. # docker-compose config services: customer: container_name: myapp8-customer-int depends_on: migrator: condition: service_completed_successfully image: reg.mydomain.tld/myapp8/customer:430d4ca ports: - published: 9001 target: 9001 restart: always dealer: container_name: myapp8-dealer-int depends_on: migrator: condition: service_completed_successfully image: reg.mydomain.tld/myapp8/dealer:430d4ca ports: - published: 9002 target: 9002 restart: always migrator: container_name: myapp8-migrator-int image: reg.mydomain.tld/myapp8/migrator:430d4ca offer: container_name: myapp8-offer-int depends_on: migrator: condition:
[Kernel-packages] [Bug 1978475] Re: Docker container ports cannot be allocated
This issue did not exist on Kernels lower than: 5.13.0-1028-aws 5.13.0-1028-aws broke Docker completely and 5.13.0-1029-aws breaks Docker partially -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1978475 Title: Docker container ports cannot be allocated Status in linux-aws-5.13 package in Ubuntu: Confirmed Bug description: This is a follow-up bug to https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.13/+bug/1977919 I can confirm that the problem is indeed not fully fixed. @electricdaemon said: > Test kernel posted fixes crash but has another bug with unkillable stuck defunct docker-proxy service causing more issues. Bug is not solved. Tested on Linux AWS Lightsail instance. What I'm seeing is that docker-compose stacks either don't start at all or only start partially. In both cases the affected containers cannot start due to their host port being already allocated. I can say with absolute certainty that the ports on the host are dedicated to container applications and no other service is actually bound to the affected port numbers. # uname -a Linux ip-10-0-69-193 5.13.0-1029-aws #32~20.04.1-Ubuntu SMP Thu Jun 9 13:03:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # apt-cache policy docker containerd docker: Installed: (none) Candidate: 1.5-2 Version table: 1.5-2 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal/universe amd64 Packages containerd: Installed: (none) Candidate: 1.5.9-0ubuntu1~20.04.4 Version table: 1.5.9-0ubuntu1~20.04.4 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1.3.3-0ubuntu2 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages # docker-compose --version docker-compose version 1.29.2, build 5becea4c root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose up -d Creating network "myappserv-int_default" with the default driver Creating myapp-migrator-int ... done Creating myapp-dealer-int ... Creating myapp-offer-int... Creating myapp-customer-int ... Creating myapp-customer-int ... error Creating myapp-dealer-int ... done Creating myapp-offer-int... done : port is already allocated ERROR: for customer Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (fe4112364528b0e7d192c793929c579e8a81af715118c8f83ad7e65e7397f3be): Bind for 0.0.0.0:9001 failed: port is already allocated ERROR: Encountered errors while bringing up the project. root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose down Stopping myapp8-offer-int ... done Stopping myapp8-dealer-int ... done Removing myapp8-customer-int ... done Removing myapp8-offer-int... done Removing myapp8-dealer-int ... done Removing myapp8-migrator-int ... done Removing network myappserv-int_default root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose up -d Creating network "myappserv-int_default" with the default driver Creating myapp8-migrator-int ... done Creating myapp8-offer-int... Creating myapp8-customer-int ... Creating myapp8-customer-int ... error WARNING: Host is already in use by another container Creating myapp8-offer-int... done ERROR: for myapp8-customer-int Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (72fc08854cd278e63cd3234e7fb03c08cb045efdcfb9e42075a1250d893645d5): Bind for 0.0.0.0:9001 failed Creating myapp8-dealer-int ... done ERROR: for customer Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (72fc08854cd278e63cd3234e7fb03c08cb045efdcfb9e42075a1250d893645d5): Bind for 0.0.0.0:9001 failed: port is already allocated ERROR: Encountered errors while bringing up the project. # docker-compose config services: customer: container_name: myapp8-customer-int depends_on: migrator: condition: service_completed_successfully image: reg.mydomain.tld/myapp8/customer:430d4ca ports: - published: 9001 target: 9001 restart: always dealer: container_name: myapp8-dealer-int depends_on: migrator: condition: service_completed_successfully image: reg.mydomain.tld/myapp8/dealer:430d4ca ports: - published: 9002 target: 9002 restart: always migrator: container_name: myapp8-migrator-int image: reg.mydomain.tld/myapp8/migrator:430d4ca offer: container_name: myapp8-offer-int depends_on: migrator: condition: service_completed_successfully
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
Created a new bug report: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.13/+bug/1978475 Hopefully @electricdaemon and other affected users can help to provide a reproducible test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Released Status in linux-azure-5.13 source package in Focal: Fix Released Status in linux-gcp-5.13 source package in Focal: Fix Released Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Released Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP:
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
I can confirm that the problem is indeed not fully fixed. @electricdaemon said: > Test kernel posted fixes crash but has another bug with unkillable stuck defunct docker-proxy service causing more issues. Bug is not solved. Tested on Linux AWS Lightsail instance. And that's the problem that I'm seeing as well. Still gathering data for a bug report. # uname -a Linux ip-10-0-69-193 5.13.0-1029-aws #32~20.04.1-Ubuntu SMP Thu Jun 9 13:03:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose up -d Creating network "myappserv-int_default" with the default driver Creating myapp-migrator-int ... done Creating myapp-dealer-int ... Creating myapp-offer-int... Creating myapp-customer-int ... Creating myapp-customer-int ... error Creating myapp-dealer-int ... done Creating myapp-offer-int... done : port is already allocated ERROR: for customer Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (fe4112364528b0e7d192c793929c579e8a81af715118c8f83ad7e65e7397f3be): Bind for 0.0.0.0:9001 failed: port is already allocated ERROR: Encountered errors while bringing up the project. root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose down Stopping myapp8-offer-int ... done Stopping myapp8-dealer-int ... done Removing myapp8-customer-int ... done Removing myapp8-offer-int... done Removing myapp8-dealer-int ... done Removing myapp8-migrator-int ... done Removing network myappserv-int_default root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose up -d Creating network "myappserv-int_default" with the default driver Creating myapp8-migrator-int ... done Creating myapp8-offer-int... Creating myapp8-customer-int ... Creating myapp8-customer-int ... error WARNING: Host is already in use by another container Creating myapp8-offer-int... done ERROR: for myapp8-customer-int Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (72fc08854cd278e63cd3234e7fb03c08cb045efdcfb9e42075a1250d893645d5): Bind for 0.0.0.0:9001 failed Creating myapp8-dealer-int ... done ERROR: for customer Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (72fc08854cd278e63cd3234e7fb03c08cb045efdcfb9e42075a1250d893645d5): Bind for 0.0.0.0:9001 failed: port is already allocated ERROR: Encountered errors while bringing up the project. # docker-compose config services: customer: container_name: myapp8-customer-int depends_on: migrator: condition: service_completed_successfully image: reg.mydomain.tld/myapp8/customer:430d4ca ports: - published: 9001 target: 9001 restart: always dealer: container_name: myapp8-dealer-int depends_on: migrator: condition: service_completed_successfully image: reg.mydomain.tld/myapp8/dealer:430d4ca ports: - published: 9002 target: 9002 restart: always migrator: container_name: myapp8-migrator-int image: reg.mydomain.tld/myapp8/migrator:430d4ca offer: container_name: myapp8-offer-int depends_on: migrator: condition: service_completed_successfully image: reg.mydomain.tld/myapp8/offer:430d4ca ports: - published: 9003 target: 9003 restart: always version: '3' # netstat -tulpn | egrep "(Foreign|docker-proxy)" Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 0.0.0.0:90010.0.0.0:* LISTEN 1090/docker-proxy tcp0 0 0.0.0.0:90020.0.0.0:* LISTEN 4519/docker-proxy tcp0 0 0.0.0.0:90030.0.0.0:* LISTEN 4539/docker-proxy tcp0 0 0.0.0.0:80550.0.0.0:* LISTEN 1037/docker-proxy tcp0 0 0.0.0.0:19000 0.0.0.0:* LISTEN 997/docker-proxy tcp0 0 127.0.0.1:4 0.0.0.0:* LISTEN 1077/docker-proxy tcp0 0 0.0.0.0:80650.0.0.0:* LISTEN 1016/docker-proxy tcp6 0 0 :::9001 :::*LISTEN 1096/docker-proxy tcp6 0 0 :::9002 :::*LISTEN 4525/docker-proxy tcp6 0 0 :::9003 :::*LISTEN 4544/docker-proxy tcp6 0 0 :::8055 :::*LISTEN 1043/docker-proxy tcp6 0 0 :::19000
[Kernel-packages] [Bug 1975862] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593168/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593171/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593170/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593167/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593169/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593166/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593158/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593159/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593163/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593162/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593164/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593161/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593165/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593160/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593156/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593157/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975862] [NEW] Can't mount NFS share
Public bug reported: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected una ** Tags added: apport-collected una ** Description changed: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.24 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: sebastian 4875 F pulseaudio + /dev/snd/controlC0: sebastian 4875 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20.3 + InstallationDate: Installed on 2021-03-20 (432 days ago) + InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 + IwConfig: + lono wireless extensions. + + enp34s0 no wireless extensions. + MachineType: Micro-Star International Co., Ltd. MS-7B89 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash + ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-44-generic N/A + linux-backports-modules-5.13.0-44-generic N/A + linux-firmware 1.187.31 + RfKill: + + Tags: una + Uname: Linux 5.13.0-44-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/30/2019 + dmi.bios.release: 5.14 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2.60 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: B450M MORTAR MAX (MS-7B89) + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Micro-Star International Co., Ltd. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: MS-7B89 + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: 1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. -- You received this bug notification because you are a member of Ke
[Kernel-packages] [Bug 1975862] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1975862/+attachment/5593155/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975862 Title: Can't mount NFS share Status in linux package in Ubuntu: Confirmed Bug description: i can't mount NFS Share on Kernel 5.13.0-41 and 5.13.0-44. I mount via fstab : 10.1.1.200:/Multimedia /media/multimedia nfs4rw,users,soft 0 0 If i boot up with kernel 5.13.0-40 everything works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 4875 F pulseaudio /dev/snd/controlC0: sebastian 4875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (432 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-44-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-44-generic N/A linux-backports-modules-5.13.0-44-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975862/+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 1975422] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592057/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592058/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592056/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592059/+files/acpidump.txt ** 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/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592052/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592051/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592055/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592054/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592053/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592050/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592047/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592048/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592046/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592049/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592045/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1975422] Re: Error mount nfs Share via fstab
apport information ** Tags added: apport-collected una ** Description changed: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.24 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: sebastian 1568 F pulseaudio + /dev/snd/controlC0: sebastian 1568 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20.3 + InstallationDate: Installed on 2021-03-20 (428 days ago) + InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 + IwConfig: + lono wireless extensions. + + enp34s0 no wireless extensions. + MachineType: Micro-Star International Co., Ltd. MS-7B89 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash + ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-41-generic N/A + linux-backports-modules-5.13.0-41-generic N/A + linux-firmware 1.187.31 + RfKill: + + Tags: una + Uname: Linux 5.13.0-41-generic x86_64 + UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: False + dmi.bios.date: 12/30/2019 + dmi.bios.release: 5.14 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2.60 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: B450M MORTAR MAX (MS-7B89) + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Micro-Star International Co., Ltd. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: MS-7B89 + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: 1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1975422/+attachment/5592044/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: Confirmed Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sebastian 1568 F pulseaudio /dev/snd/controlC0: sebastian 1568 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2021-03-20 (428 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B89 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=UUID=ca450908-f231-4e70-b01b-01cc18c39400 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.187.31 RfKill: Tags: una Uname: Linux 5.13.0-41-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/30/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Mic
[Kernel-packages] [Bug 1975422] [NEW] Error mount nfs Share via fstab
Public bug reported: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975422 Title: Error mount nfs Share via fstab Status in linux package in Ubuntu: New Bug description: I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40, there is no problem. If i boot up with kernel 5.13.0-41 i become an error. I use Linux mint 20.3. i have this error with two different computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975422/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Try nvidia.NVreg_PreserveVideoMemoryAllocations=1 as suggested by @vanvugt You may wanna change the file path of the temporary file thought for better performance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A
[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
I'm using a RTX 3080 Ti on a Z690 Desktop motherboard and enabling the S0ix option fixed the problem for me. I've added the following option "nvidia.NVreg_EnableS0ixPowerManagement=1" to GRUB_CMDLINE_LINUX_DEFAULT. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte
[Kernel-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection
Eh... so on a fresh 22.04 installation (dell xps 13) my internet connection drops rougly every minute or so. It all worked fine on 21.04, the wifi hasn't changed. This is horrible I have to say not sure if this is the right bug report for it. Any terminal output I should present? -- 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/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in linux package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.15 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 pr500k-9912ec-1 36301ded-0ac5-4a86-9621-87290ef159af /org/freedesktop/NetworkManager/ActiveConnection/5 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI
[Kernel-packages] [Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
Seems fixed in linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+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 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)
Was able to reproduce this bug on two of my machines aswell. Both were using Nvidia 3000 Series graphics. Booting the 5.15.0-18 Kernel or 5.16 Mainline Kernels didn't have this issue. Seems like only 5.15.0-22 is affected by this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+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 1964440] Re: 5.15.0-22: No console displayed on EFI systems
Was able to reproduce this issue on two of my machines aswell. Both were installed in EFI Mode. Booting the older 5.15.0-18 kernel or 5.16 mainline kernels work around this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems Status in linux package in Ubuntu: Confirmed Bug description: DISCLAIMER: This is my second-ever bug report. Apologies in advance for any missing or inaccurate info. I am willing to troubleshoot and supply more/better info as needed. PROBLEM DESCRIPTION: After upgrading the kernel on my Ubuntu 22.04 Server test system from 5.15.0-18 to 5.15.0-22, I see absolutely no console output on my display past the grub menu. I can give the system a few seconds to finish booting, log in blindly and watch the activity LEDs on e.g. the network interface as i run a ping or similar. I can also log in remotely via SSH, and/or use a serial console. So the system definitely does boot. But my actual display/screen shows no console output. ENVIRONMENT: (Output gathered via SSH while display was showing no output) testuser@testserver:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy testuser@testserver:~$ uname -a Linux testserver 5.15.0-22-generic #22-Ubuntu SMP Tue Feb 8 10:16:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This was initially discovered on an Ubuntu Server VM running in EFI mode on VirtualBox 6.1.32. System was installed with the daily 'jammy-live-server-amd64.iso' image from 2022-03-07, fully upgraded as of 2022-03-10. Switching Graphics Controller in Virtualbox does not help, nor does 'nomodeset' or 'noacpi'. I am able to reproduce the issue on real hardware and with different physical graphics cards. Similar symptoms can also be observed in Ubuntu Desktop (still using EFI) by attempting to switch to tty with CTRL + ALT + F[3-6], or by taking note of the missing plymouth screen during boot. Systems installed/booted in legacy BIOS mode (both Server and Desktop) do not appear to be affected. I have tried reinstalling on both virtual and hardware platforms, with same result before and after upgrading the kernel. HOW TO REPRODUCE - Ubuntu Server: - Boot existing Ubuntu Server EFI installation with 5.15.0-18 and observe console output - Set GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=10 in /etc/default/grub (to enable rollback) - Run update-grub - Run sudo apt full-upgrade and watch linux version 5.15.0-22 get installed - Reboot and observe your display (no console output will be shown after grub) HOW TO REPRODUCE - Ubuntu Desktop: - Download Ubuntu 22.04 Desktop daily ISO - Write ISO to USB - Boot from USB in EFI mode - Install system - Run sudo apt full-upgrade and upgrade linux* to kernel 5.15.0-22 - Reboot and observe missing plymouth screen during boot - Wait for graphical login screen to appear - Press CTRL + ALT + F[3-6] (screen will go black and/or freeze) - Press CTRL + ALT + F1 (screen will unfreeze and/or return to gdm greeter) WORKAROUNDS: If you still have 5.15.0-18 or earlier installed, select it in Grub. and/or install mainline kernel 5.16.11+ (for testing only - will not work if you have Secure Boot enabled). Alternatively, re-install/convert/boot your system to boot in legacy BIOS mode. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220307) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
[Kernel-packages] [Bug 1961406] Re: Known bug in IGC kernel module causes shutdown bug in z690 environments
Today a new linux image was available (update from 5.15.12 to 5.15.19). After installation the problems with AlderLake/z690 network module IGC are solved. ``` phoenix@dev:~$ cat /proc/version_signature Ubuntu 5.15.0-22.22-generic 5.15.19 ``` I can now happily reboot and shutdown my box :) Can someone please close this issue, because I does not seem to have the permission to do so. -- 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/1961406 Title: Known bug in IGC kernel module causes shutdown bug in z690 environments Status in linux package in Ubuntu: Confirmed Bug description: I own a Asus z690 Apex board, and shutdown hangs because of a bug in IGC driver. I cannot provide any logs because this happens after filesystem driver has been shut down and display/graphics have been turned of. The PC simply never turns off. I can disable the network interface in UEFI Bios, then the problem disappears. As far as I know a newer 5.15.x version already contains a fix. Since most users that own a AlderLake / z690 will be affected by this bug it should be fixed before release. I read about some MSI boards does not have that problem, but any other mainboards (asus, asrocks, gigabyte etc) seem to have this bug. I updated my bios and tried different shutdown commands without success Related links: - https://groups.google.com/g/linux.debian.bugs.dist/c/i6buM9KpulI?pli=1 - https://bbs.archlinux.org/viewtopic.php?id=272338 - https://www.reddit.com/r/Fedora/comments/r3hxt0/restartshut_down_problem_on_kernel_5154201/ ``` phoenix@dev:~$ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 phoenix@dev:~$ cat /proc/version_signature Ubuntu 5.15.0-18.18-generic 5.15.12 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 18 13:37:10 2022 InstallationDate: Installed on 2021-06-11 (252 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=1d617086-e30d-4dd3-a313-3b435ea89649 ro quiet splash mitigations=off systemd.unified_cgroup_hierarchy=false vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-01-14 (34 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 11.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS Z690 APEX 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 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd01/26/2022:br11.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ690APEX:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1961406/+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 1961406] Re: Known bug in IGC kernel module causes shutdown bug in z690 environments
** Summary changed: - Known bug in IGC causes shutdown bug in z690 environments + Known bug in IGC kernel module causes shutdown bug in z690 environments -- 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/1961406 Title: Known bug in IGC kernel module causes shutdown bug in z690 environments Status in linux package in Ubuntu: Confirmed Bug description: I own a Asus z690 Apex board, and shutdown hangs because of a bug in IGC driver. I cannot provide any logs because this happens after filesystem driver has been shut down and display/graphics have been turned of. The PC simply never turns off. I can disable the network interface in UEFI Bios, then the problem disappears. As far as I know a newer 5.15.x version already contains a fix. Since most users that own a AlderLake / z690 will be affected by this bug it should be fixed before release. I read about some MSI boards does not have that problem, but any other mainboards (asus, asrocks, gigabyte etc) seem to have this bug. I updated my bios and tried different shutdown commands without success Related links: - https://groups.google.com/g/linux.debian.bugs.dist/c/i6buM9KpulI?pli=1 - https://bbs.archlinux.org/viewtopic.php?id=272338 - https://www.reddit.com/r/Fedora/comments/r3hxt0/restartshut_down_problem_on_kernel_5154201/ ``` phoenix@dev:~$ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 phoenix@dev:~$ cat /proc/version_signature Ubuntu 5.15.0-18.18-generic 5.15.12 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 18 13:37:10 2022 InstallationDate: Installed on 2021-06-11 (252 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=1d617086-e30d-4dd3-a313-3b435ea89649 ro quiet splash mitigations=off systemd.unified_cgroup_hierarchy=false vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-01-14 (34 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 11.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS Z690 APEX 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 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd01/26/2022:br11.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ690APEX:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1961406/+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 1961406] Re: Known bug in IGC causes shutdown bug in z690 environments
When I unload the **igc** module while system is running it triggers a reboot, just like described here: - https://lore.kernel.org/all/924175a188159f4e03bd69908a91e606b574139b.ca...@gmx.de/ The 5.15.12 kernel seems to fix the issue for **igb** kernel module but not for **igc**. According to this forum thread (last message) kernel version 5.15.13 solves the problem for **igc**: - https://bbs.archlinux.org/viewtopic.php?pid=2014226#p2014226 -- 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/1961406 Title: Known bug in IGC causes shutdown bug in z690 environments Status in linux package in Ubuntu: Confirmed Bug description: I own a Asus z690 Apex board, and shutdown hangs because of a bug in IGC driver. I cannot provide any logs because this happens after filesystem driver has been shut down and display/graphics have been turned of. The PC simply never turns off. I can disable the network interface in UEFI Bios, then the problem disappears. As far as I know a newer 5.15.x version already contains a fix. Since most users that own a AlderLake / z690 will be affected by this bug it should be fixed before release. I read about some MSI boards does not have that problem, but any other mainboards (asus, asrocks, gigabyte etc) seem to have this bug. I updated my bios and tried different shutdown commands without success Related links: - https://groups.google.com/g/linux.debian.bugs.dist/c/i6buM9KpulI?pli=1 - https://bbs.archlinux.org/viewtopic.php?id=272338 - https://www.reddit.com/r/Fedora/comments/r3hxt0/restartshut_down_problem_on_kernel_5154201/ ``` phoenix@dev:~$ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 phoenix@dev:~$ cat /proc/version_signature Ubuntu 5.15.0-18.18-generic 5.15.12 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 18 13:37:10 2022 InstallationDate: Installed on 2021-06-11 (252 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=1d617086-e30d-4dd3-a313-3b435ea89649 ro quiet splash mitigations=off systemd.unified_cgroup_hierarchy=false vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-01-14 (34 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 11.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS Z690 APEX 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 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd01/26/2022:br11.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ690APEX:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1961406/+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 1961406] Re: Known bug in IGC causes shutdown bug in z690 environments
Found this related kernel patch for igb and igc: - https://bugzilla.kernel.org/show_bug.cgi?id=215129 The post states that for igb kernel module a fix is included in 5.15.12. I tested with kernel 5.15.12 (Ubuntu 5.15.0-18.18-generic 5.15.12) and the bug remains in my case using igc kernel module. ** Bug watch added: Linux Kernel Bug Tracker #215129 https://bugzilla.kernel.org/show_bug.cgi?id=215129 -- 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/1961406 Title: Known bug in IGC causes shutdown bug in z690 environments Status in linux package in Ubuntu: Confirmed Bug description: I own a Asus z690 Apex board, and shutdown hangs because of a bug in IGC driver. I cannot provide any logs because this happens after filesystem driver has been shut down and display/graphics have been turned of. The PC simply never turns off. I can disable the network interface in UEFI Bios, then the problem disappears. As far as I know a newer 5.15.x version already contains a fix. Since most users that own a AlderLake / z690 will be affected by this bug it should be fixed before release. I read about some MSI boards does not have that problem, but any other mainboards (asus, asrocks, gigabyte etc) seem to have this bug. I updated my bios and tried different shutdown commands without success Related links: - https://groups.google.com/g/linux.debian.bugs.dist/c/i6buM9KpulI?pli=1 - https://bbs.archlinux.org/viewtopic.php?id=272338 - https://www.reddit.com/r/Fedora/comments/r3hxt0/restartshut_down_problem_on_kernel_5154201/ ``` phoenix@dev:~$ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 phoenix@dev:~$ cat /proc/version_signature Ubuntu 5.15.0-18.18-generic 5.15.12 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 18 13:37:10 2022 InstallationDate: Installed on 2021-06-11 (252 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=1d617086-e30d-4dd3-a313-3b435ea89649 ro quiet splash mitigations=off systemd.unified_cgroup_hierarchy=false vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-01-14 (34 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 11.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS Z690 APEX 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 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd01/26/2022:br11.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ690APEX:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1961406/+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 1962162] [NEW] Suspend/Resume/Reboot fails with 5.15 Kernel
Public bug reported: Suspend/Resume and don't seem to work with the shipped 5.15 Kernel. When rebooting or shutting down the system gets stuck at "Reached Target: System Poweroff" or "Reboot". Installing the mainline kernel 5.16.11 fixes this issue and the system is able to properly shutdown/reboot and suspend. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 24 12:53:52 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) MachineType: Micro-Star International Co., Ltd. MS-7D29 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_m9rbzq@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_m9rbzq ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220217.git6342082c-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.24 dmi.board.asset.tag: Default string dmi.board.name: MEG Z690I UNIFY (MS-7D29) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.24:bd01/21/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D29:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ690IUNIFY(MS-7D29):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D29 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1962162 Title: Suspend/Resume/Reboot fails with 5.15 Kernel Status in linux package in Ubuntu: New Bug description: Suspend/Resume and don't seem to work with the shipped 5.15 Kernel. When rebooting or shutting down the system gets stuck at "Reached Target: System Poweroff" or "Reboot". Installing the mainline kernel 5.16.11 fixes this issue and the system is able to properly shutdown/reboot and suspend. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 24 12:53:52 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) MachineType: Micro-Star International Co., Ltd. MS-7D29 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_m9rbzq@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_m9rbzq ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220217.git6342082c-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.24 dmi.board.asset.tag: Default string dmi.board.name: MEG Z690I UNIFY (MS-7D29) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
Seems like it is fixed in kernel 5.14: https://gitlab.freedesktop.org/drm/amd/-/issues/1783 Any chance to get the fix backported to 20.04? ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1783 https://gitlab.freedesktop.org/drm/amd/-/issues/1783 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+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 1961406] [NEW] Known bug in IGC causes shutdown bug in z690 environments
Public bug reported: I own a Asus z690 Apex board, and shutdown hangs because of a bug in IGC driver. I cannot provide any logs because this happens after filesystem driver has been shut down and display/graphics have been turned of. The PC simply never turns off. I can disable the network interface in UEFI Bios, then the problem disappears. As far as I know a newer 5.15.x version already contains a fix. Since most users that own a AlderLake / z690 will be affected by this bug it should be fixed before release. I read about some MSI boards does not have that problem, but any other mainboards (asus, asrocks, gigabyte etc) seem to have this bug. I updated my bios and tried different shutdown commands without success Related links: - https://groups.google.com/g/linux.debian.bugs.dist/c/i6buM9KpulI?pli=1 - https://bbs.archlinux.org/viewtopic.php?id=272338 - https://www.reddit.com/r/Fedora/comments/r3hxt0/restartshut_down_problem_on_kernel_5154201/ ``` phoenix@dev:~$ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 phoenix@dev:~$ cat /proc/version_signature Ubuntu 5.15.0-18.18-generic 5.15.12 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 18 13:37:10 2022 InstallationDate: Installed on 2021-06-11 (252 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=1d617086-e30d-4dd3-a313-3b435ea89649 ro quiet splash mitigations=off systemd.unified_cgroup_hierarchy=false vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-01-14 (34 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 11.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS Z690 APEX 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 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd01/26/2022:br11.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ690APEX:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1961406/+attachment/5561812/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961406 Title: Known bug in IGC causes shutdown bug in z690 environments Status in linux package in Ubuntu: Confirmed Bug description: I own a Asus z690 Apex board, and shutdown hangs because of a bug in IGC driver. I cannot provide any logs because this happens after filesystem driver has been shut down and display/graphics have been turned of. The PC simply never turns off. I can disable the network interface in UEFI Bios, then the problem disappears. As far as I know a newer 5.15.x version already contains a fix. Since most users that own a AlderLake / z690 will be affected by this bug it should be fixed before release. I read about some MSI boards does not have that problem, but any other mainboards (asus, asrocks, gigabyte etc) seem to have this bug. I updated my bios and tried different shutdown commands without success Related links: - https://groups.google.com/g/linux.debian.bugs.dist/c/i6buM9KpulI?pli=1 - https://bbs.archlinux.org/viewtopic.php?id=272338 - https://www.reddit.com/r/Fedora/comments/r3hxt0/restartshut_down_problem_on_kernel_5154201/ ``` phoenix@dev:~$ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 phoenix@dev:~$ cat /proc/version_signature Ubuntu 5.15.0-18.18-generic 5.15.12 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic
[Kernel-packages] [Bug 1960460] Re: Fails to import ZFS rpool during boot
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: 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/1960460 Title: Fails to import ZFS rpool during boot Status in systemd package in Ubuntu: New Bug description: Fresh install using 20220202 Daily ISO with ZFS + Encryption selected from the installer The system ends up in busybox after entering the unlock key. Here is a part of the logs captured from the screen, the complete log can be found as an attachement: find: /dev/zvol/: No such file or directory /init: line 971: dirname: not found BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu2) multi-call binary. Usage: basename FILE [SUFFIX] Strip directory path and SUFFIX from FILE Please unlock disk keystore-:_ Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied mount: mounting rpool/ROOT/ubuntu_u169ph on /root// failed: Permission denied Error: 1 Failed to mount rpool/ROOT/ubuntu ui69ph on /root//. Manually mount the filesystem and exit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960460/+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 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
Hi Tim, I can confirm that 5.4.0-99.112 fixes the cifs issue. Testing in our environment does not show any freezes accessing cifs shares while using 5.4.0-99.112. Best Regards, Sebastian -- 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/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip> snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_cstate input_leds iwlwifi serio_raw snd intel_wmi_thunderbolt rtsx_pci_ms dell_wmi_descriptor wmi_bmof processor_thermal_device ucsi_acp> pinctrl_cannonlake video pinctrl_intel ---[ end trace 80828f22da45a19b ]--- RIP: 0010:__slab_free+0
[Kernel-packages] [Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
Problem can be reproduced with 5.13.0-28.31~20.04.1 as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+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 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
Just a quick heads up on my tests with different kernel versions. I have installed all available Updates for Ubuntu 20.04 (including samba-*= 2:4.13.17~dfsg-0ubuntu0.21.04.1; CVE-2022-0336). These are the results: GA: 5.4.0-98.111~lp1959665.1 -> no freezes in 3 hours of testing 5.4.0-97.110 -> still keeps freezing HWE: 5.13.0-27.29~20.04.1 -> no freezes in 1 hour of testing 5.13.0-28.31~20.04.1 -> no freezes in 1 hour of testing ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0336 -- 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/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip> snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm dell_wmi
[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
Hi, thanks for the quick reply. I can confirm, that while running on 5.4.0-98-generic #111~lp1959665.1 I was able to access all of our cifs shares without issues. A script, which creates, reads, modifies and deletes files on different cifs shares also works without any issue. Removing the latest cifs patches from kernel 5.4.0-97.110 seems to fix our issue. I will keep testing on 5.4.0-98-generic #111~lp1959665.1. Best regards, Sebastian -- 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/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip> snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm dell_wmi snd_seq_device rapl dell_smbios snd_time
[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
** Summary changed: - linux-image-9.4.0-97.110 freezes by accessing cifs shares + linux-image-5.4.0-97.110 freezes by accessing cifs shares ** Description changed: - Ubuntu 20.04 with kernel image 9.4.0-97.110 randomly freezes when we + Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: - ? proc_self_get_link+0x70/0xd0 - proc_self_get_link+0x70/0xd0 - link_path_walk.part.0+0x478/0x550 - ? trailing_symlink+0x1d1/0x280 - path_openat+0xb7/0x290 - do_filp_open+0x91/0x100 - ? unuse_pde+0x30/0x30 - do_sys_open+0x17e/0x290 - __x64_sys_openat+0x20/0x30 - __orig_openat+0x71/0xc0 [eset_rtp] - ? __switch_to_asm+0x40/0x70 - ? __switch_to_asm+0x34/0x70 - ? __switch_to_asm+0x40/0x70 - ? __x64_sys_futex+0x13f/0x170 - ? __switch_to_asm+0x34/0x70 - ? __switch_to_asm+0x40/0x70 - ? __switch_to_asm+0x34/0x70 - ? __switch_to_asm+0x40/0x70 - __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] - do_syscall_64+0x57/0x190 - entry_SYSCALL_64_after_hwframe+0x44/0xa9 + ? proc_self_get_link+0x70/0xd0 + proc_self_get_link+0x70/0xd0 + link_path_walk.part.0+0x478/0x550 + ? trailing_symlink+0x1d1/0x280 + path_openat+0xb7/0x290 + do_filp_open+0x91/0x100 + ? unuse_pde+0x30/0x30 + do_sys_open+0x17e/0x290 + __x64_sys_openat+0x20/0x30 + __orig_openat+0x71/0xc0 [eset_rtp] + ? __switch_to_asm+0x40/0x70 + ? __switch_to_asm+0x34/0x70 + ? __switch_to_asm+0x40/0x70 + ? __x64_sys_futex+0x13f/0x170 + ? __switch_to_asm+0x34/0x70 + ? __switch_to_asm+0x40/0x70 + ? __switch_to_asm+0x34/0x70 + ? __switch_to_asm+0x40/0x70 + __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] + do_syscall_64+0x57/0x190 + entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 - ? unuse_pde+0x30/0x30 - do_sys_open+0x17e/0x290 - __x64_sys_openat+0x20/0x30 - __orig_openat+0x71/0xc0 [eset_rtp] - ? __switch_to_asm+0x40/0x70 - ? __switch_to_asm+0x34/0x70 - ? __switch_to_asm+0x40/0x70 - ? __x64_sys_futex+0x13f/0x170 - ? __switch_to_asm+0x34/0x70 - ? __switch_to_asm+0x40/0x70 - ? __switch_to_asm+0x34/0x70 - ? __switch_to_asm+0x40/0x70 - __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] - do_syscall_64+0x57/0x190 - entry_SYSCALL_64_after_hwframe+0x44/0xa9 + ? unuse_pde+0x30/0x30 + do_sys_open+0x17e/0x290 + __x64_sys_openat+0x20/0x30 + __orig_openat+0x71/0xc0 [eset_rtp] + ? __switch_to_asm+0x40/0x70 + ? __switch_to_asm+0x34/0x70 + ? __switch_to_asm+0x40/0x70 + ? __x64_sys_futex+0x13f/0x170 + ? __switch_to_asm+0x34/0x70 + ? __switch_to_asm+0x40/0x70 + ? __switch_to_asm+0x34/0x70 + ? __switch_to_asm+0x40/0x70 + __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] + do_syscall_64+0x57/0x190 + entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08:
[Kernel-packages] [Bug 1959665] [NEW] linux-image-9.4.0-97.110 freezes by accessing cifs shares
Public bug reported: Ubuntu 20.04 with kernel image 9.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip> snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_cstate input_leds iwlwifi serio_raw snd intel_wmi_thunderbolt rtsx_pci_ms dell_wmi_descriptor wmi_bmof processor_thermal_device ucsi_acp> pinctrl_cannonlake video pinctrl_intel ---[ end trace 80828f22da45a19b ]--- RIP: 0010:__slab_free+0x199/0x360 Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 79 4d 3b 6c 24 20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 3b 5c 24 28 75 e8 48 8b 44 24 28 49 89 4c 24 28 49 89 44 RSP: 0018:a6ca85a8f8c0 EFLAGS: 00010246 RAX: 9921db223620 RBX: 80800046 RCX: 9921db223620 RDX: 9921db223620 RSI: f5c79c6c88c0 RDI: 992338c07800 RBP: a6ca85a8f968 R08: 0001 R09: c1514620 R10: 9921db223620 R11: 0001 R12: f5c79c6c88c0 R13: 9921db223620 R14: 992338c07800 R15: 9922e0c4a800 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0:
[Kernel-packages] [Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
** Summary changed: - After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking + After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+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 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking
According to my logs in the past few days, these versions have worked fine: 5.10.0-1045.47-oem 5.11.0-37.41~20.04.2-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+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 1958494] [NEW] After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking
Public bug reported: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (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-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+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 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking
** Attachment added: "IMG_20220120_073821207.jpg" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+attachment/771/+files/IMG_20220120_073821207.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+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 1949793] Re: Thunderbolt 3 NIC driver is loaded too early and won't establish connection
*** This bug is a duplicate of bug 1949790 *** https://bugs.launchpad.net/bugs/1949790 ** This bug has been marked a duplicate of bug 1949790 Thunderbolt 3 NIC driver is loaded too early and won't establish connection -- 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/1949793 Title: Thunderbolt 3 NIC driver is loaded too early and won't establish connection Status in linux package in Ubuntu: Confirmed Bug description: I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10 GBase-T NIC (atlantic). The issue is that during boot it only detects the interface as 5 GBe, as seen in dmesg: enp11s0: atlantic: link change old 0 new 5000 This prevents the interface from establishing a connection. With Ubuntu 21.04 and previous versions this issue didn't exist. I found a couple workarounds for this problem: 1. Enable Thunderbolt Security (User Authorization or Secure Connect) in the BIOS. This prevents the computer from suspending however, so this workaround isn't feasible. 2. Run sudo rmmod atlantic && modprobe atlantic and the NIC will connect at 10 GBe without issues as seen below: atlantic :0b:00.0 enp11s0: atlantic: link change old 0 new 1 From the obervations above, I draw the conclusion that the module gets loaded too early with Thunderbolt Security disabled and should happen at a later point in time. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: spyfly 3576 F pulseaudio /dev/snd/pcmC2D0p: spyfly 3576 F...m pulseaudio /dev/snd/controlC1: spyfly 3576 F pulseaudio /dev/snd/controlC0: spyfly 3576 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 15:47:34 2021 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-10-19 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_qbynho@/vmlinuz-5.13.0-20-generic root=ZFS=rpool/ROOT/ubuntu_qbynho ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.20 dmi.board.name: X570 Phantom Gaming-ITX/TB3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949793/+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 1949790] [NEW] Thunderbolt 3 NIC driver is loaded too early and won't establish connection
Public bug reported: I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10 GBase-T NIC (atlantic). The issue is that during boot it only detects the interface as 5 GBe, as seen in dmesg: enp11s0: atlantic: link change old 0 new 5000 This prevents the interface from establishing a connection. With Ubuntu 21.04 and previous versions this issue didn't exist. I found a couple workarounds for this problem: 1. Enable Thunderbolt Security (User Authorization or Secure Connect) in the BIOS. This prevents the computer from suspending however, so this workaround isn't feasible. 2. Run sudo rmmod atlantic && modprobe atlantic and the NIC will connect at 10 GBe without issues as seen below: atlantic :0b:00.0 enp11s0: atlantic: link change old 0 new 1 >From the obervations above, I draw the conclusion that the module gets loaded too early with Thunderbolt Security disabled and should happen at a later point in time. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: spyfly 3576 F pulseaudio /dev/snd/pcmC2D0p: spyfly 3576 F...m pulseaudio /dev/snd/controlC1: spyfly 3576 F pulseaudio /dev/snd/controlC0: spyfly 3576 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 15:47:34 2021 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-10-19 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_qbynho@/vmlinuz-5.13.0-20-generic root=ZFS=rpool/ROOT/ubuntu_qbynho ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.20 dmi.board.name: X570 Phantom Gaming-ITX/TB3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1949790 Title: Thunderbolt 3 NIC driver is loaded too early and won't establish connection Status in linux package in Ubuntu: New Bug description: I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10 GBase-T NIC (atlantic). The issue is that during boot it only detects the interface as 5 GBe, as seen in dmesg: enp11s0: atlantic: link change old 0 new 5000 This prevents the interface from establishing a connection. With Ubuntu 21.04 and previous versions this issue didn't exist. I found a couple workarounds for this problem: 1. Enable Thunderbolt Security (User Authorization or Secure Connect) in the BIOS. This prevents the computer from suspending however, so this workaround isn't feasible. 2. Run sudo rmmod atlantic && modprobe atlantic and the NIC will connect at 10 GBe without issues as seen below: atlantic :0b:00.0 enp11s0: atlantic: link change old 0 new 1 From the obervations above, I draw the conclusion that the module gets loaded too early with Thunderbolt Security disabled and should happen at a later point in time. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: spyfly 3576 F
[Kernel-packages] [Bug 1949793] [NEW] Thunderbolt 3 NIC driver is loaded too early and won't establish connection
Public bug reported: I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10 GBase-T NIC (atlantic). The issue is that during boot it only detects the interface as 5 GBe, as seen in dmesg: enp11s0: atlantic: link change old 0 new 5000 This prevents the interface from establishing a connection. With Ubuntu 21.04 and previous versions this issue didn't exist. I found a couple workarounds for this problem: 1. Enable Thunderbolt Security (User Authorization or Secure Connect) in the BIOS. This prevents the computer from suspending however, so this workaround isn't feasible. 2. Run sudo rmmod atlantic && modprobe atlantic and the NIC will connect at 10 GBe without issues as seen below: atlantic :0b:00.0 enp11s0: atlantic: link change old 0 new 1 >From the obervations above, I draw the conclusion that the module gets loaded too early with Thunderbolt Security disabled and should happen at a later point in time. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: spyfly 3576 F pulseaudio /dev/snd/pcmC2D0p: spyfly 3576 F...m pulseaudio /dev/snd/controlC1: spyfly 3576 F pulseaudio /dev/snd/controlC0: spyfly 3576 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 15:47:34 2021 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-10-19 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_qbynho@/vmlinuz-5.13.0-20-generic root=ZFS=rpool/ROOT/ubuntu_qbynho ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.20 dmi.board.name: X570 Phantom Gaming-ITX/TB3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1949793 Title: Thunderbolt 3 NIC driver is loaded too early and won't establish connection Status in linux package in Ubuntu: New Bug description: I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10 GBase-T NIC (atlantic). The issue is that during boot it only detects the interface as 5 GBe, as seen in dmesg: enp11s0: atlantic: link change old 0 new 5000 This prevents the interface from establishing a connection. With Ubuntu 21.04 and previous versions this issue didn't exist. I found a couple workarounds for this problem: 1. Enable Thunderbolt Security (User Authorization or Secure Connect) in the BIOS. This prevents the computer from suspending however, so this workaround isn't feasible. 2. Run sudo rmmod atlantic && modprobe atlantic and the NIC will connect at 10 GBe without issues as seen below: atlantic :0b:00.0 enp11s0: atlantic: link change old 0 new 1 From the obervations above, I draw the conclusion that the module gets loaded too early with Thunderbolt Security disabled and should happen at a later point in time. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: spyfly 3576 F
[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
The latest Ubuntu 21.10 install still comes with zfs-kmod-2.0.3, which prevents the system from booting in the first place. Installing zfs-dkms via the recovery mode, which updates the zfs-kmod to version 2.0.6, fixed the issue for me. I hope that the release image of Ubuntu 21.10 will ship with zfs- kmod-2.0.6 in the kernel by default. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930754] Re: e1000e extremly slow
5.10.0-1049.51 works for me too, many thanks indeed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e on TGP PCH encounters a network speed issue that rx speed is below 1MB/s [Fix] Intel provides 2 patches to fix this https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=263466 [Test] Verified by our Dell and Lenovo platforms and the bug reporter. [Where problems could occur] The fix only applies to e1000e with TGP PCH, and add a flag "E1000_FFLT_DBG_DONT_GATE_WAKE_DMA_CLK". The impact should be minimized and should not lead to other regressions. = We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
I also experienced this bug on Ubuntu 21.10 Beta during boot on a fresh ZFS Install with Encryption. The only way to boot into GNOME without crashing was booting through recovery mode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: In Progress Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931301] Re: NIC unavailable after suspend to RAM
Have tested the linux-image-5.11.0-33-generic:amd64 5.11.0-33.35 from proposed and I can verify it fixed the issue for me. Switched back to the non-proposed 5.11.0-31 kernel and am looking forward to the new update. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: [SRU Justification] [Impact] The network card will be unavailable after system resume if the interface is not UP before suspend. [Fix] It's because we added the WOL support for this driver. The driver with WoL feature does detach the network interface even the interface is DOWN. However, it doesn't attach the network interface back on resume if it was DOWN. That's why it's unavailable after resume. Fix this by correctly netif_device_attach according to the interface status. [Test Case] 1. Plug the ethernet cable to the Atheros E220x ethernet adapter 2. Suspend the system and check if the ethernet interface available after resume 3. Unplug the ethernet cable 4. Suspend the system and check if the ethernet interface available after resume [Regression Potential] Low. The driver code would be identical to working Groovy version after fix. == Original Bug Description == Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+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 1930754] Re: e1000e extremly slow
Hi Yuan-Chen I tried: "echo on | sudo tee /sys/bus/pci/devices/\:00\:16.0/power/control" I also tried unloading mei* kernel modules. However it didn't solve the isssue. Here is the requested info: # lspci -vvnns 00:1f.6 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (13) I219-LM [8086:15fb] (rev 20) Subsystem: Dell Ethernet Connection (13) I219-LM [1028:0a20] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://sourceforge.net/projects/e1000/ root@latitude-5420:~# modinfo e1000e | grep ver filename: /lib/modules/5.10.0-1038-oem/updates/drivers/net/ethernet/intel/e1000e/e1000e.ko version:3.8.7-NAPI description:Intel(R) PRO/1000 Network Driver srcversion: 035BD57B8D93A45D1668FCC vermagic: 5.10.0-1038-oem SMP mod_unload modversions But it didn't help. I am currently using the wireless adapter until a find a solution. Sadly, the only solution provided by technical support was to re-install Ubuntu, which I will do when I find free time. Many thanks, Sebastian -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: Confirmed Bug description: We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930754/+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 1930754] Re: e1000e extremly slow
Thanks @Yuan-Chen. Yes, I did try but it didn't work for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: Confirmed Bug description: We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930754/+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 1930754] Re: e1000e extremly slow
Thanks All for your great help. I am also affected by this issue with my Dell 5420 equipped with a I219-LM card (just arrived home yesterday). I came across the AskUbuntu thread from Dell Community forums: https://www.dell.com/community/Latitude/Dell-latitude-5420-5520-intel-ethernet-on-ubuntu-20-04/m-p/7889980 After the "sudo ethtool -C rx-usecs 6000" command I keep seeing rx_errors and rx_crc_errors with: sudo ethtool -S | grep -i err Do you know why? Many thanks, Sebastian -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: Confirmed Bug description: We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930754/+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 1931301] Re: NIC unavailable after suspend to RAM
Sure thing Chris, here's the dmesg log. Before I forget: thank you for helping me out here, I really appreciate it. ** Attachment added: "5.11.0-24-generic.dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+attachment/5510164/+files/5.11.0-24-generic.dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+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 1931301] Re: NIC unavailable after suspend to RAM
this went horribly wrong, since suspend itself did not work at all ;-) ( freezing of tasks failed after 20.010 seconds ) ** Attachment added: "5.13.0-051300-generic.dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+attachment/5509674/+files/5.13.0-051300-generic.dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+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 1931301] Re: NIC unavailable after suspend to RAM
Did you change anything else in this kernel? Because it seemed to work correctly. ** Attachment added: "5.11.0-24-generic.dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+attachment/5509673/+files/5.11.0-24-generic.dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+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 1934537] [NEW] package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux-image-5.11.0-22-generic_5.11.0
Public bug reported: package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux- image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2058 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Jul 1 21:03:22 2021 ErrorMessage: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20KH006DGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent file=/cdrom/preseed/hostname.seed quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu45 SourcePackage: linux Title: package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET76W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006DGE 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.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN23ET76W(1.51):bd04/21/2021:br1.51:efr1.22:svnLENOVO:pn20KH006DGE:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH006DGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH006DGE 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-package hirsute -- 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/1934537 Title: package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53 -linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden Status in linux package in Ubuntu: New Bug description: package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53 -linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2058 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Jul 1 21:03:22 2021 ErrorMessage: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20KH006DGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent file=/cdrom/preseed/hostname.seed quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu45 SourcePackage: linux Title: package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden UpgradeStatus: No upgrade log
