[Kernel-packages] [Bug 2009243] Re: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card
As a workaround you can try the ubuntu upstream kernels. I installed 6.2.11 from here: https://kernel.ubuntu.com/~kernel- ppa/mainline/v6.2.11/ And sound was working out of the box again (kinda, I still had to open alasmixer and set to Headphones instead of Speakers). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009243 Title: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: 2023-03-03 Attempted install of kernel 5.19.0-35 using the Linux Mint package installer LM 21.1 Vera, release 21.1). Clobbered my Sound Blaster AE-7. Could not even locate the device using Sound manager utility on Linux Mint Panel (the enumerated device showed up as the embedded sound chip on the mobo which I had previously disabled in the UEFI setup). Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift restore feature which worked fine before the update to 5.19.0-35. Tried again to install 5.19.0-35 the same way, just to be sure. The SB AE-7 got clobbered again. So restored back to 5.19.0-32 generic one more time, using Timeshift. SB AE-7 works fine now with this lower version kernel. Current hardware config: Asus Prime Z790-P wifi mobo. Intel Core i3-13100 processor (with Intel UHD 730 graphics). Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz. 3 x Nvme SSD. Boot drive is Western Digital Black SN770 500gb. Asus Nvidia RTX-3050 PCIe graphics card. Creative Labs Sound Blaster AE-7 audio card (PCIe). On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio) is disabled in UEFI. UEFI is AMI/BIOS, revision 0812. Linux Mint 21.1 is running on barebones hardware, no VM involved. No other O/S's are installed on the machine. - Running sudo lspci -vnvn > lspci-vnvn.log gave the following error message... pcilib: sysfs_read_vpd: read failed: No such device --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikey 4106 F wireplumber /dev/snd/controlC0: mikey 4106 F wireplumber /dev/snd/seq:mikey 4105 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-31 (32 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 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.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: vera Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2023 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0812 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790-P WIFI 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.:bvr0812:bd02/24/2023:br8.12:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI: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/2009243/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux- riscv-5.15/5.15.0-1031.35~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-focal ** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Fix Released Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 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: skip DistroRelease: Ubuntu 20.04 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 Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 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.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
[Kernel-packages] [Bug 2016371] [NEW] kernel NULL pointer dereference in apparmor_parser
Public bug reported: Since about a month or so, I get many oopses from apparmor, such as this one: [ 14.620816] BUG: kernel NULL pointer dereference, address: 0130 [ 14.620822] #PF: supervisor read access in kernel mode [ 14.620825] #PF: error_code(0x) - not-present page [ 14.620829] PGD 0 P4D 0 [ 14.620834] Oops: [#1] PREEMPT SMP PTI [ 14.620838] CPU: 0 PID: 1105 Comm: apparmor_parser Not tainted 5.19.0-38-generic #39~22.04.1-Ubuntu [ 14.620842] Hardware name: LENOVO 20FES3TE00/20FES3TE00, BIOS N1GETA2W (1.81 ) 06/12/2020 [ 14.620845] RIP: 0010:aa_unpack+0x127/0x540 [ 14.620853] Code: 00 48 85 c0 0f 84 29 04 00 00 48 8d 75 a0 48 8d 7d b0 4c 8b 7d c0 e8 e8 ea ff ff 48 89 c3 48 3d 00 f0 ff ff 0f 87 00 02 00 00 <4c> 8b b0 30 01 00 00 4d 85 f6 0f 84 38 01 00 00 49 8b 86 c8 00 00 [ 14.620857] RSP: 0018:b07141cc3ce0 EFLAGS: 00010207 [ 14.620861] RAX: RBX: RCX: [ 14.620864] RDX: RSI: RDI: [ 14.620867] RBP: b07141cc3d48 R08: R09: [ 14.620869] R10: R11: R12: b07141cc3da8 [ 14.620872] R13: b07141cc3da0 R14: 9755c5518000 R15: 9755c5500010 [ 14.620875] FS: 7f53ef091740() GS:9756f960() knlGS: [ 14.620879] CS: 0010 DS: ES: CR0: 80050033 [ 14.620882] CR2: 0130 CR3: 000106b64006 CR4: 003706f0 [ 14.620886] DR0: DR1: DR2: [ 14.620888] DR3: DR6: fffe0ff0 DR7: 0400 [ 14.620891] Call Trace: [ 14.620893] [ 14.620899] aa_replace_profiles+0x97/0x1010 [ 14.620906] ? _copy_from_user+0x55/0x90 [ 14.620913] policy_update+0xdb/0x180 [ 14.620918] profile_replace+0xbb/0x150 [ 14.620923] vfs_write+0xb5/0x2a0 [ 14.620929] ksys_write+0x67/0xf0 [ 14.620933] __x64_sys_write+0x19/0x30 [ 14.620937] do_syscall_64+0x59/0x90 [ 14.620941] ? irqentry_exit_to_user_mode+0x9/0x20 [ 14.620946] ? irqentry_exit+0x43/0x50 [ 14.620949] ? exc_page_fault+0x92/0x1b0 [ 14.620954] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 14.620960] RIP: 0033:0x7f53eef14a37 [ 14.620964] Code: 10 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 14.620968] RSP: 002b:7fffa3676028 EFLAGS: 0246 ORIG_RAX: 0001 [ 14.620972] RAX: ffda RBX: 5628aad3df60 RCX: 7f53eef14a37 [ 14.620975] RDX: 00018000 RSI: 5628aad6e810 RDI: 0006 [ 14.620978] RBP: 00018000 R08: R09: 5628aad6e810 [ 14.620980] R10: R11: 0246 R12: 5628aad6e810 [ 14.620983] R13: 00018000 R14: 5628a9b26c5b R15: 0006 [ 14.620989] [ 14.620991] Modules linked in: snd_soc_avs snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_hda_codec_hdmi snd_soc_acpi snd_ctl_led snd_soc_core snd_hda_codec_conexant snd_compress snd_hda_codec_generic ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl_msr snd_intel_dspcfg intel_rapl_common snd_intel_sdw_acpi intel_tcc_cooling x86_pkg_temp_thermal snd_hda_codec intel_powerclamp snd_hda_core btusb thinkpad_acpi btrtl binfmt_misc kvm_intel snd_hwdep nvram btbcm snd_pcm ledtrig_audio uvcvideo btintel kvm iwlmvm snd_seq_midi videobuf2_vmalloc btmtk mei_pxp mei_hdcp snd_seq_midi_event videobuf2_memops rapl mac80211 snd_rawmidi videobuf2_v4l2 input_leds intel_cstate bluetooth snd_seq videobuf2_common libarc4 joydev serio_raw hid_sensor_accel_3d hid_sensor_custom_intel_hinge hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_als nls_iso8859_1 wmi_bmof think_lmi firmware_attributes_class snd_seq_device videodev ecdh_generic [ 14.621071] hid_sensor_trigger iwlwifi snd_timer industrialio_triggered_buffer ecc mc kfifo_buf snd cfg80211 mei_me hid_sensor_iio_common intel_pch_thermal intel_xhci_usb_role_switch mei industrialio soundcore platform_profile mac_hid sch_fq_codel coretemp msr parport_pc ppdev ramoops pstore_blk lp reed_solomon efi_pstore parport pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_crypt wacom usbhid hid_sensor_custom hid_sensor_hub hid_generic intel_ishtp_hid hid i915 drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core crct10dif_pclmul drm_kms_helper crc32_pclmul syscopyarea ghash_clmulni_intel sysfillrect sysimgblt aesni_intel fb_sys_fops nvme rtsx_pci_sdmmc i2c_i801 crypto_simd intel_ish_ipc xhci_pci cryptd drm psmouse e1000e nvme_core i2c_smbus rtsx_pci intel_ishtp xhci_pci_renesas wmi video [ 14.621163] CR2: 0130 [ 14.621166] ---[ end trace ]--- [ 14.
[Kernel-packages] [Bug 1950792] Re: No boot possible - Cannot open root device
Still a problem on _random_ supermicro hardware: i have 15 identical nodes, set kernel parameters for `console=ttyS0 console=tty0` and now _one_ node will not commission or therefore provision with this error. Maas (snap) is at 3.2.7-12037-g.c688dd446 The maas UI doesn't update the parameters passed when saved, user has to refresh the page or it keeps showing up as the last set of parameters at page-load. After setting the parameters back to blank, this one node still cannot boot from MAAS - whatever broke, broke persistently. -- 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/1950792 Title: No boot possible - Cannot open root device Status in MAAS: Triaged Status in linux package in Ubuntu: Incomplete Bug description: MaaS cannot boot on my X11DPi-NT and will therefore fail to commission. It will instantly fail after grub. It will fail to boot saying that is not able to open root device. I even tried supplying the squashfs via python on a different port as the url is somehow cut off a bit, but to no avail. The python webserver doesn't even see any connection try. ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs python webserver: python3 -m http.server 8080) Steps to reproduce: 1. Setup maas ;) 2. Try to commision server 3. See the kernel and initrd download fly by 4. Boom kernel panic Hardware: Supermicro X11DPi-NT with UEFI http Networkboot enabled NIC: Intel X722 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1950792/+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 2016374] [NEW] package nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befo
Public bug reported: Installation stalled and didn't complete. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 15 09:09:25 2023 DpkgTerminalLog: Removing linux-modules-nvidia-470-generic-hwe-20.04 (5.15.0-69.76~20.04.1+1) ... dpkg: error processing package nvidia-kernel-common-470 (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal dpkg: too many errors, stopping DuplicateSignature: package:nvidia-kernel-common-470:470.182.03-0ubuntu0.20.04.1 Removing linux-modules-nvidia-470-generic-hwe-20.04 (5.15.0-69.76~20.04.1+1) ... dpkg: error processing package nvidia-kernel-common-470 (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2021-12-13 (487 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/2016374 Title: package nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Installation stalled and didn't complete. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 15 09:09:25 2023 DpkgTerminalLog: Removing linux-modules-nvidia-470-generic-hwe-20.04 (5.15.0-69.76~20.04.1+1) ... dpkg: error processing package nvidia-kernel-common-470 (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal dpkg: too many errors, stopping DuplicateSignature: package:nvidia-kernel-common-470:470.182.03-0ubuntu0.20.04.1 Removing linux-modules-nvidia-470-generic-hwe-20.04 (5.15.0-69.76~20.04.1+1) ... dpkg: error processing package nvidia-kernel-common-470 (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2021-12-13 (487 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2016374/+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 2016374] Re: package nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before
** Tags removed: need-duplicate-check -- 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/2016374 Title: package nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Installation stalled and didn't complete. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 15 09:09:25 2023 DpkgTerminalLog: Removing linux-modules-nvidia-470-generic-hwe-20.04 (5.15.0-69.76~20.04.1+1) ... dpkg: error processing package nvidia-kernel-common-470 (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal dpkg: too many errors, stopping DuplicateSignature: package:nvidia-kernel-common-470:470.182.03-0ubuntu0.20.04.1 Removing linux-modules-nvidia-470-generic-hwe-20.04 (5.15.0-69.76~20.04.1+1) ... dpkg: error processing package nvidia-kernel-common-470 (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2021-12-13 (487 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2016374/+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 2012830] Re: Audio speed up on HDMI, with 4K resolution and refresh rate 60Hz
@Koba :
Important information :
lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
Completely new installation of Ubuntu 22.04.02 (HDD deleted).
After installation and update all, installed 5.19.9000-37-generic, to have
audio via HDMI. also installed synaptic and SSH, no further installation.
My Display settings :
xrandr
Screen 0: minimum 16 x 16, current 3840 x 2160, maximum 32767 x 32767
XWAYLAND0 connected primary 3840x2160+0+0 (normal left inverted right x axis y
axis) 1210mm x 680mm
3840x2160 59.98*+
2048x1536 59.95
And NO audio speed up 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/2012830
Title:
Audio speed up on HDMI, with 4K resolution and refresh rate 60Hz
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 22.10
Release: 22.10
Wayland
5.19.9000-37-generic
(please refer to bug-report
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136. My
installed SW is the result of the fixed Problem by Koba, No HDMI audio
if e.g. RX560 will be used, since 5.19.0-35)
The audio speed up does mean, that the audio will be played with
"speed=2x" (or something like that)
5.19.9000-37-generic, 3840x2180, refresh rate 60Hz, audio speed up issue
5.19.9000-37-generic, 1920x1080, refresh rate 60Hz, no audio speed up issue
5.19.9000-37-generic, 3840x2180, refresh rate 30Hz, no audio speed up issue
But I did test it on different releases :
5.19.0-21-generic, 3840x2180, refresh rate 60Hz, audio speed up issue
5.19.0-21-generic, 1920x1080, refresh rate 60Hz, no audio speed up issue
5.19.0-21-generic, 3840x2180, refresh rate 30Hz, no audio speed up issue
5.19.0-32-generic, 3840x2180, refresh rate 60Hz, audio speed up issue
5.19.0-32-generic, 1920x1080, refresh rate 60Hz, no audio speed up issue
5.19.0-32-generic, 3840x2180, refresh rate 30Hz, no audio speed up issue
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin
HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1002:aae0]
Subsystem: ASUSTeK Computer Inc. Baffin HDMI/DP Audio [Radeon RX 550 640SP /
RX 560/560X] [1043:aae0]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
For more detailed information about my system (please refer to bug-
report : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009815
("Ubuntu-bug linux" didn't work with the following message : "The
problem can not be reported : This report is about a package that is
not installed)
What I expect :
Normal understandable audio if Resolution=3840x2180 and refresh rate=60Hz,
What happened instead :
Audio speed up, it sounds like chirps.
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard1516 F wireplumber
/dev/snd/controlC1: richard1516 F wireplumber
/dev/snd/seq:richard1513 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2023-03-04 (22 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
IwConfig:
lono wireless extensions.
enp3s0no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.9000-37-generic
root=UUID=df59b1c2-c5b9-483d-b033-7c6b2264dc75 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.9000-37.38~22.04.1-generic 5.19.17
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.19.9000-37-generic N/A
linux-backports-modules-5.19.9000-37-generic N/A
linux-firmware20220923.gitf09bebf3-0ubuntu1.4
RfKill:
Tags: wayland-session kinetic
Uname: Linux 5.19.9000-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/18/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4802
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev x.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4802:bd09/18/2013:br
[Kernel-packages] [Bug 2016388] [NEW] Kernel Panic on powerdown on NUC8I3BEH1
Public bug reported: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "Photo of panic trace" https://bugs.launchpad.net/bugs/2016388/+attachment/5664254/+files/20230414_161829.jpg -- 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/2016388 Title: Kernel Panic on powerdown on NUC8I3BEH1 Status in linux package in Ubuntu: New Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1
This issue seems to persist falling back to kernel 5.4.0-144 -- 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/2016388 Title: Kernel Panic on powerdown on NUC8I3BEH1 Status in linux package in Ubuntu: New Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1
Photo of console showing panic trace using 5.4.0-144 ** Attachment added: "Photo of panic trace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664275/+files/5.4.0-144_20230415_091831.jpg -- 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/2016388 Title: Kernel Panic on powerdown on NUC8I3BEH1 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016388 Title: Kernel Panic on powerdown on NUC8I3BEH1 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 1950792] Re: No boot possible - Cannot open root device
Figured out what made that one node different from the rest: its UEFI network boot stack had both PXE and HTTP enabled, while the others were PXE only. After i added the kernel boot parameters, MAAS started to truncate the HTTP URI by a few characters (and now keeps doing that even if the kernel commandline options are cleared) which doesnt imapct the PXE clients but does break the HTTP ones (this node worked fine before the params were added). For anyone stuck in this situation, the workaround seems to be to disable HTTP-based image acquisition in the system's BIOS configuration menu - PXE only on the IP stack desired will avoid the oddly truncated HTTP URI which occurs after setting kernel boot parameters. -- 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/1950792 Title: No boot possible - Cannot open root device Status in MAAS: Triaged Status in linux package in Ubuntu: Incomplete Bug description: MaaS cannot boot on my X11DPi-NT and will therefore fail to commission. It will instantly fail after grub. It will fail to boot saying that is not able to open root device. I even tried supplying the squashfs via python on a different port as the url is somehow cut off a bit, but to no avail. The python webserver doesn't even see any connection try. ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs python webserver: python3 -m http.server 8080) Steps to reproduce: 1. Setup maas ;) 2. Try to commision server 3. See the kernel and initrd download fly by 4. Boom kernel panic Hardware: Supermicro X11DPi-NT with UEFI http Networkboot enabled NIC: Intel X722 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1950792/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1
hmm. The issue persists going back to 5.4.0-135 also... Trying 5.4.0-131 next, but if that it's still happening the issue may be else ware? I don't reboot or shutdown this machine very often, the last time I can confirm I shut down without a panic was around March 14th. ** Attachment added: "5.4.0-135_20230415_093229.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664276/+files/5.4.0-135_20230415_093229.jpg -- 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/2016388 Title: Kernel Panic on powerdown on NUC8I3BEH1 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1
Same thing with 131. So I have no idea what's going on. I upgraded the RAM in this machine around March 14th, which is why I know that was the last time I rebooted and I believe I would have noticed a panic. I also confirm it seems all reboots result in the same panic (e.g. "sudo reboot" and also using the XFCE gui to shutdown or reboot). Looking at my dpkg output, it looks like I've installed a lot of kernels and presumably they all would have required a reboot, I only noticed this kernel panic on shutdown yesterday. rc linux-image-5.4.0-121-generic 5.4.0-121.137 amd64Signed ke> rc linux-image-5.4.0-122-generic 5.4.0-122.138 amd64Signed ke> rc linux-image-5.4.0-124-generic 5.4.0-124.140 amd64Signed ke> rc linux-image-5.4.0-126-generic 5.4.0-126.142 amd64Signed ke> ii linux-image-5.4.0-131-generic 5.4.0-131.147 amd64Signed ke> rc linux-image-5.4.0-135-generic 5.4.0-135.152 amd64Signed ke> ii linux-image-5.4.0-144-generic 5.4.0-144.161 amd64Signed ke> ii linux-image-5.4.0-146-generic 5.4.0-146.163 amd64Signed ke> I'll try 121 as a final attempt. ** Attachment added: "Photo of panic trace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664278/+files/5.4.0-131_20230415_094504.jpg -- 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/2016388 Title: Kernel Panic on powerdown on NUC8I3BEH1 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1
Confirmed on 121. Another thing I realized is that I also updated the BIOS when I upgraded the RAM. Updated to BE0092. I have no idea what the previous BIOS version I was using (whatever shipped with the machine initially), but this one sill seems the most up to date version. I'll try downgrading BIOS to BE0090. ** Attachment added: "5.4.0-121_20230415_100513.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664316/+files/5.4.0-121_20230415_100513.jpg -- 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/2016388 Title: Kernel Panic on powerdown on NUC8I3BEH1 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1
Same thing with BIOS 0090 and kernel 5.4.0-135 ** Attachment added: "Photo of panic trace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664317/+files/BIOS0090_5.4.0-135_20230415_103355.jpg -- 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/2016388 Title: Kernel Panic on powerdown on NUC8I3BEH1 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 1972140] Re: UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20
This keeps happening in kernel 5.19.0-38-generic. I installed the 4 debs from the link above https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972140/comments/13 then with grub I booted the linux-image- unsigned-5.18.0-4-generic_5.18.0-4.4 kernel. Result: It refuses to load the athk5 module. This is the dmesg output I get in modprobe aswell: [4.314514] ath: disagrees about version of symbol ieee80211_get_channel_khz [4.314516] ath: Unknown symbol ieee80211_get_channel_khz (err -22) [4.314519] ath: disagrees about version of symbol wiphy_apply_custom_regulatory [4.314520] ath: Unknown symbol wiphy_apply_custom_regulatory (err -22) [4.314523] ath: disagrees about version of symbol freq_reg_info [4.314523] ath: Unknown symbol freq_reg_info (err -22) I will try to compile the kernel myself and check that is looking for the right modules. -- 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/1972140 Title: UBSAN: array-index-out-of-bounds in /build/linux- HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 Status in linux package in Ubuntu: Confirmed Bug description: [114914.279420] [114914.279431] UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 [114914.279436] index 4 is out of range for type 'ieee80211_tx_rate [4]' [114914.279440] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P IOE 5.15.0-27-generic #28-Ubuntu [114914.279445] Hardware name: Dell Inc. Precision WorkStation T7500 /0D881F, BIOS A18 10/15/2018 [114914.279448] Call Trace: [114914.279451] [114914.279455] show_stack+0x52/0x58 [114914.279465] dump_stack_lvl+0x4a/0x5f [114914.279475] dump_stack+0x10/0x12 [114914.279478] ubsan_epilogue+0x9/0x45 [114914.279482] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [114914.279487] ? iommu_dma_unmap_page+0x4a/0x50 [114914.279492] ath5k_tx_frame_completed.constprop.0+0x279/0x2c0 [ath5k] [114914.279507] ath5k_tx_processq+0xb1/0x1c0 [ath5k] [114914.279519] ath5k_tasklet_tx+0x7b/0xf0 [ath5k] [114914.279531] tasklet_action_common.constprop.0+0xc0/0xf0 [114914.279539] tasklet_action+0x22/0x30 [114914.279543] __do_softirq+0xd9/0x2e3 [114914.279550] irq_exit_rcu+0x8c/0xb0 [114914.279554] common_interrupt+0x8a/0xa0 [114914.279560] [114914.279562] [114914.279563] asm_common_interrupt+0x1e/0x40 [114914.279568] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [114914.279574] Code: 3d 14 5b be 67 e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [114914.279577] RSP: 0018:adc58009be28 EFLAGS: 0292 [114914.279582] RAX: RBX: cdc57ee79f00 RCX: 0020 [114914.279584] RDX: 02c71492 RSI: 3d66 RDI: 99807a40 [114914.279587] RBP: adc58009be78 R08: R09: 000c3500 [114914.279589] R10: 0005 R11: 071c71c71c71c71c R12: 99ad3580 [114914.279592] R13: 0004 R14: 0004 R15: 688390cd49d1 [114914.279597] ? cpuidle_enter_state+0x246/0x620 [114914.279601] cpuidle_enter+0x2e/0x40 [114914.279605] cpuidle_idle_call+0x13e/0x1e0 [114914.279610] do_idle+0x83/0xf0 [114914.279614] cpu_startup_entry+0x20/0x30 [114914.279617] start_secondary+0x12a/0x180 [114914.279622] secondary_startup_64_no_verify+0xc2/0xcb [114914.279630] [114914.279632] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 17869 F pulseaudio /dev/snd/controlC1: js1 17869 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun May 8 23:36:44 2022 InstallationDate: Installed on 2020-02-02 (826 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Dell Inc. Precision WorkStation T7500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=93fc02c6-baa4-4282-96d7-ea5ad53b0c78 ro ipv6.disable=1 splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.
[Kernel-packages] [Bug 2016398] [NEW] stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
Public bug reported: Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot the VM, and start the default distribution kernel, I am able to replicate the issue, the second filesystem being unable to unmount, with "target is busy" with no files open according to standard usermode tools, when chroot is called on it I tried to look at patches in git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar and git log --oneline --grep="sauce" but none of them really look relevant. I could be VERY wrong in this matter though SUMMARY: Long story short, (I am VERY sorry about the length:) I make an overlayfs, I make a second overlayfs with the first overlayfs as the second one's lowerdir, I chroot into the second overlayfs, and then later I can't unmount the second one as it says "Target is busy", but the user mode tools don't show any files open at all. If I mount the second overlayfs, and then unmount it without ever chroot-ing into it I AM able to unmount it The attached script should replicate the issue This doesn't seem to happen on the vanilla Linux kernel, with the same as close as possible config that Ubuntu uses Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nerdopolis 3007 F wireplumber /dev/snd/controlC0: nerdopolis 3007 F wireplumber /dev/snd/seq:nerdopolis 3003 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 15 19:08:48 2023 InstallationDate: Installed on 2023-04-09 (6 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230408) MachineType: ASRock B650M PG Riptide ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgkubuntu-root ro quiet splash amdgpu.sg_display=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2023 dmi.bios.release: 5.26 dmi.bios.vendor: American Megatrend
[Kernel-packages] [Bug 2016398] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Bug description: Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot the VM, and start the default distribution kernel, I am able to replicate the issue, the second filesystem being unable to unmount, with "target is busy" with no files open according to standard usermode tools, when chroot is called on it I tried to look at patches in git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar and git log --oneline --grep="sauce" but none of them really look relevant. I could be VERY wrong in this matter though SUMMARY: Long story short, (I am VERY sorry about the length:) I make an overlayfs, I make a second overlayfs with the first overlayfs as the second one's lowerdir, I chroot into the second overlayfs, and then later I can't unmount the second one as it says "Target is busy", but the user mode tools don't show any files open at all. If I mount the second overlayfs, and then unmount it without ever chroot-ing into it I AM able to unmount it The attached script should replicate the issue This doesn't seem to happen on the vanilla Linux kernel, with the same as close as possible config that Ubuntu uses Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nerdopolis 3007 F wireplumber /dev/snd/controlC0: nerdopolis 3007 F wireplumber /dev/snd/seq:nerdopolis 3003 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 15 19:08:48 2023 InstallationDate: Installed on 2023-04-09 (6 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230408) MachineType: ASRock B650M PG Riptide ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic roo
[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
To further add: Running my scripts in their entirety with a self compiled vanilla kernel instead of Ubuntu's kernel, and I have 0 usages of the overlay module when the script completes. On Ubuntu's kernel the usage goes up and up and up, and never goes down, even though the processes that start the namespaces are all gone. -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Bug description: Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot the VM, and start the default distribution kernel, I am able to replicate the issue, the second filesystem being unable to unmount, with "target is busy" with no files open according to standard usermode tools, when chroot is called on it I tried to look at patches in git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar and git log --oneline --grep="sauce" but none of them really look relevant. I could be VERY wrong in this matter though SUMMARY: Long story short, (I am VERY sorry about the length:) I make an overlayfs, I make a second overlayfs with the first overlayfs as the second one's lowerdir, I chroot into the second overlayfs, and then later I can't unmount the second one as it says "Target is busy", but the user mode tools don't show any files open at all. If I mount the second overlayfs, and then unmount it without ever chroot-ing into it I AM able to unmount it The attached script should replicate the issue This doesn't seem to happen on the vanilla Linux kernel, with the same as close as possible config that Ubuntu uses Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nerdopolis 3007 F wireplumber /dev/snd/controlC0: nerdopolis 3007 F wireplumber /dev/snd/seq:nerdopolis 3003 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 15 19:08:48 2023 InstallationDate: Install
