[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
So yes. Grub2 2.12 with those patches fixes this issue for Jammy, Mantic and Noble. We need to apply the fix to all these releases. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2052411] [NEW] thunderbolt: interrupt for TX ring 0 is already enabled
Public bug reported: After upgrading to linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1 I lost use of an HID device via thunderbolt (still working via USB). This coincided with the following dmesg trace. [26360.900981] [ cut here ] [26360.900984] thunderbolt :22:00.0: interrupt for TX ring 0 is already enabled [26360.901065] WARNING: CPU: 19 PID: 263006 at drivers/thunderbolt/nhi.c:146 ring_interrupt_active+0x270/0x350 [thunderbolt] [26360.901108] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xfrm_user xfrm_algo xt_addrtype br_netfilter ccm xt_CHECKSUM xt_MASQUERADE xt_conntrack snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_sof_probes snd_soc_hdac_hdmi cmac udp_diag ipt_REJECT nf_reject_ipv4 algif_hash snd_hda_codec_realtek nf_conntrack_netlink xt_tcpudp nft_ct snd_hda_codec_generic algif_skcipher nvidia_uvm(PO) nft_compat nft_masq nft_queue af_alg nft_chain_nat nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_tables nf_conntrack nfnetlink_queue nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge stp llc nfnetlink tcp_diag inet_diag overlay bnep snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof intel_uncore_fr equency intel_uncore_frequency_common [26360.901169] intel_tcc_cooling snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core x86_pkg_temp_thermal intel_powerclamp snd_soc_acpi_intel_match coretemp snd_soc_acpi soundwire_generic_allocation soundwire_bus nvidia_drm(PO) iwlmvm kvm_intel snd_soc_core snd_compress nvidia_modeset(PO) i915 snd_hda_codec_hdmi ac97_bus mac80211 snd_pcm_dmaengine kvm btusb crct10dif_pclmul polyval_clmulni btrtl polyval_generic uvcvideo ghash_clmulni_intel drm_buddy btbcm aesni_intel snd_hda_intel videobuf2_vmalloc hid_sensor_als btintel snd_hda_scodec_cs35l41_spi uvc ttm snd_intel_dspcfg crypto_simd btmtk videobuf2_memops mei_hdcp mei_pxp intel_rapl_msr libarc4 snd_intel_sdw_acpi cryptd videobuf2_v4l2 nvidia(PO) binfmt_misc irqbypass snd_usb_audio hid_sensor_trigger bluetooth iwlwifi snd_hda_codec thinkpad_acpi industrialio_triggered_buffer videodev drm_display_helper spi_nor kfifo_buf snd_usbmidi_lib snd_seq_midi snd_hda_core videobuf2_common rapl hid_sensor_iio_common snd_ump hid_magicmouse think_lmi snd_hda_scodec_cs35l41_i2c [26360.901228] snd_seq_midi_event ecdh_generic intel_cstate nls_iso8859_1 serio_raw cec snd_hda_scodec_cs35l41 processor_thermal_device_pci industrialio firmware_attributes_class wmi_bmof input_leds joydev apple_mfi_fastcharge mc snd_rawmidi mtd nvram ecc snd_hwdep rc_core mei_me processor_thermal_device snd_hda_cs_dsp_ctls cfg80211 snd_pcm snd_seq cs_dsp hid_multitouch processor_thermal_rfim mei snd_soc_cs35l41_lib processor_thermal_mbox drm_kms_helper snd_seq_device processor_thermal_rapl i2c_algo_bit snd_timer intel_rapl_common mac_hid snd soundcore serial_multi_instantiate ledtrig_audio int3403_thermal platform_profile int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad acpi_tad sch_fq_codel msr parport_pc ppdev drm lp parport efi_pstore ip_tables x_tables autofs4 hid_sensor_hub cdc_ncm cdc_ether usbnet r8152 mii usbhid hid_generic rtsx_pci_sdmmc i2c_i801 nvme spi_intel_pci crc32_pclmul psmouse thunderbolt i2c_smbus spi_intel nvme_core ucsi_acpi intel_lpss_pci rtsx_pc i typec_ucsi intel_lpss xhci_pci [26360.901294] nvme_common idma64 xhci_pci_renesas i2c_hid_acpi typec i2c_hid hid video pinctrl_tigerlake wmi [26360.901305] CPU: 19 PID: 263006 Comm: kworker/19:2 Tainted: P OE 6.5.0-15-generic #15~22.04.1-Ubuntu [26360.901309] Hardware name: LENOVO 21FV003CAU/21FV003CAU, BIOS N3ZET21W (1.08 ) 07/07/2023 [26360.901311] Workqueue: pm pm_runtime_work [26360.901317] RIP: 0010:ring_interrupt_active+0x270/0x350 [thunderbolt] [26360.901348] Code: 89 5d c8 44 89 45 d4 e8 8e da 38 cc 44 8b 45 d4 48 8b 4d c0 49 89 d9 48 8b 55 b8 48 89 c6 48 c7 c7 78 70 5e c0 e8 50 7e 97 cb <0f> 0b 4d 8b 7f 08 44 8b 5d c8 49 8b 77 18 45 84 ed 0f 85 d9 fe ff [26360.901351] RSP: 0018:b091a6213c48 EFLAGS: 00010046 [26360.901354] RAX: RBX: c05eb6db RCX: [26360.901357] RDX: RSI: RDI: [26360.901358] RBP: b091a6213c98 R08: R09: [26360.901360] R10: R11: R12: 0001 [26360.901361] R13: 0001 R14: 00038200 R15: 9763017d0240 [26360.901363] FS: () GS:976a3f6c() knlGS: [26360.901366] CS: 0010 DS: ES: CR0: 80050033 [26360.901368] CR2: 7ffc979f4d00 CR3: 00010fd6 CR4: 00752ee0 [26360.901370] PKRU:
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
The command log for the work-around for a broken jammy install:
>>>
sudo su -
zpool export -a
zpool import -N -R /mnt rpool
zpool import -N -R /mnt bpool
UUID=$(zfs list | awk '/^bpool\/BOOT\/ubuntu_/ {print $1}' | sed
's/bpool\/BOOT\/ubuntu_//g')
zfs import rpool/ROOT/ubuntu_$UUID
zfs import bpool/BOOT/ubuntu_$UUID
zfs mount -a
mount --make-private --rbind /dev /mnt/dev
mount --make-private --rbind /proc /mnt/proc
mount --make-private --rbind /sys /mnt/sys
mount --make-private --rbind /run /mnt/run
chroot /mnt /bin/bash --login
mount -a
cp /etc/apt/sources.list /etc/apt/sources.list.jammy
sudo nano /etc/sources.list.noble
With these contents:
deb http://us.archive.ubuntu.com/ubuntu/ noble main restricted universe
multiverse
deb http://us.archive.ubuntu.com/ubuntu/ noble-updates main restricted universe
multiverse
deb http://us.archive.ubuntu.com/ubuntu/ noble-backports main restricted
universe multiverse
deb http://security.ubuntu.com/ubuntu noble-security main restricted universe
multiverse
cp /etc/apt/sources.list.noble /etc/sources.list
apt update
add-apt-repository ppa:ubuntu-uefi-team/build
nano /etc/apt/sources.list.d/ubuntu-uefi-team-ubuntu-build-jammy.list
#change the active line to:
deb [trusted=yes]
https://ppa.launchpadcontent.net/ubuntu-uefi-team/build/ubuntu/ noble main
# save and exit
apt update
apt install grub-efi-amd64 grub-efi-amd64-signed
# This will pull in the depends from Grub2 2.12~rc1 from the Nolble Repo's
grub-install --target=x86_64-efi --efi-directory=/boot/efi \
--bootloader-id=ubuntu --recheck --no-floppy
update-intramfs -c -k all
# Change the repo sources back to Jammy
cp /etc/apt/sources.list.jammy /etc/apt/sources.list
apt update
Test:
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204a
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204b
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204c
# Or if there are still snapshots of bpool there...
zfs list -t snapshot
#Output:
#NAME USED AVAIL REFER MOUNTPOINT
#bpool/BOOT/ubuntu_2nlhsy@20230204a 0B - 298M -
#bpool/BOOT/ubuntu_2nlhsy@20230204b 0B - 298M -
#bpool/BOOT/ubuntu_2nlhsy@20230204c 0B - 298M -
#Exit Gracefully:
exit
mount | grep -v zfs | tac | awk '/\/mnt/ {print $3}' | \
xargs -i{} umount -lf {}
zpool export -a
reboot
>>>
--
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/2051999
Title:
Grub2 2.06 has upstream bug that results in Non-booting with ZFS after
snapshot of bpool.
Status in grub2 package in Ubuntu:
Confirmed
Status in grub2-unsigned package in Ubuntu:
Confirmed
Status in zfs-linux package in Ubuntu:
New
Bug description:
There is an upstream Bug with Grub where if you create snapshots of bpool, it
results in a non-booting System. The problem was found to be an upstream Bug
with Grub2:
https://savannah.gnu.org/bugs/index.php?64297
Multiple Ubuntu 22.04.3 Users Affected:
https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug
https://ubuntuforums.org/showthread.php?t=2494957
Brought up as an issue at OpenZFS:
https://github.com/openzfs/zfs/issues/13873
If you look at this comment
(https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was
found the Savanaugh at GNU released a fix for it in Grub2 2.12, here:
https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c
Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch
to Grub2 2.06 so that Users are not caught of in this bug for or
currently supported LTS Release.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: grub-efi-amd64 2.06-2ubuntu14.4
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Thu Feb 1 16:40:28 2024
InstallationDate: Installed on 2021-09-23 (861 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: grub2-unsigned
UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
@rlaager --- When I said reconfigure, i did: >>> sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi \ --bootloader-id=ubuntu --recheck --no-floppy >>> So yes, was that. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Wahoo! Found the magic combination. chrooted into the broken jammy system. Add a Noble sources list. Add the ppa. Edit the added /etc/apt/sources.list.d/ubuntu-uefi-team-ubuntu-build-jammy.list's active line to: >>> deb [trusted=yes] https://ppa.launchpadcontent.net/ubuntu-uefi-team/build/ubuntu/ noble main >>> Update the apt cache Install grub-efi-amd64 & grub-efi-amd64-signed from the ppa. Reconfigure Grub2 and update the initramfs images. Change the sources list back to the original jammy sources.list There were still existing snapshots there. Exit the chroot. Umount the mounts. Export the pools. Reboot. Booted fine. Fixed. Successful. Booting from Grub2 2.12. Writing up the work-around to fix it. I can post it on my ZFS -Fixes/Work-Arounds GitHub Repo. ...Or I can post it here. Maybe here is best. That way it is a known work-around for broken affected systems, until we can figure out the next step. The next step would be, how do we get Grub2 2.12 into Jammy through the updates channel? I would say it first needs to go to jammy proposed, then tested that it works through an update process. Then respin the installer ISO or include it in the next point release.. Since there is a fix, we don't need to create new victims. Just thinking out loud. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2052138] Re: After screen turns off and you turn it back on, weird corruption
** Tags added: amdgpu
** Tags added: flicker suspend-resume
** Summary changed:
- After screen turns off and you turn it back on, weird corruption
+ [amdgpu] After screen turns off and you turn it back on, weird corruption
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2052138
Title:
[amdgpu] After screen turns off and you turn it back on, weird
corruption
Status in linux package in Ubuntu:
New
Bug description:
When the laptop main screen turns off due to inactivity and then you
turn it back on, there is a weird corruption.
Restart helps.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.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 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 2 10:14:53 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[17aa:3a58]
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev c4) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:3a58]
InstallationDate: Installed on 2024-01-12 (21 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN60WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 7 16ACHg6
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052138/+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 2052138] [NEW] [amdgpu] After screen turns off and you turn it back on, weird corruption
You have been subscribed to a public bug:
When the laptop main screen turns off due to inactivity and then you
turn it back on, there is a weird corruption.
Restart helps.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.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 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 2 10:14:53 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[17aa:3a58]
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev c4) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:3a58]
InstallationDate: Installed on 2024-01-12 (21 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN60WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 7 16ACHg6
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 amdgpu apport-bug corruption flicker mantic suspend-resume ubuntu
--
[amdgpu] After screen turns off and you turn it back on, weird corruption
https://bugs.launchpad.net/bugs/2052138
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Any chance this test needs a re-run of “grub-install”, not just “update- grub” (as you would get from a reconfigure)? -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2052406] [NEW] Jammy update: v5.15.145 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.145 upstream stable release from git://git.kernel.org/ ksmbd: use ksmbd_req_buf_next() in ksmbd_verify_smb_message() ksmdb: use cmd helper variable in smb2_get_ksmbd_tcon() ksmbd: Remove redundant 'flush_workqueue()' calls ksmbd: remove md4 leftovers ksmbd: remove smb2_buf_length in smb2_hdr ksmbd: remove smb2_buf_length in smb2_transform_hdr ksmbd: change LeaseKey data type to u8 array ksmbd: use oid registry functions to decode OIDs ksmbd: Remove unused parameter from smb2_get_name() ksmbd: Remove unused fields from ksmbd_file struct definition ksmbd: set both ipv4 and ipv6 in FSCTL_QUERY_NETWORK_INTERFACE_INFO ksmbd: Fix buffer_check_err() kernel-doc comment ksmbd: Fix smb2_set_info_file() kernel-doc comment ksmbd: Delete an invalid argument description in smb2_populate_readdir_entry() ksmbd: Fix smb2_get_name() kernel-doc comment ksmbd: register ksmbd ib client with ib_register_client() ksmbd: set 445 port to smbdirect port by default ksmbd: smbd: call rdma_accept() under CM handler ksmbd: smbd: create MR pool ksmbd: smbd: change the default maximum read/write, receive size ksmbd: smbd: fix missing client's memory region invalidation ksmbd: smbd: validate buffer descriptor structures ksmbd: add support for key exchange ksmbd: use netif_is_bridge_port ksmbd: store fids as opaque u64 integers ksmbd: shorten experimental warning on loading the module ksmbd: Remove a redundant zeroing of memory ksmbd: replace usage of found with dedicated list iterator variable smb3: fix ksmbd bigendian bug in oplock break, and move its struct to smbfs_common ksmbd: remove filename in ksmbd_file ksmbd: smbd: change prototypes of RDMA read/write related functions ksmbd: smbd: introduce read/write credits for RDMA read/write ksmbd: smbd: simplify tracking pending packets ksmbd: smbd: change the return value of get_sg_list ksmbd: smbd: handle multiple Buffer descriptors ksmbd: fix wrong smbd max read/write size check ksmbd: Fix some kernel-doc comments ksmbd: smbd: fix connection dropped issue ksmbd: smbd: relax the count of sges required ksmbd: smbd: Remove useless license text when SPDX-License-Identifier is already used ksmbd: remove duplicate flag set in smb2_write ksmbd: remove unused ksmbd_share_configs_cleanup function ksmbd: use wait_event instead of schedule_timeout() ksmbd: request update to stale share config ksmbd: remove unnecessary generic_fillattr in smb2_open ksmbd: don't open-code file_path() ksmbd: don't open-code %pD ksmbd: constify struct path ksmbd: remove generic_fillattr use in smb2_open() ksmbd: casefold utf-8 share names and fix ascii lowercase conversion ksmbd: change security id to the one samba used for posix extension ksmbd: set file permission mode to match Samba server posix extension behavior ksmbd: fill sids in SMB_FIND_FILE_POSIX_INFO response ksmbd: fix encryption failure issue for session logoff response ksmbd: set NTLMSSP_NEGOTIATE_SEAL flag to challenge blob ksmbd: decrease the number of SMB3 smbdirect server SGEs ksmbd: reduce server smbdirect max send/receive segment sizes ksmbd: hide socket error message when ipv6 config is disable ksmbd: make utf-8 file name comparison work in __caseless_lookup() ksmbd: call ib_drain_qp when disconnected ksmbd: validate share name from share config response ksmbd: replace one-element arrays with flexible-array members ksmbd: set SMB2_SESSION_FLAG_ENCRYPT_DATA when enforcing data encryption for this share ksmbd: use F_SETLK when unlocking a file ksmbd: Fix resource leak in smb2_lock() ksmbd: Convert to use sysfs_emit()/sysfs_emit_at() APIs ksmbd: send proper error response in smb2_tree_connect() ksmbd: Implements sess->rpc_handle_list as xarray ksmbd: fix typo, syncronous->synchronous ksmbd: Remove duplicated codes ksmbd: update Kconfig to note Kerberos support and fix indentation ksmbd: Fix spelling mistake "excceed" -> "exceeded" ksmbd: Fix parameter name and comment mismatch ksmbd: fix possible memory leak in smb2_lock() ksmbd: fix wrong signingkey creation when encryption is AES256 ksmbd: remove unused is_char_allowed function ksmbd: delete asynchronous work from list ksmbd: fix slab-out-of-bounds in init_smb2_rsp_hdr ksmbd: avoid out of bounds access in decode_preauth_ctxt() ksmbd: set NegotiateContextCount once instead of every inc ksmbd: avoid duplicate negotiate ctx offset increments ksmbd: remove unused compression negotiate ctx packing fs: introduce lock_rename_child() helper ksmbd: fix racy issue from using ->d_parent and ->d_name ksmbd: destroy
[Kernel-packages] [Bug 2049634] Re: smb1: wsize blocks of bytes followed with binary zeros on copy, destroying data
Hi R. Diez, I had a bit of spare time, and took a closer look. I can reproduce the issue, and I can see the zeros. It does indeed happen on every copy. I tried 6.8-rc3, so it is still broken there. I will write to the maintainer about getting this fixed as soon as I locate the commit that introduced the issue. So far I figured out that it has been broken since 6.3-rc1. I'm currently bisecting between 6.2 and 6.3-rc1, will let you know what I find in the next couple days. Thanks, Matthew ** Summary changed: - SMB 1 broken in kernel 6.5.0.14.14~22.04.7 + smb1: wsize blocks of bytes followed with binary zeros on copy, destroying data ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Description changed: - Hi all: + [Impact] - I upgraded my Ubuntu yesterday and automatically got the newer Linux - Kernel version 6.5.0-14-generic #14~22.04.1-Ubuntu. Previously, I was - running kernel version 6.2 . + Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize + set will see data destruction when copying files from their systems onto + a cifs smb 1.0 mount. - I still have a legacy system on the network using SMB protocol version - 1.0. + wsize defaults to 65535 bytes, but when set to smaller values, like + 16850, users will see blocks of 16850 bytes copied over, followed by + 3900 binary zeros, followed by the next block of data followed by more + binary zeros. - With the new kernel version, copying files does not work reliably - anymore. Some random byte blocks in the destination files are - overwritten with binary zeros. It happens quite often. + A workaround is to increase wsize, but this only works for small files, + as any files larger than wsize will see the bug. - This is not the first time the Linux guys temporarily break SMB protocol version 1.0, see for example this bug report of mine: - https://bugs.launchpad.net/ubuntu/+bug/2033732 + Most users will want to use the 6.2 HWE kernel until this is fixed. - I checked package linux-image-generic-hwe-22.04 with Synaptic, and now it lists just 2 versions: - 6.5.0.14.14~22.04.7 (jammy-updates) - 5.15.0.25.27 (jammy) - Is there a way to go back to the latest 6.2 kernel version? + [Testcase] - How do I prevent Ubuntu from upgrading to 6.5 next time around? I have searched the Internet, but I haven't - found yet a usable answer. I don't want to go back all the way to Kernel 5.15 if I can avoid it. + Start two VMs, one for the server, and the other, the client. - Thanks in advance, - rdiez + Server + -- + + $ sudo apt update + $ sudo apt upgrade + $ sudo apt install samba + $ sudo vim /etc/samba/smb.conf + server min protocol = NT1 + [sambashare] + comment = Samba on Ubuntu + path = /home/ubuntu/sambashare + read only = no + browsable = yes + $ mkdir ~/sambashare + $ sudo smbpasswd -a ubuntu + + Client + -- + + $ sudo apt update + $ sudo apt install cifs-utils + $ mkdir ~/share + $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 //192.168.122.172/sambashare ~/share + $ ( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl enc -aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-squeezing --format '40/1 "%02x"' --format '"\n"' >"testdata.txt" ) + $ sha256sum testdata.txt + 9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2 testdata.txt + + Now copy the file to the share. + + Client + -- + $ cp testdata.txt share/ + + Server + -- + $ sha256sum sambashare/testdata.txt + 9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866 sambashare/testdata.txt + + The SHA256 hash is different. If you view the file with less, you will + find a block of wsize=16850 bytes, then 3900 bytes of binary zeros, + followed by another wsize=16850 bytes, then 3900 bytes of binary zeros, + etc. + + An example of a broken file is: + https://launchpadlibrarian.net/712573213/testdata-back-from-server.txt + + [Where problems could occur] + + [Other info] + + Currently bisecting. Introduced in 6.3-rc1. Currently broken on mainline + 6.8-rc3. ** Tags added: seg -- 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/2049634 Title: smb1: wsize blocks of bytes followed with binary zeros on copy, destroying data Status in linux package in Ubuntu: In Progress Status in linux source package in Mantic: In Progress Status in
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Since it is also built for Mantic, I would expect it works for Mantic Also. (Will confirm later.) I spun up a Jammy ZFS image. Changed the sources list to Noble. Added the PPA. Installed packages 'grub2 & shim'... Let it pull in the depends it needed. Change the sources.list back to jammy. Did some snapshots of bpool. Reconfigured grub, as it would do in an update... It said that was successful, so at that point was hopeful. Had fingers crossed. Rebooted, failed. Booted straight to BIOS. Shutdown > Cold boot > Failed. Booted straight to BIOS. So Grub2 2.12 works for the problems with Mantic and Noble, but not as a fix to Jammy 22.04. That sort of goes back to those last 4 patches (Grub2 related to ZFS) working to fix this problem for Noble & Mantic, but (somehow) need to be backported to fix Jammy. Dang. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2044657] Re: Multiple data corruption issues in zfs
@Timo I just saw the 2.2.0-0ubuntu1~23.10.2 announcement for mantic.
IMHO cherry picking is not a very good approach when it comes to 2.2.2.
I followed the ZFS github repo closely during the time of the bug in
November and December until 2.2.2 came out on the ZFS GitHub repo and
there where multiple fixes going into 2.2.2. which where important IIRC.
So we are waiting for an official package for Ubuntu now for a very long
time for this kind of severe bug and we still don't end up with the
intended fixes by the ZFS devs, which have given quite some thought on
what to put into 2.2.2.
I would strongly suggest to go with the 2.2.2 package not just one
commit. I am running 2.2.2 on Ubuntu with a custom package for quite
some time now (see earlier post) and everything looks good so far.
--
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/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2052404] [NEW] Jammy update: v5.15.144 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.144 upstream stable release from git://git.kernel.org/ r8152: add vendor/device ID pair for D-Link DUB-E250 r8152: add vendor/device ID pair for ASUS USB-C2500 netfilter: nf_tables: fix 'exist' matching on bigendian arches mm/memory_hotplug: handle memblock_add_node() failures in add_memory_resource() memblock: allow to specify flags with memblock_add_node() MIPS: Loongson64: Handle more memory types passed from firmware ksmbd: fix memory leak in smb2_lock() afs: Fix refcount underflow from error handling race HID: lenovo: Restrict detection of patched firmware only to USB cptkbd net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX qca_debug: Prevent crash on TX ring changes qca_debug: Fix ethtool -G iface tx behavior qca_spi: Fix reset behavior atm: solos-pci: Fix potential deadlock on _queue_lock atm: solos-pci: Fix potential deadlock on _queue_lock net: vlan: introduce skb_vlan_eth_hdr() net: fec: correct queue selection octeontx2-af: fix a use-after-free in rvu_nix_register_reporters octeontx2-pf: Fix promisc mcam entry action octeontx2-af: Update RSS algorithm index qed: Fix a potential use-after-free in qed_cxt_tables_alloc net: Remove acked SYN flag from packet in the transmit queue correctly net: ena: Destroy correct number of xdp queues upon failure net: ena: Fix xdp drops handling due to multibuf packets net: ena: Fix XDP redirection error stmmac: dwmac-loongson: Make sure MDIO is initialized before use sign-file: Fix incorrect return values check vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space() dpaa2-switch: fix size of the dma_unmap net: stmmac: use dev_err_probe() for reporting mdio bus registration failure net: stmmac: Handle disabled MDIO busses from devicetree net: atlantic: fix double free in ring reinit logic cred: switch to using atomic_long_t fuse: dax: set fc->dax to NULL in fuse_dax_conn_free() ALSA: hda/hdmi: add force-connect quirk for NUC5CPYB ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants ALSA: hda/realtek: Apply mute LED quirk for HP15-db PCI: loongson: Limit MRRS to 256 drm/mediatek: Add spinlock for setting vblank event in atomic_begin usb: aqc111: check packet for fixup for true limit stmmac: dwmac-loongson: Add architecture dependency UBUNTU: [Config] updateconfigs for CONFIG_DWMAC_LOONGSON blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" blk-cgroup: bypass blkcg_deactivate_policy after destroying bcache: avoid oversize memory allocation by small stripe_size bcache: remove redundant assignment to variable cur_idx bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() bcache: avoid NULL checking to c->root in run_cache_set() platform/x86: intel_telemetry: Fix kernel doc descriptions HID: glorious: fix Glorious Model I HID report HID: add ALWAYS_POLL quirk for Apple kb HID: hid-asus: reset the backlight brightness level on resume HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation net: usb: qmi_wwan: claim interface 4 for ZTE MF290 HID: hid-asus: add const to read-only outgoing usb buffer btrfs: do not allow non subvolume root targets for snapshot soundwire: stream: fix NULL pointer dereference for multi_link ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS arm64: mm: Always make sw-dirty PTEs hw-dirty in pte_modify team: Fix use-after-free when an option instance allocation fails drm/amdgpu/sdma5.2: add begin/end_use ring callbacks ring-buffer: Fix memory leak of free page tracing: Update snapshot buffer on resize if it is allocated ring-buffer: Do not update before stamp when switching sub-buffers ring-buffer: Have saved event hold the entire event ring-buffer: Fix writing to the buffer with max_data_size ring-buffer: Fix a race in rb_time_cmpxchg() for 32 bit archs ring-buffer: Do not try to put back write_stamp USB: gadget: core: adjust uevent timing on gadget unbind powerpc/ftrace: Create a dummy stackframe to fix stack unwind powerpc/ftrace: Fix stack teardown in ftrace_no_trace r8152: avoid to change cfg for all devices r8152: remove rtl_vendor_mode function r8152: fix the autosuspend doesn't work Linux 5.15.144 UBUNTU: Upstream stable to v5.15.144 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Portia Stephens (portias) Status: In Progress ** Tags:
[Kernel-packages] [Bug 2051720]
This issue is still present in kernel 6.7.3 -- 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/2051720 Title: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210) Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: ``` kernel: Bluetooth: hci0: command 0xfc05 tx timeout ``` This issue started with kernel 6.5. Bluetooth has been broken ever since. The issue was not present in earlier versions of the kernel. ``` $ uname -a Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsusb | grep -i bluetooth Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth ``` ``` $ journalctl -b | egrep -i bluetooth Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth. Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support. Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed (-110) ``` ``` linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all [installed,automatic] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2051720/+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 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
It worked: The grub issue with a PPA solved it for NNoble Code: apt policy grub-common grub-common: Installed: 2.12-1ubuntu1~ppa1 Candidate: 2.12-1ubuntu1~ppa1 Version table: *** 2.12-1ubuntu1~ppa1 500 500 https://ppa.launchpadcontent.net/ubuntu-uefi-team/build/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status 2.12~rc1-12ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages zfs list -r -t snapshot -o name,creation bpool NAME CREATION bpool/BOOT/ubuntu_l7y21m@autozsys_bk6cdb Fri Feb 2 10:41 2024 bpool/BOOT/ubuntu_l7y21m@autozsys_sin22d Sat Feb 3 17:22 2024 bpool/BOOT/ubuntu_l7y21m@autozsys_41kebx Sat Feb 3 17:23 2024 bpool/BOOT/ubuntu_l7y21m@autozsys_25r5is Sun Feb 4 13:55 2024 bpool/BOOT/ubuntu_l7y21m@autozsys_1n6o7d Sun Feb 4 14:07 2024 bpool/BOOT/ubuntu_l7y21m@2-4-2024test Sun Feb 4 14:09 2024 As seen by the bottom "bpool/BOOT/ubuntu_l7y21m@2-4-2024test Sun Feb 4 14:09 2024" -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
I've added the PPA for Noble just now, will report after a manual bpool snapshot **The following packages will be upgraded: automake autopoint ayatana-indicator-common bind9-dnsutils bind9-host bind9-libs cpio gcc-14-base gcc-14-base:i386 gettext gettext-base grub-common grub-efi-amd64-bin grub-efi-amd64-signed grub-pc grub-pc-bin grub2-common language-pack-gnome-en libasan8 libatomic1 libatomic1:i386 libcc1-0 libgcc-s1 libgcc-s1:i386 libgfortran5 libgnutls30 libgomp1 libhwasan0 libitm1 liblsan0 libneon27 libp11-kit0 libpcap0.8 libquadmath0 libstdc++6 libstdc++6:i386 libtsan2 libubsan1 linux-firmware openssh-client p11-kit p11-kit-modules python3-mako ufw 44 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2052396] [NEW] package nvidia-driver-470 470.223.02-0ubuntu1 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: i try ... ProblemType: Package DistroRelease: Ubuntu 24.04 Package: nvidia-driver-470 470.223.02-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Feb 4 21:02:52 2024 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2023-08-04 (184 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.2ubuntu2 apt 2.7.10 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-driver-470 470.223.02-0ubuntu1 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- 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/2052396 Title: package nvidia-driver-470 470.223.02-0ubuntu1 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: i try ... ProblemType: Package DistroRelease: Ubuntu 24.04 Package: nvidia-driver-470 470.223.02-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Feb 4 21:02:52 2024 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2023-08-04 (184 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.2ubuntu2 apt 2.7.10 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-driver-470 470.223.02-0ubuntu1 failed to install/upgrade: problèmes de dépendances - laissé non configuré 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/2052396/+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 2052394] [NEW] package nvidia-dkms-470 470.223.02-0ubuntu1 failed to install/upgrade: le sous-processus paquet nvidia-dkms-470 script post-installation installé a renvoyé un éta
Public bug reported: try to restore my ubuntu ProblemType: Package DistroRelease: Ubuntu 24.04 Package: nvidia-dkms-470 470.223.02-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Feb 4 21:02:52 2024 ErrorMessage: le sous-processus paquet nvidia-dkms-470 script post-installation installé a renvoyé un état de sortie d'erreur 3 InstallationDate: Installed on 2023-08-04 (184 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.2ubuntu2 apt 2.7.10 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.223.02-0ubuntu1 failed to install/upgrade: le sous-processus paquet nvidia-dkms-470 script post-installation installé a renvoyé un état de sortie d'erreur 3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- 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/2052394 Title: package nvidia-dkms-470 470.223.02-0ubuntu1 failed to install/upgrade: le sous-processus paquet nvidia-dkms-470 script post-installation installé a renvoyé un état de sortie d'erreur 3 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: try to restore my ubuntu ProblemType: Package DistroRelease: Ubuntu 24.04 Package: nvidia-dkms-470 470.223.02-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Feb 4 21:02:52 2024 ErrorMessage: le sous-processus paquet nvidia-dkms-470 script post-installation installé a renvoyé un état de sortie d'erreur 3 InstallationDate: Installed on 2023-08-04 (184 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.2ubuntu2 apt 2.7.10 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.223.02-0ubuntu1 failed to install/upgrade: le sous-processus paquet nvidia-dkms-470 script post-installation installé a renvoyé un état de sortie d'erreur 3 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/2052394/+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 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
@mafoelffen You can find builds of GRUB 2.12 for Ubuntu in this PPA: https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/build NOTE that the stuff in that PPA isn't signed, so you need to disable UEFI secure boot to test it easily. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2006557] Re: Enable rdma-sniffer for libpcap
This bug was fixed in the package libpcap - 1.10.4-4ubuntu3 --- libpcap (1.10.4-4ubuntu3) noble; urgency=medium * Don't require ibverbs on i386 -- Jeremy Bícha Fri, 02 Feb 2024 16:41:24 -0500 ** Changed in: libpcap (Ubuntu) Status: Fix Committed => Fix Released -- 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/2006557 Title: Enable rdma-sniffer for libpcap Status in libpcap package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Invalid Status in libpcap package in Debian: Won't Fix Bug description: Hi, The request is to build and configure stock package libpcap with rdma-sniffer enabled. We'd like users of rdma devices to be able to sniff on them using stock tcpdump. Currently when using default tcpdump It does not list rdma devices. $ tcpdump -D |grep -i rdma $ when using locally build tcpdump (with rdma enabled) $ cd $ ./tcpdump -D |grep -i rdma 24.rocep4s0 (RDMA sniffer) 25.rocep7s0f0 (RDMA sniffer) 26.rocep7s0f1 (RDMA sniffer) 27.rocep10s0f0 (RDMA sniffer) 28.rocep10s0f1 (RDMA sniffer) 29.rocep33s0f0 (RDMA sniffer) 30.rocep33s0f1 (RDMA sniffer) 31.rocep36s0f0 (RDMA sniffer) 32.ibp36s0f1 (RDMA sniffer) Locally build steps: clone sources: $ mkdir tcpdumpbuild $ cd tcpdumpbuild/ $ git clone https://github.com/the-tcpdump-group/tcpdump.git $ git clone https://github.com/the-tcpdump-group/libpcap.git install required packages (including rdma packages so libpcap is built with rdma enabled): $ apt install flex bison librdmacm-dev librdmacm1 rdma-core rdmacm-utils configure and build $ cd libpcap $ ./autogen.sh $ ./configure --enable-rdma=yes $ make cd ../tcpdump/ ./autogen.sh ./configure $ make now ./tcpdump -D can show rdma devices. Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpcap/+bug/2006557/+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 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Forgot to mention... Those "@feature" changes, that are suspected as being the problems when enabled... unfortunately cannot be done on an already created bpool. Those can only be set at pool "creation time". So I'm working on a script to recreate bpool which those specific option settings from the existing bpool, offline from an installer LiveUSB, environment. If I try it from online, it will not export the bpool. It just says "busy". Using an additional USB flash drive to temporarily hold the backup from bpool to destroy and recreate the bpool. That is the path I'm investigating and testing currently. That currently is, in the absence of a Grub2 2.12 that works with those conditions. If the new Grub2 2.12 does work with the older option setting, then a lot of thigs will be resolved, and a work-around will not be needed to fix existing installs nor new options set in ubuntu-desktop-installer. I installed just Grub 2.12~rc1 to 22.04.3 with the associated long line of depends. It wasn't pretty. And it did not correct the problem. That was not an answer to recommend. But at this point in time, because of Grub 2.12 not building and is vaporware. We don't have enough here to test, and make informed decisions. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 1626838] Re: yakkety compiling failed on ubuntu trusty
** Changed in: linux (Ubuntu) Status: Confirmed => New ** Project changed: ubuntu-ubuntu-server => 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/1626838 Title: yakkety compiling failed on ubuntu trusty Status in trusty-backports: Won't Fix Status in Yakkety Backports: Won't Fix Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hi ubuntu kernel team, I am compiling my own ubuntu kernel on ubuntu trusty, and I git clone https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety, the build almost success, but failed at the end with missing modules, I haven't done any change for the source code : Then I start a docker container using xenial image, try the same build steps, I can successfullly build kernel deb pkgs . Do you have idea why it throw missing module error on ubuntu trusty ? Thanks . root@kbuild:~/yakkety# uname -a Linux kbuild 3.13.0-58-generic #97-Ubuntu SMP Wed Jul 8 02:56:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@kbuild:~/yakkety# apt-get build-dep linux-image-4.4.0-36-generic root@kbuild:~/yakkety# fakeroot debian/rules clean root@kbuild:~/yakkety# AUTOBUILD=1 fakeroot debian/rules binary-generic --ignore make[2]: Leaving directory `/root/yakkety/debian/build/build-generic' make[1]: Leaving directory `/root/yakkety' Debug: module-check-generic install -d /root/yakkety/debian.master/abi/4.4.0-34.53/amd64 find /root/yakkety/debian/build/build-generic/ -name \*.ko | \ sed -e 's/.*\/\([^\/]*\)\.ko/\1/' | sort > /root/yakkety/debian.master/abi/4.4.0-34.53/amd64/generic.modules II: Checking modules for generic... reading new modules...read 4590 modules. reading old modules... MISS: spl MISS: splat MISS: zavl MISS: zcommon MISS: zfs MISS: znvpair MISS: zpios MISS: zunicode read 4598 modules : new(0) missing(8) EE: Missing modules (start begging for mercy) make: *** [module-check-generic] Error 1 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 23 03:51 seq crw-rw 1 root audio 116, 33 Sep 23 03:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-58-generic root=UUID=80575ee5-f6ee-41e2-bab6-e4af1c26d1c1 ro nofb nomodeset vga=normal console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 RelatedPackageVersions: linux-restricted-modules-3.13.0-58-generic N/A linux-backports-modules-3.13.0-58-generic N/A linux-firmware 1.127.16 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.13.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2015.1.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2015.1.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1626838/+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 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048945 Title: scsi_eh_* process using idle CPU after upgrade to kernel 6.5 Status in linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Possibly related to https://lkml.kernel.org/linux- scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/ Getting alerts from monitoring tools about high average CPU usage. Machine reporting the following: root@server:~# uptime 17:04:34 up 14 days, 6:33, 2 users, load average: 15.66, 15.88, 15.94 root@server:~# top -d 1 top - 17:04:49 up 14 days, 6:33, 2 users, load average: 15.59, 15.85, 15.93 Tasks: 223 total, 1 running, 222 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.7 us, 1.4 sy, 0.0 ni, 49.3 id, 48.6 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7896.6 total, 1772.6 free, 1163.9 used, 4960.0 buff/cache MiB Swap: 2048.0 total, 1784.6 free,263.4 used. 6431.6avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 88 root 20 0 0 0 0 D 55.4 0.0 11275:46 scsi_eh_1 root@server:~# lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge linux-image-virtual-hwe-22.04-edge: Installed: 6.5.0.14.14~22.04.6 Candidate: 6.5.0.14.14~22.04.7 Version table: 6.5.0.14.14~22.04.7 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 6.5.0.14.14~22.04.6 100 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jan 10 17:02:50 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Tags: jammy third-party-packages Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 27 10:31 seq crw-rw 1 root audio 116, 33 Dec 27 10:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc IwConfig: lono wireless extensions. eth0 no wireless extensions. 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: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vmwgfxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-14-generic N/A linux-backports-modules-6.5.0-14-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy Uname: Linux 6.5.0-14-generic x86_64
[Kernel-packages] [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-aws-6.5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048945 Title: scsi_eh_* process using idle CPU after upgrade to kernel 6.5 Status in linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Possibly related to https://lkml.kernel.org/linux- scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/ Getting alerts from monitoring tools about high average CPU usage. Machine reporting the following: root@server:~# uptime 17:04:34 up 14 days, 6:33, 2 users, load average: 15.66, 15.88, 15.94 root@server:~# top -d 1 top - 17:04:49 up 14 days, 6:33, 2 users, load average: 15.59, 15.85, 15.93 Tasks: 223 total, 1 running, 222 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.7 us, 1.4 sy, 0.0 ni, 49.3 id, 48.6 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7896.6 total, 1772.6 free, 1163.9 used, 4960.0 buff/cache MiB Swap: 2048.0 total, 1784.6 free,263.4 used. 6431.6avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 88 root 20 0 0 0 0 D 55.4 0.0 11275:46 scsi_eh_1 root@server:~# lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge linux-image-virtual-hwe-22.04-edge: Installed: 6.5.0.14.14~22.04.6 Candidate: 6.5.0.14.14~22.04.7 Version table: 6.5.0.14.14~22.04.7 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 6.5.0.14.14~22.04.6 100 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jan 10 17:02:50 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Tags: jammy third-party-packages Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 27 10:31 seq crw-rw 1 root audio 116, 33 Dec 27 10:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc IwConfig: lono wireless extensions. eth0 no wireless extensions. 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: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vmwgfxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-14-generic N/A linux-backports-modules-6.5.0-14-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy Uname: Linux 6.5.0-14-generic x86_64
[Kernel-packages] [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048945 Title: scsi_eh_* process using idle CPU after upgrade to kernel 6.5 Status in linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Possibly related to https://lkml.kernel.org/linux- scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/ Getting alerts from monitoring tools about high average CPU usage. Machine reporting the following: root@server:~# uptime 17:04:34 up 14 days, 6:33, 2 users, load average: 15.66, 15.88, 15.94 root@server:~# top -d 1 top - 17:04:49 up 14 days, 6:33, 2 users, load average: 15.59, 15.85, 15.93 Tasks: 223 total, 1 running, 222 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.7 us, 1.4 sy, 0.0 ni, 49.3 id, 48.6 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7896.6 total, 1772.6 free, 1163.9 used, 4960.0 buff/cache MiB Swap: 2048.0 total, 1784.6 free,263.4 used. 6431.6avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 88 root 20 0 0 0 0 D 55.4 0.0 11275:46 scsi_eh_1 root@server:~# lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge linux-image-virtual-hwe-22.04-edge: Installed: 6.5.0.14.14~22.04.6 Candidate: 6.5.0.14.14~22.04.7 Version table: 6.5.0.14.14~22.04.7 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 6.5.0.14.14~22.04.6 100 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jan 10 17:02:50 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Tags: jammy third-party-packages Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 27 10:31 seq crw-rw 1 root audio 116, 33 Dec 27 10:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc IwConfig: lono wireless extensions. eth0 no wireless extensions. 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: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vmwgfxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-14-generic N/A linux-backports-modules-6.5.0-14-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy Uname: Linux 6.5.0-14-generic x86_64
[Kernel-packages] [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe-6.5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048945 Title: scsi_eh_* process using idle CPU after upgrade to kernel 6.5 Status in linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Possibly related to https://lkml.kernel.org/linux- scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/ Getting alerts from monitoring tools about high average CPU usage. Machine reporting the following: root@server:~# uptime 17:04:34 up 14 days, 6:33, 2 users, load average: 15.66, 15.88, 15.94 root@server:~# top -d 1 top - 17:04:49 up 14 days, 6:33, 2 users, load average: 15.59, 15.85, 15.93 Tasks: 223 total, 1 running, 222 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.7 us, 1.4 sy, 0.0 ni, 49.3 id, 48.6 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7896.6 total, 1772.6 free, 1163.9 used, 4960.0 buff/cache MiB Swap: 2048.0 total, 1784.6 free,263.4 used. 6431.6avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 88 root 20 0 0 0 0 D 55.4 0.0 11275:46 scsi_eh_1 root@server:~# lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge linux-image-virtual-hwe-22.04-edge: Installed: 6.5.0.14.14~22.04.6 Candidate: 6.5.0.14.14~22.04.7 Version table: 6.5.0.14.14~22.04.7 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 6.5.0.14.14~22.04.6 100 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jan 10 17:02:50 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Tags: jammy third-party-packages Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 27 10:31 seq crw-rw 1 root audio 116, 33 Dec 27 10:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc IwConfig: lono wireless extensions. eth0 no wireless extensions. 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: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vmwgfxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-14-generic N/A linux-backports-modules-6.5.0-14-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy Uname: Linux 6.5.0-14-generic x86_64
[Kernel-packages] [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5
Status changed to 'Confirmed' because the bug affects multiple users. ** 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-aws-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048945 Title: scsi_eh_* process using idle CPU after upgrade to kernel 6.5 Status in linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Possibly related to https://lkml.kernel.org/linux- scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/ Getting alerts from monitoring tools about high average CPU usage. Machine reporting the following: root@server:~# uptime 17:04:34 up 14 days, 6:33, 2 users, load average: 15.66, 15.88, 15.94 root@server:~# top -d 1 top - 17:04:49 up 14 days, 6:33, 2 users, load average: 15.59, 15.85, 15.93 Tasks: 223 total, 1 running, 222 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.7 us, 1.4 sy, 0.0 ni, 49.3 id, 48.6 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7896.6 total, 1772.6 free, 1163.9 used, 4960.0 buff/cache MiB Swap: 2048.0 total, 1784.6 free,263.4 used. 6431.6avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 88 root 20 0 0 0 0 D 55.4 0.0 11275:46 scsi_eh_1 root@server:~# lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge linux-image-virtual-hwe-22.04-edge: Installed: 6.5.0.14.14~22.04.6 Candidate: 6.5.0.14.14~22.04.7 Version table: 6.5.0.14.14~22.04.7 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 6.5.0.14.14~22.04.6 100 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jan 10 17:02:50 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Tags: jammy third-party-packages Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 27 10:31 seq crw-rw 1 root audio 116, 33 Dec 27 10:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc IwConfig: lono wireless extensions. eth0 no wireless extensions. 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: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vmwgfxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-14-generic N/A linux-backports-modules-6.5.0-14-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus:
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
I'm working on trying various differing work-arounds with what is there natively. I tried building the newest git on Grub2 2.12. Fails building at a point which is says way fixed for the error i am getting, but still fails on the make at the same point. (asorti ot defined) I'm also working on another theory, recreating bpool with differing options, on the theory that on the creation of bpool, that some on the zpool options are causing Grub2 to fail with those added challenges. I'll keep you up-to date how those go. Trying to balance my time between "real life", helping the upstream Intel Graphics Support Engineers with drivers issues with Ubuntu, and helping Users with other issues. ...All while trying to find underlying information answers for this issue. What get's me, it that "feature" or "ability" that this is failing on, being able to snapshot bpool, because that is the failure point we need to protect from, was covered by Zsys, and why Canonical came up with that in the first place. It worked in 20.04 LTS... There was not a problem there, with that installed. We were able to do that in that release. Marketing-wise, it put Ubuntu ahead of things with that "need" covered well. Zsys was removed from being a default install (no mention why), but I still see commits to it. The need to make snapshots of the boot related files is still there. I wish I knew more on the why Zsys feel from favor. I thought basically,besides some minor changes, it was a great idea to do what it was intended to do. Some users, have gone around this problem by using ZFS Boot Menu (ZBM). But that is not a solution, Rather it removes the conditions, by what they have to do in the restructure to make it work. For it, bpool cannot exist. There cannot be a separate /boot. /boot has to be inside the root pool, and not inside it's own ZFS dataset... If this restructure is done this way, then those conditions do not exist. That is why is works. No that ZBM gets around the problem itself. If you crate a dataset for /boot itself, to make snapshots of boot related files, then ZBM does not work, even before the snapshots are made. It simply cannot find the boot related files, that way. (At all.) So to do a snapshot of boot related files, after that restructure, you end up having to snapshot the whole root pool, No, we need to find a way to get Grub2 and ZFS to play together nicely, and be stable. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Also affect Mantic... ** Also affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2044657] Re: Multiple data corruption issues in zfs
So, I did test the -proposed package for mantic on a clean install by creating a test-pool and running the zhammer.sh linked #16. … As expected on an unpatched system the error occurred during the first iteration: [zhammer::1858] zhammer_1858_0 differed from zhammer_1858_538! [zhammer::1858] Hexdump diff follows --- zhammer_1858_0.hex 2024-02-03 12:44:07.478205144 + +++ zhammer_1858_538.hex2024-02-03 12:44:07.478205144 + @@ -1,3 +1,3 @@ - ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff || + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 4000 [zhammer::1858] Uname: Linux zfstest 6.5.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 9 17:03:36 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux [zhammer::1858] ZFS userspace: zfs-2.2.0-0ubuntu1~23.10.1 [zhammer::1858] ZFS kernel: zfs-kmod-2.2.0-0ubuntu1~23.10 [zhammer::1858] Module: /lib/modules/6.5.0-15-generic/kernel/zfs/zfs.ko.zst [zhammer::1858] Srcversion: 92158472E32FE6AEEEC7201 [zhammer::1858] SHA256: 177442f43f4c94537f8b003ab28ed33d00240c175e500370ad5bdd5c50234655 parallel: This job failed: zhammer /test 1000 16k 1 7 … After enabling the -proposed repository, installing the updates and restarting the system is looks like the userspace-tools are now on the patched version (zfs-2.2.0-0ubuntu1~23.10.1), however the kernel module is still on the old version (without the .1) and, as expected, the bug is still reproducible: [zhammer::1706] zhammer_1706_0 differed from zhammer_1706_1204! [zhammer::1706] Hexdump diff follows --- zhammer_1706_0.hex 2024-02-04 14:29:28.296850257 + +++ zhammer_1706_1204.hex 2024-02-04 14:29:28.296850257 + @@ -1,3 +1,3 @@ - ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff || + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 4000 [zhammer::1706] Uname: Linux zfstest 6.5.0-17-generic #17-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 11 14:01:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux [zhammer::1706] ZFS userspace: zfs-2.2.0-0ubuntu1~23.10.2 [zhammer::1706] ZFS kernel: zfs-kmod-2.2.0-0ubuntu1~23.10 [zhammer::1706] Module: /lib/modules/6.5.0-17-generic/kernel/zfs/zfs.ko.zst [zhammer::1706] Srcversion: 92158472E32FE6AEEEC7201 [zhammer::1706] SHA256: 0f6a069f6c3045e7c86507d7c158691d4ace8c6785888579652236fbdf8c66c0 parallel: This job failed: zhammer /test 1000 16k 1 2 … Only when I am explicitly using the zfs-dkms package instead of the build-in kernel module, the correct module is loaded and the bug can’t be triggered any more even after 5 iterations (x10.000 files). Therefore, I can conclude, that the fix itself is working correctly, however the package distributed in the -proposed repository does not include the correct kernel module. However, as this is the way most people are using ZFS on Ubuntu (instead of using the dkms module) this fix also has to be introduced in the current kernel package to fix the problem. -- 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/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Jammy: Fix Committed Status in zfs-linux source package in Lunar: Won't Fix Status in zfs-linux source package in Mantic: Fix Committed Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). * In the absence of the upgrade a cherry-pick will address this particular popular issue alone - without addressing other issues w.r.t. Redbleed / SLS, bugfixes around trim support, and other related improvements that were discovered and fixed around the same time as this popular issue. [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) *
[Kernel-packages] [Bug 2052376] [NEW] Speakers make the sound of sand when audio is played over HDMI in stereo mode
Public bug reported: Since updating the package from 1.2.6.3-1ubuntu1.9 to 1.2.6.3-1ubuntu1.10, when playing audio from a speaker connected over HDMI, using the default stereo audio preset adds the sound of sand to the audio being played. Switching to the 5.1 audio preset fixes the issue. In case it's relevant: My HDMI port is connected to an NVIDIA GPU, which is the dedicated GPU in the laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-ucm-conf 1.2.6.3-1ubuntu1.10 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Feb 4 09:41:15 2024 InstallationDate: Installed on 2022-02-19 (714 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-ucm-conf UpgradeStatus: Upgraded to jammy on 2022-06-05 (608 days ago) ** Affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy regression-update ** Description changed: Since updating the package from 1.2.6.3-1ubuntu1.9 to - 1.2.6.3-1ubuntu1.10, using the default stereo audio preset causes - playback to add the sound of sand to audio played over HDMI. Switching - to the 5.1 audio preset fixes the issue. + 1.2.6.3-1ubuntu1.10, when playing audio from a speaker connected over + HDMI, using the default stereo audio preset adds the sound of sand to + the audio being played. Switching to the 5.1 audio preset fixes the + issue. In case it's relevant: My HDMI port is connected to an NVIDIA GPU, which is the dedicated GPU in the laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-ucm-conf 1.2.6.3-1ubuntu1.10 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Feb 4 09:41:15 2024 InstallationDate: Installed on 2022-02-19 (714 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-ucm-conf UpgradeStatus: Upgraded to jammy on 2022-06-05 (608 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2052376 Title: Speakers make the sound of sand when audio is played over HDMI in stereo mode Status in alsa-ucm-conf package in Ubuntu: New Bug description: Since updating the package from 1.2.6.3-1ubuntu1.9 to 1.2.6.3-1ubuntu1.10, when playing audio from a speaker connected over HDMI, using the default stereo audio preset adds the sound of sand to the audio being played. Switching to the 5.1 audio preset fixes the issue. In case it's relevant: My HDMI port is connected to an NVIDIA GPU, which is the dedicated GPU in the laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-ucm-conf 1.2.6.3-1ubuntu1.10 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Feb 4 09:41:15 2024 InstallationDate: Installed on 2022-02-19 (714 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-ucm-conf UpgradeStatus: Upgraded to jammy on 2022-06-05 (608 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2052376/+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
