[Bug 2066320] Re: gcp: set CONFIG_IDPF=y for Intel Infrastructure Data Path Function Driver
*** This bug is a duplicate of bug 2058052 *** https://bugs.launchpad.net/bugs/2058052 ** This bug has been marked a duplicate of bug 2058052 Enable Intel IDPF support on ARM64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066320 Title: gcp: set CONFIG_IDPF=y for Intel Infrastructure Data Path Function Driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2066320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066320] Re: gcp: set CONFIG_IDPF=y for Intel Infrastructure Data Path Function Driver
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Noble) ** No longer affects: linux (Ubuntu Oracular) ** Changed in: linux-gcp (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu Oracular) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu Noble) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: linux-gcp (Ubuntu Oracular) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: linux-gcp (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Oracular) Status: New => In Progress ** Description changed: - BugLink: https://bugs.launchpad.net/bugs/ + BugLink: https://bugs.launchpad.net/bugs/2066320 [Impact] GCE C3 Metal instance type requires the Intel IDPF driver for networking to function. On the Mantic kernel, this was built into the kernel: # grep IDPF /boot/config-6.5.0-1020-gcp CONFIG_IDPF=y On Noble, this is now been included as a module, in modules-extra: # grep IDPF /boot/config-6.8.0-1007-gcp CONFIG_IDPF=m # dpkg -S /lib/modules/6.8.0-1007-gcp/kernel/drivers/net/ethernet/intel/idpf/idpf.ko.zst linux-modules-extra-6.8.0-1007-gcp: /lib/modules/6.8.0-1007-gcp/kernel/drivers/net/ethernet/intel/idpf/idpf.ko.zst modules-extra is not included in GCP cloud images, and thus, C3 Metal instance types have no networking. They cannot install modules-extra either. [Fix] Set CONFIG_IDPF=y for GCP kernels. Leave -generic as CONFIG_IDPF=m for all architectures. [Testcase] $ grep -Rin "IDPF" /boot/config-$(uname -r) CONFIG_IDPF=y Check /lib/modules/$(uname -r)/kernel/drivers/net/ethernet/intel/idpf/idpf.ko [Where problems could occur] We are building the IDPF driver into the kernel image. This will slightly increase the kernel size by a negligible amount. ** Tags added: noble sts ** Description changed: BugLink: https://bugs.launchpad.net/bugs/2066320 [Impact] GCE C3 Metal instance type requires the Intel IDPF driver for networking to function. On the Mantic kernel, this was built into the kernel: # grep IDPF /boot/config-6.5.0-1020-gcp CONFIG_IDPF=y On Noble, this is now been included as a module, in modules-extra: # grep IDPF /boot/config-6.8.0-1007-gcp CONFIG_IDPF=m # dpkg -S /lib/modules/6.8.0-1007-gcp/kernel/drivers/net/ethernet/intel/idpf/idpf.ko.zst linux-modules-extra-6.8.0-1007-gcp: /lib/modules/6.8.0-1007-gcp/kernel/drivers/net/ethernet/intel/idpf/idpf.ko.zst modules-extra is not included in GCP cloud images, and thus, C3 Metal instance types have no networking. They cannot install modules-extra either. [Fix] Set CONFIG_IDPF=y for GCP kernels. Leave -generic as CONFIG_IDPF=m for all architectures. [Testcase] $ grep -Rin "IDPF" /boot/config-$(uname -r) - CONFIG_IDPF=y + CONFIG_IDPF=m Check /lib/modules/$(uname -r)/kernel/drivers/net/ethernet/intel/idpf/idpf.ko + + A test package is available in the following ppa: + + https://launchpad.net/~mruffell/+archive/ubuntu/sf385823-test + + If you install it, the IDPF driver will be available in the kernel + image, instead of the module being built. + + e.g. + + $ grep -Rin "IDPF" /boot/config-$(uname -r) + CONFIG_IDPF=y [Where problems could occur] We are building the IDPF driver into the kernel image. This will slightly increase the kernel size by a negligible amount. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066320 Title: gcp: set CONFIG_IDPF=y for Intel Infrastructure Data Path Function Driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2066320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066320] [NEW] gcp: set CONFIG_IDPF=y for Intel Infrastructure Data Path Function Driver
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/ [Impact] GCE C3 Metal instance type requires the Intel IDPF driver for networking to function. On the Mantic kernel, this was built into the kernel: # grep IDPF /boot/config-6.5.0-1020-gcp CONFIG_IDPF=y On Noble, this is now been included as a module, in modules-extra: # grep IDPF /boot/config-6.8.0-1007-gcp CONFIG_IDPF=m # dpkg -S /lib/modules/6.8.0-1007-gcp/kernel/drivers/net/ethernet/intel/idpf/idpf.ko.zst linux-modules-extra-6.8.0-1007-gcp: /lib/modules/6.8.0-1007-gcp/kernel/drivers/net/ethernet/intel/idpf/idpf.ko.zst modules-extra is not included in GCP cloud images, and thus, C3 Metal instance types have no networking. They cannot install modules-extra either. [Fix] Set CONFIG_IDPF=y for GCP kernels. Leave -generic as CONFIG_IDPF=m for all architectures. [Testcase] $ grep -Rin "IDPF" /boot/config-$(uname -r) CONFIG_IDPF=y Check /lib/modules/$(uname -r)/kernel/drivers/net/ethernet/intel/idpf/idpf.ko [Where problems could occur] We are building the IDPF driver into the kernel image. This will slightly increase the kernel size by a negligible amount. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066320 Title: gcp: set CONFIG_IDPF=y for Intel Infrastructure Data Path Function Driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2066320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907932] Re: drop rb_safe_level() from ruby-curses to fix irqtop from missing symbols and deprecation warnings
Attached is a debdiff which solves this issue for focal. ** Patch added: "Attached is a debdiff for ruby-curses on focal" https://bugs.launchpad.net/ubuntu/+source/ruby-curses/+bug/1907932/+attachment/5779433/+files/lp1907932_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907932 Title: drop rb_safe_level() from ruby-curses to fix irqtop from missing symbols and deprecation warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-curses/+bug/1907932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907932] Re: drop rb_safe_level() from ruby-curses to fix irqtop from missing symbols and deprecation warnings
Attached is a debdiff for jammy which solves this issue. ** Summary changed: - ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0", affects at least irqtop + drop rb_safe_level() from ruby-curses to fix irqtop from missing symbols and deprecation warnings ** Description changed: - irqtop emits the following warning: - /usr/bin/irqtop:545: warning: rb_safe_level will be removed in Ruby 3.0 - This warning clutters the whole screen and makes irqtop unusable. + [Impact] - My config: - Kernel: 5.4.0-58-lowlatency #64-Ubuntu SMP PREEMPT x86_64 GNU/Linux - irqtop: 2.4-2ubuntu0.2 - ruby: 1:2.7+1 - ruby-curses: 1.2.4-1build1 - ethtool: 1:5.4-1 + rb_safe_level() had been marked for deprecation for some time, and was + finally removed in Ruby 3.0. + + ruby-curses uses rb_safe_level(), and it causes issues with its + rdepends, most notably irqtop. + + irqtop is unusuable on Jammy, with it failing to start due to not + finding the rb_safe_level symbol. + + $ sudo irqtop + :85:in `require': /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/curses.so: undefined symbol: rb_safe_level - /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/curses.so (LoadError) + from :85:in `require' + from /usr/lib/ruby/vendor_ruby/curses.rb:18:in `rescue in ' + from /usr/lib/ruby/vendor_ruby/curses.rb:14:in `' + from :85:in `require' + from :85:in `require' + from /usr/bin/irqtop:9:in `' + + On Focal, irqtop fills the screen with deprecation warnings making the + tool unusable. + + /usr/bin/irqtop:545: warning: rb_safe_level will be removed in Ruby 3.0 + + [Testcase] + + $ sudo apt install irqtop + $ sudo irqtop + + On Jammy: + Check to see if the tool launches, and you no longer get the "undefined symbol: rb_safe_level - /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/curses.so (LoadError)" error. + + on Focal: + Launch the tool, press enter several times to refresh the results. There should be no mention of "/usr/bin/irqtop:545: warning: rb_safe_level will be removed in Ruby 3.0", and the tool should be readable. + + Test packages are available in the following ppa: + + https://launchpad.net/~mruffell/+archive/ubuntu/sf385554-test + + If you install the test packages, irqtop will function normally. + + [Where Problems Could Occur] + + We are removing a long deprecated string safety check, which I assure + you, does not change the security of the tools using the ruby-curses + library, due to most levels being disabled already in ruby itself. + + As for the effect on the programs that depend on ruby-curses, ruby- + curses only has 2 redepends, one of which is irqtop: + + $ apt rdepends ruby-curses + ruby-curses + Reverse Depends: + Depends: irqtop + Depends: ruby-blade + + If a regression were to occur, it would only impact irqtop and ruby- + blade users. Users could downgrade ruby-curses while a fix is developed. + + [Other Info] + + This was fixed in the below commit, in version 1.3.2: + + commit a9b9db9b5d5a4b52e3d0e0eaf0fbb2be839a3c29 + From: Eric Wong + Date: Sat, 30 Nov 2019 01:45:21 + + Subject: drop rb_safe_level check + Link: https://github.com/ruby/curses/commit/a9b9db9b5d5a4b52e3d0e0eaf0fbb2be839a3c29 + + Both Focal and Jammy required a backport. Only window and mouse events + are implemented in 1.2.4, so I removed the hunks that targeted events + that were implemented later. ** Patch added: "Debdiff for ruby-curses on jammy" https://bugs.launchpad.net/ubuntu/+source/ruby-curses/+bug/1907932/+attachment/5779432/+files/lp1907932_jammy.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907932 Title: drop rb_safe_level() from ruby-curses to fix irqtop from missing symbols and deprecation warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-curses/+bug/1907932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907932] Re: ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0", affects at least irqtop
** No longer affects: iptables-netflow (Ubuntu) ** Changed in: ruby-curses (Ubuntu) Status: New => In Progress ** Tags added: focal jammy sts ** Also affects: ruby-curses (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ruby-curses (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ruby-curses (Ubuntu) Status: In Progress => Fix Released ** Changed in: ruby-curses (Ubuntu Focal) Status: New => In Progress ** Changed in: ruby-curses (Ubuntu Jammy) Status: New => In Progress ** Changed in: ruby-curses (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: ruby-curses (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: ruby-curses (Ubuntu Focal) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: ruby-curses (Ubuntu Jammy) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907932 Title: ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0", affects at least irqtop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-curses/+bug/1907932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065456] Re: segfault when importing *.tif as book cover
** Also affects: calibre (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: calibre (Ubuntu Oracular) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065456 Title: segfault when importing *.tif as book cover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/2065456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065265] Re: can not build linux-image-signed.deb
Hi Light_Kernel_Ops, The linux-signed package is signed with Canonical's Secure Boot Signing Key, making the kernel bootable on systems that have secure boot enabled. This key is not public for obvious reasons, and only particular Kernel team members have access to it. Where do you want to publish your kernel? Is it for regular users, does it contain a particular fix you are needing, or is it for a specific IOT hardware device? If you have your own fleet of company laptops for example, you can enroll your own secure boot key into their MOKs, and sign the built kernel with that. Let me know what you are trying to achieve, and I will see if I can help. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065265 Title: can not build linux-image-signed.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
Hi Theodore, Ubuntu carries a little delta ontop of debian, and requires a merge, so I think it is best to wait a week for the final e2fsprogs release before we perform the merge. https://merges.ubuntu.com/e/e2fsprogs/REPORT Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065047] Re: df -h reports resource unavailable for CIFS mounts
*** This bug is a duplicate of bug 2060780 *** https://bugs.launchpad.net/bugs/2060780 Hi JB2Cool, Yes, you are correct. You are seeing the exact same as bug 2060780, that was introduced between 5.15.0-101 and 5.15.0-102 and fixed in 5.15.0-105. For AWS, the fix is in: $ git log --grep "smb3: Replace smb2pdu 1-element arrays with flex-arrays" Ubuntu-aws-5.15.0-1* commit 9f1d43ea8e5f7e49485eb2e3288524af2fb5a5d5 Author: Kees Cook Date: Fri Feb 17 16:24:40 2023 -0800 smb3: Replace smb2pdu 1-element arrays with flex-arrays ... $ git describe --contains 9f1d43ea8e5f7e49485eb2e3288524af2fb5a5d5 Ubuntu-aws-5.15.0-1060.66~247 Please upgrade to 5.15.0-1060-aws or later. Thanks, Matthew ** This bug has been marked a duplicate of bug 2060780 CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065047 Title: df -h reports resource unavailable for CIFS mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-5.15/+bug/2065047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064291] Re: Ubuntu 24.04 crashed multiple times
Hi Bernard, These are userspace application crashes. Try and wait for a kernel crash to occur. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064291 Title: Ubuntu 24.04 crashed multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064291] Re: Ubuntu 24.04 crashed multiple times
Hi Bernard, The crash seems to bring your system down before the logs are able to be written to disk, so there is no oops present in your dmesg. Its pretty common. Would you be able to capture a kernel crashdump (kdump). Follow the instructions in: https://ubuntu.com/server/docs/kernel-crash-dump All you really need to do is: $ sudo apt install linux-crashdump Say yes twice. Then reboot. Attempt to open app center or something to cause the crash. When the system crashes, it will take a minute or so, as it copies the system memory to a file. When the system comes back, see if there is a crashdump in /var/crash/ If there is, see if there is a dmesg.log in that folder. If there is, upload that file. You don't have to upload the whole kdump. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064291 Title: Ubuntu 24.04 crashed multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064999] [NEW] Prevent soft lockups during IOMMU streaming DMA mapping by limiting nvme max_hw_sectors_kb to cache optimised size
slow to a halt
and soft or hardlockups occur, waiting for iova_rbtree_lock.
A test kernel is available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf374805-test
If you install the kernel and leave it running, the soft lockups will no
longer occur.
[Where problems could occur]
We are changing the value of max_hw_sectors_kb for NVMe devices, for
systems with IOMMU enabled. For those without IOMMU or IOMMU disabled,
it will remain the same as it is now.
The value is the minimum between the maximum supported by hardware, and
the largest that fits into cache. For some workloads, this might have a
small impact on performance, due to the need to split up larger IOVA
allocations into multiple smaller ones, but there should be a larger net
gain due to IOVA allocations now fitting into the cache, and completing
much faster than a single large one.
If a regression were to occur, users could disable the IOMMU as a
workaround.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: jammy sts
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: jammy sts
** Description changed:
- BugLink: https://bugs.launchpad.net/bugs/
+ BugLink: https://bugs.launchpad.net/bugs/2064999
[Impact]
On systems with IOMMU enabled, every streaming DMA mapping involves an IOVA
to be allocated and freed. For small mappings, IOVA sizes are normally cached,
so IOVA allocations complete in a reasonable time. For larger mappings, things
can be significantly slower to the point where softlockups occur due to lock
contention
on iova_rbtree_lock.
- commit 9257b4a206fc ("iommu/iova: introduce per-cpu caching to iova
allocation")
+ commit 9257b4a206fc ("iommu/iova: introduce per-cpu caching to iova
allocation")
introduced a scalable IOVA cache mechanism, that helps increase performance up
- to 128kb mappings.
+ to 128kb mappings.
On systems that do larger streaming DMA mappings, e.g. a NVMe device
with:
/sys/block/nvme0n1/queue/max_hw_sectors_kb
2048
The 2048kb mapping takes significantly longer, causing lock contention on the
iova_rbtree_lock, as other resources such as ethernet NICs are also trying to
acquire the lock.
We hit the following soft lockup:
watchdog: BUG: soft lockup - CPU#60 stuck for 24s!
CPU: 60 PID: 608304 Comm: segment-merger- Tainted: PW EL
5.15.0-76-generic #83~20.04.1-Ubuntu
RIP: 0010:_raw_spin_unlock_irqrestore+0x25/0x30
Call Trace:
-
- fq_flush_timeout+0x82/0xc0
- ? fq_ring_free+0x170/0x170
- call_timer_fn+0x2e/0x120
- run_timer_softirq+0x433/0x4c0
- ? lapic_next_event+0x21/0x30
- ? clockevents_program_event+0xab/0x130
- __do_softirq+0xdd/0x2ee
- irq_exit_rcu+0x7d/0xa0
- sysvec_apic_timer_interrupt+0x80/0x90
-
-
- asm_sysvec_apic_timer_interrupt+0x1b/0x20
+
+ fq_flush_timeout+0x82/0xc0
+ ? fq_ring_free+0x170/0x170
+ call_timer_fn+0x2e/0x120
+ run_timer_softirq+0x433/0x4c0
+ ? lapic_next_event+0x21/0x30
+ ? clockevents_program_event+0xab/0x130
+ __do_softirq+0xdd/0x2ee
+ irq_exit_rcu+0x7d/0xa0
+ sysvec_apic_timer_interrupt+0x80/0x90
+
+
+ asm_sysvec_apic_timer_interrupt+0x1b/0x20
RIP: 0010:_raw_spin_unlock_irqrestore+0x25/0x30
...
- alloc_iova+0x1d8/0x1f0
- alloc_iova_fast+0x5c/0x3a0
- iommu_dma_alloc_iova.isra.0+0x128/0x170
- ? __kmalloc+0x1ab/0x4b0
- iommu_dma_map_sg+0x1a4/0x4c0
- __dma_map_sg_attrs+0x72/0x80
- dma_map_sg_attrs+0xe/0x20
- nvme_map_data+0xde/0x800 [nvme]
- ? recalibrate_cpu_khz+0x10/0x10
- ? ktime_get+0x46/0xc0
- nvme_queue_rq+0xaf/0x1f0 [nvme]
- ? __update_load_avg_se+0x2a2/0x2c0
- __blk_mq_try_issue_directly+0x15b/0x200
- blk_mq_request_issue_directly+0x51/0xa0
- blk_mq_try_issue_list_directly+0x7f/0xf0
- blk_mq_sched_insert_requests+0xa4/0xf0
- blk_mq_flush_plug_list+0x103/0x1c0
- blk_flush_plug_list+0xe3/0x110
- blk_mq_submit_bio+0x29d/0x600
- __submit_bio+0x1e5/0x220
- ? ext4_inode_block_valid+0x9f/0xc0
- submit_bio_noacct+0xac/0x2c0
- ? xa_load+0x61/0xa0
- submit_bio+0x50/0x140
- ext4_mpage_readpages+0x6a2/0xe20
- ? __mod_lruvec_page_state+0x6b/0xb0
- ext4_readahead+0x37/0x40
- read_pages+0x95/0x280
- page_cache_ra_unbounded+0x161/0x220
- do_page_cache_ra+0x3d/0x50
- ondemand_readahead+0x137/0x330
- page_cache_async_ra+0xa6/0xd0
- filemap_get_pages+0x224/0x660
- ? filemap_get_pages+0x9e/0x660
- filemap_read+0xbe/0x410
- generic_file_read_iter+0xe5/0x150
- ext4_file_read_iter+0x5b/0x1
[Bug 2064827] Re: [5.19.0-1030-lowlatency] BUG: kernel NULL pointer dereference, address: 00000000000006b1
Hi Sophi, The 5.19 HWE kernel for Jammy is no longer supported. Its support period was for the lifetime of the 22.10 Kinetic Kudu release, which is now end of life. Can you upgrade to a supported kernel, e.g. the latest 5.15 Jammy kernel or the current 6.5 HWE kernel, and retry? Is there any reason you are using the -lowlatency variant? $ sudo apt install linux-lowlatency-hwe-22.04 $ sudo reboot $ uname -rv 6.5.0-28-lowlatency #29.1~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 17:17:55 UTC or $ sudo apt install linux-generic-hwe-22.04 for the -generic variant. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064827 Title: [5.19.0-1030-lowlatency] BUG: kernel NULL pointer dereference, address: 06b1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: cifs: Copying file to same directory results in page fault
Hi everyone, Thank you for testing, and its great to hear that it fixes the issue. The Jammy HWE kernel is still queued up to be built, it should be built over the next few days. You can keep an eye on it at https://kernel.ubuntu.com/reports/kernel-stable-board/ Regardless, we should be on track to release s2024.04.01 on the week of 13th May, so around two weeks time, as per https://kernel.ubuntu.com/. I will write back once the kernel has been released, in about two weeks. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: cifs: Copying file to same directory results in page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064291] Re: Ubuntu 24.04 crashed multiple times
Hi Bernard, Can you have a look at your /var/log/kern.log and /var/log/syslog files, and look for what is known as a kernel oops? It looks like some of the examples in this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919 Would you be able to copy and paste any you find into a text file and upload to the bug? I will have a look. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064291 Title: Ubuntu 24.04 crashed multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: cifs: Copying file to same directory results in page fault
Hi everyone, The kernel team has built the patch into the s2024.04.1 SRU cycle, as 6.5.0-35-generic. An ETA for this is the week of 13th of May, as per https://kernel.ubuntu.com/ Would anyone be able to help test the kernel by installing 6.5.0-35-generic from -proposed and doing a cifs mount and copying files? Currently only the Mantic kernel is built. The HWE kernel for Jammy hasn't been built yet, but I will write back once it is available. The kernel is currently in the kernel team's proposed2 ppa, instead of the usual -proposed pocket, but you can have a look here: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed2 Instructions to install (On a mantic system): 1) sudo add-apt-repository ppa:canonical-kernel-team/proposed2 2) sudo apt update 3) sudo apt install linux-image-6.5.0-35-generic linux-modules-6.5.0-35-generic linux-modules-extra-6.5.0-35-generic linux-headers-6.5.0-35-generic 4) sudo rm /etc/apt/sources.list.d/canonical-kernel-team-ubuntu-proposed2-mantic.sources 5) sudo apt update 6) sudo reboot 7) uname -rv 6.5.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 26 11:23:57 UTC 2024 Let me know if this kernel fixes the issue for you, and if it does, I'll mark the bug as verified. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: cifs: Copying file to same directory results in page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
Hi Krister, Thanks for the heads up about 1.47.1 upstream, it does indeed look like a release is coming soon. It seems Debian unstable already has 1.7.1-rc1: https://packages.debian.org/sid/e2fsprogs When the Ubuntu archive opens for OO, we will merge 1.47.1~rc1-1 from debian unstable, and then submit the patches for SRU to noble, mantic, jammy and focal. Should be a few days. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
Attached is a V2 patch for Noble for e2fsprogs. ** Patch added: "Debdiff for e2fsprogs on noble V2" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5772258/+files/lp2036467_noble_V2.debdiff ** Patch removed: "Debdiff for e2fsprogs on noble" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5738302/+files/lp2036467_noble.debdiff ** Patch removed: "Debdiff for e2fsprogs on lunar" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707894/+files/lp2036467_lunar.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: cifs: Copying file to same directory results in page fault
Hi everyone, Thanks for helping to test the test kernel, and I am glad that it fixes the issue. I have written a SRU template and have set it as the description of the bug. I have submitted the revert to the Kernel team mailing list for SRU: Cover Letter: https://lists.ubuntu.com/archives/kernel-team/2024-April/150433.html Patch: https://lists.ubuntu.com/archives/kernel-team/2024-April/150434.html I'll go and have a talk to the kernel team now. This is a regression, yes, but I am not sure if they will be interested in respinning the 2024.04.01 SRU cycle to include the fix, due to it being quite late in the cycle. https://kernel.ubuntu.com/ We just did an emergency respin last week to fix bug 2060780, which was another cifs regression for the 5.15 series, with an unrelated cause. I'll write back with what the kernel team say, and hopefully give you an estimated time of release. If its this SRU cycle, or the next. Thanks, Matthew PS: Peter, I tried Debian 12.5 and I still can't reproduce the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: cifs: Copying file to same directory results in page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: cifs: Copying file to same directory results in page fault
** Summary changed: - Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). + cifs: Copying file to same directory results in page fault ** Description changed: - Remote filesystems mounted as CIFS are not working after update to - Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after updating - to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64). + BugLink: https://bugs.launchpad.net/bugs/2060919 - The remote filesystem is correctly mounted and seems to work but trying - to write data to the filesystem ends in a kernel error exception. After - that error the CIFS filesystem just became unusable. + [Impact] - Previous Kernel version works correctly. + Copying or modifying a file to the same directory within a cifs mount + results in a page fault, and the process that initiated the copy being + killed. This could be cp, nautilus, etc. - = - Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64) - = - # lsb_release -rd - No LSB modules are available. - Description: Ubuntu 23.10 - Release: 23.10 + This results in the following oops: - # uname -a - Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux + BUG: unable to handle page fault for address: fffe + #PF: supervisor read access in kernel mode + #PF: error_code(0x) - not-present page + PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 + Oops: [#1] PREEMPT SMP NOPTI + CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu + RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] + Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 + RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 + RAX: RBX: fffe RCX: + RDX: RSI: RDI: + RBP: aab6865ffc28 R08: 0001 R09: + R10: 00023854 R11: R12: + R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 + FS: 7bd4d594b6c0() GS:90753f80() knlGS: + CS: 0010 DS: ES: CR0: 80050033 + CR2: fffe CR3: 00017022a000 CR4: 00750ef0 + PKRU: 5554 + Call Trace: + + ? show_regs+0x6d/0x80 + ? __die+0x24/0x80 + ? page_fault_oops+0x99/0x1b0 + ? kernelmode_fixup_or_oops+0xb2/0x140 + ? __bad_area_nosemaphore+0x1a5/0x2c0 + ? bad_area_nosemaphore+0x16/0x30 + ? do_kern_addr_fault+0x7b/0xa0 + ? exc_page_fault+0x1a4/0x1b0 + ? asm_exc_page_fault+0x27/0x30 + ? cifs_flush_folio+0x41/0xf0 [cifs] + ? cifs_flush_folio+0x37/0xf0 [cifs] + cifs_remap_file_range+0x172/0x660 [cifs] + do_clone_file_range+0x101/0x2d0 + vfs_clone_file_range+0x3f/0x150 + ioctl_file_clone+0x52/0xc0 + do_vfs_ioctl+0x68f/0x910 + ? __fget_light+0xa5/0x120 + __x64_sys_ioctl+0x7d/0xf0 + do_syscall_64+0x59/0x90 + ? kmem_cache_free+0x22/0x3e0 + ? putname+0x5b/0x80 + ? exit_to_user_mode_prepare+0x30/0xb0 + ? syscall_exit_to_user_mode+0x37/0x60 + ? do_syscall_64+0x68/0x90 + ? do_syscall_64+0x68/0x90 + ? do_syscall_64+0x68/0x90 - # cat /proc/version_signature - Ubuntu 6.5.0-27.28-generic 6.5.13 + There is no known workaround. - - How to reproduce the problem - - For instance, I'm using KeePassXC (https://launchpad.net/ubuntu/+source/keepassxc) to update a database located at CIFS filesystem. Any change done to that database causes this Kernel error exception: + [Fix] - abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: fffe - abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode - abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page - abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 - abr 11 09:34:59 fpgmsi kernel: Oops: [#1] PREEMPT SMP NOPTI - abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu - abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022 - abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] - abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 - abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 - abr 11 09:34:59 fpgmsi kernel: RAX:
[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Hi Axel, Sorry about you getting spammed about all these verifications. The robot that posts these messages looks for the Launchpad bug number in the package changelogs, and just makes a post for every package it sees it in. You might not know, but Ubuntu has slightly over 100 kernels these days, across all series releases. These are split in the primary kernels, like -generic, and then all the derivatives like -aws, -azure, -gcp, -fips, -virtual, and so on, and then including the HWE kernels and their derivatives too. This got fixed in all the 5.15 kernels, so the robot goes crazy and spams those "please verify" comments for all the derivatives. We usually just verify the -generic kernel only, unless it has greater impact to one of those derivatives. There's no further action needed on your part. The fix won't be removed for not verifying a derivative you have never heard of. Hope that clears it up a bit. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
** No longer affects: linux-raspi (Ubuntu) ** No longer affects: linux-hwe-6.5 (Ubuntu) ** No longer affects: linux-azure (Ubuntu) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: Jose Ogando Justo (joseogando) => (unassigned) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
** Changed in: linux (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
Hi everyone, As promised, I uploaded test kernels to the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2060919-test They are based on 6.5.0-27-generic to keep it simple. It just has "cifs: fix flushing folio regression for 6.1 backport". Thats it. Pretty small patch: commit 9dc02a5b7540d18a69bcbaf8f4fa428e32075b4b (HEAD -> lp2060919-test) Author: Matthew Ruffell Date: Fri Apr 19 17:25:48 2024 +1200 Revert "cifs: fix flushing folio regression for 6.1 backport" This reverts commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1. diff --git a/fs/smb/client/cifsfs.c b/fs/smb/client/cifsfs.c index 55a6d0296ec8..82313b253463 100644 --- a/fs/smb/client/cifsfs.c +++ b/fs/smb/client/cifsfs.c @@ -1245,7 +1245,7 @@ static int cifs_flush_folio(struct inode *inode, loff_t pos, loff_t *_fstart, lo int rc = 0; folio = filemap_get_folio(inode->i_mapping, index); - if (!folio) + if (IS_ERR(folio)) return 0; size = folio_size(folio); They are going to take about three hours to build, so check back later on. It's close to my EOD, and I can't watch these builds complete. Please note this package is NOT SUPPORTED by Canonical, and is for TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment. Instructions to Install (On a jammy or mantic system): 1) sudo add-apt-repository ppa:mruffell/lp2060919-test 2) sudo apt update 3) sudo apt install linux-image-unsigned-6.5.0-27-generic linux-modules-6.5.0-27-generic linux-modules-extra-6.5.0-27-generic linux-headers-6.5.0-27-generic 4) sudo reboot 5) uname -rv 6.5.0-27.28+TEST2060919v20240419b1 or 6.5.0-27.28~22.04.1+TEST2060919v20240419b1 Make sure the +TEST2060919v20240419b1 is present. Can you let me know if it solves the problem? Additionally, if you could help me create a reproducer that would help immensely. Remember, they still need to build, check the ppa link to make sure it built successfully and is published before installing. About 3 hours from now. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
Hello, I can't actually reproduce the issue, I seem to be missing something. 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 //192.168.122.185/sambashare ~/share Password for ubuntu@//192.168.122.185/sambashare: $ mount -l ... //192.168.122.185/sambashare on /home/ubuntu/share type cifs (rw,relatime,vers=3.1.1,cache=strict,username=ubuntu,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.122.185,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1) $ ls hallo.txt hello.txt sample.txt sample2.txt $ sudo cp hello.txt hello.txt.1 $ ll total 2097176 drwxr-xr-x 2 root root0 Apr 19 04:46 ./ drwxr-x--- 5 ubuntu ubuntu 4096 Apr 19 03:57 ../ -rwxr-xr-x 1 root root 1960 Apr 19 03:55 hallo.txt* -rwxr-xr-x 1 root root 1960 Apr 19 04:04 hello.txt* -rwxr-xr-x 1 root root 1960 Apr 19 04:46 hello.txt.1* -rwxr-xr-x 1 root root 1073741824 Apr 19 04:01 sample.txt* -rwxr-xr-x 1 root root 1073741824 Apr 19 04:04 sample2.txt* No oops in dmesg. I'm not sure what I'm doing wrong. Maybe you can help. Anyway, I had a look at the stack trace, and it seems to be related to the regression reported here: https://lore.kernel.org/linux- mm/a76b370f93cb928c049b94e1fde0d2da506dfcb2.ca...@amazon.com/T/ But I think its slightly different in the Ubuntu 6.5 kernel. The thread mentions that: commit 7b2404a886f8b91250c31855d287e632123e1746 Author: David Howells Date: Fri Dec 1 00:22:00 2023 + Subject: cifs: Fix flushing, invalidation and file size with copy_file_range() Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b2404a886f8b91250c31855d287e632123e1746 introduced the issue to Debian's 6.1 kernel. This got backported to Ubuntu in: commit 3adbe2ccd8b9b8fde93e03958d6176945794d288 Author: David Howells Date: Fri Dec 1 00:22:00 2023 + Subject: cifs: Fix flushing, invalidation and file size with copy_file_range() $ git describe --contains 3adbe2ccd8b9b8fde93e03958d6176945794d288 Ubuntu-6.5.0-20.20~107 Which we have been using for some time now. Reading the regression mailing list thread, they mention that things work differently in 6.1: > Yeah. __filemap_get_folio() works differently in v6.1.y. There it returns a > folio or NULL. In 6.7 it returns a folio or a negative error code. The error > check in cifs_flush_folio() needs to change to something like: > > folio = filemap_get_folio(inode->i_mapping, index); > if (!folio) > return -ENOMEM; > > David okay... so 6.1 is different from 6.5. Since we were okay with the patch, we probably didn't need to add anything further. But they fixed 6.1 with: commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1 Author: Steve French Date: Fri Jan 12 23:08:51 2024 -0600 Subject: cifs: fix flushing folio regression for 6.1 backport Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/mantic/commit/?id=21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1 Now, Ubuntu kernels in between upstream stable releases get patches from current upstream stable and long term upstream stable trees. We got both 6.1.x and 6.7.x patches recently... so we pulled in this fix, and it landed in: $ git describe --contains 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1 Ubuntu-6.5.0-27.28~162 Wow, what a coincidence. I think this patch is probably not needed in 6.5, and causes the issue. How about I build you a test kernel with "cifs: fix flushing folio regression for 6.1 backport" reverted, and then we see if it fixes things? If it does, I will send a revert to the kernel team. If it doesn't then I will have another look. I'll write back once a test kernel is ready. I'll build you both Jammy HWE and Mantic kernels. If you can help me make a reproducer, that would be great. I can test myself then. Thanks, Matthew ** Tags added: seg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Hi everyone, 5.15.0-105-generic has been released to -updates now. It fixes the cifs issue. https://launchpad.net/ubuntu/+source/linux/5.15.0-105.115 Please let us know if you find any more issues. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] Re: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
Performing verification for Focal. I started two VMs, one Jammy, which is the nfs server, and one Focal, which is the client. I used the instructions in the testcase sections of this bug, and also bug 2049262. The Focal VM has nfs-common 1:1.3.4-2.5ubuntu3.6 from -updates. Let's try the testcase for this bug, covering the regression. $ sudo mount -t nfs4 -o vers=4.2 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:12:50 2024 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:13:23 2024 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -t nfs4 -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:13:30 2024 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -t nfs4 -o vers=4,minorversion=2 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:13:36 2024 mount.nfs4: trying text-based options 'minorversion=2,vers=4.2,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -t nfs4 -o vers=4,minorversion=1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:13:41 2024 mount.nfs4: trying text-based options 'minorversion=1,vers=4.2,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -t nfs4 -o vers=4,minorversion=0 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:13:47 2024 mount.nfs4: trying text-based options 'minorversion=0,vers=4.2,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt This behaviour is wrong, as even when we specify the minorversion as .1 or .0, we always get .2, no matter what. We can reproduce the issue. I then enabled -proposed, and installed nfs-common 1:1.3.4-2.5ubuntu3.7. Let's retry the testcase. $ sudo mount -t nfs4 -o vers=4.2 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:17:28 2024 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:17:35 2024 mount.nfs4: trying text-based options 'vers=4.1,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -t nfs4 -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:17:40 2024 mount.nfs4: trying text-based options 'vers=4.0,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -t nfs4 -o vers=4,minorversion=2 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:17:48 2024 mount.nfs4: trying text-based options 'vers=4,vers=4.2,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -t nfs4 -o vers=4,minorversion=1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:17:54 2024 mount.nfs4: trying text-based options 'vers=4,vers=4.1,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -t nfs4 -o vers=4,minorversion=0 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Fri Apr 19 03:18:01 2024 mount.nfs4: trying text-based options 'vers=4,vers=4.0,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt This looks much better. When we specify both '-t nfs4' and '-o vers=4.x' we get the version we asked for. The version in -proposed fixes the issue. Again, I will run through the original testcase for bug, 2049262: $ sudo cat /proc/fs/nfsd/versions -2 +3 +4 +4.1 +4.2 $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Fri Apr 19 03:22:14 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -o vers=4.2 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Fri Apr 19 03:22:22 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Fri Apr 19 03:22:28 2024 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Fri Apr 19 03:22:34 2024 mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt Looks OK. $ sudo cat /proc/fs/nfsd/versions -2 +3 +4 -4.0 +4.1 +4.2 $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Fri Apr 19 03:24:31 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.109,clientaddr=192.168.122.161' $ sudo umount /mnt $ sudo mount -o vers=4.2 -vvv
[Bug 2062113] Re: CIFS SMB does not work on linux-image-5.15.0-102-generic
*** This bug is a duplicate of bug 2060780 *** https://bugs.launchpad.net/bugs/2060780 ** This bug has been marked a duplicate of bug 2060780 CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062113 Title: CIFS SMB does not work on linux-image-5.15.0-102-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Performing verification for Jammy. I started two Jammy VMs. One is a server and the other a client. Server -- $ sudo apt update $ sudo apt upgrade $ sudo apt install samba $ sudo vim /etc/samba/smb.conf [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 //192.168.122.172/sambashare ~/share The client is using 5.15.0-102-generic from updates: $ uname -rv 5.15.0-102-generic #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024 $ sudo -s # while true; do echo "$(date) hallo" >> ./share/hallo.txt; sleep 1 ; done Launch a separate terminal and run: $ df -h ~/share df: /home/ubuntu/share: Resource temporarily unavailable The issue is seen. I then enabled -proposed and installed 5.15.0-105-generic. I had to use the -proposed2 repository due to the packages not being present in the primary archive -proposed repository. https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed2 $ uname -rv 5.15.0-105-generic #115-Ubuntu SMP Mon Apr 15 09:52:04 UTC 2024 $ sudo -s # while true; do echo "$(date) hallo" >> ./share/hallo.txt; sleep 1 ; done $ df -h ~/share FilesystemSize Used Avail Use% Mounted on //192.168.122.247/sambashare 9.6G 2.1G 7.5G 23% /home/ubuntu/share CIFS is back to working again, and we can df the share and see the disk usage. The respun kernel in -proposed fixes the issue, happy to mark verified for Jammy. ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Hi everyone, the fix will also be available for Focal, as part of it getting the Jammy HWE kernel. It will be released at the same time as Jammy's kernel is released. We got the notification above that the kernel should be in -proposed, but I have been refreshing -proposed all day and the kernel is still not copied in just yet. Once it reaches -proposed, I will test it, and let you know when you can do some testing too. But for the moment, we need to be patient while it gets copied into -proposed. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
The new kernel is tagged as 5.15.0-105-generic, and it is a respin of 5.15.0-103-generic with the fix. https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/log/?h=Ubuntu-5.15.0-105.115 It should be available in -proposed soon, the Kernel Team are still rebuilding all the 5.15 derivatives. I'll write back once it is in -proposed for testing. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061248] Re: kernel 5.15.0-102 - CIFS mount problem (NAS)
*** This bug is a duplicate of bug 2060780 *** https://bugs.launchpad.net/bugs/2060780 Come over to bug 2060780 and talk about it with us there. ** This bug has been marked a duplicate of bug 2060780 CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061248 Title: kernel 5.15.0-102 - CIFS mount problem (NAS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Hi everyone, 5.15.0-104-generic just hit jammy-proposed a couple minutes ago. It isn't available for focal users yet. Can someone please test 5.15.0-104-generic on jammy and let me know if it fixes the issue? Thanks. Instructions to Install (On a mantic system): 1) cat << EOF | sudo tee /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed main universe EOF 2) sudo apt update 3) sudo apt install linux-image-5.15.0-104-generic linux-modules-5.15.0-104-generic linux-modules-extra-5.15.0-104-generic linux-headers-5.15.0-104-generic 4) sudo rm /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list 5) sudo apt update 6) sudo reboot 5.15.0-104-generic #114-Ubuntu SMP Thu Mar 28 15:39:51 UTC 2024 Just a note that 5.15.0-104-generic is a part of the 2024.04.01 SRU cycle, and will likely be released at the end of month, as per https://kernel.ubuntu.com/, and won't be coming out any sooner. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] Re: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
Thanks for pointing out the missing patch Heitor. I was indeed missing it. Please review and sponsor the V2 debdiff. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059197 Title: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] Re: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
Sanity testing the test package: https://launchpad.net/~mruffell/+archive/ubuntu/lp2059197-test nfs-common 1:1.3.4-2.5ubuntu3.6+lp2059197v20240411b1 Testcase for this bug, i.e. the regression. $ sudo mount -t nfs4 -o vers=4.2 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:14:52 2024 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:10:26 2024 mount.nfs4: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo mount -t nfs4 -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:15:02 2024 mount.nfs4: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo mount -t nfs4 -o vers=4,minorversion=2 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:15:48 2024 mount.nfs4: trying text-based options 'vers=4,vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo mount -t nfs4 -o vers=4,minorversion=1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:13:33 2024 mount.nfs4: trying text-based options 'vers=4,vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo mount -t nfs4 -o vers=4,minorversion=0 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:15:54 2024 mount.nfs4: trying text-based options 'vers=4,vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' Looks OK. Testcase for the original bug, 2049262: $ sudo cat /proc/fs/nfsd/versions -2 +3 +4 +4.1 +4.2 $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:17:55 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.2 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:18:01 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:18:05 2024 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:18:12 2024 mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' Looks OK. $ sudo cat /proc/fs/nfsd/versions -2 +3 +4 -4.0 +4.1 +4.2 $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:20:40 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.2 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:20:47 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:20:53 2024 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:21:02 2024 mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported Looks OK. $ sudo cat /proc/fs/nfsd/versions -2 +3 +4 -4.0 +4.1 -4.2 $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:22:32 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.2 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:22:38 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported $ sudo umount /mnt umount: /mnt: not mounted. $ sudo mount -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:22:44 2024 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:22:49 2024 mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported Looks OK. $ sudo cat /proc/fs/nfsd/versions -2 +3 +4 -4.1 -4.2 $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:23:46 2024 mount.nfs: trying text-based options
[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Hi everyone, Reading: https://lore.kernel.org/lkml/2024020616.454699-1-kova...@altlinux.org/T/ It seems the issue was introduced in commit 33eae65c6f49770fec7a662935d4eb4a6406d24b Author: Paulo Alcantara Date: Wed Dec 13 12:25:57 2023 -0300 Subject: smb: client: fix OOB in SMB2_query_info_init() Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=33eae65c6f49770fec7a662935d4eb4a6406d24b this was indeed landed in 5.15.0-102-generic: $ git log --grep "smb: client: fix OOB in SMB2_query_info_init()" origin/master-next commit ed30eac9715d0bd5512ee42ca8e8f340d2d9d2d5 ... $ git describe --contains ed30eac9715d0bd5512ee42ca8e8f340d2d9d2d5 Ubuntu-5.15.0-102.112~472 The link mentions it is supposedly fixed in: commit b5d623611c9cda84ebb5e5bd044587955eaf782f Author: Kees Cook Date: Fri Feb 17 16:24:40 2023 -0800 Subject: smb3: Replace smb2pdu 1-element arrays with flex-arrays Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b5d623611c9cda84ebb5e5bd044587955eaf782f Looking at the Jammy kernel tree: $ git log --grep "smb3: Replace smb2pdu 1-element arrays with flex-arrays" origin/master-next commit b5d623611c9cda84ebb5e5bd044587955eaf782f $ git describe --contains b5d623611c9cda84ebb5e5bd044587955eaf782f Ubuntu-5.15.0-104.114~23 It seems it is already applied and tagged in 5.15.0-104-generic. This seems to be built, but not quite in -proposed yet: https://kernel.ubuntu.com/reports/kernel-stable-board/ I will write back as soon as 5.15.0-104-generic is in -proposed, with instructions on how to test it, and see if it fixes the issue. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Tags added: seg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060797] Re: df says Resource temporarily unavailable after kernel upgrade to 5.15.0-102
*** This bug is a duplicate of bug 2060780 *** https://bugs.launchpad.net/bugs/2060780 Hi everyone, I will provide updates on the other bug 2060780. ** This bug has been marked a duplicate of bug 2060780 CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060797 Title: df says Resource temporarily unavailable after kernel upgrade to 5.15.0-102 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2060797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] Re: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
Attached is a new debdiff which includes the missing patch. I did another look upstream, but I think we are okay now. ** Patch added: "Debdiff for nfs-utils on Focal V2" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+attachment/5763564/+files/lp2059197_focal_V2.debdiff ** Changed in: nfs-utils (Ubuntu Focal) Status: Incomplete => In Progress ** Description changed: [Impact] When specifying both '-t nfs4' and '-o vers=4.x' on the mount command line, mount.nfs ignores any specific version set with '-o vers=4.x' or '-o vers=4,minorversion=x', and simply attempts version negotiation, which due to my recent changes in bug 2049262, would land on the highest supported nfs version, likely 4.2. Users who specify what version they want should get the version they ask for, and thus, this is a regression introduced in 1:1.3.4-2.5ubuntu3.6. A workaround is to drop '-t nfs4' and to use mount.nfs directly instead, i.e.: $ sudo mount.nfs -o vers=4.1 -vvv jammy-nfs-server:/ /mnt [Testcase] Create two VMs, one jammy and one focal. The jammy VM will be the server. Server VM: $ sudo hostnamectl set-hostname jammy-nfs-server $ sudo apt update && sudo apt upgrade -y $ sudo apt install nfs-kernel-server $ sudo mkdir /export $ sudo mkdir /export/users $ sudo mkdir /home/users $ sudo vi /etc/fstab # add the following line: /home/users /export/users none bind 0 0 $ sudo mount -a $ sudo vi /etc/exports # add the following lines: /export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync) /export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync) $ sudo systemctl restart nfs-server.service Focal VM: $ sudo hostnamectl set-hostname focal-nfs-client $ sudo apt update && sudo apt upgrade -y $ sudo apt install nfs-common And then try mounting with both '-t nfs4' and '-o vers=4.1': $ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Wed Apr 3 00:51:23 2024 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.217,clientaddr=192.168.122.9' and then try with both '-t nfs4' and '-o vers=4,minorversion=1': $ sudo mount -t nfs4 -o vers=4,minorversion=1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Wed Apr 3 02:19:03 2024 mount.nfs4: trying text-based options 'minorversion=1,vers=4.2,addr=192.168.122.217,clientaddr=192.168.122.9' In each of those mounts, it incorrectly uses protocol version 4.2, instead of requested 4.1. If you install the test packages in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2059197-test then vers should always be 4.1, instead of 4.2. [Where problems can occur] It is quite clear now that changing version negotiation and parsing is quite problematic, after the number of regressions the previous 1:1.3.4-2.5ubuntu3.6 caused the community, and the sheer number of commits upstream took to resolve lingering issues. We need to be careful, to make sure we don't introduce any further regressions. This time, we are only changing how mount.nfs parses and processes command line arguments for version specification, and not changing version negotiation itself. This could impact NFS clients, when they go to mount NFS filesystems. If a regression were to occur, then users might have to manually mount their NFS filesystems or look into autofs. There should be no breaking changes to any behaviour when mounting NFS filesystems. There are no changes to nfs server. [Other Info] This was fixed multiple times, across the following three commits: commit 1e3ca7fe199531a372bb8e1c1033d8973097be50 Author: NeilBrown Date: Wed Jul 26 13:47:42 2017 -0400 Subject: mount: move handling of "-t nfs4" into nfs_nfs_version() Link: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=1e3ca7fe199531a372bb8e1c1033d8973097be50 - + commit 050153ef6a86ff5ab06ef65be36336824a323779 Author: NeilBrown Date: Wed Jul 26 13:51:51 2017 -0400 Subject: mount: Fix problems with parsing minorversion= Link: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=050153ef6a86ff5ab06ef65be36336824a323779 - + commit 71b807e1a69940beb31fdeb481c2e54509e8bd32 Author: Steve Dickson Date: Thu Mar 1 13:52:47 2018 -0500 Subject: mount.nfs: minorversion setting is being ignored with the -t flag Link: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=71b807e1a69940beb31fdeb481c2e54509e8bd32 + commit 5f32083c759b468f5b0cb9302e4fe2848d37cc5b + From: Steve Dickson + Date: Tue, 10 Apr 2018 10:25:40 -0400 + Subject: mount.nfs: Fix auto protocol negotiation + Link: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=5f32083c759b468f5b0cb9302e4fe2848d37cc5b + Jammy has all of these, and does not need any fixes. -- You received this bug notification
[Bug 2059197] Re: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
** Patch removed: "Debdiff for nfs-utils on Focal" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+attachment/5761398/+files/lp2059197_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059197 Title: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
Hi R. Diez, The 6.5.0-27-generic kernel just got released, so it should make its way to an archive mirror near you in the next couple of hours, and should solve your SMB 1 issue. The 6.8 kernel should be good to go when you get it in the next couple of months. Let us know if you encounter any more SMB 1 issues in the future. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] Re: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
Hi Jeff, Again, I apologise for introducing this regression, but we are on our way to getting this fixed. The fixes are: commit 1e3ca7fe199531a372bb8e1c1033d8973097be50 Author: NeilBrown Date: Wed Jul 26 13:47:42 2017 -0400 Subject: mount: move handling of "-t nfs4" into nfs_nfs_version() Link: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=1e3ca7fe199531a372bb8e1c1033d8973097be50 commit 050153ef6a86ff5ab06ef65be36336824a323779 Author: NeilBrown Date: Wed Jul 26 13:51:51 2017 -0400 Subject: mount: Fix problems with parsing minorversion= Link: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=050153ef6a86ff5ab06ef65be36336824a323779 commit 71b807e1a69940beb31fdeb481c2e54509e8bd32 Author: Steve Dickson Date: Thu Mar 1 13:52:47 2018 -0500 Subject: mount.nfs: minorversion setting is being ignored with the -t flag Link: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=71b807e1a69940beb31fdeb481c2e54509e8bd32 I have built these into a test package, if you are interested in taking a look. Please note this package is NOT SUPPORTED by Canonical, and is for TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment. Instructions to install (On a Focal system): 1) sudo add-apt-repository ppa:mruffell/lp2059197-test 2) sudo apt update 3) sudo apt install nfs-common 4) sudo apt-cache policy nfs-common | grep Installed Installed: 1:1.3.4-2.5ubuntu3.6+lp2059197v20240403b1 If you try mount your share with the version specified, it should work. I'll write back once we have a package in -proposed with the fix. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059197 Title: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] Re: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
Attached is a debdiff for Focal which fixes this issue. ** Summary changed: - Issue with nfs4.0 mounts after upgrade to 3.6 + Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together ** Summary changed: - Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together + mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together ** Description changed: - Hello, + [Impact] - On Ubuntu Server 20.04.6 LTS with the update of nfs-common package => - "nfs-common/focal-updates 1:1.3.4-2.5ubuntu3.5" to "nfs-common/focal- - updates 1:1.3.4-2.5ubuntu3.6" I started having issues mounting ntf4.0 - volumes. The NFS server supports 4.0, 4.1 and 4.2 + When specifying both '-t nfs4' and '-o vers=4.x' on the mount command + line, mount.nfs ignores any specific version set with '-o vers=4.x' or + '-o vers=4,minorversion=x', and simply attempts version negotiation, + which due to my recent changes in bug 2049262, would land on the highest + supported nfs version, likely 4.2. - The issue appears when using '-t ntfs4' and setting the version using -o - vers=. + Users who specify what version they want should get the version they ask + for, and thus, this is a regression introduced in 1:1.3.4-2.5ubuntu3.6. - When using 1:1.3.4-2.5ubuntu3.5 I am able to use '-o vers' to set the version when using -t ntfs4 eg - mount -t nfs4 -o vers=4.0 -vvv SERVER.local:/srv/data /mnt/test - mount.nfs4: trying text-based options 'vers=4.0,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' + A workaround is to drop '-t nfs4' and to use mount.nfs directly instead, + i.e.: - mount -t nfs4 -o vers=4.1 -vvv SERVER.local:/srv/data /mnt/test - mount.nfs4: trying text-based options 'vers=4.1,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' + $ sudo mount.nfs -o vers=4.1 -vvv jammy-nfs-server:/ /mnt - However after upgrading to 1:1.3.4-2.5ubuntu3.6 it always mounts as nfs4.2 - mount -t nfs4 -o vers=4.0 -vvv SERVER.local:/srv/data /mnt/test - mount.nfs4: trying text-based options 'vers=4.2,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' + [Testcase] - mount -t nfs4 -o vers=4.1 -vvv SERVER.local:/srv/data /mnt/test - mount.nfs4: trying text-based options 'vers=4.2,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' + Create two VMs, one jammy and one focal. - I would have expected the specified version in -o vers to be used when - using '-t nfs4' + The jammy VM will be the server. - When using '-t nfs' I am able to mount volumes as nfs 4.0. I understand - that 1:1.3.4-2.5ubuntu3.6 fixes version negotiation so maybe this isn't - a bug and the intent with '-t nfs4' is to always use the highest - version. If so please feel free to close the report + Server VM: + $ sudo hostnamectl set-hostname jammy-nfs-server + $ sudo apt update && sudo apt upgrade -y + $ sudo apt install nfs-kernel-server + $ sudo mkdir /export + $ sudo mkdir /export/users + $ sudo mkdir /home/users + $ sudo vi /etc/fstab # add the following line: + /home/users /export/users none bind 0 0 + $ sudo mount -a + $ sudo vi /etc/exports # add the following lines: + /export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync) + /export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync) + $ sudo systemctl restart nfs-server.service + + Focal VM: + $ sudo hostnamectl set-hostname focal-nfs-client + $ sudo apt update && sudo apt upgrade -y + $ sudo apt install nfs-common + + And then try mounting with both '-t nfs4' and '-o vers=4.1': + + $ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt + mount.nfs4: timeout set for Wed Apr 3 00:51:23 2024 + mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.217,clientaddr=192.168.122.9' + + and then try with both '-t nfs4' and '-o vers=4,minorversion=1': + + $ sudo mount -t nfs4 -o vers=4,minorversion=1 -vvv jammy-nfs-server:/ /mnt + mount.nfs4: timeout set for Wed Apr 3 02:19:03 2024 + mount.nfs4: trying text-based options 'minorversion=1,vers=4.2,addr=192.168.122.217,clientaddr=192.168.122.9' + + In each of those mounts, it incorrectly uses protocol version 4.2, + instead of requested 4.1. + + If you install the test packages in the following ppa: + + https://launchpad.net/~mruffell/+archive/ubuntu/lp2059197-test + + then vers should always be 4.1, instead of 4.2. + + [Where problems can occur] + + It is quite clear now that changing version negotiation and parsing is + quite problematic, after the number of regressions the previous + 1:1.3.4-2.5ubuntu3.6 caused the community, and the sheer number of + commits upstream took to resolve lingering issues. + + We need to be careful, to make sure we don't introduce any further + regressions. + + This time, we are only changing how mount.nfs parses and processes + command line arguments for version specification, and not changing + version negotiation itself. This could impact NFS clients, when they go + to mount NFS filesystems. + + If a regression were to occur, then users
[Bug 2059197] Re: Issue with nfs4.0 mounts after upgrade to 3.6
Hi Jeff, I believe this is a valid bug. I can reproduce it: On Focal: $ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Wed Apr 3 00:51:23 2024 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.217,clientaddr=192.168.122.9' On Jammy: $ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Wed Apr 3 00:57:08 2024 mount.nfs4: trying text-based options 'vers=4.1,addr=192.168.122.217,clientaddr=192.168.122.213' I apologise for introducing this particular regression when I changed the version negotiation. Let me try and find a fix and build a test package. In the meantime, you can use a workaround of dropping "-t nfs4" and changing "mount" to "mount.nfs", i.e.: $ sudo mount.nfs -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Wed Apr 3 00:51:59 2024 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.217,clientaddr=192.168.122.9' I will write back shortly. Thanks, Matthew ** Also affects: nfs-utils (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: nfs-utils (Ubuntu) Status: New => Fix Released ** Changed in: nfs-utils (Ubuntu Focal) Status: New => In Progress ** Changed in: nfs-utils (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: nfs-utils (Ubuntu Focal) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059197 Title: Issue with nfs4.0 mounts after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949723] Re: systemd-resolved segfault in hashmap_iterate_entry
** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) Importance: Low => Medium ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949723 Title: systemd-resolved segfault in hashmap_iterate_entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
Thank you for the help sorting autopkgtests Mauricio. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2033892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
Performing verification for Jammy I set up two Jammy VMs, one a nfs-server and the other an autofs/nfs- client. The client is using coreutils 8.32-4.1ubuntu1.1 from -updates. $ apt-cache policy coreutils | grep Installed Installed: 8.32-4.1ubuntu1.1 I set up the nfs server and autofs mounts as the Testcase indicates. $ ls -l ls: cannot access 'export-missing': No such file or directory total 4 drwxr-xr-x 3 root root 4096 Mar 20 22:16 export d? ? ?? ?? export-missing $ mount -l | grep mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=692,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=21588) 192.168.122.65:/export on /mnt2/export type nfs (rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.122.65,mountvers=3,mountport=47718,mountproto=udp,local_lock=none,addr=192.168.122.65) The mounts were previously unmounted, but when I issue 'ls -l', the mounts occur, which is not wanted, and we error out on the non-existant export-missing mount. I then enabled -proposed, and installed coreutils 8.32-4.1ubuntu1.2. $ apt-cache policy coreutils | grep Installed Installed: 8.32-4.1ubuntu1.2 From there, lets try the 'ls -l': $ ls -l total 0 drwxr-xr-x 2 root root 0 Mar 20 22:25 export drwxr-xr-x 2 root root 0 Mar 20 22:25 export-missing $ mount -l | grep mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=648,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=16856) This time the mounts do not occur, we just get a listing of the possible autofs mounts. We can confirm with 'mount -l' that nothing was actually actioned. The package in -proposed fixes the issues. Happy to mark verified for Jammy. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2033892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054218] Re: kvm: Running perf against qemu processes results in page fault inside guest
Performing verification for mantic.
I deployed mantic onto a bare metal server, with kernel 6.5.0-26-generic from
-updates.
I installed a KVM stack, synced a cloud image, and tested VM creation.
$ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy
arch=amd64
$ uvt-kvm ssh jammy-a
Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-101-generic x86_64)
From there, I found the PID of the VM:
$ ps aux | grep qemu
libvirt+1799 107 1.5 9642380 1044752 ? Sl 03:21 0:38
/usr/bin/qemu-system-x86_64 -name guest=jammy-a,debug-threads=on -S -object
{"qom-ty
We run perf:
$ sudo perf top -p 1799
$ virsh console jammy-a
Connected to domain 'jammy-a'
Escape character is ^] (Ctrl + ])
[ 161.413890] BUG: unable to handle page fault for address: fe18cdb1c028
[ 161.419474] #PF: supervisor read access in kernel mode
[ 161.423707] #PF: error_code(0x) - not-present page
[ 161.427949] PGD 17ffca0[ 161.429508] BUG: unable to handle page fault for
address: fe18cdb1c028
[ 161.429513] #PF: supervisor read access in kernel mode
[ 161.429516] #PF: error_code(0x) - n
The VM suffers a page fault and crashes, and is not accessible over ssh.
$ uvt-kvm ssh jammy-a
(no response).
I then enabled -proposed, and installed 6.5.0-27-generic:
$ uname -rv
6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024
$ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy
arch=amd64
$ uvt-kvm ssh jammy-a
Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-101-generic x86_64)
We get the pid of the VM:
$ ps aux | grep qemu
libvirt+1786 42.5 1.5 7960876 1022308 ? Sl 03:37 0:40
/usr/bin/qemu-system-x86_64 -name guest=jammy-a,debug-threads=on -S -object
{"qom-ty
We run perf:
$ sudo perf top -p 1786
This time, the VM does not crash, and stays running:
$ virsh console jammy-a
Connected to domain 'jammy-a'
Escape character is ^] (Ctrl + ])
jammy-a login:
jammy-a login:
We can also ssh to the VM just fine:
$ uvt-kvm ssh jammy-a
Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-101-generic x86_64)
This is much better. The kernel in -proposed fixes the issue, happy to
mark verified for mantic.
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054218
Title:
kvm: Running perf against qemu processes results in page fault inside
guest
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054218/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044420] Re: gtkpod segfaults when attempting to display songs
gtkpod has been removed from debian, and thus removed from noble, so no need to fix there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044420 Title: gtkpod segfaults when attempting to display songs To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2044420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044420] Re: gtkpod segfaults when attempting to display songs
Attached is a debdiff for mantic which fixes this issue. ** Patch added: "Debdiff for gtkpod on mantic" https://bugs.launchpad.net/ubuntu/+source/gtkpod/+bug/2044420/+attachment/5757356/+files/lp2044420_mantic.debdiff ** Changed in: glib2.0 (Ubuntu Noble) Status: Triaged => Fix Released ** No longer affects: gtkpod (Ubuntu Noble) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044420 Title: gtkpod segfaults when attempting to display songs To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2044420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056143] Re: block/loop: No longer allows to create partitions
Performing verification for Jammy. I started a fresh VM, with 5.15.0-101-generic from updates. I ran the following reproducer: $ fallocate -l 1G /tmp/blob $ LOOPDEV=$(sudo losetup --find --show /tmp/blob) $ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100% Error: Partition(s) 1 on /dev/loop4 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. I then enabled -proposed, and installed 5.15.0-102-generic: $ uname -rv 5.15.0-102-generic #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024 Running the reproducer: $ fallocate -l 1G /tmp/blob $ LOOPDEV=$(sudo losetup --find --show /tmp/blob) $ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100% $ losetup -a /dev/loop4: []: (/tmp/blob) $ ll /dev ... brw-rw 1 root disk 7, 4 Mar 19 03:45 loop4 brw-rw 1 root disk259, 0 Mar 19 03:45 loop4p1 ... Things are now working as intended. The kernel in -proposed solves the issue. Happy to mark verified for Jammy. ** Tags removed: verification-needed-jammy-linux ** Tags added: sts verification-done-jammy-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056143 Title: block/loop: No longer allows to create partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
The fix for noble should be present in 6.8.0-16-generic and later. Marking as Fix committed for Noble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
Performing verification for mantic. I started two VMs. A jammy VM for the cifs server, and a mantic VM, for the client. I set the jammy VM up as per the testcase. I set the mantic VM up as per the testcase. The mantic VM uses kernel 6.5.0-25-generic from -updates. $ uname -rv 6.5.0-25-generic #25-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 7 14:58:39 UTC 2024 I created the testdata, took the SHA256 hash, and copied it over: $ ( 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 $ cp testdata.txt share/ On the jammy VM, I confirmed the hash has changed: $ sha256sum sambashare/testdata.txt 9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866 sambashare/testdata.txt $ less sambashare/testdata.txt Looking at the file with less, I see the large blocks of zeros. I then enabled -proposed, and installed 6.5.0-27-generic: $ uname -rv 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 I mounted the share: $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 //192.168.122.65/sambashare ~/share Password for ubuntu@//192.168.122.65/sambashare: Looking in dmesg, I see: [ 57.280020] Key type cifs.spnego registered [ 57.280035] Key type cifs.idmap registered [ 57.280345] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers [ 57.280861] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers [ 57.281307] CIFS: VFS: wsize rounded down to 16384 to multiple of PAGE_SIZE 4096 [ 57.281599] CIFS: Attempting to mount //192.168.122.65/sambashare the line of interest is "CIFS: VFS: wsize rounded down to 16384 to multiple of PAGE_SIZE 4096" showing we now have a wsize of 16384, and we can see this with mount -l: $ mount -l //192.168.122.65/sambashare on /home/ubuntu/share type cifs (rw,relatime,vers=1.0,cache=strict,username=ubuntu,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.122.65,soft,unix,posixpaths,serverino,mapposix,acl,rsize=1048576,wsize=16384,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1) I then copied the file over: $ cp testdata.txt share/ Looking at the SHA256 sum on the Jammy server: $ sha256sum sambashare/testdata.txt 9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2 sambashare/testdata.txt When looking at the file with less, there are no more binary zeros. The kernel in -proposed fixes the issue, happy to mark verified for mantic. ** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056549] Re: Problems with nfs-common after upgrade to 3.6
Hi Rainer. I think we will leave it as is. Keep using v4.0 for now, and you should be fine. I'll close the bug. Andreas, I will remove regression-update if that is okay with you. Thanks, Matthew ** Changed in: nfs-utils (Ubuntu Focal) Status: New => Invalid ** Changed in: nfs-utils (Ubuntu) Status: New => Invalid ** Tags removed: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056549 Title: Problems with nfs-common after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056549] Re: Problems with nfs-common after upgrade to 3.6
Hi Rainer, Thanks for trying that out, and it is great to hear that v4.0 works for you, and you added it to your /etc/fstab as a good workaround for the meantime. Are you interested in debugging why your system hangs when trying v4.2 and v4.1? or do you want to leave it there? 4.0 will keep working for you with 1:1.3.4-2.5ubuntu3.6. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056549 Title: Problems with nfs-common after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056743] Re: Keyboard stops working after suspend on Dell XPS 13
I think the fix was included in 5.15.149 upstream; https://lwn.net/Articles/963359/ Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID The kernel team have just pulled in 5.15.148, and haven't started on 149. They will likely get to it in the next week or so. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056743 Title: Keyboard stops working after suspend on Dell XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056549] Re: Problems with nfs-common after upgrade to 3.6
Hi Rainer, Thanks for the screenshots. The updated package changes how the '-o vers=4' parameter works. The old / wrong behaviour would always use nfs v4.0 no matter what. All other nfs-common versions apart from the version in focal would try v4.2, then if that didn't work, then v4.1, and then v4.0, and then eventually v3.0, in a laddering fashion. You can see in your second screenshot that: $ mount -vvv -o vers=4 /srv/www/nextcloud/data ...,vers=4.2,... See, it now tries v4.2 by default? I guess your QNAP appliance is not replying to v4.2 version negotiation correctly. It is suppose to ladder down to 4.1 and then 4.0, but maybe the QNAP server doesn't reply correctly and nfs-common just waits. Can you try each specific version and report back? $ mount -vvv -o vers=4.2 /srv/www/nextcloud/data // this should hang? $ mount -vvv -o vers=4.1 /srv/www/nextcloud/data // unknown. $ mount -vvv -o vers=4.0 /srv/www/nextcloud/data // this should work As a workaround in the meantime, you can edit your /etc/fstab to set nfsvers=4.0, and you should be restored to what it was before. Just add a ".0" to the end of "nfsvers=4". Do you happen to have access to the QNAP appliance to configure NFS versions? Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056549 Title: Problems with nfs-common after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056549] Re: Problems with nfs-common after upgrade to 3.6
Hi Rainer, I developed the nfs-utils update of 1:1.3.4-2.5ubuntu3.6, and I am very interested to hear more about the possible regression. The intention was to fix version negotiation when using the '-t nfs4' or '-o vers=4' parameters in your mount command. You can find more about it here: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2049262 Since you are affected, you must be using '-t nfs4' or '-o vers=4'. Can you please let us know the /etc/fstab entry for this mount point? Could you also do a mount manually with -vvv appended to the mount command line? $ mount -vvv /my_nfs_path/ e.g. $ sudo mount -o vers=4 -vvv nfs-server:/ /mnt I would really like to see the verbose output. Please include it in your comment. What version NFS are you using? It must be 4.x, since the changes only affect 4.x negotiation. Let me know these details and I will investigate asap. Thanks, Matthew ** Also affects: nfs-utils (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056549 Title: Problems with nfs-common after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly
Yes, 6.5.0-25-generic is available for both jammy and mantic systems. It was released earlier this week. Is anyone able to try it out and let me know if it fixes the issue? Thanks. ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053041 Title: Issue when shutting down computer: internal hard drive is not shut down properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056297] Re: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04
*** This bug is a duplicate of bug 2046844 *** https://bugs.launchpad.net/bugs/2046844 Hi cipricus, This is a security feature working as intended. Ubuntu recently decided to disable unprivileged access to user namespaces. You can find more information it about it here: https://ubuntu.com/blog/ubuntu-23-10-restricted-unprivileged-user-namespaces https://discourse.ubuntu.com/t/spec-unprivileged-user-namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626 https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844 It was included (but turned off in 23.10). In 24.04, it has been turned on. We have been adding apparmor profiles for most packaged applications. Saying that, firefox downloaded from tarballs or other places don't come with an apparmor profile, so the mitigation isn't relaxed for them. You can enable user namespaces by either making a apparmor profile for your firefox installs, making sure the directory where firefox is installed is correct in the profile, or by just enabling user namespaces for your system. There is instructions to do this in the first blog link. Thanks, Matthew ** This bug has been marked a duplicate of bug 2046844 AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056297 Title: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055147] Re: Kernel upgrade to 6.5.0-21-generic fails to boot
Hi Sly, We do actually test as many dkms builds as we can. Well, mainly all the kernel modules present in the Ubuntu archive, like evdi-dkms. The trouble starts when you get dkms sources from other places that we don't know about, like the DisplayLink installer that I linked above. You, me, and other users just install it, and forget all about it, until something breaks. The real solution is to get rid of as many out of tree kernel modules as we can. In the case of evdi, a few people have tried, and failed, to get it into the mainline kernel. Upstream aren't interested in tidying it up for inclusion, so it just rots out of tree. Anyway, I am glad that it works for you now. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055147 Title: Kernel upgrade to 6.5.0-21-generic fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055147] Re: Kernel upgrade to 6.5.0-21-generic fails to boot
Hi Sly, Your evdi kernel module for DisplayLink docks failed to compile. It likely couldn't generate your initramfs, leaving your 6.5.0-21-generic not able to boot. Your logs say its trying to build version 1.11.0: ERROR (dkms apport): binary package for evdi: 1.11.0 not found Error! Bad return status for module build on kernel: 6.5.0-21-generic (x86_64) Consult /var/lib/dkms/evdi/1.11.0/build/make.log for more information. This is a bit old and outdated. You can re-install the DisplayLink drivers from the upstream source, that has a newer version of evdi: https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu That will probably remove the old evdi and install a newer one. Alternatively, you can remove the old evdi dkms entry and install evdi- dkms from the Ubuntu repositories which has a evdi compatible with 6.5.0-21-generic. DisplayLink support is kinda bad on Ubuntu, but its what we must do to have working displays with our docks. Thanks, Matthew ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055147 Title: Kernel upgrade to 6.5.0-21-generic fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly
Hi everyone, @angros47, yes, this issue looks to be what you are experiencing here. https://bugs.archlinux.org/task/80064 mentions that the issue was introduced in: commit aa3998dbeb3abce63653b7f6d4542e7dcd022590 Author: Damien Le Moal Date: Sat Aug 26 09:43:39 2023 +0900 Subject: ata: libata-scsi: Disable scsi device manage_system_start_stop Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa3998dbeb3abce63653b7f6d4542e7dcd022590 This was first included in... 6.5.0-17-generic. The bug mentions the fix is: commit 24eca2dce0f8d19db808c972b0281298d0bafe99 Author: Damien Le Moal Date: Wed Oct 25 15:46:12 2023 +0900 Subject: scsi: sd: Introduce manage_shutdown device flag Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=24eca2dce0f8d19db808c972b0281298d0bafe99 This is currently queued up for 6.5.0-25-generic, which is currently in -proposed for mantic, and is currently being built for jammy. If you are on mantic / 23.10, please try the -proposed kernel: Instructions to Install (On a mantic system): 1) cat << EOF | sudo tee /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed main universe EOF 2) sudo apt update 3) sudo apt install linux-image-6.5.0-25-generic linux-modules-6.5.0-25-generic linux-modules-extra-6.5.0-25-generic linux-headers-6.5.0-25-generic 4) sudo rm /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list 5) sudo apt update 6) sudo reboot 7) uname -rv 6.5.0-25-generic #25-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 7 14:58:39 UTC 2024 For jammy / 22.04 users, I have built 6.5.0-21-generic with the fix ontop of it, for anyone who wants to try it and report back that it actually fixes the issue. Please note this package is NOT SUPPORTED by Canonical, and is for TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment. Instructions to Install (On a jammy system): 1) sudo add-apt-repository ppa:mruffell/lp2053041-test 2) sudo apt update 3) sudo apt install linux-image-unsigned-6.5.0-21-generic linux-modules-6.5.0-21-generic linux-modules-extra-6.5.0-21-generic linux-headers-6.5.0-21-generic 4) sudo reboot 5) uname -rv 6.5.0-21-generic #21~22.04.1+TEST2053041v20240226b1-Ubuntu SMP PREEMPT_DYNAMIC Mo If asked to abort removing the running kernel, say no. You can also wait, and I'll write back when 6.5.0-25-generic enters -proposed for Jammy, will be a day or two. If the patch works, then the kernel SRU cycle will complete in the first week of March, as per https://kernel.ubuntu.com/, so you don't have too much longer to wait until 6.5.0-25-generic becomes available. Thanks, Matthew ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053041 Title: Issue when shutting down computer: internal hard drive is not shut down properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
Reviews from Senior Kernel Team Members: ACK 1 https://lists.ubuntu.com/archives/kernel-team/2024-February/149051.html ACK 2 https://lists.ubuntu.com/archives/kernel-team/2024-February/149061.html Applied https://lists.ubuntu.com/archives/kernel-team/2024-February/149119.html Will let you know when this gets tagged to a kernel release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049262] Re: mount.nfs: fix version negotiation laddering with parameters '-t nfs4' or '-o vers=4'
Performing verification for Focal. I set up a Jammy VM to be the nfs server, using the instructions in the SRU template. $ sudo cat /proc/fs/nfsd/versions -2 -3 +4 -4.0 +4.1 +4.2 4.0 is not allowed, but 4.1 and 4.2 are. I then started a fresh Focal VM, and installed nfs-common 1.3.4-2.5ubuntu3.5 from -updates. I then tried to mount the NFS share: $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Mon Feb 26 01:21:35 2024 mount.nfs: trying text-based options 'vers=4,addr=192.168.122.17,clientaddr=192.168.122.19' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported as the bug report describes, when we specify -o vers=4 on the mount command line, it only tries 4.0 and no other version. I then enabled -proposed and installed nfs-common 1.3.4-2.5ubuntu3.6. Trying the mount again: $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Mon Feb 26 01:27:47 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.17,clientaddr=192.168.122.19' $ ll /mnt total 12 drwxr-xr-x 3 root root 4096 Feb 26 01:10 ./ drwxr-xr-x 19 root root 4096 Feb 26 01:13 ../ drwxr-xr-x 2 root root 4096 Feb 26 01:10 users/ This time it correctly tries version 4.2, and since 4.2 is allowed, the mount succeeds. To test the laddering, I went to the nfs-server and then edited /etc/nfs.conf and changed: vers4.2=n and restarted nfs-server.service. Back on the Focal VM, we now see: $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Mon Feb 26 01:30:40 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.17,clientaddr=192.168.122.19' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.17,clientaddr=192.168.122.19' $ ll /mnt total 12 drwxr-xr-x 3 root root 4096 Feb 26 01:10 ./ drwxr-xr-x 19 root root 4096 Feb 26 01:13 ../ drwxr-xr-x 2 root root 4096 Feb 26 01:10 users/ The laddering works, and we try version 4.2, then 4.1 which succeeds. Lets also turn off 4.1 on the server, and enable 4.0: vers4.0=y vers4.1=n now on the client, we see: $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Mon Feb 26 01:32:53 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.17,clientaddr=192.168.122.19' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.17,clientaddr=192.168.122.19' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.17,clientaddr=192.168.122.19' $ ll /mnt total 12 drwxr-xr-x 3 root root 4096 Feb 26 01:10 ./ drwxr-xr-x 19 root root 4096 Feb 26 01:13 ../ drwxr-xr-x 2 root root 4096 Feb 26 01:10 users/ We laddered all the way down to 4.0 and connected, since we just allowed it. This works great. The package in -proposed fixes the issue. Happy to mark verified for Focal. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049262 Title: mount.nfs: fix version negotiation laddering with parameters '-t nfs4' or '-o vers=4' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2049262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Performing verification for Bionic. Bionic seems to hibernate okay on both Xen and KVM based instances, so I tested both t2.medium and c5.large instance types. Each had 20gb of storage, with advanced > enable encryption > yes. I also made sure to enable Advanced settings > Stop State (Hibernation) Support > Enabled. I started two sets of instances, one with 1.0.0-0ubuntu4~18.04.5 from -updates, and the other with 1.0.0-0ubuntu4~18.04.6 from -proposed. After leaving each instance for a few minutes to finish setting up hibinit-agent.service, I pressed Instance State > Hibernate. Both instances hibernated successfully, and within 30 seconds of pressing the hibernate button. I then started both instances, and ssh'd in. My screen sessions were both active, so hibernation was successful. The base case of no additional swapfile configured results in correct hibernation for both -updates and -proposed packages. I then followed the below steps, and added an additional swapfile to each instance. $ sudo fallocate -l 4G /swapfile $ sudo dd if=/dev/zero of=/swapfile bs=1024 count=4194304 $ sudo chmod 600 /swapfile $ sudo mkswap /swapfile $ sudo swapon /swapfile $ echo "/swapfile swap swap defaults 0 0" | sudo tee -a /etc/fstab $ swapon --show NAME TYPE SIZE USED PRIO /swapfile file 4G 0B -2 I went back to the console and pressed Instance State > Hibernate. This time, both instances hibernated successfully, and completed within 30 seconds of pressing the hibernate button. Bionic has a different behaviour to that of Focal and onward, where the -updates package would stay running, and be force stopped 20 minutes later. On Bionic, both hibernate successfully. I then started both instances. Both instances came up correctly, and I could ssh in. But my screen sessions were missing, and journalctl showed this was a fresh boot for both instances. It seems Bionic has issues resuming from hibernation when there is an additional swapfile set, but most users do not notice it, because the instance comes up and starts correctly, as if hibernation had been successful. Journalctl in both suggests that it wasn't aware that it was hibernated in the first place as no attempt to resume was made, so perhaps we are setting the resume= variable on the kernel command line wrong. I checked, and Bionic sets it as: resume_offset=401408 resume=PARTUUID=80f6dacd-01 I checked the offsets manually with $ findmnt -no PARTUUID -T /swap-hibinit 80f6dacd-01 $ sudo filefrag -v /swap-hibinit Filesystem type is: ef53 File size of /swap-hibinit is 4194304000 (1024000 blocks of 4096 bytes) ext: logical_offset:physical_offset: length: expected: flags: 0:0.. 0: 401408..401408: 1: everything matched. Very strange. It should have resumed... Regardless of the outcome, I checked journalctl of the previous boot, and for the instance with -updates enabled, we see: Jun 03 05:04:02 ip-172-31-26-1 systemd-logind[1108]: Suspend key pressed. Jun 03 05:04:02 ip-172-31-26-1 systemd-logind[1108]: Requested operation not supported, ignoring. Jun 03 05:04:02 ip-172-31-26-1 kernel: Adding 4095996k swap on /swap-hibinit. Priority:-3 extents:5 across:43827 Jun 03 05:04:02 ip-172-31-26-1 systemd[1]: Reached target Sleep. Jun 03 05:04:02 ip-172-31-26-1 systemd[1]: Starting Hibernate... Jun 03 05:04:02 ip-172-31-26-1 kernel: PM: Image not found (code -16) Jun 03 05:04:02 ip-172-31-26-1 systemd-sleep[3321]: Suspending system... Jun 03 05:04:02 ip-172-31-26-1 kernel: PM: hibernation entry /swap-hibinit is still enabled at priority -3, so this specific launchpad bug still exists on Bionic, and the /swap file will be selected for hibernation instead, due to it having a priority of -2. On the instance with -proposed enabled: Jun 03 05:04:02 ip-172-31-25-176 systemd-logind[3432]: Suspend key pressed. Jun 03 05:04:02 ip-172-31-25-176 systemd-logind[3432]: Requested operation not supported, ignoring. Jun 03 05:04:02 ip-172-31-25-176 kernel: Adding 4095996k swap on /swap-hibinit. Priority:32767 extents:5 across: Jun 03 05:04:02 ip-172-31-25-176 systemd[1]: Reached target Sleep. Jun 03 05:04:02 ip-172-31-25-176 systemd[1]: Starting Hibernate... Jun 03 05:04:02 ip-172-31-25-176 kernel: PM: Image not found (code -16) Jun 03 05:04:02 ip-172-31-25-176 systemd-sleep[4314]: Suspending system... Jun 03 05:04:02 ip-172-31-25-176 kernel: PM: hibernation entry /swap-hibinit is added with priority 32767, and will be selected over /swapfile, since it beats -2. The changes in this SRU are still beneficial and needed, and worth the regression risk even though there is no behavioural change to the user with the package in -proposed versus the package in -updates. It also keeps the code in ec2-hibinit-agent in sync with focal and onward regards to changes. I think we should look into the hibernation issue with Bionic in a separate bug, and track it there, and keep this bug about making sure /swap-hibinit is enabled with
[Bug 1976125] Re: The webcam image displayed has problems
*** This bug is a duplicate of bug 1967843 *** https://bugs.launchpad.net/bugs/1967843 This is probably fixed in clutter-gst-3.0 3.0.27-2ubuntu1 that we released a couple days ago. Run "sudo apt update" and "sudo apt upgrade" and it will pull in the fixed package. Marking as a duplicate of bug 1967843 for the moment. ** This bug has been marked a duplicate of bug 1967843 cheese display corrupted under Ubuntu 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976125 Title: The webcam image displayed has problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975811] Re: cheese image gray with werical strips
*** This bug is a duplicate of bug 1967843 *** https://bugs.launchpad.net/bugs/1967843 This is probably fixed in clutter-gst-3.0 3.0.27-2ubuntu1 that we released a couple days ago. Run "sudo apt update" and "sudo apt upgrade" and it will pull in the fixed package. Marking as a duplicate of bug 1967843 for the moment. ** This bug has been marked a duplicate of bug 1967843 cheese display corrupted under Ubuntu 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975811 Title: cheese image gray with werical strips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Performing verification for Jammy. For some reason hibernation just refused to work on any Xen based instance type, but it works fine on KVM based instances, such as c5, t3 etc. This is being looked into on bug 1968062, but I think it affects Jammy as well. Diverging from the testcase, and using c5.large (kvm) instances instead of t2.medium (xen). I started a c5.large instance with 20gb of storage, with advanced > enable encryption > yes. I also made sure to enable Advanced settings > Stop State (Hibernation) Support > Enabled. I waited for hibinit-agent.service to complete by watching $ sudo systemctl status hibinit-agent.service This is using the current version of ec2-hibinit-agent from -updates: $ apt-cache policy ec2-hibinit-agent | grep Installed Installed: 1.0.0-0ubuntu11 I went to the EC2 console and pressed Instance State > Hibernate. The instance stopped within 30 seconds, and hibernation was successful. I started the instance again. From there, I made a swapfile, and enabled it: $ sudo fallocate -l 4G /swapfile $ sudo dd if=/dev/zero of=/swapfile bs=1024 count=4194304 $ sudo chmod 600 /swapfile $ sudo mkswap /swapfile $ sudo swapon /swapfile $ echo "/swapfile swap swap defaults 0 0" | sudo tee -a /etc/fstab $ swapon --show NAME TYPE SIZE USED PRIO /swapfile file 4G 0B -2 I went back to the console and pressed Instance State > Hibernate. The follow was written to journalctl: May 26 05:06:22 ip-172-31-45-200 systemd-logind[519]: Suspend key pressed. May 26 05:06:22 ip-172-31-45-200 systemd-logind[519]: Requested suspend operation not supported, ignoring. May 26 05:06:22 ip-172-31-45-200 kernel: Adding 4095996k swap on /swap-hibinit. Priority:-3 extents:5 across:4505596k SSFS May 26 05:06:22 ip-172-31-45-200 root[2917]: ACPI action undefined: LNXSLPBN:00 The instance did not hibernate, and stayed running for 20 minutes, until it timed out and was force stopped. We can see from the logs that /swap-hibinit was added at priority -3, and /swapfile is -2. /swapfile was chosen for hibernation, but as since kernel command line and grub is not set up for this, it fails. I terminated the instance. I then created a new instance, again a c5.large, with 20gb of storage, with Advanced > Enable Encryption > yes. I also made sure to enable Advanced settings > Stop State (Hibernation) Support > Enabled. I waited for hibinit-agent.service to complete by watching $ sudo systemctl status hibinit-agent.service I enabled -proposed, and installed ec2-hibinit-agent 1.0.0-0ubuntu11.22.04.1 Setting up ec2-hibinit-agent (1.0.0-0ubuntu11.22.04.1) ... Installing new version of config file /etc/acpi/actions/sleep.sh ... $ apt-cache policy ec2-hibinit-agent | grep Installed Installed: 1.0.0-0ubuntu11.22.04.1 I went to the EC2 console and pressed Instance State > Hibernate. Again, the instance stopped within 30 seconds, and hibernation was successful. I started the instance again, and configured a second swapfile: From there, I made a swapfile, and enabled it: $ sudo fallocate -l 4G /swapfile $ sudo dd if=/dev/zero of=/swapfile bs=1024 count=4194304 4194304+0 records in 4194304+0 records out 4294967296 bytes (4.3 GB, 4.0 GiB) copied, 31.7073 s, 135 MB/s $ sudo chmod 600 /swapfile $ sudo mkswap /swapfile Setting up swapspace version 1, size = 4 GiB (4294963200 bytes) no label, UUID=ae0bbc8e-4558-4e6a-936b-ed1341b45056 $ sudo swapon /swapfile $ echo "/swapfile swap swap defaults 0 0" | sudo tee -a /etc/fstab $ swapon --show NAME TYPE SIZE USED PRIO /swapfile file 4G 0B -2 Then, I went back to the EC2 console and selected Instance State > Hibernate. The instance stopped within 30 seconds, hibernating successfully. I then started the instance again, and I could log in: My screen session is still there, so hibernation went as planned. $ screen -r There are several suitable screens on: 3655.pts-4.ip-172-31-27-182 (05/26/22 04:24:13) (Detached) 3472.pts-1.ip-172-31-27-182 (05/26/22 04:19:43) (Detached) Type "screen [-d] -r [pid.]tty.host" to resume one of them. The new package, 1.0.0-0ubuntu11.22.04.1 in -proposed fixes the issue, and I am able to hibernate with an additional swapfile set. Happy to mark as verified for Jammy. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Performing verification for Impish. For some reason hibernation just refused to work on any Xen based instance type, but it works fine on KVM based instances, such as c5, t3 etc. This is being looked into on bug 1968062, but I think it affects Impish as well. Diverging from the testcase, and using c5.large (kvm) instances instead of t2.medium (xen). I started a c5.large instance with 20gb of storage, with advanced > enable encryption > yes. I also made sure to enable Advanced settings > Stop State (Hibernation) Support > Enabled. I waited for hibinit-agent.service to complete by watching $ sudo systemctl status hibinit-agent.service This is using the current version of ec2-hibinit-agent from -updates: $ apt-cache policy ec2-hibinit-agent | grep Installed Installed: 1.0.0-0ubuntu11 I went to the EC2 console and pressed Instance State > Hibernate. The instance stopped within 30 seconds, and hibernation was successful. I started the instance again. From there, I made a swapfile, and enabled it: $ sudo fallocate -l 4G /swapfile $ sudo dd if=/dev/zero of=/swapfile bs=1024 count=4194304 $ sudo chmod 600 /swapfile $ sudo mkswap /swapfile $ sudo swapon /swapfile $ echo "/swapfile swap swap defaults 0 0" | sudo tee -a /etc/fstab $ swapon --show NAME TYPE SIZE USED PRIO /swapfile file 4G 0B -2 I went back to the console and pressed Instance State > Hibernate. The follow was written to journalctl: May 26 05:06:22 ip-172-31-45-200 systemd-logind[519]: Suspend key pressed. May 26 05:06:22 ip-172-31-45-200 systemd-logind[519]: Requested suspend operation not supported, ignoring. May 26 05:06:22 ip-172-31-45-200 kernel: Adding 4095996k swap on /swap-hibinit. Priority:-3 extents:5 across:4505596k SSFS May 26 05:06:22 ip-172-31-45-200 root[2917]: ACPI action undefined: LNXSLPBN:00 The instance did not hibernate, and stayed running for 20 minutes, until it timed out and was force stopped. We can see from the logs that /swap-hibinit was added at priority -3, and /swapfile is -2. /swapfile was chosen for hibernation, but as since kernel command line and grub is not set up for this, it fails. I terminated the instance. I then created a new instance, again a c5.large, with 20gb of storage, with Advanced > Enable Encryption > yes. I also made sure to enable Advanced settings > Stop State (Hibernation) Support > Enabled. I waited for hibinit-agent.service to complete by watching $ sudo systemctl status hibinit-agent.service I enabled -proposed, and installed ec2-hibinit-agent 1.0.0-0ubuntu11.21.10.1 Setting up ec2-hibinit-agent (1.0.0-0ubuntu11.21.10.1) ... Installing new version of config file /etc/acpi/actions/sleep.sh ... $ apt-cache policy ec2-hibinit-agent | grep Installed Installed: 1.0.0-0ubuntu11.21.10.1 I went to the EC2 console and pressed Instance State > Hibernate. Again, the instance stopped within 30 seconds, and hibernation was successful. I started the instance again, and configured a second swapfile: From there, I made a swapfile, and enabled it: $ sudo fallocate -l 4G /swapfile $ sudo dd if=/dev/zero of=/swapfile bs=1024 count=4194304 4194304+0 records in 4194304+0 records out 4294967296 bytes (4.3 GB, 4.0 GiB) copied, 31.5124 s, 136 MB/s $ sudo chmod 600 /swapfile $ sudo mkswap /swapfile Setting up swapspace version 1, size = 4 GiB (4294963200 bytes) no label, UUID=ae0bbc8e-4558-4e6a-936b-ed1341b45056 $ sudo swapon /swapfile $ echo "/swapfile swap swap defaults 0 0" | sudo tee -a /etc/fstab $ swapon --show NAME TYPE SIZE USED PRIO /swapfile file 4G 0B -2 Then, I went back to the EC2 console and selected Instance State > Hibernate. The instance stopped within 30 seconds, hibernating successfully. I then started the instance again, and I could log in: My screen session is still there, so hibernation went as planned. $ screen -r There are several suitable screens on: 3655.pts-4.ip-172-31-27-182 (05/26/22 04:24:13) (Detached) 3472.pts-1.ip-172-31-27-182 (05/26/22 04:19:43) (Detached) Type "screen [-d] -r [pid.]tty.host" to resume one of them. The new package, 1.0.0-0ubuntu11.21.10.1 in -proposed fixes the issue, and I am able to hibernate with an additional swapfile set. Happy to mark as verified for Impish. ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Performing verification for Focal. For some reason hibernation just refused to work on any Xen based instance type, but it works fine on KVM based instances, such as c5, t3 etc. This is being looked into on bug 1968062, but I think it affects Focal as well. Diverging from the testcase, and using c5.large (kvm) instances instead of t2.medium (xen). I started a c5.large instance with 20gb of storage, with advanced > enable encryption > yes. I also made sure to enable Advanced settings > Stop State (Hibernation) Support > Enabled. I waited for hibinit-agent.service to complete by watching $ sudo systemctl status hibinit-agent.service This is using the current version of ec2-hibinit-agent from -updates: $ apt-cache policy ec2-hibinit-agent | grep Installed Installed: 1.0.0-0ubuntu9.1 I went to the EC2 console and pressed Instance State > Hibernate. The instance stopped within 30 seconds, and hibernation was successful. I started the instance again. From there, I made a swapfile, and enabled it: $ sudo fallocate -l 4G /swapfile $ sudo dd if=/dev/zero of=/swapfile bs=1024 count=4194304 $ sudo chmod 600 /swapfile $ sudo mkswap /swapfile $ sudo swapon /swapfile $ echo "/swapfile swap swap defaults 0 0" | sudo tee -a /etc/fstab $ swapon --show NAME TYPE SIZE USED PRIO /swapfile file 4G 0B -2 I went back to the console and pressed Instance State > Hibernate. The follow was written to journalctl: May 26 03:25:27 ip-172-31-26-217 systemd-logind[523]: Suspend key pressed. May 26 03:25:27 ip-172-31-26-217 systemd-logind[523]: Requested suspend operation not supported, ignoring. May 26 03:25:27 ip-172-31-26-217 udisksd[525]: udisks_mount_get_mount_path: assertion 'mount->type == UDISKS_MOUNT_TYPE_FILESYSTEM' failed May 26 03:25:27 ip-172-31-26-217 kernel: Adding 4095996k swap on /swap-hibinit. Priority:-3 extents:9 across:5087228k SSFS May 26 03:25:27 ip-172-31-26-217 root[2720]: ACPI action undefined: LNXSLPBN:00 The instance did not hibernate, and stayed running for 20 minutes, until it timed out and was force stopped. We can see from the logs that /swap-hibinit was added at priority -3, and /swapfile is -2. /swapfile was chosen for hibernation, but as since kernel command line and grub is not set up for this, it fails. I terminated the instance. I then created a new instance, again a c5.large, with 20gb of storage, with Advanced > Enable Encryption > yes. I also made sure to enable Advanced settings > Stop State (Hibernation) Support > Enabled. I waited for hibinit-agent.service to complete by watching $ sudo systemctl status hibinit-agent.service I enabled -proposed, and installed ec2-hibinit-agent 1.0.0-0ubuntu9.2 Setting up ec2-hibinit-agent (1.0.0-0ubuntu9.2) ... Installing new version of config file /etc/acpi/actions/sleep.sh ... $ apt-cache policy ec2-hibinit-agent | grep Installed Installed: 1.0.0-0ubuntu9.2 I went to the EC2 console and pressed Instance State > Hibernate. Again, the instance stopped within 30 seconds, and hibernation was successful. I started the instance again, and configured a second swapfile: From there, I made a swapfile, and enabled it: $ sudo fallocate -l 4G /swapfile $ sudo dd if=/dev/zero of=/swapfile bs=1024 count=4194304 4194304+0 records in 4194304+0 records out 4294967296 bytes (4.3 GB, 4.0 GiB) copied, 31.7563 s, 135 MB/s $ sudo chmod 600 /swapfile $ sudo mkswap /swapfile Setting up swapspace version 1, size = 4 GiB (4294963200 bytes) no label, UUID=ffbed86f-8317-4c16-8ab2-19fd5c3190aa $ sudo swapon /swapfile $ echo "/swapfile swap swap defaults 0 0" | sudo tee -a /etc/fstab $ swapon --show NAME TYPE SIZE USED PRIO /swapfile file 4G 0B -2 Then, I went back to the EC2 console and selected Instance State > Hibernate. The instance stopped within 30 seconds, hibernating successfully. I then started the instance again, and I could log in: My screen session is still there, so hibernation went as planned. $ screen -r There are several suitable screens on: 3655.pts-4.ip-172-31-27-182 (05/26/22 04:24:13) (Detached) 3472.pts-1.ip-172-31-27-182 (05/26/22 04:19:43) (Detached) Type "screen [-d] -r [pid.]tty.host" to resume one of them. The new package, 1.0.0-0ubuntu9.2 in -proposed fixes the issue, and I am able to hibernate with an additional swapfile set. Happy to mark as verified for Focal. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973434] Re: massive performance issues since 22.04 upgrade
Hi Henning, That is great news that "intel_iommu=off" on the kernel command line did the trick. You can follow this bug to get updates on when we will be disabling IOMMU by default in the 5.15 kernel. It should be soon, the patches are already submitted, and reviewed by the kernel team. The next step is for the patch to be applied to the git tree and the next kernel update built. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699 I'll let you know once there is a kernel in -proposed with IOMMU disabled. The patches missed this current SRU cycle, and will be in the next one, so it might be in a few weeks / months time. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973434 Title: massive performance issues since 22.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971699] Re: disable Intel DMA remapping by default
A user has reported extensive performance issues with a Lenovo Thinkpad X1 Extreme Gen 2 laptop computer, in bug 1973434. The user reports video playback hangs, browser hangs and virtual machines hanging. Their dmesg indicates the system has 2x IOMMUs and there are 25 groups being configured. They tested "intel_iommu=off", and the performance issues are no longer seen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973434] Re: massive performance issues since 22.04 upgrade
Hi Henning, Just a thought, could you try booting with IOMMU disabled? Edit /etc/default/grub, and append "intel_iommu=off" to GRUB_CMDLINE_LINUX_DEFAULT. Then save, and run "sudo update-grub" and reboot. Between 21.10 and 22.04 we enabled CONFIG_INTEL_IOMMU_DEFAULT_ON=y, and it has caused all sorts of odd issues, including performance related ones, so its worth a shot. We will be reverting the change to CONFIG_INTEL_IOMMU_DEFAULT_ON, and turning it off again in a kernel update in the near future. If "intel_iommu=off" doesn't help, then a make oldconfig with the 22.04 config and 5.17.7 would be interesting to see. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973434 Title: massive performance issues since 22.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Performing verification for Jammy. Starting with the broken 3.0.27-2build2 in -release, running gst-launch-1.0 videotestsrc ! jpegenc ! jpegdec ! clutterautovideosink shows a grey picture with vertical bars. Opening cheese, we see the same vertical bars, poor video performance and purple lines. I enabled -proposed and installed 3.0.27-2ubuntu1, and re-ran gst-launch-1.0 videotestsrc ! jpegenc ! jpegdec ! clutterautovideosink and had cheese running. Performance was great, nice and smooth, and picture is correct. Tested with my Logitech C720 webcam, and attached is a screenshot of everything running with 3.0.27-2ubuntu1 from -proposed. Happy to mark as verified for Jammy. ** Attachment added: "Screenshot of verification for Jammy" https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+attachment/5589910/+files/Screenshot%20from%202022-05-16%2010-14-41.png ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1967843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971699] Re: disable Intel DMA remapping by default
A user has ran into a storage performance issue, and it has been traced back to CONFIG_INTEL_IOMMU_DEFAULT_ON being enabled. They have a Dell XtremIO FC storage server, running VMWare ESXi 7.0U3, with 4x pvscsi controllers (2 LUNs per controller), running a single large LV with 8-way 1MB stripe. There are Ubuntu 20.04 and 22.04 VMs running on the same server. The VMs are attached to the storage unit through iSCSI. When running the following FIO script: [write1] filename=/dev/xio2data/prd01 readwrite=randwrite random_generator=tausworthe64 blocksize=8K ioengine=libaio iodepth=32 direct=1 runtime=30 numjobs=8 group_reporting invalidate=0 On 20.04 with 5.4.0-109-generic they see: WRITE: bw=1010MiB/s (1059MB/s), 1010MiB/s-1010MiB/s (1059MB/s-1059MB/s), io=29.6GiB (31.8GB), run=30007-30007msec They note a 2%-3% %SYS load. On 22.04 with 5.15.0-27-generic they see: WRITE: bw=568MiB/s (595MB/s), 568MiB/s-568MiB/s (595MB/s-595MB/s), io=16.6GiB (17.9GB), run=30007-30007msec They note a consistent 18%-19% %SYS load, and poor performance. It seems VMWare emulates a IOMMU, and their VMs were configuring 8 IOMMU groups for their PCI devices, and it was significantly impacting iSCSI performance. When intel_iommu=off was supplied on the kernel command line, the performance issue is no longer present. This is a suitable workaround for the time being. This user is in agreement with and asking for CONFIG_INTEL_IOMMU_DEFAULT_ON to be disabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971699] Re: disable Intel DMA remapping by default
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
** Patch added: "debdiff for ec2-hibinit-agent for bionic" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5588358/+files/lp1968805_bionic_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Attached is a V2 patch for Focal. ** Patch added: "debdiff for ec2-hibinit-agent for focal" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5588357/+files/lp1968805_focal_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Attached is a V2 patch for Impish. ** Patch added: "debdiff for ec2-hibinit-agent for impish" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5588356/+files/lp1968805_impish_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Attached is a V2 patch for Jammy ** Patch added: "debdiff for ec2-hibinit-agent for jammy" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5588355/+files/lp1968805_jammy_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Attached is a V2 patch for Kinetic. ** Patch added: "debdiff for ec2-hibinit-agent for kinetic" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5588354/+files/lp1968805_kinetic_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
** Also affects: ec2-hibinit-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Kinetic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Changed in: ec2-hibinit-agent (Ubuntu Bionic) Status: New => In Progress ** Changed in: ec2-hibinit-agent (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: ec2-hibinit-agent (Ubuntu Bionic) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Patch removed: "debdiff for ec2-hibinit-agent for impish" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5580293/+files/lp1968805_impish.debdiff ** Patch removed: "debdiff for ec2-hibinit-agent for jammy" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5580294/+files/lp1968805_jammy.debdiff ** Patch removed: "debdiff for ec2-hibinit-agent for bionic" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5581947/+files/lp1968805_bionic.debdiff ** Patch removed: "debdiff for ec2-hibinit-agent for focal" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5580292/+files/lp1968805_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
The fix has now been merged upstream with:
commit a2303d269610a6e7415c5045766da605eaa7e30f
From: Matthew Ruffell
Date: Wed, 20 Apr 2022 15:59:25 +1200
Subject: Swapon with maximum priority before hibernation
Link:
https://github.com/aws/amazon-ec2-hibinit-agent/commit/a2303d269610a6e7415c5045766da605eaa7e30f
** Description changed:
[Impact]
It is not uncommon for users to add a swapfile to their AWS instance, in
case they run short of memory. For users that optionally enable
Hibernation support, the swapfile generated by ec2-hibinit-agent, /swap-
hibinit, needs to always be the highest priority when it comes to
suspend the system, since ec2-hibinit-agent sets up /swap-hibinit to be
the correct way to suspend and resume via the resume=UUID= and
resume_offeset= kernel command line parameters.
ec2-hibinit-agent keeps /swap-hibinit swapoff during normal instance
use, and right before Hibernation occurs, /etc/acpi/actions/sleep.sh
swapon /swap-hibinit, and calls systemctl hibernate:
do_hibernate() {
if [ -d /run/systemd/system ]; then
systemctl hibernate
case "$2" in
SBTN)
swapon /swap-hibinit && do_hibernate
Something changed between 18.04 and 20.04, such that new swapfiles are
added with a lower priority than the previous swapfile when they are
swapon:
On Focal and later, we see behaviour like if we simply swapon /swap-hibinit
generated by ec2-hibinit-agent, we
see it is -2:
$ sudo swapon /swap-hibinit
$ swapon --show
NAME TYPE SIZE USED PRIO
/swap-hibinit file 3.9G 0B -2
Turning it off:
$ sudo swapoff /swap-hibinit
$ swapon --show
NAME TYPE SIZE USED PRIO
Lets add /swapfile in:
$ sudo swapon /swapfile
$ swapon --show
NAME TYPE SIZE USED PRIO
/swapfile file 4G 0B -2
Now we enable /swap-hibinit again, and see it is -3:
$ sudo swapon /swap-hibinit
$ swapon --show
NAME TYPE SIZE USED PRIO
/swapfile file 4G 0B -2
/swap-hibinit file 3.9G 0B -3
Lets add in another swapfile, /swapfile-second, and we see -2, -3, -4:
$ sudo swapon /swapfile-second
$ swapon --show
NAME TYPE SIZE USED PRIO
/swapfilefile 4G 0B -2
/swap-hibinitfile 3.9G 0B -3
/swapfile-second file 4G 0B -4
What happens is that if we have a swapfile, say, /swapfile at default
priority -2, when we go to hibernate, the swapon in
/etc/acpi/actions/sleep.sh will set the priority of /swap-hibinit to -3.
systemd / the kernel will then select the highest priority swapfile to
hibernate to, in this case /swapfile, which is NOT setup for resume= or
resume_offset= on the kernel command line, and hibernation will fail.
Apr 11 21:08:15 ip-172-31-84-225 kernel: [ 240.990073] Adding 4095996k
swap on /swap-hibinit. Priority:-3 extents:6 across:4644860k SSFS
This leaves the instance in the "Stopping" state on the EC2 console
until it hits the 20 minute timeout, at which point it is force stopped.
The fix is to set the priority when we swapon /swap-hibinit to something
higher than any other swapfile, to ensure we hibernate to /swap-hibinit.
[Testcase]
From the EC2 console, select "Launch Instance".
Create a:
- t2.medium
- Ubuntu 20.04, 21.04 or 22.04
- 20gb storage space, advanced > enable encryption > yes.
- Advanced settings > Stop State (Hibernation) Support > Enabled
On boot wait for ec2-hibinit-agent to complete hibinit-agent.service,
and see that /swap-hibinit is created, and swapoff.
$ ll /swap-hibinit
Add a swapfile, and switch it on:
$ sudo fallocate -l 4G /swapfile
$ sudo dd if=/dev/zero of=/swapfile bs=1024 count=4194304
$ sudo chmod 600 /swapfile
$ sudo mkswap /swapfile
$ sudo swapon /swapfile
$ echo "/swapfile swap swap defaults 0 0" | sudo tee -a /etc/fstab
$ swapon --show
NAME TYPE SIZE USED PRIO
/swapfile file 4G 0B -2
Go back to EC2 console, "Instance State" > "Hibernate".
You will see this in journalctl:
Mar 15 11:41:54 ip-172-31-27-108 kernel: [ 520.121761] Adding 16095656k swap
on /swap-hibinit. Priority:-3 extents:13 across:17611176k SSFS
Mar 15 11:41:54 ip-172-31-27-108 root: ACPI action undefined: LNXSLPBN:00
and the instance will not hibernate. EC2 console will report "Stopping"
for 20 minutes until it times out and is force stopped.
If you enable the following ppa and install the test ec2-hibinit-agent
package:
https://launchpad.net/~mruffell/+archive/ubuntu/sf331069-test
Hibernation should succeed within a minute or two.
[Where problems could occur]
This change will only affect users of instances where Hibernation has
been explicitly enabled, either from the EC2 instance launch advanced
settings, or via the "--hibernation-o
[Bug 1972747] Re: Speakup modules missing from kernel after upgrad to Ubuntu Jammy/22.04
*** This bug is a duplicate of bug 1967702 *** https://bugs.launchpad.net/bugs/1967702 Hi John. We are looking to get this fixed with 5.15.0-30-generic, currently in -proposed. Should have a release to -updates very soon now. ** This bug has been marked a duplicate of bug 1967702 Enable speakup kernel modules to allow the speakup screen reader to function -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972747 Title: Speakup modules missing from kernel after upgrad to Ubuntu Jammy/22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972011] Re: cheese camara app Vertical Lines
*** This bug is a duplicate of bug 1967843 *** https://bugs.launchpad.net/bugs/1967843 ** This bug has been marked a duplicate of bug 1967843 cheese display corrupted under Ubuntu 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972011 Title: cheese camara app Vertical Lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
I built the patch Jan provided into a test package, available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1967843-test When I install it, the testcase is fixed, shown in the attachment, and cheese works as normal. Jeremy, shall we submit the patch to Debian, and SRU to Ubuntu? It seems the upstream clutter-gst project is now archived and not accepting new patches. ** Attachment added: "Working testcase with test package" https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+attachment/5584223/+files/Screenshot%20from%202022-04-27%2012-29-41.png ** Also affects: clutter-gst-3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1967843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Jan also added a testcase to the upstream bug, that calls clutter-gst directly and does not require cheese: $ gst-launch-1.0 videotestsrc ! jpegenc ! jpegdec ! clutterautovideosink Attached is a picture running the testcase with clutter-gst-3.0 3.0.27-2build2, showing distorted picture. ** Attachment added: "Testcase with distorted screen" https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+attachment/5584222/+files/Screenshot%20from%202022-04-27%2012-24-18.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1967843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970202] Re: linux-generic kernels are missing nbd modules
Hi Thomas, nbd modules are shipped on all Ubuntu kernels, in the standard linux- modules package. I started a fresh Impish VM and it was there, and loadable: $ find /usr/lib/modules -name nbd.ko /usr/lib/modules/5.13.0-35-generic/kernel/drivers/block/nbd.ko $ grep -Rin "nbd" /boot/config-5.13.0-35-generic 2563:CONFIG_BLK_DEV_NBD=m 2577:CONFIG_BLK_DEV_RNBD=y 2578:CONFIG_BLK_DEV_RNBD_CLIENT=m 2579:CONFIG_BLK_DEV_RNBD_SERVER=m $ sudo apt-file search nbd.ko | grep generic linux-modules-5.13.0-19-generic: /lib/modules/5.13.0-19-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-20-generic: /lib/modules/5.13.0-20-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-21-generic: /lib/modules/5.13.0-21-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-22-generic: /lib/modules/5.13.0-22-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-23-generic: /lib/modules/5.13.0-23-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-25-generic: /lib/modules/5.13.0-25-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-27-generic: /lib/modules/5.13.0-27-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-28-generic: /lib/modules/5.13.0-28-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-30-generic: /lib/modules/5.13.0-30-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-35-generic: /lib/modules/5.13.0-35-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-37-generic: /lib/modules/5.13.0-37-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-39-generic: /lib/modules/5.13.0-39-generic/kernel/drivers/block/nbd.ko linux-modules-5.13.0-40-generic: /lib/modules/5.13.0-40-generic/kernel/drivers/block/nbd.ko $ sudo modprobe nbd $ lsmod | grep nbd nbd53248 0 I then went on and mounted a qcow2 image to be sure, and it works fine. Could you please elaborate on what you are trying to do, and maybe I can help debug what isn't working? Thanks, Matthew ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970202 Title: linux-generic kernels are missing nbd modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
** Tags added: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Attached is a debdiff of ec2-hibinit-agent for Bionic, since it needs it too. ** Patch added: "debdiff for ec2-hibinit-agent for bionic" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5581947/+files/lp1968805_bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
I opened a pull request upstream with the same patch: https://github.com/aws/amazon-ec2-hibinit-agent/pull/22 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
Hi Tiago, The kernel team have reviewed the patch, and it has received 2x acks [1] and it has been applied [2] to the Jammy kernel git tree [3]. [1] https://lists.ubuntu.com/archives/kernel-team/2022-April/129208.html [2] https://lists.ubuntu.com/archives/kernel-team/2022-April/129498.html [3] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=438e2ff5cbc602384724c217880f216221b93ffc I am expecting it to be contained in the 2022.04.18 Kernel SRU cycle, https://kernel.ubuntu.com/, and I will write back with more details once it has been built and placed into -proposed for verification. Thanks, Matthew ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967702 Title: Enable speakup kernel modules to allow the speakup screen reader to function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Attached is a debdiff for ec2-hibinit-agent on Jammy which fixes this issue. ** Patch added: "debdiff for ec2-hibinit-agent for jammy" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5580294/+files/lp1968805_jammy.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Attached is a debdiff for ec2-hibinit-agent for impish which fixes this issue. ** Patch added: "debdiff for ec2-hibinit-agent for impish" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5580293/+files/lp1968805_impish.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Attached is a debdiff for ec2-hibinit-agent on Focal which fixes this issue. ** Patch added: "debdiff for ec2-hibinit-agent for focal" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+attachment/5580292/+files/lp1968805_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] [NEW] Hibernation fails when an additional swapfile is added due to priority mismatch
is users that do not use /swap-hibinit, and use their
own swapfile for hibernation, and overwrite the changes ec2-hibinit-
agent makes to grub files to set the resume=UUID and
resume_offset= values. I believe such users would likely remove
or purge the ec2-hibinit-agent package, since hibinit-agent.service runs
at startup and re-adds the grub configuration for /swap-hibinit whether
you like it or not, and having /swap-hibinit around would waste disk
space that you would be paying for. Because of this, I believe that this
change will not break users who hibernate to their own swapfiles,
because they would have removed ec2-hibinit-agent on instance creation.
[Other info]
Chris Newcomer came across the above upstream bug, which seems to be the
same issue:
https://github.com/aws/amazon-ec2-hibinit-agent/issues/20
The reporter, Ben Mares, suggests a patch to /etc/acpi/actions/sleep.sh
to either read the value of a bash environment variable swap_priority,
or default to 10.
https://github.com/aws/amazon-ec2-hibinit-agent/pull/21
I'm not exactly on board with the environment variable, or the default
magic number of 10, as we don't know how our users are setting up
swapfiles, and what priorities they set them to. I think we should
instead just set the priority to the maximum, 32767 instead.
** Affects: ec2-hibinit-agent (Ubuntu)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: ec2-hibinit-agent (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: ec2-hibinit-agent (Ubuntu Impish)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: ec2-hibinit-agent (Ubuntu Jammy)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Also affects: ec2-hibinit-agent (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ec2-hibinit-agent (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: ec2-hibinit-agent (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: ec2-hibinit-agent (Ubuntu Focal)
Status: New => In Progress
** Changed in: ec2-hibinit-agent (Ubuntu Impish)
Status: New => In Progress
** Changed in: ec2-hibinit-agent (Ubuntu Jammy)
Status: New => In Progress
** Changed in: ec2-hibinit-agent (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: ec2-hibinit-agent (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: ec2-hibinit-agent (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: ec2-hibinit-agent (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: ec2-hibinit-agent (Ubuntu Impish)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: ec2-hibinit-agent (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
[Impact]
It is not uncommon for users to add a swapfile to their AWS instance, in
case they run short of memory. For users that optionally enable
Hibernation support, the swapfile generated by ec2-hibinit-agent, /swap-
hibinit, needs to always be the highest priority when it comes to
suspend the system, since ec2-hibinit-agent sets up /swap-hibinit to be
the correct way to suspend and resume via the resume=UUID= and
resume_offeset= kernel command line parameters.
ec2-hibinit-agent keeps /swap-hibinit swapoff during normal instance
use, and right before Hibernation occurs, /etc/acpi/actions/sleep.sh
swapon /swap-hibinit, and calls systemctl hibernate:
do_hibernate() {
- if [ -d /run/systemd/system ]; then
- systemctl hibernate
+ if [ -d /run/systemd/system ]; then
+ systemctl hibernate
case "$2" in
- SBTN)
- swapon /swap-hibinit && do_hibernate
+ SBTN)
+ swapon /swap-hibinit && do_hibernate
Something changed between 18.04 and 20.04, such that new swapfiles are
added with a lower priority than the previous swapfile when they are
swapon:
On Focal and later, we see behaviour like if we simply swapon /swap-hibinit
generated by ec2-hibinit-agent, we
see it is -2:
$ sudo swapon /swap-hibinit
$ swapon --show
NAME TYPE SIZE USED PRIO
/swap-hibinit file 3.9G 0B -2
Turning it off:
$ sudo swapoff /swap-hibinit
$ swapon --show
NAME TYPE SIZE USED PRIO
Lets add /swapfile in:
$ sudo swapon /swapfile
$ swapon --show
NAME TYPE SIZE USED PRIO
/swapfile file 4G 0B -2
Now we enable /swap-hibinit again, and see it is -3:
$ sudo swapon /swap-hibinit
$ swapon --show
NAME TYPE SIZE USED PRIO
/swapfile file 4G 0B -2
/swap-hibinit file 3.9G 0B -3
Lets add in another swapfile, /swapfile-second, and we see -
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Hi Jack, I booted a Fedora 36 Beta live image like you suggested, and cheese works fine there on my machine. Their cheese includes the above patch. I had a look around, it has a 5.17 kernel, and gstreamer 1.20. Ubuntu has gstreamer 1.20.1, and when I booted my machine into a 5.17 kernel, I found that the issue still persists. So it doesn't appear to be a kernel issue. Will have to try and keep narrowing it down. Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
