[Touch-packages] [Bug 1988119] Re: systemd-udevd: Run net_setup_link on 'change' uevents to prevent DNS outages on Azure
Hello everyone, I know there are quite a few people watching this bug, so I will provide a status update. The test package has been looking good throughout our internal testing, and we have proceeded to build the next systemd update, version 237-3ubuntu10.55, and it is currently in the bionic-security -proposed ppa. If you would like to help test, that would be greatly appreciated. Please use a fresh VM on Azure, and please don't put the package into production just yet. Instructions to install (On a Bionic system): 1) sudo add-apt-repository ppa:ubuntu-security-proposed/ppa 2) sudo apt update 3) sudo apt install libnss-systemd libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev 4) sudo apt-cache policy systemd | grep Installed Installed: 237-3ubuntu10.55 5) sudo rm /etc/apt/sources.list.d/ubuntu-security-proposed-ubuntu-ppa-bionic.list 6) sudo apt update >From there you can run the reproducer: $ sudo udevadm trigger && sudo systemctl restart systemd-networkd $ ping google.com PING google.com (172.253.122.138) 56(84) bytes of data. 64 bytes from bh-in-f138.1e100.net (172.253.122.138): icmp_seq=1 ttl=103 time=1.67 ms if you do test, comment here on how it went. Again, please don't put the package into production until it has had a little more testing, and we will get this released to the world as quickly and safely as we can. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988119 Title: systemd-udevd: Run net_setup_link on 'change' uevents to prevent DNS outages on Azure Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: [Impact] A widespread outage was caused on Azure instances earlier today, when systemd 237-3ubuntu10.54 was published to the bionic-security pocket. Instances could no longer resolve DNS queries, breaking networking. For affected users, the following workarounds are available. Use whatever is most convenient. - Reboot your instances - or - - Issue "udevadm trigger -cadd -yeth0 && systemctl restart systemd-networkd" as root The trigger was found to be open-vm-tools issuing "udevadm trigger". Azure has a specific netplan setup that uses the `driver` match to set up networking. If a udevadm trigger is executed, the KV pair that contains this info is lost. Next time netplan is executed, the server loses it's DNS information. This is the same as bug 1902960 experienced on Focal two years ago. The root cause was found to be a bug in systemd, where if we receive a "Remove" action from a change uevent, we need to run net_setup_link(), we need to skip device rename and keep the old name. [Testcase] Start an instance up on Azure, any type. Simply issue udevadm trigger and reload systemd-networkd: $ ping google.com PING google.com (172.253.62.102) 56(84) bytes of data. 64 bytes from bc-in-f102.1e100.net (172.253.62.102): icmp_seq=1 ttl=56 time=1.85 ms $ sudo udevadm trigger && sudo systemctl restart systemd-networkd $ ping google.com ping: google.com: Temporary failure in name resolution To fix a broken instance, you can run: $ sudo udevadm trigger -cadd -yeth0 && sudo systemctl restart systemd- networkd and then install the test packages below: Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf343528-test If you install them, the issue should no longer occur. [Where problems could occur] If a regression were to occur, it would affect systemd-udevd processing 'change' events from network devices, which could lead to network outages. Since this would happen when systemd-networkd is restarted on postinstall, a regression would cause widespread outages due to this SRU being targeted to the security pocket, where unattended-upgrades will automatically install from. Side effects could include incorrect udevd device properties. It is very important that this SRU is well tested before release. [Other info] This was fixed in Systemd 247 with the following commit: commit e0e789c1e97e2cdf1cafe0c6b7d7e43fa054f151 Author: Yu Watanabe Date: Mon, 14 Sep 2020 15:21:04 +0900 Subject: udev: re-assign ID_NET_DRIVER=, ID_NET_LINK_FILE=, ID_NET_NAME= properties on non-'add' uevent Link: https://github.com/systemd/systemd/commit/e0e789c1e97e2cdf1cafe0c6b7d7e43fa054f151 This was backported to Focal's systemd 245.4-4ubuntu3.4 in bug 1902960 two years ago. Focal required a heavy backport, which was performed by Dan Streetman. Focals backport can be found in d/p/lp1902960-udev-re- assign-ID_NET_DRIVER-ID_NET_LINK_FILE-ID_NET.patch, or the below pastebin: https://paste.ubuntu.com/p/K5k7bGt3Wx/ The changes between the Focal backport and the Bionic backport are: - We use udev_device_get_action()
[Touch-packages] [Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Attached is a debdiff for systemd on Bionic which fixes this bug. ** Description changed: - Two servers today that updated systemd to "systemd 237-3ubuntu10.54" - https://ubuntu.com/security/notices/USN-5583-1 + [Impact] - could not resolve dns anymore. - no dns servers, normally set through dhcp. + A widespread outage was caused on Azure instances earlier today, when + systemd 237-3ubuntu10.54 was published to the bionic-security pocket. + Instances could no longer resolve DNS queries, breaking networking. - Ubuntu 18.04 + For affected users, the following workarounds are available. Use whatever is most convenient. + - Reboot your instances + - or - + - Issue "udevadm trigger -cadd -yeth0 && systemctl restart systemd-networkd" as root - Temp fix. - 1. Edit /etc/systemd/resolved.conf - 1. Add/Uncomment # FallbackDNS=168.63.129.16 - 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service - 1. Confirm dns working with systemd-resolve google.com + The trigger was found to be open-vm-tools issuing "udevadm trigger". + Azure has a specific netplan setup that uses the `driver` match to set + up networking. If a udevadm trigger is executed, the KV pair that + contains this info is lost. Next time netplan is executed, the server + loses it's DNS information. + + This is the same as bug 1902960 experienced on Focal two years ago. + + The root cause was found to be a bug in systemd, where if we receive a + "Remove" action from a change uevent, we need to run net_setup_link(), + we need to skip device rename and keep the old name. + + [Testcase] + + Start an instance up on Azure, any type. Simply issue udevadm trigger + and reload systemd-networkd: + + $ ping google.com + PING google.com (172.253.62.102) 56(84) bytes of data. + 64 bytes from bc-in-f102.1e100.net (172.253.62.102): icmp_seq=1 ttl=56 time=1.85 ms + $ sudo udevadm trigger && sudo systemctl restart systemd-networkd + $ ping google.com + ping: google.com: Temporary failure in name resolution + + To fix a broken instance, you can run: + + $ sudo udevadm trigger -cadd -yeth0 && sudo systemctl restart systemd- + networkd + + and then install the test packages below: + + Test packages are available in the following ppa: + + https://launchpad.net/~mruffell/+archive/ubuntu/sf343528-test + + If you install them, the issue should no longer occur. + + [Where problems could occur] + + If a regression were to occur, it would affect systemd-udevd processing + 'change' events from network devices, which could lead to network + outages. Since this would happen when systemd-networkd is restarted on + postinstall, a regression would cause widespread outages due to this SRU + being targeted to the security pocket, where unattended-upgrades will + automatically install from. + + Side effects could include incorrect udevd device properties. + + It is very important that this SRU is well tested before release. + + [Other info] + + This was fixed in Systemd 247 with the following commit: + + commit e0e789c1e97e2cdf1cafe0c6b7d7e43fa054f151 + Author: Yu Watanabe + Date: Mon, 14 Sep 2020 15:21:04 +0900 + Subject: udev: re-assign ID_NET_DRIVER=, ID_NET_LINK_FILE=, ID_NET_NAME= properties on non-'add' uevent + Link: https://github.com/systemd/systemd/commit/e0e789c1e97e2cdf1cafe0c6b7d7e43fa054f151 + + This was backported to Focal's systemd 245.4-4ubuntu3.4 in bug 1902960 + two years ago. Focal required a heavy backport, which was performed by + Dan Streetman. Focals backport can be found in d/p/lp1902960-udev-re- + assign-ID_NET_DRIVER-ID_NET_LINK_FILE-ID_NET.patch, or the below + pastebin: + + https://paste.ubuntu.com/p/K5k7bGt3Wx/ + + The changes between the Focal backport and the Bionic backport are: + + - We use udev_device_get_action() instead of device_get_action() + - device_action_from_string() is used to get to enum DeviceAction + - We return 0 from the "if (a == DEVICE_ACTION_MOVE) " hunk instead of "goto no_rename" + - log_device_* has been changed to log_*. + + See attached debdiff for Bionic backport. ** Summary changed: - Update to systemd 237-3ubuntu10.54 broke dns + systemd-udevd: Run net_setup_link on 'change' uevents to prevent DNS outages on Azure ** Patch added: "Debdiff for systemd on Bionic" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+attachment/5612617/+files/lp1988119_bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988119 Title: systemd-udevd: Run net_setup_link on 'change' uevents to prevent DNS outages on Azure Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: [Impact] A widespread outage was caused on Azure instances earlier today, when systemd 237-3ubuntu10.54 was published to the bionic-security pocket. Instances could no longer
[Touch-packages] [Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Tags added: bionic sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987998] [NEW] LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot
, and to
be marked as extern from security/landlock/setup.h.
[Testcase]
Launch a Jammy or Kinetic VM.
1. Edit /etc/default/grub and append the following to
GRUB_CMDLINE_LINUX_DEFAULT:
"lsm=landlock,bpf,apparmor"
2. sudo update-grub
3. reboot
The system will panic on boot.
If you install the test kernel from the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf343286-test
Instead of a panic occurring, the kernel should display all LSMs
initialising, and continue to boot.
[0.288224] LSM: Security Framework initializing
[0.289457] landlock: Up and running.
[0.290290] LSM support for eBPF active
[0.291189] AppArmor: AppArmor initialized
[Where problems could occur]
The risk of regression in changing Landlock from LSMBLOB_NEEDED to
LSMBLOB_NOT_NEEDED is low, due to Landlock not needing a slot in the
secid array in struct lsmblob in the first place.
The refactor is minor and unlikely to introduce any issues with Landlock
or its security promises.
I feel that simply fixing this small bug is less regression risk than
reverting the entire 25 patch patchset and applying the latest V37
upstream patchset, which has undergone significant changes from mid
2020. I think its best we consume the newer patchset once it makes its
way into mainline in a future kernel instead.
If a regression were to occur, users could configure 2 LSMs instead of
all 3, or not enable Landlock.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: linux (Ubuntu Kinetic)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: jammy kinetic sts
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
- BugLink: https://bugs.launchpad.net/bugs/
+ BugLink: https://bugs.launchpad.net/bugs/1987998
[Impact]
The Ubuntu kernel carries an out of tree patchet, known as "LSM: Module
stacking for AppArmor" upstream, to enable stackable LSMs for
containers. The revision the Ubuntu kernel carries is an older one, from
2020, and has some slight divergences from the latest revision in
development.
One such divergence, is support for Landlock as a stackable LSM. When
the stackable LSM patchset was applied, Landlock was still in
development and not mainlined yet, and wasn't present in the earlier
revision of the "LSM: Module stacking for AppArmor" patchset. Support
for this was added by us.
There was a minor omission made during enabling support for Landlock.
The LSM slot type was marked as LSMBLOB_NEEDED, when it should have been
LSMBLOB_NOT_NEEDED.
Landlock itself does not provide any of the hooks that use a struct
lsmblob, such as secid_to_secctx, secctx_to_secid, inode_getsecid,
cred_getsecid, kernel_act_as task_getsecid_subj task_getsecid_obj and
ipc_getsecid.
When we set .slot = LSMBLOB_NEEDED, this indicates that we need an entry
in struct lsmblob, and we need to increment LSMBLOB_ENTRIES by one to
fit the entry into the secid array:
#define LSMBLOB_ENTRIES ( \
-(IS_ENABLED(CONFIG_SECURITY_SELINUX) ? 1 : 0) + \
-(IS_ENABLED(CONFIG_SECURITY_SMACK) ? 1 : 0) + \
-(IS_ENABLED(CONFIG_SECURITY_APPARMOR) ? 1 : 0) + \
-(IS_ENABLED(CONFIG_BPF_LSM) ? 1 : 0))
+ (IS_ENABLED(CONFIG_SECURITY_SELINUX) ? 1 : 0) + \
+ (IS_ENABLED(CONFIG_SECURITY_SMACK) ? 1 : 0) + \
+ (IS_ENABLED(CONFIG_SECURITY_APPARMOR) ? 1 : 0) + \
+ (IS_ENABLED(CONFIG_BPF_LSM) ? 1 : 0))
struct lsmblob {
-u32 secid[LSMBLOB_ENTRIES];
+ u32 secid[LSMBLOB_ENTRIES];
};
Currently, we don't increment LSMBLOB_ENTRIES by one to make an entry
for Landlock, so for the Ubuntu kernel, we can fit a maximum of two
entries, one for Apparmor and one for bpf.
If you try and configure three LSMs like so and reboot:
GRUB_CMDLINE_LINUX_DEFAULT="lsm=landlock,bpf,apparmor"
You will receive the following panic:
LSM: Security Framework initializing
landlock: Up and running.
LSM support for eBPF active
Kernel panic - not syncing: security_add_hooks Too many LSMs registered.
CPU: 0
[Kernel-packages] [Bug 1968062] Re: Jammy / Kinetic: Enable Hibernation for Xen Based Instance Types
Performing verification for Jammy.
I started one of each of the below instance types, trying to cover one
of all Xen based instance types:
c3.large, c4.large, i3.large, m3.medium, m4.large, r3.large, r4.large,
t2.medium.
Each instance had between 20 to 30gb of encrypted storage, and
hibernation was enabled in advanced settings.
>From there, I enabled -proposed, installed the 5.15.0-1019-aws kernel
and rebooted.
I checked to make sure the /swap-hibinit file was generated and the
correct size.
I started a screen session, and echod some text. I detached screen and
logged out.
I then used the AWS EC2 UI to Hibernate each instance. I waited a minute
for each instance to move to the stopped state.
>From there I started all instances.
I ssh'd into all instances and resumed my screen session.
All instance types with the 5.15.0-1019-aws kernel had successfully
hibernated and resumed, and my screen session was intact.
In my basic testing, the 5.15.0-1019-aws kernel can successfully
hibernate and resume on all Xen instance types. Happy to mark as
verified.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1968062
Title:
Jammy / Kinetic: Enable Hibernation for Xen Based Instance Types
Status in linux-aws package in Ubuntu:
Fix Committed
Status in linux-aws source package in Jammy:
Fix Committed
Status in linux-aws source package in Kinetic:
Fix Committed
Bug description:
[Impact]
Hibernation currently fails for all AWS Xen instance types
(c3/c4/i3/m3/m4/r3/r4/t2) with all Jammy 5.15 and Kinetic 5.19 linux-
aws kernels.
When attempting to hibernate, the system gets stuck in
sync_inodes_one_sb() when processing the rootfs, fails to hibernate,
and shuts down. When you start the instance, it starts fresh, and does
not resume from the incomplete hibernation image. Networking is also
broken, and you cannot ssh in.
Upon review of the jammy/linux-aws git log, it appears that the kernel
is missing AWS hibernation enablement patches entirely. These need to
be included to get hibernation working.
[Fix]
Hibernation currently works on the Amazon Linux 2 5.15 Kernel:
https://github.com/amazonlinux/linux/tree/amazon-5.15.y/mainline
After careful review of the amazon-5.15.y/mainline branch, we have
found the below set of patches authored by Amazon AWS Hibernation team
to be minimally sufficient to get hibernation working on both Jammy
5.15 and Kinetic 5.19.
xen: Restore xen-pirqs on resume from hibernation
xen-netfront: call netif_device_attach on resume
xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs.
xen: restore pirqs on resume from hibernation.
block: xen-blkfront: consider new dom0 features on restore
x86: tsc: avoid system instability in hibernation
xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq
Revert "xen: dont fiddle with event channel masking in suspend/resume"
PM / hibernate: update the resume offset on SNAPSHOT_SET_SWAP_AREA
x86/xen: close event channels for PIRQs in system core suspend callback
xen/events: add xen_shutdown_pirqs helper function
x86/xen: save and restore steal clock
xen/time: introduce xen_{save,restore}_steal_clock
xen-netfront: add callbacks for PM suspend and hibernation support
xen-blkfront: add callbacks for PM suspend and hibernation
x86/xen: add system core suspend and resume callbacks
x86/xen: Introduce new function to map HYPERVISOR_shared_info on Resume
xenbus: add freeze/thaw/restore callbacks support
xen/manage: introduce helper function to know the on-going suspend mode
xen/manage: keep track of the on-going suspend mode
These patches will be carried as SAUCE patches, and their subjects
marked with "UBUNTU: SAUCE [aws]". Their upstream is the Amazon
Hibernation team, with the repo being the Amazon Linux 2 kernel repo.
[Testcase]
1. Log into Amazon EC2.
2. Select Launch Instance.
3. Under Instance Type, select any from (c3/c4/i3/m3/m4/r3/r4/t2). I suggest
t2.medium.
4. Select the "Ubuntu 22.04 LTS HVM (SSD type)" AMI in the quicklaunch pane.
5. Select your SSH keypair.
6. In storage, select 20gb. Go to the advanced tab, and set Encrypted: Yes.
7. Under Advanced Settings for the instance, set "Stop - Hibernate" to Enable.
8. Create the Instance. SSH in.
9. Wait 5 minutes for hibinit-agent to create /swap-hibinit swapfile and
configure grub.
10. Start a screen session. Echo some text and then detach with ctrl-d.
11. Log out from instance.
12. In EC2, select "Instance State" > "Hibernate".
13. Wait 30 seconds to one minute. The state will go from "Stopping" to
"Stopped".
14. Start the instance again.
15. SSH in.
16. Attempt to resume screen session with "screen -r".
If you are not able to ssh into the instance, hibernation had failed.
If ssh works and the
[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
Hi Chris, I have some good news to share. Thanks to your detailed comments, I can reproduce the issue easily in my lab. Here is my reproducer: Start a fresh VM, either Jammy or Kinetic, just needs to use the Ubuntu -generic kernel. 1. Edit /etc/default/grub and append apparmor=0 to GRUB_CMDLINE_LINUX_DEFAULT 2. sudo update-grub 3. sudo apt update 4. sudo apt install auditd 5. Append the following to /etc/audit/rules.d/audit.rules: -a exit,always -F arch=b64 -S execve -a exit,always -F arch=b32 -S execve 6. sudo reboot 7. sudo apt install stress-ng 8. stress-ng --exec $(nproc) 9. Check the following for memory leaks: $ watch "sudo cat /proc/meminfo | grep SUnreclaim" $ watch "sudo cat /proc/slabinfo | grep kmalloc-2k" $ sudo slabtop At this point SUnreclaim will grow rapidly, at a rate of 3mb or so per second. If you leave it for a few minutes, it will consume hundreds of megabytes. I have been doing some testing, and the Jammy 5.15.0-46-generic and Kinetic 5.19.0-15-generic kernels are affected. I tried 5.15.0-25-generic as well, and it had the same issue. I tried mainline 5.15 and 5.19 from the Ubuntu mainline repo, but they did not reproduce the issue at all. Interesting. It currently looks like a custom Ubuntu SAUCE patch to either apparmor or audit is causing the memory leak. I'm going to start investigating this more deeply. For now, I think that you should run with apparmor=1 on the kernel command line as a workaround while we root cause and get this fixed. I'll keep you updated on what I find. Thanks, Matthew ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Tags added: jammy kinetic seg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987430 Title: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: Since updating to kernel 5.15.0-46-generic (package version 5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel memory; our first server with 8 GB of RAM just fatally OOMed, causing us to detect this. Inspection of OOM reports, /proc/meminfo, and /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k slabs: Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab info: Aug 23 12:51:11 cluster kernel: [361299.864757] Name Used Total [...] Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k 6676584KB6676596KB Most of our machines appear to be leaking slab memory at a rate of around 20 to 40 Mbytes/hour, with some machines leaking much faster; the champions are leaking kernel memory at 145 Mbytes/hour and 237 Mbytes/hour. We aren't running any proprietary kernel modules and our only unusual kernel configuration is that we've disabled AppArmor with 'apparmor=0' on the kernel command line. /proc/version_signature: Ubuntu 5.15.0-46.49-generic 5.15.39 Full kernel command line from the Dell R240 system that fatally OOMd: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 console=tty0 apparmor=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
Hi Chris, I stood up a Jammy VM, and tried with and without apparmor=0 on the kernel command line, for a few hours at a time. The /proc/slabinfo for kmalloc-2k and /proc/meminfo for unreclaimable slabs were stable and did not grow, so it must be related to your workload. What sort of workloads are running on your servers? If you stand up a fresh VM and minimally configure it, can you still see the kernel memory leak? Or do you need your workload to provoke it? If you do have a set of commands to reproduce the issue, please list them here. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987430 Title: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs Status in linux package in Ubuntu: Confirmed Bug description: Since updating to kernel 5.15.0-46-generic (package version 5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel memory; our first server with 8 GB of RAM just fatally OOMed, causing us to detect this. Inspection of OOM reports, /proc/meminfo, and /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k slabs: Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab info: Aug 23 12:51:11 cluster kernel: [361299.864757] Name Used Total [...] Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k 6676584KB6676596KB Most of our machines appear to be leaking slab memory at a rate of around 20 to 40 Mbytes/hour, with some machines leaking much faster; the champions are leaking kernel memory at 145 Mbytes/hour and 237 Mbytes/hour. We aren't running any proprietary kernel modules and our only unusual kernel configuration is that we've disabled AppArmor with 'apparmor=0' on the kernel command line. /proc/version_signature: Ubuntu 5.15.0-46.49-generic 5.15.39 Full kernel command line from the Dell R240 system that fatally OOMd: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 console=tty0 apparmor=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896350] Re: nbd: requests can become stuck when disconnecting from server with qemu-nbd
Performing verification for Focal. I started a fresh Focal VM, and installed qemu-utils. I then ran reproducer.sh from the testcase section. The kernel is 5.4.0-124-generic from -updates. Within 30 seconds of starting the reproducer, the testcase script hung, and the following was in dmesg: Aug 23 04:49:26 focal-nbd kernel: block nbd15: NBD_DISCONNECT Aug 23 04:49:26 focal-nbd kernel: block nbd15: Send disconnect failed -32 Aug 23 04:49:26 focal-nbd sudo[1804]: pam_unix(sudo:session): session closed for user root Aug 23 04:49:26 focal-nbd sudo[1807]: ubuntu : TTY=pts/0 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/qemu-nbd --connect=/dev/nbd15 --cache=writeback --format=qcow2 foo.img Aug 23 04:49:26 focal-nbd sudo[1807]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0) Aug 23 04:49:26 focal-nbd kernel: ldm_validate_partition_table(): Disk read failed. Aug 23 04:49:26 focal-nbd kernel: Dev nbd15: unable to read RDB block 0 Aug 23 04:49:26 focal-nbd kernel: nbd15: unable to read partition table Aug 23 04:49:56 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 30 seconds Aug 23 04:50:26 focal-nbd systemd-udevd[419]: nbd15: Worker [1198] processing SEQNUM=5582 is taking a long time Aug 23 04:50:27 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 60 seconds Aug 23 04:50:58 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 90 seconds Aug 23 04:51:29 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 120 seconds Aug 23 04:51:59 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 150 seconds Aug 23 04:52:26 focal-nbd systemd-udevd[419]: nbd15: Worker [1198] processing SEQNUM=5582 killed Aug 23 04:52:30 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 180 seconds Aug 23 04:53:27 focal-nbd kernel: INFO: task qemu-nbd:1815 blocked for more than 120 seconds. Aug 23 04:53:27 focal-nbd kernel: Not tainted 5.4.0-124-generic #140-Ubuntu Aug 23 04:53:27 focal-nbd kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 23 04:53:27 focal-nbd kernel: qemu-nbdD0 1815 1 0x Aug 23 04:53:27 focal-nbd kernel: Call Trace: Aug 23 04:53:27 focal-nbd kernel: __schedule+0x2e3/0x740 Aug 23 04:53:27 focal-nbd kernel: ? __kfifo_to_user_r+0xa0/0xa0 Aug 23 04:53:27 focal-nbd kernel: schedule+0x42/0xb0 Aug 23 04:53:27 focal-nbd kernel: blk_mq_freeze_queue_wait+0x4b/0xb0 Aug 23 04:53:27 focal-nbd kernel: ? __wake_up_pollfree+0x40/0x40 Aug 23 04:53:27 focal-nbd kernel: blk_mq_freeze_queue+0x1b/0x20 Aug 23 04:53:27 focal-nbd kernel: nbd_add_socket+0x5e/0x1d0 [nbd] Aug 23 04:53:27 focal-nbd kernel: nbd_ioctl+0x2f7/0x410 [nbd] Aug 23 04:53:27 focal-nbd kernel: blkdev_ioctl+0x383/0xa30 Aug 23 04:53:27 focal-nbd kernel: block_ioctl+0x3d/0x50 Aug 23 04:53:27 focal-nbd kernel: do_vfs_ioctl+0x407/0x670 Aug 23 04:53:27 focal-nbd kernel: ? putname+0x4a/0x50 Aug 23 04:53:27 focal-nbd kernel: ksys_ioctl+0x67/0x90 Aug 23 04:53:27 focal-nbd kernel: __x64_sys_ioctl+0x1a/0x20 Aug 23 04:53:27 focal-nbd kernel: do_syscall_64+0x57/0x190 Aug 23 04:53:27 focal-nbd kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Aug 23 04:53:27 focal-nbd kernel: RIP: 0033:0x7fd12b7573ab Aug 23 04:53:27 focal-nbd kernel: Code: Bad RIP value. Aug 23 04:53:27 focal-nbd kernel: RSP: 002b:7fd129fa2a18 EFLAGS: 0246 ORIG_RAX: 0010 Aug 23 04:53:27 focal-nbd kernel: RAX: ffda RBX: 0001 RCX: 7fd12b7573ab Aug 23 04:53:27 focal-nbd kernel: RDX: 000b RSI: ab00 RDI: 000d Aug 23 04:53:27 focal-nbd kernel: RBP: 7fd129fa2aa8 R08: R09: 0001 Aug 23 04:53:27 focal-nbd kernel: R10: R11: 0246 R12: 7fd129fa2ab0 Aug 23 04:53:27 focal-nbd kernel: R13: 000d R14: 1f40 R15: 7fd12b80 I then rebooted, enabled -proposed and installed kernel 5.4.0-125-generic. I left the reproducer.sh script running for a bit over an hour, and it was still running perfectly fine when I got back to it. Requests are still moving smoothly, and no longer getting stuck. The 5.4.0-125-generic kernel in -proposed fixes the issue. Happy to mark it verified. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896350 Title: nbd: requests can become stuck when disconnecting from server with qemu-nbd Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status
[Kernel-packages] [Bug 1968062] Re: Jammy / Kinetic: Enable Hibernation for Xen Based Instance Types
** Description changed:
[Impact]
Hibernation currently fails for all AWS Xen instance types
(c3/c4/i3/m3/m4/r3/r4/t2) with all Jammy 5.15 and Kinetic 5.19 linux-aws
kernels.
When attempting to hibernate, the system gets stuck in
sync_inodes_one_sb() when processing the rootfs, fails to hibernate, and
shuts down. When you start the instance, it starts fresh, and does not
resume from the incomplete hibernation image. Networking is also broken,
and you cannot ssh in.
Upon review of the jammy/linux-aws git log, it appears that the kernel
is missing AWS hibernation enablement patches entirely. These need to be
included to get hibernation working.
[Fix]
Hibernation currently works on the Amazon Linux 2 5.15 Kernel:
https://github.com/amazonlinux/linux/tree/amazon-5.15.y/mainline
After careful review of the amazon-5.15.y/mainline branch, we have found
the below set of patches authored by Amazon AWS Hibernation team to be
minimally sufficient to get hibernation working on both Jammy 5.15 and
Kinetic 5.19.
- x86: Disable KASLR when Xen is detected
xen: Restore xen-pirqs on resume from hibernation
xen-netfront: call netif_device_attach on resume
xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs.
xen: restore pirqs on resume from hibernation.
block: xen-blkfront: consider new dom0 features on restore
x86: tsc: avoid system instability in hibernation
xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq
Revert "xen: dont fiddle with event channel masking in suspend/resume"
PM / hibernate: update the resume offset on SNAPSHOT_SET_SWAP_AREA
x86/xen: close event channels for PIRQs in system core suspend callback
xen/events: add xen_shutdown_pirqs helper function
x86/xen: save and restore steal clock
xen/time: introduce xen_{save,restore}_steal_clock
xen-netfront: add callbacks for PM suspend and hibernation support
xen-blkfront: add callbacks for PM suspend and hibernation
x86/xen: add system core suspend and resume callbacks
x86/xen: Introduce new function to map HYPERVISOR_shared_info on Resume
xenbus: add freeze/thaw/restore callbacks support
xen/manage: introduce helper function to know the on-going suspend mode
xen/manage: keep track of the on-going suspend mode
These patches will be carried as SAUCE patches, and their subjects
marked with "UBUNTU: SAUCE [aws]". Their upstream is the Amazon
Hibernation team, with the repo being the Amazon Linux 2 kernel repo.
[Testcase]
1. Log into Amazon EC2.
2. Select Launch Instance.
3. Under Instance Type, select any from (c3/c4/i3/m3/m4/r3/r4/t2). I suggest
t2.medium.
4. Select the "Ubuntu 22.04 LTS HVM (SSD type)" AMI in the quicklaunch pane.
5. Select your SSH keypair.
6. In storage, select 20gb. Go to the advanced tab, and set Encrypted: Yes.
7. Under Advanced Settings for the instance, set "Stop - Hibernate" to Enable.
8. Create the Instance. SSH in.
9. Wait 5 minutes for hibinit-agent to create /swap-hibinit swapfile and
configure grub.
10. Start a screen session. Echo some text and then detach with ctrl-d.
11. Log out from instance.
12. In EC2, select "Instance State" > "Hibernate".
13. Wait 30 seconds to one minute. The state will go from "Stopping" to
"Stopped".
14. Start the instance again.
15. SSH in.
16. Attempt to resume screen session with "screen -r".
If you are not able to ssh into the instance, hibernation had failed. If
ssh works and the screen session is still running, hibernation was
successful.
Alternatively, the CPC team can run their Hibernation testsuite over
Jammy and Kinetic.
We have built test kernels for Jammy and Kinetic with the patches, and
they are available in the below ppa:
+ https://launchpad.net/~gerald-yang-tw/+archive/ubuntu/aws-hibernate-test
+
If you try and hibernate and resume with the test kernels, hibernation
is successful.
[Where problems could occur]
We are adding a significant amount of code to the Xen subsystem, spread
across many commits. This code has not been mainlined, and is instead
maintained out of tree by the Amazon AWS Hibernation team.
The changes target hibernation, block devices, and clock devices,
specific to those used on AWS Xen instances. Most of these patches have
been applied to Xenial, Bionic, Focal and other series for a long time,
but some patches are new for 5.15 onward.
The changes will only target linux-aws to try and limit regression risk
to AWS users, and any regressions will be limited to users of Xen based
instance types (c3/c4/i3/m3/m4/r3/r4/t2), covering both Xen 4.2 and Xen
4.11.
If a regression were to occur, the instance would likely fail to
hibernate, and at worst, write an incomplete hibernation image to the
swapfile. The kernel will see this on start, and instead of resuming
from the hibernation image, will start fresh. It is unlikely to
[Kernel-packages] [Bug 1968062] Re: Jammy / Kinetic: Enable Hibernation for Xen Based Instance Types
** Summary changed:
- jammy/linux-aws hibernation timeout on xen instances
+ Jammy / Kinetic: Enable Hibernation for Xen Based Instance Types
** Also affects: linux-aws (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Jammy)
Importance: Undecided => Critical
** Changed in: linux-aws (Ubuntu Kinetic)
Importance: Undecided => Critical
** Changed in: linux-aws (Ubuntu Jammy)
Assignee: (unassigned) => gerald.yang (gerald-yang-tw)
** Changed in: linux-aws (Ubuntu Kinetic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
- Hibernation testing of jammy/linux-aws 5.15.0-1003-aws is failing on all
- xen instance types (c3/c4/i3/m3/m4/r3/r4/t2). The failure happens while
- attempting to resume from the first attempt to hibernate. Testing on
- nitro instances types (c5/m5/r5/t3) all pass.
+ [Impact]
- After the resume, the system is inaccessible via ssh. The console
- screenshot does change, but the console log obtained from `aws ec2 get-
- console-output` does not.
+ Hibernation currently fails for all AWS Xen instance types
+ (c3/c4/i3/m3/m4/r3/r4/t2) with all Jammy 5.15 and Kinetic 5.19 linux-aws
+ kernels.
+
+ When attempting to hibernate, the system gets stuck in
+ sync_inodes_one_sb() when processing the rootfs, fails to hibernate, and
+ shuts down. When you start the instance, it starts fresh, and does not
+ resume from the incomplete hibernation image. Networking is also broken,
+ and you cannot ssh in.
+
+ Upon review of the jammy/linux-aws git log, it appears that the kernel
+ is missing AWS hibernation enablement patches entirely. These need to be
+ included to get hibernation working.
+
+ [Fix]
+
+ Hibernation currently works on the Amazon Linux 2 5.15 Kernel:
+ https://github.com/amazonlinux/linux/tree/amazon-5.15.y/mainline
+
+ After careful review of the amazon-5.15.y/mainline branch, we have found
+ the below set of patches authored by Amazon AWS Hibernation team to be
+ minimally sufficient to get hibernation working on both Jammy 5.15 and
+ Kinetic 5.19.
+
+ x86: Disable KASLR when Xen is detected
+ xen: Restore xen-pirqs on resume from hibernation
+ xen-netfront: call netif_device_attach on resume
+ xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs.
+ xen: restore pirqs on resume from hibernation.
+ block: xen-blkfront: consider new dom0 features on restore
+ x86: tsc: avoid system instability in hibernation
+ xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq
+ Revert "xen: dont fiddle with event channel masking in suspend/resume"
+ PM / hibernate: update the resume offset on SNAPSHOT_SET_SWAP_AREA
+ x86/xen: close event channels for PIRQs in system core suspend callback
+ xen/events: add xen_shutdown_pirqs helper function
+ x86/xen: save and restore steal clock
+ xen/time: introduce xen_{save,restore}_steal_clock
+ xen-netfront: add callbacks for PM suspend and hibernation support
+ xen-blkfront: add callbacks for PM suspend and hibernation
+ x86/xen: add system core suspend and resume callbacks
+ x86/xen: Introduce new function to map HYPERVISOR_shared_info on Resume
+ xenbus: add freeze/thaw/restore callbacks support
+ xen/manage: introduce helper function to know the on-going suspend mode
+ xen/manage: keep track of the on-going suspend mode
+
+ These patches will be carried as SAUCE patches, and their subjects
+ marked with "UBUNTU: SAUCE [aws]". Their upstream is the Amazon
+ Hibernation team, with the repo being the Amazon Linux 2 kernel repo.
+
+ [Testcase]
+
+ 1. Log into Amazon EC2.
+ 2. Select Launch Instance.
+ 3. Under Instance Type, select any from (c3/c4/i3/m3/m4/r3/r4/t2). I suggest
t2.medium.
+ 4. Select the "Ubuntu 22.04 LTS HVM (SSD type)" AMI in the quicklaunch pane.
+ 5. Select your SSH keypair.
+ 6. In storage, select 20gb. Go to the advanced tab, and set Encrypted: Yes.
+ 7. Under Advanced Settings for the instance, set "Stop - Hibernate" to Enable.
+ 8. Create the Instance. SSH in.
+ 9. Wait 5 minutes for hibinit-agent to create /swap-hibinit swapfile and
configure grub.
+ 10. Start a screen session. Echo some text and then detach with ctrl-d.
+ 11. Log out from instance.
+ 12. In EC2, select "Instance State" > "Hibernate".
+ 13. Wait 30 seconds to one minute. The state will go from "Stopping" to
"Stopped".
+ 14. Start the instance again.
+ 15. SSH in.
+ 16. Attempt to resume screen session with "screen -r".
+
+ If you are not able to ssh into the instance, hibernation had failed. If
+ ssh works and the screen session is still running, hibernation was
+ successful.
+
+ Alternativ
[Sts-sponsors] [Bug 1979933] Re: snmptrapd Segmentation Faults When Calling my_load_defaults()
Performing verification for Focal I install snmptrapd 5.8+dfsg-2ubuntu2.4 from updates, and edited /etc/snmp/snmptrapd.conf to have the following contents: disableAuthorization yes traphandle default /usr/bin/logger sqlMaxQueue 1 sqlSaveInterval 9 I disabled all snmptrapd services: $ sudo systemctl stop snmptrapd.service $ sudo systemctl stop snmpd.service and then tried to start snmptrapd, but received a segmentation fault: $ sudo /usr/sbin/snmptrapd -LOw -f Segmentation fault >From syslog: Aug 4 00:47:45 focal-snmp kernel: [ 1615.972207] snmptrapd[5293]: segfault at 8 ip 7f4879003680 sp 7ffe914993f0 error 4 in libmysqlclient.so.21.2.30[7f4878f93000+13] Aug 4 00:47:45 focal-snmp kernel: [ 1615.972229] Code: 5c 41 5d 41 5e 5d c3 e8 0e 17 f9 ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 55 48 89 e5 41 55 49 89 fd 41 54 53 48 83 ec 08 <4c> 8b 67 08 48 8b 47 10 4c 29 e0 48 83 f8 37 0f 86 cb 00 00 00 49 I then enabled -proposed and installed snmptrapd 5.8+dfsg-2ubuntu2.5. Again, I stopped the services: $ sudo systemctl stop snmptrapd.service $ sudo systemctl stop snmpd.service and tried to start snmptrapd: $ sudo /usr/sbin/snmptrapd -LOw -f mysql_real_connect() failed Error 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) This time we no longer segmentation fault, and snmptrapd keeps running. The package in -proposed fixes the issue, happy to mark verified. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1979933 Title: snmptrapd Segmentation Faults When Calling my_load_defaults() Status in net-snmp package in Ubuntu: Fix Released Status in net-snmp source package in Focal: Fix Committed Bug description: [Impact] When starting snmptrapd configured to connect to a mysql server, we segmentation fault when calling my_load_defaults(): $ sudo /usr/sbin/snmptrapd -LOw -f Segmentation fault (core dumped) (gdb) bt #0 0x7efd8d9f15b0 in MEM_ROOT::Alloc (length=56, this=this@entry=0x0) at ./include/my_alloc.h:157 #1 init_default_directories (alloc=alloc@entry=0x0) at ./mysys/my_default.cc:1632 #2 0x7efd8d9f817a in my_load_defaults (conf_file=0x7efd8e751f64 "my", groups=0x7efd8e7550c8, argc=0x7ffd8941b674, argv=0x7ffd8941b678, alloc=0x0, default_directories=0x555a8abccc00) at ./mysys/my_default.cc:692 #3 0x7efd8e74fe1b in netsnmp_mysql_init () from /lib/x86_64-linux-gnu/libnetsnmptrapd.so.35 #4 0x555a8a9e3873 in main (argc=, argv=) at snmptrapd.c:1196 What happens is that we are calling my_load_defaults() even though we have mysql_options(), and the arguments we pass into my_load_defaults() are NULL, which eventually get de-referenced. The fix is to change the configure script to only call my_load_defaults() if we don't have mysql_options(). [Testcase] $ sudo apt update $ sudo apt install snmp snmpd snmptrapd snmp-mibs-downloader Edit /etc/snmp/snmptrapd.conf and add the following entries: disableAuthorization yes traphandle default /usr/bin/logger sqlMaxQueue 1 sqlSaveInterval 9 Save and exit. It is easier to reproduce if you stop and disable all services: $ sudo systemctl stop snmptrapd.service $ sudo systemctl stop snmpd.service Then try running: $ sudo /usr/sbin/snmptrapd -LOw -f Segmentation fault (core dumped) There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf339433-test When running this test package, you will instead see: $ sudo /usr/sbin/snmptrapd -LOw -f mysql_real_connect() failed Error 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) (I don't have a mysql server configured, but we don't segfault anymore). [Where problems can occur] We are changing how snmptrapd initialises and begins connections to a mysql server, and if a regression were to occur, it would be limited to users of snmptrapd with the mysql backend. Other database backends would not be affected. Other binaries produced would also not be affected. [Other Info] The issue was fixed upstream by the following commit: commit 011342d8e453b9e0585bf77f659d80c648df8c9f Author: Bart Van Assche Date: Sat Aug 18 09:28:14 2018 -0700 Subject: snmptrapd: Let configure check for mysql_options() Link: https://github.com/net-snmp/net-snmp/commit/011342d8e453b9e0585bf77f659d80c648df8c9f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1979933/+subscriptions -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
[Sts-sponsors] [Bug 1979933] Re: snmptrapd Segmentation Faults When Calling my_load_defaults()
The new upload in the -unapproved upload queue has been bumped by a security update, and so, attaching a new debdiff rebased to the current package in -updates and -security. Mauricio, could you please sponsor the new debdiff? I took the feedback on Description field formatting into account, should be fixed on this debdiff. ** Patch added: "Debdiff for net-snmp for Focal V2" https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1979933/+attachment/5606368/+files/lp1979933_focal_V2.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1979933 Title: snmptrapd Segmentation Faults When Calling my_load_defaults() Status in net-snmp package in Ubuntu: Fix Released Status in net-snmp source package in Focal: In Progress Bug description: [Impact] When starting snmptrapd configured to connect to a mysql server, we segmentation fault when calling my_load_defaults(): $ sudo /usr/sbin/snmptrapd -LOw -f Segmentation fault (core dumped) (gdb) bt #0 0x7efd8d9f15b0 in MEM_ROOT::Alloc (length=56, this=this@entry=0x0) at ./include/my_alloc.h:157 #1 init_default_directories (alloc=alloc@entry=0x0) at ./mysys/my_default.cc:1632 #2 0x7efd8d9f817a in my_load_defaults (conf_file=0x7efd8e751f64 "my", groups=0x7efd8e7550c8, argc=0x7ffd8941b674, argv=0x7ffd8941b678, alloc=0x0, default_directories=0x555a8abccc00) at ./mysys/my_default.cc:692 #3 0x7efd8e74fe1b in netsnmp_mysql_init () from /lib/x86_64-linux-gnu/libnetsnmptrapd.so.35 #4 0x555a8a9e3873 in main (argc=, argv=) at snmptrapd.c:1196 What happens is that we are calling my_load_defaults() even though we have mysql_options(), and the arguments we pass into my_load_defaults() are NULL, which eventually get de-referenced. The fix is to change the configure script to only call my_load_defaults() if we don't have mysql_options(). [Testcase] $ sudo apt update $ sudo apt install snmp snmpd snmptrapd snmp-mibs-downloader Edit /etc/snmp/snmptrapd.conf and add the following entries: disableAuthorization yes traphandle default /usr/bin/logger sqlMaxQueue 1 sqlSaveInterval 9 Save and exit. It is easier to reproduce if you stop and disable all services: $ sudo systemctl stop snmptrapd.service $ sudo systemctl stop snmpd.service Then try running: $ sudo /usr/sbin/snmptrapd -LOw -f Segmentation fault (core dumped) There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf339433-test When running this test package, you will instead see: $ sudo /usr/sbin/snmptrapd -LOw -f mysql_real_connect() failed Error 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) (I don't have a mysql server configured, but we don't segfault anymore). [Where problems can occur] We are changing how snmptrapd initialises and begins connections to a mysql server, and if a regression were to occur, it would be limited to users of snmptrapd with the mysql backend. Other database backends would not be affected. Other binaries produced would also not be affected. [Other Info] The issue was fixed upstream by the following commit: commit 011342d8e453b9e0585bf77f659d80c648df8c9f Author: Bart Van Assche Date: Sat Aug 18 09:28:14 2018 -0700 Subject: snmptrapd: Let configure check for mysql_options() Link: https://github.com/net-snmp/net-snmp/commit/011342d8e453b9e0585bf77f659d80c648df8c9f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1979933/+subscriptions -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] Please review and sponsor net-snmp for LP #1979933 for AT
Hi Dariusz, Heitor, Maurico, Could I please get this debdiff reviewed and sponsored? AT have been asking for it. https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1979933 Thanks, Matthew On Tue, Jul 5, 2022 at 10:44 AM Matthew Ruffell wrote: > > Hi everyone, > > Can you please review and sponsor LP #1979933, net-snmp? > > https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1979933 > > AT are happy with their test package and it fixes the issue for them. > > It is another straightforward SRU. > > Thanks, > Matthew -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896350] Re: nbd: requests can become stuck when disconnecting from server with qemu-nbd
Performing verification for Jammy. I created a new Jammy VM, and installed qemu-utils. The kernel is 5.15.0-41-generic from -updates. I ran my reproducer.sh script from the testcase, and within a minute, the nbd request got stuck, and we started seeing hung task timeout oops messages in dmesg: Jul 20 04:56:20 jammy-nbd kernel: block nbd15: NBD_DISCONNECT Jul 20 04:56:20 jammy-nbd kernel: block nbd15: Send disconnect failed -32 Jul 20 04:56:20 jammy-nbd sudo[5267]: pam_unix(sudo:session): session closed for user root Jul 20 04:56:20 jammy-nbd sudo[5271]: ubuntu : TTY=pts/0 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/qemu-nbd --connect=/dev/nbd15 --cache=writeback --format=qcow2 foo.img Jul 20 04:56:20 jammy-nbd sudo[5271]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) Jul 20 04:56:20 jammy-nbd kernel: ldm_validate_partition_table(): Disk read failed. Jul 20 04:56:20 jammy-nbd kernel: Dev nbd15: unable to read RDB block 0 Jul 20 04:56:20 jammy-nbd kernel: nbd15: unable to read partition table Jul 20 04:56:51 jammy-nbd kernel: block nbd15: Possible stuck request 64946bb4: control (read@524087296,65536B). Runtime 30 seconds Jul 20 04:57:19 jammy-nbd systemd-udevd[440]: nbd15: Worker [2561] processing SEQNUM=3062 is taking a long time Jul 20 04:57:21 jammy-nbd kernel: block nbd15: Possible stuck request 64946bb4: control (read@524087296,65536B). Runtime 60 seconds Jul 20 04:57:52 jammy-nbd kernel: block nbd15: Possible stuck request 64946bb4: control (read@524087296,65536B). Runtime 90 seconds Jul 20 04:58:23 jammy-nbd kernel: block nbd15: Possible stuck request 64946bb4: control (read@524087296,65536B). Runtime 120 seconds Jul 20 04:58:23 jammy-nbd kernel: INFO: task qemu-nbd:5280 blocked for more than 120 seconds. Jul 20 04:58:23 jammy-nbd kernel: Not tainted 5.15.0-41-generic #44-Ubuntu Jul 20 04:58:23 jammy-nbd kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 20 04:58:23 jammy-nbd kernel: task:qemu-nbdstate:D stack:0 pid: 5280 ppid: 1 flags:0x0002 Jul 20 04:58:23 jammy-nbd kernel: Call Trace: Jul 20 04:58:23 jammy-nbd kernel: Jul 20 04:58:23 jammy-nbd kernel: __schedule+0x23d/0x590 Jul 20 04:58:23 jammy-nbd kernel: ? call_rcu+0xe/0x10 Jul 20 04:58:23 jammy-nbd kernel: schedule+0x4e/0xb0 Jul 20 04:58:23 jammy-nbd kernel: blk_mq_freeze_queue_wait+0x69/0xa0 Jul 20 04:58:23 jammy-nbd kernel: ? wait_woken+0x70/0x70 Jul 20 04:58:23 jammy-nbd kernel: blk_mq_freeze_queue+0x1b/0x30 Jul 20 04:58:23 jammy-nbd kernel: nbd_add_socket+0x76/0x1f0 [nbd] Jul 20 04:58:23 jammy-nbd kernel: __nbd_ioctl+0x18b/0x340 [nbd] Jul 20 04:58:23 jammy-nbd kernel: ? security_capable+0x3d/0x60 Jul 20 04:58:23 jammy-nbd kernel: nbd_ioctl+0x81/0xb0 [nbd] Jul 20 04:58:23 jammy-nbd kernel: blkdev_ioctl+0x12e/0x270 Jul 20 04:58:23 jammy-nbd kernel: ? __fget_files+0x86/0xc0 Jul 20 04:58:23 jammy-nbd kernel: block_ioctl+0x46/0x50 Jul 20 04:58:23 jammy-nbd kernel: __x64_sys_ioctl+0x91/0xc0 Jul 20 04:58:23 jammy-nbd kernel: do_syscall_64+0x5c/0xc0 Jul 20 04:58:23 jammy-nbd kernel: ? exit_to_user_mode_prepare+0x37/0xb0 Jul 20 04:58:23 jammy-nbd kernel: ? syscall_exit_to_user_mode+0x27/0x50 Jul 20 04:58:23 jammy-nbd kernel: ? __x64_sys_recvmsg+0x1d/0x20 Jul 20 04:58:23 jammy-nbd kernel: ? do_syscall_64+0x69/0xc0 Jul 20 04:58:23 jammy-nbd kernel: ? syscall_exit_to_user_mode+0x27/0x50 Jul 20 04:58:23 jammy-nbd kernel: ? __x64_sys_recvmsg+0x1d/0x20 Jul 20 04:58:23 jammy-nbd kernel: ? do_syscall_64+0x69/0xc0 Jul 20 04:58:23 jammy-nbd kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Jul 20 04:58:23 jammy-nbd kernel: RIP: 0033:0x7f6c47e47aff Jul 20 04:58:23 jammy-nbd kernel: RSP: 002b:7f6c464d1820 EFLAGS: 0246 ORIG_RAX: 0010 Jul 20 04:58:23 jammy-nbd kernel: RAX: ffda RBX: 0001 RCX: 7f6c47e47aff Jul 20 04:58:23 jammy-nbd kernel: RDX: 0009 RSI: ab00 RDI: 000b Jul 20 04:58:23 jammy-nbd kernel: RBP: 7f6c464d1910 R08: R09: 0001 Jul 20 04:58:23 jammy-nbd kernel: R10: R11: 0246 R12: 000b Jul 20 04:58:23 jammy-nbd kernel: R13: 7f6c464d1900 R14: 1f40 R15: 7f6c3c000b90 Jul 20 04:58:23 jammy-nbd kernel: I then rebooted, and enabled -proposed and installed the 5.15.0-43-generic kernel. I started the reproducer.sh script and left it to run for an hour. At the end of the hour, the script was still running strong. Requests no longer get stuck when we issue NBD_DISCONNECT, and the issue is solved. The kernel in -proposed fixes the issue, happy to mark verified. ** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1896350] Re: nbd: requests can become stuck when disconnecting from server with qemu-nbd
Fix released for linux-azure:
linux-azure (5.4.0-1086.91)
linux-azure (5.15.0.1014.17)
Marking back to Fix Committed for Jammy and In progress for Focal to
track progress in -generic variants.
** Changed in: linux (Ubuntu Jammy)
Status: Fix Released => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896350
Title:
nbd: requests can become stuck when disconnecting from server with
qemu-nbd
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Won't Fix
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
Won't Fix
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Released
Bug description:
BugLink: https://bugs.launchpad.net/bugs/1896350
[Impact]
After 2516ab1("nbd: only clear the queue on device teardown"), present
in 4.12-rc1 onward, the ioctl NBD_CLEAR_SOCK can no longer clear
requests currently being processed. This change was made to fix a race
between using the NBD_CLEAR_SOCK ioctl to clear requests, and teardown
of the device clearing requests. This worked for the most part, as
several years ago systemd was not set up to watch nbd devices for
changes in their state.
But after:
commit f82abfcda58168d9f667e2094d438763531d3fa6
From: Tony Asleson
Date: Fri, 8 Feb 2019 15:47:10 -0600
Subject: rules: watch metadata changes on nbd devices
Link:
https://github.com/systemd/systemd/commit/f82abfcda58168d9f667e2094d438763531d3fa6
in systemd v242-rc1, nbd* devices were added to a udev rule to watch
those devices for changes with the inotify subsystem. From man udev:
> watch
> Watch the device node with inotify; when the node is closed after being
> opened for writing, a change uevent is synthesized.
>
> nowatch
> Disable the watching of a device node with inotify.
This changed the behaviour of device teardown, since systemd now keeps
tabs on the device with inotify, outstanding requests cannot be
cleared as nbd_xmit_timeout() will always return 'BLK_EH_RESET_TIMER',
and requests get stuck, never to complete, because a disconnect has
occurred, and never to timeout, as their timers keep being reset.
Symptoms of this issue is that the nbd subsystem gets stuck with
messages like:
block nbd15: NBD_DISCONNECT
block nbd15: Send disconnect failed -32
...
block nbd15: Possible stuck request 7fcf62ba: control
(read@523915264,24576B). Runtime 30 seconds
...
block nbd15: Possible stuck request 7fcf62ba: control
(read@523915264,24576B). Runtime 150 seconds
...
INFO: task qemu-nbd:1267 blocked for more than 120 seconds.
Not tainted 5.15.0-23-generic #23-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:qemu-nbdstate:D stack:0 pid: 1267 ppid: 1
flags:0x0002
Call Trace:
__schedule+0x23d/0x590
? call_rcu+0xe/0x10
schedule+0x4e/0xb0
blk_mq_freeze_queue_wait+0x69/0xa0
? wait_woken+0x70/0x70
blk_mq_freeze_queue+0x1b/0x30
nbd_add_socket+0x76/0x1f0 [nbd]
__nbd_ioctl+0x18b/0x340 [nbd]
? security_capable+0x3d/0x60
nbd_ioctl+0x81/0xb0 [nbd]
blkdev_ioctl+0x12e/0x270
? __fget_files+0x86/0xc0
block_ioctl+0x46/0x50
__x64_sys_ioctl+0x91/0xc0
do_syscall_64+0x5c/0xc0
entry_SYSCALL_64_after_hwframe+0x44/0xae
Additionally, in syslog you will also see systemd-udevd get stuck:
systemd-udevd[419]: nbd15: Worker [2004] processing SEQNUM=5661 is
taking a long time
$ ps aux
...
4191194 root D 0.1 systemd-udevd -
We can workaround the issue by adding a higher priority udev rule to
not watch nbd* devices.
$ cat << EOF >> /etc/udev/rules.d/97-nbd-device.rules
# Disable inotify watching of change events for NBD devices
ACTION=="add|change", KERNEL=="nbd*", OPTIONS:="nowatch"
EOF
$ sudo udevadm control --reload-rules
$ sudo udevadm trigger
[Fix]
The fix relies on infrastructure provided by the flag
NBD_CMD_INFLIGHT, which was introduced in 5.16, and added to in 5.19.
We need to backport all commits related to NBD_CMD_INFLIGHT to our
kernels for the fix to be effective.
For Focal, Impish and Jammy:
commit 4e6eef5dc25b528e08ac5b5f64f6ca9d9987241d
Author: Yu Kuai
Date: Thu Sep 16 17:33:44 2021 +0800
Subject: nbd: don't handle response without a corresponding request message
Link:
https://github.com/torvalds/linux/commit/4e6eef5dc25b528e08ac5b5f64f6ca9d9987241d
commit 07175cb1baf4c51051b1fbd391097e349f9a02a9
Author: Yu Kuai
Date: Thu Sep 16 17:33:45 2021 +0800
Subject: nbd: make sure request completion won't concurrent
Link:
[Sts-sponsors] Please review and sponsor LP1968742 hwloc for Nvidia
Hi Everyone, Could you please review and sponsor: https://bugs.launchpad.net/ubuntu/+source/hwloc/+bug/1968742 It has a very straightforward test case, and the patch is also very straightforward. Kinetic already has the patch and Focal, Impish are not affected, Again, I really need to apply for SRU developer or coredev membership Thanks, Matthew -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978423] [NEW] cifs: Double free in cifs_smb3_do_mount() when mount fails in cifs_get_root()
Public bug reported:
BugLink: https://bugs.launchpad.net/bugs/1978423
[Impact]
When attempting to mount a cifs share, and it fails while the kernel is
attempting to get the root inode, typically in cifs_get_root(), a double
free can occur leading to a general protection fault which panics the
system.
For example, if we try to mount a cifs share with an out of date
kerberos ticket:
[ 479.783182] CIFS: Attempting to mount \\cifs-host\cifs-share
[ 479.791769] CIFS: VFS: Verify user has a krb5 ticket and keyutils is
installed
[ 479.791774] CIFS: VFS: \\cifs-host Send error in SessSetup = -126
[ 479.791777] CIFS: VFS: cifs_read_super: get root inode failed
We hit a general protection fault:
[ 479.826541] general protection fault, probably for non-canonical address
0x2a8e69ddd8028c0: [#1] SMP NOPTI
[ 479.826546] CPU: 9 PID: 8826 Comm: nautilus Kdump: loaded Tainted: P
OE 5.11.0-40-generic #44~20.04.2-Ubuntu
[ 479.826549] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference
Platform, BIOS VMW71.00V.18227214.B64.2106252220 06/25/2021
[ 479.826551] RIP: 0010:kfree+0x5d/0x420
[ 479.826574] CR2: 559ba2c12000 CR3: 002160152002 CR4: 007706e0
[ 479.826597] Call Trace:
[ 479.826598]
[ 479.826603] smb3_cleanup_fs_context_contents.part.0+0x19/0xc0 [cifs]
[ 479.826660] smb3_cleanup_fs_context+0x18/0x30 [cifs]
[ 479.826694] delayed_free+0x1f/0x30 [cifs]
[ 479.826720] rcu_core+0x32a/0x500
[ 479.826725] rcu_core_si+0xe/0x10
[ 479.826727] __do_softirq+0xe0/0x29b
[ 479.826731] asm_call_irq_on_stack+0xf/0x20
[ 479.826734]
[ 479.826735] do_softirq_own_stack+0x3d/0x50
[ 479.826739] irq_exit_rcu+0xa4/0xb0
[ 479.826743] sysvec_apic_timer_interrupt+0x3d/0x90
[ 479.826748] ? asm_sysvec_apic_timer_interrupt+0xa/0x20
[ 479.826750] asm_sysvec_apic_timer_interrupt+0x12/0x20
[ 479.826753] RIP: 0033:0x7f410e544e98
[Fix]
The issue happens because we fall through a goto label, and free the
same cifs_sb->ctx pointer twice. The first happens when we fall through
out_super to out:
790 struct dentry *
791 cifs_smb3_do_mount(struct file_system_type *fs_type,
792 int flags, struct smb3_fs_context *old_ctx)
793 {
...
883 out_super:
884 deactivate_locked_super(sb);
885 out:
886 if (cifs_sb) {
887 kfree(cifs_sb->prepath);
888 smb3_cleanup_fs_context(cifs_sb->ctx);
889 kfree(cifs_sb);
890 }
891 return root;
892 }
The second happens in deactivate_locked_super() when we eventually make
way to delayed_free() after many function calls inbetween:
3779 static void delayed_free(struct rcu_head *p)
3780 {
3781 struct cifs_sb_info *cifs_sb = container_of(p, struct cifs_sb_info,
rcu);
3782
3783 unload_nls(cifs_sb->local_nls);
3784 smb3_cleanup_fs_context(cifs_sb->ctx);
3785 kfree(cifs_sb);
3786 }
smb3_cleanup_fs_context() frees cifs_sb->ctx, as well as all of its
pointers in the struct.
I came across the following mailing list discussion about a double free
occurring during cifs_smb3_do_mount() when we fail to get a reference to
a root dentry [2][3].
[2] https://www.spinics.net/lists/linux-cifs/msg24485.html
[3] https://www.spinics.net/lists/linux-cifs/msg24486.html
For the mailing list discussion, there is a patch submitted [4], and it
was merged into mainline in 5.17-rc5 in the below commit:
[4] https://www.spinics.net/lists/linux-cifs/msg24487.html
commit 3d6cc9898efdfb062efb74dc18cfc700e082f5d5
Author: Ronnie Sahlberg
Date: Fri Feb 11 02:59:15 2022 +1000
Subject: cifs: fix double free race when mount fails in cifs_get_root()
Link:
https://github.com/torvalds/linux/commit/3d6cc9898efdfb062efb74dc18cfc700e082f5d5
This was fixed-released in 5.13.0-48-generic and 5.15.0-23-generic.
[Testcase]
Attempt to mount a cifs share where it would fail during the initial
mount, e.g. attempting to mount a cifs share with kerberos
authentication, with an out of date or invalid kerberos ticket.
[Where problems could occur]
The fix adds a return to the out_super label, to prevent fallthrough to
out. All resources will still be cleaned up correctly through the call
to deactivate_locked_super(), which will eventually reach delayed_free()
and free the resources there, so there won't be any memory leaks of any
sort that arise due to the patch.
If a regression were to occur, it would affect users of cifs mounts,
that error out and fail during the initial mounting stage.
A workaround would be to correct the issue that prevents mount in the
first place, so it would avoid the teardown code on mount failure.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Impish)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Fix Released
** Tags: sts
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Also affects: linux (Ubuntu Impish)
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
Hi Prudhvi, We might be chasing a different issue than just IOMMU being on. Do you have the same symptoms as Henning? You might be better off filing a new bug and we can debug your issues specifically. Henning, are you still building your own kernels? Are things better on the recently released 5.19-rc1? Are you able to try a clean install of 22.04? Did everything work fine under 21.10? Henning, there is a new kernel in -proposed, 5.15.0-36-generic, where IOMMU is disabled again by default, and it should clear up the IOMMU issues people are having. It should be released around the 20th, give or take a few days if any CVEs turn up. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To
[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
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976125 Title: The webcam image displayed has problems Status in linux package in Ubuntu: Confirmed Bug description: i try open cheese webcam but image displayed has problems. i try another webcam app like Guvcview can display image normally ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 Uname: Linux 5.17.9-xanmod1 x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 28 03:16:15 2022 InstallationDate: Installed on 2022-05-27 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220524) MachineType: Dell Inc. Inspiron 3442 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2020 dmi.bios.release: 65.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0T57PC dmi.board.vendor: Dell Inc. dmi.board.version: A16 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0T57PC:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651: dmi.product.name: Inspiron 3442 dmi.product.sku: 0651 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-27 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220524) NonfreeKernelModules: wl Package: linux (not installed) Tags: jammy wayland-session Uname: Linux 5.17.9-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-27 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220524) NonfreeKernelModules: wl Package: linux (not installed) Tags: jammy wayland-session Uname: Linux 5.18.0-051800-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: may 957 F wireplumber /dev/snd/controlC0: may 957 F wireplumber /dev/snd/seq:may 955 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-27 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220524) MachineType: Dell Inc. Inspiron 3442 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=66fdd066-3dea-4636-91d9-699dadf894ce ro quiet splash mitigation=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy wayland-session Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/02/2020 dmi.bios.release: 65.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0T57PC dmi.board.vendor: Dell Inc. dmi.board.version: A16 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified
[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
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975811 Title: cheese image gray with werical strips Status in linux package in Ubuntu: Confirmed Bug description: corrado@corrado-n2-jammy:~$ Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Missing chrome or resource URL: resource://gre/modules/UpdateListener.jsm Missing chrome or resource URL: resource://gre/modules/UpdateListener.mjs Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu May 26 11:41:07 2022 InstallationDate: Installed on 2022-04-23 (32 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: corrado1745 F pulseaudio /dev/snd/controlC0: corrado1745 F pulseaudio CRDA: N/A CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (32 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=f6e13096-f42d-4b60-af9c-bfeccec1808b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3
[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
Re: [Sts-sponsors] ec2-hibinit-agent
Thank you Dan. Heitor, can you please go ahead and get B -> J on the upload queue? It would be great if you could, hopefully AWS aren't watching the SLA timer too closely. Dan, I will apply for coredev. I will stop dragging my feet and start preparing an application. Thanks, Matthew On Fri, May 20, 2022 at 2:09 AM Dan Streetman wrote: > > uploaded to kinetic! > > And *ahem* maybe one of you should think about applying for coredev > soon, you know just in case i get hit by a bus or something :-) -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] Please review and sponsor LP1968805 ec2-hibinit-agent for Amazon AWS
Just a friendly ping. Can I please get these debdiffs reviewed and sponsored? The patch has been accepted upstream, and it should do the trick. Thanks, Matthew On Wed, May 11, 2022 at 5:37 PM Matthew Ruffell wrote: > > Hi everyone, > > AWS EC2 engineering teams have reviewed the patch, and have merged the > commit to upstream now. > > https://github.com/aws/amazon-ec2-hibinit-agent/pull/22 > > 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 > > I have uploaded fresh debdiffs to the launchpad bug to account for > minor version changes due to kinetic being the newest development > release, and added the correct forwarded tag. > > Can you please review and sponsor the changes? > > Thanks, > Matthew > > On Thu, Apr 28, 2022 at 3:35 AM Mauricio Faria de Oliveira > wrote: > > > > Hey Matthew, > > > > Sorry for the delay in getting to this. My own opinion below: > > > > Yes, I believe that having positive reviews and QA from upstream would be > > ideal, > > and since upstream is AWS themselves, it'd seem to fit a WoCustomer status > > (although admittedly this is the first time I see this scenario :-) > > > > cheers, > > > > On Wed, Apr 27, 2022 at 2:52 AM Matthew Ruffell > > wrote: > > > > > > Upstream has responded that they have seen the pull request, and they are > > > going > > > to assign it to one of their engineers to review: > > > > > > > Thanks for reporting and putting together a patch - the engineering > > > > team in > > > > EC2 that maintains the agent is aware of the patch and are prioritizing > > > > testing it. I'll ask them to give you an ETA when they have one. > > > > > > https://github.com/aws/amazon-ec2-hibinit-agent/issues/20#issuecomment-1104679221 > > > > > > Do you want to wait until we get a positive review from upstream? I > > > suppose we > > > can tell AWS that the case can be WoCus while we are waiting for upstream > > > to > > > review, and it will pause the SLA timer. > > > > > > On Thu, Apr 21, 2022 at 5:54 PM Matthew Ruffell > > > wrote: > > > > > > > > Hi everyone, > > > > > > > > Could you please review LP #1968805 [1], and sponsor the uploads if it > > > > looks > > > > okay? > > > > > > > > [1] > > > > https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805 > > > > > > > > I think bumping the priority to 32767 is the best solution for this > > > > particular > > > > case, since it would be higher than priorities users would be using in > > > > the wild, > > > > if they happen to have multiple swapfiles configured. > > > > > > > > I have submitted the patches upstream, but no word back. The upstream > > > > is AWS > > > > though, so maybe I might be able to put the SLA on hold for feedback > > > > there, > > > > but otherwise, we have about one month left on the SLA to get this > > > > fixed, so > > > > I wasn't going to wait. > > > > > > > > I did ask the CPC team about their feelings on the patches, but I > > > > didn't get > > > > much of a response other than from Chris Newcomer in the CPC channel. > > > > > > > > If you were going to test this for yourself, best stick with Focal for > > > > the > > > > moment, as Jammy is broken on xen instance types, and is being tracked > > > > separately in > > > > https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062 > > > > > > > > Let me know if you have any feedback, or think this should be fixed in a > > > > different way. > > > > > > > > And yes, Dan, this is probably a duplicate of > > > > https://bugs.launchpad.net/bugs/1910252 > > > > where the real root cause is that systemd blindly hibernates to the > > > > highest > > > > priority swapfile, as it has no way to know what resume device and > > > > offset the > > > > kernel is configured to resume from. SRUing such a change might be > > > > difficult > > > > as those who accept the standard behaviour wo
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To
[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
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage
[Desktop-packages] [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 Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in Cheese: Unknown Status in OEM Priority Project: Confirmed Status in cheese package in Ubuntu: Invalid Status in clutter-gst-3.0 package in Ubuntu: Fix Released Status in clutter-gst-3.0 source package in Jammy: Fix Committed Bug description: Impact == The cheese app is unusable with color bands showing in the main view. This bug doesn't affect all webcams. It's unknown what percentage of webcams are affected. Test Case On a system that experiences this bug: Install the update Run the cheese app Verify that the main view shows what your webcam can see normally. Click the camera button in the bottom toolbar area. Check if the photo looks normal. You can find it in ~/Pictures/Webcam What Could Go Wrong === Only 4 apps in Ubuntu use clutter-gst: empathy, cheese, lyricue, pinpoint clutter-gst has been archived by GNOME. (It's recommended for apps to use GTK4 instead of GTK3 + Clutter). That means it's not possible for this patch to be accepted upstream. Instead, distros like Arch Linux are applying this patch. This patch removes 2 renderers that don't work (RGBx and BGRx) but still keeps ones that do work: RGBA and BRGA. Original Bug Report === The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug
[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
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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
[Kernel-packages] [Bug 1971699] Re: disable Intel DMA remapping by default
** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] Please review and sponsor LP1968805 ec2-hibinit-agent for Amazon AWS
Hi everyone, AWS EC2 engineering teams have reviewed the patch, and have merged the commit to upstream now. https://github.com/aws/amazon-ec2-hibinit-agent/pull/22 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 I have uploaded fresh debdiffs to the launchpad bug to account for minor version changes due to kinetic being the newest development release, and added the correct forwarded tag. Can you please review and sponsor the changes? Thanks, Matthew On Thu, Apr 28, 2022 at 3:35 AM Mauricio Faria de Oliveira wrote: > > Hey Matthew, > > Sorry for the delay in getting to this. My own opinion below: > > Yes, I believe that having positive reviews and QA from upstream would be > ideal, > and since upstream is AWS themselves, it'd seem to fit a WoCustomer status > (although admittedly this is the first time I see this scenario :-) > > cheers, > > On Wed, Apr 27, 2022 at 2:52 AM Matthew Ruffell > wrote: > > > > Upstream has responded that they have seen the pull request, and they are > > going > > to assign it to one of their engineers to review: > > > > > Thanks for reporting and putting together a patch - the engineering team > > > in > > > EC2 that maintains the agent is aware of the patch and are prioritizing > > > testing it. I'll ask them to give you an ETA when they have one. > > > > https://github.com/aws/amazon-ec2-hibinit-agent/issues/20#issuecomment-1104679221 > > > > Do you want to wait until we get a positive review from upstream? I suppose > > we > > can tell AWS that the case can be WoCus while we are waiting for upstream to > > review, and it will pause the SLA timer. > > > > On Thu, Apr 21, 2022 at 5:54 PM Matthew Ruffell > > wrote: > > > > > > Hi everyone, > > > > > > Could you please review LP #1968805 [1], and sponsor the uploads if it > > > looks > > > okay? > > > > > > [1] > > > https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805 > > > > > > I think bumping the priority to 32767 is the best solution for this > > > particular > > > case, since it would be higher than priorities users would be using in > > > the wild, > > > if they happen to have multiple swapfiles configured. > > > > > > I have submitted the patches upstream, but no word back. The upstream is > > > AWS > > > though, so maybe I might be able to put the SLA on hold for feedback > > > there, > > > but otherwise, we have about one month left on the SLA to get this fixed, > > > so > > > I wasn't going to wait. > > > > > > I did ask the CPC team about their feelings on the patches, but I didn't > > > get > > > much of a response other than from Chris Newcomer in the CPC channel. > > > > > > If you were going to test this for yourself, best stick with Focal for the > > > moment, as Jammy is broken on xen instance types, and is being tracked > > > separately in > > > https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062 > > > > > > Let me know if you have any feedback, or think this should be fixed in a > > > different way. > > > > > > And yes, Dan, this is probably a duplicate of > > > https://bugs.launchpad.net/bugs/1910252 > > > where the real root cause is that systemd blindly hibernates to the > > > highest > > > priority swapfile, as it has no way to know what resume device and offset > > > the > > > kernel is configured to resume from. SRUing such a change might be > > > difficult > > > as those who accept the standard behaviour would have to manually update > > > their > > > configuration on their systems to tell systemd what swapfile to hibernate > > > to. > > > > > > I think talking with upstream systemd will go past the 1 month left on > > > the SLA, > > > and so these straightforward patches to ec2-hibinit-agent are probably > > > the best > > > low risk way to work around the bug, and fix AWS users. > > > > > > PS, our ec2-hibinit-agent package diverged from upstream long ago, and the > > > foundations team appear to be happy carrying patches not upstreamed. > > > > > > Thanks, > > > Matthew > > > > -- > > Mailing list: https://launchpad.net/~sts-sponsors > > Post to : sts-sponsors@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~sts-sponsors > > More help : https://help.launchpad.net/ListHelp > > > > -- > Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
[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
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972747 Title: Speakup modules missing from kernel after upgrad to Ubuntu Jammy/22.04 Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Jammy/22.04, the kernel modules for the speakup screen reader are not available . # modprobe speakup_ltlk modprobe: FATAL: Module speakup_ltlk not found in directory /lib/modules/5.15.0-27-generic Note: This bug is similar to those originally in 21.04 and 21.10. It seems that with each new release, the speakup kernel modules are left out. see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942459 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1997 F pulseaudio /dev/snd/pcmC0D0p: john 1997 F...m pulseaudio /dev/snd/controlC1: john 1997 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon May 9 20:31:45 2022 InstallationDate: Installed on 2021-08-25 (257 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=de5924a4-e0f6-4c11-a364-ea107efc1086 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-10 (0 days ago) dmi.bios.date: 12/13/2018 dmi.bios.release: 65.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd12/13/2018:br65.29:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr:sku0617: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972011 Title: cheese camara app Vertical Lines Status in linux package in Ubuntu: Confirmed Bug description: cheese camara app Vertical Lines ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 6 22:58:23 2022 InstallationDate: Installed on 2022-05-05 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Acer Aspire A715-75G ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2021 dmi.bios.release: 2.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_FMS dmi.board.vendor: CML dmi.board.version: V2.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.06 dmi.ec.firmware.release: 2.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd09/15/2021:br2.6:efr2.5:svnAcer:pnAspireA715-75G:pvrV2.06:rvnCML:rnAzalea_FMS:rvrV2.06:cvnAcer:ct10:cvrV2.06:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-75G dmi.product.sku: dmi.product.version: V2.06 dmi.sys.vendor: Acer lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b72b Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: azharkoivila 1669 F pulseaudio /dev/snd/controlC1: azharkoivila 1669 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-05 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b72b Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A715-75G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=0647f80b-2697-4287-b79a-0652c7b653ab ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2021 dmi.bios.release: 2.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_FMS dmi.board.vendor: CML dmi.board.version: V2.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.06 dmi.ec.firmware.release: 2.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd09/15/2021:br2.6:efr2.5:svnAcer:pnAspireA715-75G:pvrV2.06:rvnCML:rnAzalea_FMS:rvrV2.06:cvnAcer:ct10:cvrV2.06:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-75G dmi.product.sku: dmi.product.version: V2.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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
[Desktop-packages] [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 Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in Cheese: Unknown Status in cheese package in Ubuntu: Triaged Status in clutter-gst-3.0 package in Ubuntu: New Status in cheese source package in Jammy: Triaged Status in clutter-gst-3.0 source package in Jammy: New Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string
[Desktop-packages] [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 Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in Cheese: Unknown Status in cheese package in Ubuntu: Triaged Status in clutter-gst-3.0 package in Ubuntu: New Status in cheese source package in Jammy: Triaged Status in clutter-gst-3.0 source package in Jammy: New Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[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
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 Desktop Bugs, which is subscribed to clutter-gst-3.0 in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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
Re: [Sts-sponsors] Please review and sponsor LP1968805 ec2-hibinit-agent for Amazon AWS
Upstream has responded that they have seen the pull request, and they are going to assign it to one of their engineers to review: > Thanks for reporting and putting together a patch - the engineering team in > EC2 that maintains the agent is aware of the patch and are prioritizing > testing it. I'll ask them to give you an ETA when they have one. https://github.com/aws/amazon-ec2-hibinit-agent/issues/20#issuecomment-1104679221 Do you want to wait until we get a positive review from upstream? I suppose we can tell AWS that the case can be WoCus while we are waiting for upstream to review, and it will pause the SLA timer. On Thu, Apr 21, 2022 at 5:54 PM Matthew Ruffell wrote: > > Hi everyone, > > Could you please review LP #1968805 [1], and sponsor the uploads if it looks > okay? > > [1] https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805 > > I think bumping the priority to 32767 is the best solution for this particular > case, since it would be higher than priorities users would be using in the > wild, > if they happen to have multiple swapfiles configured. > > I have submitted the patches upstream, but no word back. The upstream is AWS > though, so maybe I might be able to put the SLA on hold for feedback there, > but otherwise, we have about one month left on the SLA to get this fixed, so > I wasn't going to wait. > > I did ask the CPC team about their feelings on the patches, but I didn't get > much of a response other than from Chris Newcomer in the CPC channel. > > If you were going to test this for yourself, best stick with Focal for the > moment, as Jammy is broken on xen instance types, and is being tracked > separately in https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062 > > Let me know if you have any feedback, or think this should be fixed in a > different way. > > And yes, Dan, this is probably a duplicate of > https://bugs.launchpad.net/bugs/1910252 > where the real root cause is that systemd blindly hibernates to the highest > priority swapfile, as it has no way to know what resume device and offset the > kernel is configured to resume from. SRUing such a change might be difficult > as those who accept the standard behaviour would have to manually update their > configuration on their systems to tell systemd what swapfile to hibernate to. > > I think talking with upstream systemd will go past the 1 month left on the > SLA, > and so these straightforward patches to ec2-hibinit-agent are probably the > best > low risk way to work around the bug, and fix AWS users. > > PS, our ec2-hibinit-agent package diverged from upstream long ago, and the > foundations team appear to be happy carrying patches not upstreamed. > > Thanks, > Matthew -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970202 Title: linux-generic kernels are missing nbd modules Status in linux package in Ubuntu: Invalid Bug description: linux-generic kernels are missing nbd modules. Since these modules are not build and not found in linux-generic-extra or other packages it is not possible to - use nbd-devices - it is not possible to mount *.qcow2 qemu virtual harddrives into your host system You can build these nbd modules yourself, but you need to compile the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-generic 5.13.0.41.50 ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps7192 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Apr 25 13:43:48 2022 HibernationDevice: RESUME=/dev/vg/swap_1 InstallationDate: Installed on 2011-10-19 (3840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2019-04-27 (1093 days ago) dmi.bios.date: 10/21/2013 dmi.bios.release: 2.15 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[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
[Sts-sponsors] Please review and sponsor LP1968805 ec2-hibinit-agent for Amazon AWS
Hi everyone, Could you please review LP #1968805 [1], and sponsor the uploads if it looks okay? [1] https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805 I think bumping the priority to 32767 is the best solution for this particular case, since it would be higher than priorities users would be using in the wild, if they happen to have multiple swapfiles configured. I have submitted the patches upstream, but no word back. The upstream is AWS though, so maybe I might be able to put the SLA on hold for feedback there, but otherwise, we have about one month left on the SLA to get this fixed, so I wasn't going to wait. I did ask the CPC team about their feelings on the patches, but I didn't get much of a response other than from Chris Newcomer in the CPC channel. If you were going to test this for yourself, best stick with Focal for the moment, as Jammy is broken on xen instance types, and is being tracked separately in https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062 Let me know if you have any feedback, or think this should be fixed in a different way. And yes, Dan, this is probably a duplicate of https://bugs.launchpad.net/bugs/1910252 where the real root cause is that systemd blindly hibernates to the highest priority swapfile, as it has no way to know what resume device and offset the kernel is configured to resume from. SRUing such a change might be difficult as those who accept the standard behaviour would have to manually update their configuration on their systems to tell systemd what swapfile to hibernate to. I think talking with upstream systemd will go past the 1 month left on the SLA, and so these straightforward patches to ec2-hibinit-agent are probably the best low risk way to work around the bug, and fix AWS users. PS, our ec2-hibinit-agent package diverged from upstream long ago, and the foundations team appear to be happy carrying patches not upstreamed. Thanks, Matthew -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
[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
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967702 Title: Enable speakup kernel modules to allow the speakup screen reader to function Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1967702 [Impact] Blind system administrators rely on the speakup accessibility feature to be able to use screen readers in text mode, like "espeakup". Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, although in recent releases it keeps being disabled. In Hirsute and Impish, it was accidentally disabled due to it moving from drivers/staging/ to drivers/accessibility/, and it was re-added by Tim Gardner in LP1942459. When it was recently re-enabled, the patch was never applied to ubuntu-unstable, and thus was never picked up by Jammy. We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and ubuntu-unstable. [Fix] We need to enable the following configuration items: CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=m and the additional modules: CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m [Testcase] Install the speakup accessibility tool: $ sudo apt install espeakup Check journalctl to see if it is able to load kernel modules: systemd[1]: Starting Software speech output for Speakup... modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory /lib/modules/5.15.0-25-generic systemd[1]: espeakup.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped Software speech output for Speakup. systemd[1]: espeakup.service: Start request repeated too quickly. systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. We should see espeakup.service start correctly, instead of failing to load speakup_soft: systemd[1]: Starting Software speech output for Speakup... kernel: input: Speakup as /devices/virtual/input/input5 kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 123) kernel: speakup 3.1.6: initialized kernel: synth name on entry is: (null) kernel: synth probe kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 122) kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 121) systemd[1]: Started Software speech output for Speakup. You can also try load the modules manually: $ sudo modprobe speakup_soft There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test If you install the test kernel, the speakup modules should load successfully. [Where problems could occur] We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x, and this shouldn't have any affect on config items being turned on, since it simply enables the speakup submenu to be shown. Enabling CONFIG_SPEAKUP* should not have any impact on users that don't use screen reader accessibility software, as it will only be loaded by users of espeakup. If a regression were to occur, users could unload the speakup modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 -
[Desktop-packages] [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 Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: In Progress Status in cheese source package in Jammy: In Progress Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte
[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
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
I have determined the root cause via git bisecting the master branch. The issue was introduced in: commit 58de82b3d463b69f4c0bef75667e47020924e28b Author: Jakub Adam Date: Tue Sep 3 13:00:30 2019 +0200 Subject: Support camera video formats with MJPEG output Link: https://gitlab.gnome.org/GNOME/cheese/-/commit/58de82b3d463b69f4c0bef75667e47020924e28b If I checkout current master branch and revert this commit, things work fine. I will report the issue to upstream, and we can go from there. -- 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
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
I have determined the root cause via git bisecting the master branch. The issue was introduced in: commit 58de82b3d463b69f4c0bef75667e47020924e28b Author: Jakub Adam Date: Tue Sep 3 13:00:30 2019 +0200 Subject: Support camera video formats with MJPEG output Link: https://gitlab.gnome.org/GNOME/cheese/-/commit/58de82b3d463b69f4c0bef75667e47020924e28b If I checkout current master branch and revert this commit, things work fine. I will report the issue to upstream, and we can go from there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: In Progress Status in cheese source package in Jammy: In Progress Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Upstream bug: https://gitlab.gnome.org/GNOME/cheese/-/issues/126 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: In Progress Status in cheese source package in Jammy: In Progress Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Upstream bug: https://gitlab.gnome.org/GNOME/cheese/-/issues/126 -- 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
[Kernel-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
I downgraded cheese from 41.1-1build1 to 3.38.0-4 and it works fine again. Seems to be a cheese 41 problem. GST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink works fine, as well as using the webcam in Google Meet with Firefox. ** No longer affects: linux (Ubuntu) ** Also affects: cheese (Ubuntu Jammy) Importance: Low Status: Incomplete ** Changed in: cheese (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: cheese (Ubuntu Jammy) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #126 https://gitlab.gnome.org/GNOME/cheese/-/issues/126 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: In Progress Status in cheese source package in Jammy: In Progress Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rv
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
I downgraded cheese from 41.1-1build1 to 3.38.0-4 and it works fine again. Seems to be a cheese 41 problem. GST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink works fine, as well as using the webcam in Google Meet with Firefox. ** No longer affects: linux (Ubuntu) ** Also affects: cheese (Ubuntu Jammy) Importance: Low Status: Incomplete ** Changed in: cheese (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: cheese (Ubuntu Jammy) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #126 https://gitlab.gnome.org/GNOME/cheese/-/issues/126 -- 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
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
I downgraded cheese from 41.1-1build1 to 3.38.0-4 and it works fine again. Seems to be a cheese 41 problem. GST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink works fine, as well as using the webcam in Google Meet with Firefox. ** No longer affects: linux (Ubuntu) ** Also affects: cheese (Ubuntu Jammy) Importance: Low Status: Incomplete ** Changed in: cheese (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: cheese (Ubuntu Jammy) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #126 https://gitlab.gnome.org/GNOME/cheese/-/issues/126 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: In Progress Status in cheese source package in Jammy: In Progress Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rv
[Kernel-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Hi Jack, Thanks for reporting. I have a Logitech C270 camera, and I am also affected. Attached is what I see, I get green and purple bars, and overall terrible performance. I am on Jammy 5.15.0-25-generic, Wayland session, gnome 42, cheese 41.1-1build1. I will start investigating. Thanks, Matthew ** Attachment added: "Issue reproduced" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967843/+attachment/5577402/+files/Screenshot%20from%202022-04-06%2011-30-47.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version:
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Hi Jack, Thanks for reporting. I have a Logitech C270 camera, and I am also affected. Attached is what I see, I get green and purple bars, and overall terrible performance. I am on Jammy 5.15.0-25-generic, Wayland session, gnome 42, cheese 41.1-1build1. I will start investigating. Thanks, Matthew ** Attachment added: "Issue reproduced" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967843/+attachment/5577402/+files/Screenshot%20from%202022-04-06%2011-30-47.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/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Hi Jack, Thanks for reporting. I have a Logitech C270 camera, and I am also affected. Attached is what I see, I get green and purple bars, and overall terrible performance. I am on Jammy 5.15.0-25-generic, Wayland session, gnome 42, cheese 41.1-1build1. I will start investigating. Thanks, Matthew ** Attachment added: "Issue reproduced" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967843/+attachment/5577402/+files/Screenshot%20from%202022-04-06%2011-30-47.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version:
[Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
Hi Tiago, Thanks for reporting! I have submitted patches to the Ubuntu kernel mailing list to get this fixed. https://lists.ubuntu.com/archives/kernel-team/2022-April/129192.html https://lists.ubuntu.com/archives/kernel-team/2022-April/129193.html https://lists.ubuntu.com/archives/kernel-team/2022-April/129194.html Next step is for the kernel team to review the patches. 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/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
[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
Hi Tiago, Thanks for reporting! I have submitted patches to the Ubuntu kernel mailing list to get this fixed. https://lists.ubuntu.com/archives/kernel-team/2022-April/129192.html https://lists.ubuntu.com/archives/kernel-team/2022-April/129193.html https://lists.ubuntu.com/archives/kernel-team/2022-April/129194.html Next step is for the kernel team to review the patches. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967702 Title: Enable speakup kernel modules to allow the speakup screen reader to function Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1967702 [Impact] Blind system administrators rely on the speakup accessibility feature to be able to use screen readers in text mode, like "espeakup". Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, although in recent releases it keeps being disabled. In Hirsute and Impish, it was accidentally disabled due to it moving from drivers/staging/ to drivers/accessibility/, and it was re-added by Tim Gardner in LP1942459. When it was recently re-enabled, the patch was never applied to ubuntu-unstable, and thus was never picked up by Jammy. We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and ubuntu-unstable. [Fix] We need to enable the following configuration items: CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=m and the additional modules: CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m [Testcase] Install the speakup accessibility tool: $ sudo apt install espeakup Check journalctl to see if it is able to load kernel modules: systemd[1]: Starting Software speech output for Speakup... modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory /lib/modules/5.15.0-25-generic systemd[1]: espeakup.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped Software speech output for Speakup. systemd[1]: espeakup.service: Start request repeated too quickly. systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. We should see espeakup.service start correctly, instead of failing to load speakup_soft: systemd[1]: Starting Software speech output for Speakup... kernel: input: Speakup as /devices/virtual/input/input5 kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 123) kernel: speakup 3.1.6: initialized kernel: synth name on entry is: (null) kernel: synth probe kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 122) kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 121) systemd[1]: Started Software speech output for Speakup. You can also try load the modules manually: $ sudo modprobe speakup_soft There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test If you install the test kernel, the speakup modules should load successfully. [Where problems could occur] We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x, and this shouldn't have any affect on config items being turned on, since it simply enables the speakup submenu to be shown. Enabling CONFIG_SPEAKUP* should not have any impact on users that don't use screen reader accessibility software, as it will only be loaded by users of espeakup. If a regression were to occur, users could unload the speakup modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1967702 [Impact] Blind system administrators rely on the speakup accessibility feature to be able to use screen readers in text mode, like "espeakup". Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, although in recent releases it keeps being disabled. In Hirsute and Impish, it was accidentally disabled due to it moving from drivers/staging/ to drivers/accessibility/, and it was re-added by Tim Gardner in LP1942459. When it was recently re-enabled, the patch was never applied to ubuntu- unstable, and thus was never picked up by Jammy. We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and ubuntu-unstable. [Fix] We need to enable the following configuration items: CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=m and the additional modules: CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m [Testcase] Install the speakup accessibility tool: $ sudo apt install espeakup Check journalctl to see if it is able to load kernel modules: systemd[1]: Starting Software speech output for Speakup... modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory /lib/modules/5.15.0-25-generic systemd[1]: espeakup.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped Software speech output for Speakup. systemd[1]: espeakup.service: Start request repeated too quickly. systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. We should see espeakup.service start correctly, instead of failing to load speakup_soft: + systemd[1]: Starting Software speech output for Speakup... + kernel: input: Speakup as /devices/virtual/input/input5 + kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 123) + kernel: speakup 3.1.6: initialized + kernel: synth name on entry is: (null) + kernel: synth probe + kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 122) + kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 121) + systemd[1]: Started Software speech output for Speakup. + You can also try load the modules manually: $ sudo modprobe speakup_soft There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test If you install the test kernel, the speakup modules should load successfully. [Where problems could occur] We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x, and this shouldn't have any affect on config items being turned on, since it simply enables the speakup submenu to be shown. Enabling CONFIG_SPEAKUP* should not have any impact on users that don't use screen reader accessibility software, as it will only be loaded by users of espeakup. If a regression were to occur, users could unload the speakup modules. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967702 Title: Enable speakup kernel modules to allow the speakup screen reader to function Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1967702 [Impact] Blind system administrators rely on the speakup accessibility feature to be able to use screen readers in text mode, like "espeakup". Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, although in recent releases it keeps being disabled. In Hirsute and Impish, it was accidentally disabled due to it moving from drivers/staging/ to drivers/accessibility/, and it was re-added by Tim Gardner in LP1942459. When it was recently re-enabled, the patch was never applied to ubuntu-unstable, and thus was never picked up by Jammy. We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and ubuntu-unstable. [Fix] We need to enable the following configuration items: CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=m and the additional modules: CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DUMMY=m
[Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1967702 [Impact] Blind system administrators rely on the speakup accessibility feature to be able to use screen readers in text mode, like "espeakup". Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, although in recent releases it keeps being disabled. In Hirsute and Impish, it was accidentally disabled due to it moving from drivers/staging/ to drivers/accessibility/, and it was re-added by Tim Gardner in LP1942459. When it was recently re-enabled, the patch was never applied to ubuntu- unstable, and thus was never picked up by Jammy. We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and ubuntu-unstable. [Fix] We need to enable the following configuration items: CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=m and the additional modules: CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m [Testcase] Install the speakup accessibility tool: $ sudo apt install espeakup Check journalctl to see if it is able to load kernel modules: systemd[1]: Starting Software speech output for Speakup... modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory /lib/modules/5.15.0-25-generic systemd[1]: espeakup.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped Software speech output for Speakup. systemd[1]: espeakup.service: Start request repeated too quickly. systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. We should see espeakup.service start correctly, instead of failing to load speakup_soft: + systemd[1]: Starting Software speech output for Speakup... + kernel: input: Speakup as /devices/virtual/input/input5 + kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 123) + kernel: speakup 3.1.6: initialized + kernel: synth name on entry is: (null) + kernel: synth probe + kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 122) + kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 121) + systemd[1]: Started Software speech output for Speakup. + You can also try load the modules manually: $ sudo modprobe speakup_soft There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test If you install the test kernel, the speakup modules should load successfully. [Where problems could occur] We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x, and this shouldn't have any affect on config items being turned on, since it simply enables the speakup submenu to be shown. Enabling CONFIG_SPEAKUP* should not have any impact on users that don't use screen reader accessibility software, as it will only be loaded by users of espeakup. If a regression were to occur, users could unload the speakup modules. -- 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 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
** 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/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
[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
** Tags added: seg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967702 Title: Enable speakup kernel modules to allow the speakup screen reader to function Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1967702 [Impact] Blind system administrators rely on the speakup accessibility feature to be able to use screen readers in text mode, like "espeakup". Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, although in recent releases it keeps being disabled. In Hirsute and Impish, it was accidentally disabled due to it moving from drivers/staging/ to drivers/accessibility/, and it was re-added by Tim Gardner in LP1942459. When it was recently re-enabled, the patch was never applied to ubuntu-unstable, and thus was never picked up by Jammy. We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and ubuntu-unstable. [Fix] We need to enable the following configuration items: CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=m and the additional modules: CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m [Testcase] Install the speakup accessibility tool: $ sudo apt install espeakup Check journalctl to see if it is able to load kernel modules: systemd[1]: Starting Software speech output for Speakup... modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory /lib/modules/5.15.0-25-generic systemd[1]: espeakup.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped Software speech output for Speakup. systemd[1]: espeakup.service: Start request repeated too quickly. systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. We should see espeakup.service start correctly, instead of failing to load speakup_soft: You can also try load the modules manually: $ sudo modprobe speakup_soft There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test If you install the test kernel, the speakup modules should load successfully. [Where problems could occur] We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x, and this shouldn't have any affect on config items being turned on, since it simply enables the speakup submenu to be shown. Enabling CONFIG_SPEAKUP* should not have any impact on users that don't use screen reader accessibility software, as it will only be loaded by users of espeakup. If a regression were to occur, users could unload the speakup modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
** Summary changed: - Accessibility features have been disabled, modules like speakup_soft and others are missing + Enable speakup kernel modules to allow the speakup screen reader to function ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Description changed: - From very old versions of Kernel for Ubuntu until version 5.13, accessibility features were enabled, allowing blind users to use screen readers in text mode, such as "speakup" via "espeakup" package. - In Kernels 5.15 packages for Ubuntu 22.04 beta, such as "linux-image-5.15.0-23-generic", accessibility features are disabled (no justification for such occurrence was listed in the file "changelog.Debian.gz"), with this the espeakup application doesn't work, it depends on the missing speakup_soft module. - Missing in the file "/boot/config-5.15.0-23-generic" comparing with the file "/boot/config-5.13.0-39-generic", the line + BugLink: https://bugs.launchpad.net/bugs/1967702 + + [Impact] + + Blind system administrators rely on the speakup accessibility feature to + be able to use screen readers in text mode, like "espeakup". + + Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, + although in recent releases it keeps being disabled. In Hirsute and + Impish, it was accidentally disabled due to it moving from + drivers/staging/ to drivers/accessibility/, and it was re-added by Tim + Gardner in LP1942459. + + When it was recently re-enabled, the patch was never applied to ubuntu- + unstable, and thus was never picked up by Jammy. + + We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and + ubuntu-unstable. + + [Fix] + + We need to enable the following configuration items: + CONFIG_ACCESSIBILITY=y - and the following lines are also missing: - # - # Speakup console speech - # CONFIG_SPEAKUP=m + + and the additional modules: + CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m + CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m - CONFIG_SPEAKUP_SYNTH_DECEXT=m + CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m - CONFIG_SPEAKUP_SYNTH_DUMMY=m - # end of Speakup console speech - ProblemType: Bug - DistroRelease: Ubuntu 22.04 - Package: linux-image-5.15.0-23-generic 5.15.0-23.23 - ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 - Uname: Linux 5.15.0-23-generic x86_64 - ApportVersion: 2.20.11-0ubuntu80 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: tiago 1259 F pulseaudio - /dev/snd/pcmC0D0p: tiago 1259 F...m pulseaudio - CasperMD5CheckResult: pass - CurrentDesktop: MATE - Date: Sun Apr 3 22:05:39 2022 - InstallationDate: Installed on 2022-04-03 (0 days ago) - InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220330) - Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD - Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver - Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - MachineType: Dell Inc. Inspiron 3583 - ProcFB: 0 i915drmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=9e0e837b-49f2-4e10-945a-f7460bcc8286 ro quiet splash vt.handoff=7 - RelatedPackageVersions: - linux-restricted-modules-5.15.0-23-generic N/A - linux-backports-modules-5.15.0-23-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu1 - SourcePackage: linux - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 12/06/2021 - dmi.bios.release: 1.17 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: 1.17.0 - dmi.board.name: 0KD03P - dmi.board.vendor: Dell Inc. - dmi.board.version: A03 - dmi.chassis.type: 10 - dmi.chassis.vendor: Dell Inc. - dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd12/06/2021:br1.17:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0KD03P:rvrA03:cvnDellInc.:ct10:cvr:sku08CA: - dmi.product.family: Inspiron - dmi.product.name: Inspiron 3583 - dmi.product.sku: 08CA - dmi.sys.vendor: Dell Inc. + [Testcase] + + Install the speakup accessibility tool: + + $ sudo apt install espeakup + + Check journalctl to see if it is able to load kernel modules: + + systemd[1]: Starting Software speech output for Speakup... + modprobe[27013]: modprobe: FATAL: Module speakup_soft not f
[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
** Summary changed: - Accessibility features have been disabled, modules like speakup_soft and others are missing + Enable speakup kernel modules to allow the speakup screen reader to function ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Description changed: - From very old versions of Kernel for Ubuntu until version 5.13, accessibility features were enabled, allowing blind users to use screen readers in text mode, such as "speakup" via "espeakup" package. - In Kernels 5.15 packages for Ubuntu 22.04 beta, such as "linux-image-5.15.0-23-generic", accessibility features are disabled (no justification for such occurrence was listed in the file "changelog.Debian.gz"), with this the espeakup application doesn't work, it depends on the missing speakup_soft module. - Missing in the file "/boot/config-5.15.0-23-generic" comparing with the file "/boot/config-5.13.0-39-generic", the line + BugLink: https://bugs.launchpad.net/bugs/1967702 + + [Impact] + + Blind system administrators rely on the speakup accessibility feature to + be able to use screen readers in text mode, like "espeakup". + + Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, + although in recent releases it keeps being disabled. In Hirsute and + Impish, it was accidentally disabled due to it moving from + drivers/staging/ to drivers/accessibility/, and it was re-added by Tim + Gardner in LP1942459. + + When it was recently re-enabled, the patch was never applied to ubuntu- + unstable, and thus was never picked up by Jammy. + + We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and + ubuntu-unstable. + + [Fix] + + We need to enable the following configuration items: + CONFIG_ACCESSIBILITY=y - and the following lines are also missing: - # - # Speakup console speech - # CONFIG_SPEAKUP=m + + and the additional modules: + CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m + CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m - CONFIG_SPEAKUP_SYNTH_DECEXT=m + CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m - CONFIG_SPEAKUP_SYNTH_DUMMY=m - # end of Speakup console speech - ProblemType: Bug - DistroRelease: Ubuntu 22.04 - Package: linux-image-5.15.0-23-generic 5.15.0-23.23 - ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 - Uname: Linux 5.15.0-23-generic x86_64 - ApportVersion: 2.20.11-0ubuntu80 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: tiago 1259 F pulseaudio - /dev/snd/pcmC0D0p: tiago 1259 F...m pulseaudio - CasperMD5CheckResult: pass - CurrentDesktop: MATE - Date: Sun Apr 3 22:05:39 2022 - InstallationDate: Installed on 2022-04-03 (0 days ago) - InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220330) - Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD - Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver - Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - MachineType: Dell Inc. Inspiron 3583 - ProcFB: 0 i915drmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=9e0e837b-49f2-4e10-945a-f7460bcc8286 ro quiet splash vt.handoff=7 - RelatedPackageVersions: - linux-restricted-modules-5.15.0-23-generic N/A - linux-backports-modules-5.15.0-23-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu1 - SourcePackage: linux - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 12/06/2021 - dmi.bios.release: 1.17 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: 1.17.0 - dmi.board.name: 0KD03P - dmi.board.vendor: Dell Inc. - dmi.board.version: A03 - dmi.chassis.type: 10 - dmi.chassis.vendor: Dell Inc. - dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd12/06/2021:br1.17:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0KD03P:rvrA03:cvnDellInc.:ct10:cvr:sku08CA: - dmi.product.family: Inspiron - dmi.product.name: Inspiron 3583 - dmi.product.sku: 08CA - dmi.sys.vendor: Dell Inc. + [Testcase] + + Install the speakup accessibility tool: + + $ sudo apt install espeakup + + Check journalctl to see if it is able to load kernel modules: + + systemd[1]: Starting Software speech output for Speakup... + modprobe[27013]: modprobe: FATAL: Module speakup_soft not f
[Desktop-packages] [Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
Hi renbag,
Thanks for attaching your smb.conf and sssd.conf, I will try add them
into my reproducer and see if I get closer to seeing the problem.
Maybe when you log in, smbd mounts the samba shares to
/home/aduser/{Public},{Shared} before kerberos manages to acquire a new
ticket and place it in /tmp, so gvfs doesn't get KRB5CCNAME set.
Maybe on your faster system, it can get the kerberos ticket before smbd
starts mounting shares.
This is still a race condition where gvfs is starting too early though.
Let me re-adjust my reproducer, and I will let you know how I get on.
Thanks,
Matthew
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1779890
Title:
Nautilus does not use a valid Kerberos ticket when accessing Samba
share
Status in gvfs:
Unknown
Status in gvfs package in Ubuntu:
Triaged
Bug description:
Nautilus prompts for username and password when accessing a Samba
share on a network drive, despite having a perfectly valid unexpired
Kerberos ticket. The Kerberos ticket is obtained automatically at
logon by authentication against a Samba Active Directory server (Samba
AD-DC).
Accessing the same Samba share with the same Kerberos ticket via
"smbclient //host/sharename -k" works fine.
One known workaround is: "nautilus -q", and then "killall gvfsd".
After that, accessing the Samba share with Nautilus works normally as
it should.
I did not experience this issue in Ubuntu 16.04. It appears that a
regression was introduced somewhere between 16.04 and 18.04.
The issue is quite annoying and confusing for the users who are used
to accessing Samba shares on the network drive without being prompted
for their username and password.
The issue appears to manifest itself usually not on the first access
to a Samba share, but on subsequent accesses after a system reboot or
upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry
file before user login appears to fix the issue for the current user
session, but then the problem reappears upon subsequent user logins or
after a system reboot.
Nemo appears to have the same problem as Nautilus.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gvfs-daemons 1.36.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jul 3 11:12:06 2018
ExecutablePath: /usr/lib/gvfs/gvfsd
InstallationDate: Installed on 2018-04-27 (66 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
LANG=en_CA.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
Hi renbag,
Thanks for attaching your smb.conf and sssd.conf, I will try add them
into my reproducer and see if I get closer to seeing the problem.
Maybe when you log in, smbd mounts the samba shares to
/home/aduser/{Public},{Shared} before kerberos manages to acquire a new
ticket and place it in /tmp, so gvfs doesn't get KRB5CCNAME set.
Maybe on your faster system, it can get the kerberos ticket before smbd
starts mounting shares.
This is still a race condition where gvfs is starting too early though.
Let me re-adjust my reproducer, and I will let you know how I get on.
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/1779890
Title:
Nautilus does not use a valid Kerberos ticket when accessing Samba
share
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
Hi renbag,
Thanks for attaching your smb.conf and sssd.conf, I will try add them
into my reproducer and see if I get closer to seeing the problem.
Maybe when you log in, smbd mounts the samba shares to
/home/aduser/{Public},{Shared} before kerberos manages to acquire a new
ticket and place it in /tmp, so gvfs doesn't get KRB5CCNAME set.
Maybe on your faster system, it can get the kerberos ticket before smbd
starts mounting shares.
This is still a race condition where gvfs is starting too early though.
Let me re-adjust my reproducer, and I will let you know how I get on.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1779890
Title:
Nautilus does not use a valid Kerberos ticket when accessing Samba
share
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Kernel-packages] [Bug 1896350] Re: nbd locks system?
Hi Dan, Thank you for your bug report. I just came across it now, as I just ran into same issue too. Your reproducer works great, and I have started debugging the issue. At this stage it doesn't seem to be a kernel bug, or a qemu-nbd bug. I think the culprit is systemd-udevd or multipathd, as when I disable systemd-udevd, things work fine. I will add more details to the bug report in a few days or so, once I have determined the root cause and come up with a fix. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896350 Title: nbd locks system? Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to use nbd on ubuntu 20.04 like so: qemu-img create -f qcow2 foo.img 500M sudo modprobe nbd sudo qemu-nbd --disconnect /dev/nbd15 || true sudo qemu-nbd --connect=/dev/nbd15 --cache=writeback --format=qcow2 foo.img sudo mkfs.ext4 -L root -O "^64bit" -E nodiscard /dev/nbd15 sudo qemu-nbd --disconnect /dev/nbd15 It seems to work on some systems, but even on those systems, strange things show up in syslog, e.g. Sep 19 15:46:02 thinky kernel: [27042.757768] block nbd15: Possible stuck request dd2d7f93: control (read@135168,126976B). Runtime 450 seconds Sep 19 15:46:26 thinky kernel: [27067.333867] INFO: task systemd-udevd:17364 blocked for more than 241 seconds. and in kern.log, e.g. ... Sep 19 16:17:27 thinky kernel: [ 71.676026] Buffer I/O error on dev nbd15, logical block 7, async page read Sep 19 16:17:27 thinky kernel: [ 71.676049] blk_update_request: I/O error, dev nbd15, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 19 16:17:27 thinky kernel: [ 71.676051] Buffer I/O error on dev nbd15, logical block 0, async page read Sep 19 16:17:27 thinky kernel: [ 71.676061] blk_update_request: I/O error, dev nbd15, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 19 16:17:27 thinky kernel: [ 71.676063] Buffer I/O error on dev nbd15, logical block 1, async page read Sep 19 16:17:27 thinky kernel: [ 71.676147] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.676324] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.676473] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.678340] nbd15: detected capacity change from 0 to 524288000 Sep 19 16:17:27 thinky kernel: [ 71.678536] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.678719] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.678947] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.679985] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.680172] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.680366] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.680647] block nbd15: Attempted send on invalid socket and the system seems to hang on reboot. Also, on another system (an up to date mac, running ubuntu 20.04 in virtualbox), the mkfs.ext4 fails, complaining the device is zero size. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dank 2948 F pulseaudio /dev/snd/controlC2: dank 2948 F pulseaudio /dev/snd/controlC0: dank 2948 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 16:28:43 2020 HibernationDevice: RESUME=UUID=7aecd5d3-2f5b-4c07-8867-801e63868a0f InstallationDate: Installed on 2017-04-29 (1239 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO ThinkServer TS140 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=ff9a24e4-277d-4baf-819b-826a33d5bb5e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-01 (141 days ago) dmi.bios.date: 09/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT99AUS dmi.board.name: ThinkServer TS140 dmi.board.vendor: LENOVO dmi.board.version: Not Defined
[Bug 1896350] Re: nbd locks system?
Hi Dan, Thank you for your bug report. I just came across it now, as I just ran into same issue too. Your reproducer works great, and I have started debugging the issue. At this stage it doesn't seem to be a kernel bug, or a qemu-nbd bug. I think the culprit is systemd-udevd or multipathd, as when I disable systemd-udevd, things work fine. I will add more details to the bug report in a few days or so, once I have determined the root cause and come up with a 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/1896350 Title: nbd locks system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
Hi everyone, Fady, renbag, I have been working on this bug on and off for a little while now, but I am stuck because I can't reproduce what you are all seeing. Having a reproducer will greatly speed up getting a fix created for this issue. In my client gvfsd is always started via systemd --user, so I must be configuring something differently. Can you try out my reproducer and let me know what you are configuring differently? Instructions to reproduce: You will need a 20.04 server instance, and a 20.04 Desktop instance. To set up the server: 1) Create a fresh 20.04 server instance 2) sudo apt update 3) sudo apt upgrade 4) sudo hostnamectl set-hostname samba-dc 5) sudo vim /etc/hosts Add an entry with its IP address, e.g.: 192.168.122.199samba-dc samba-dc.example.com 6) sudo apt install -y samba smbclient winbind libpam-winbind libnss-winbind krb5-kdc libpam-krb5 Note: skip config of kerberos KDC. 7) sudo rm /etc/krb5.conf 8) sudo rm /etc/samba/smb.conf 9) sudo samba-tool domain provision --server-role=dc --use-rfc2307 --dns-backend=SAMBA_INTERNAL --realm=samba-dc.EXAMPLE.COM --domain=SAMBA --adminpass=Password1 10) sudo cp /var/lib/samba/private/krb5.conf /etc/krb5.conf 11) sudo systemctl mask smbd nmbd winbind 12) sudo systemctl disable smbd nmbd winbind 13) sudo systemctl stop smbd nmbd winbind 14) sudo systemctl unmask samba-ad-dc 15) sudo systemctl start samba-ad-dc 16) sudo systemctl enable samba-ad-dc 17) sudo reboot 18) sudo systemctl stop systemd-resolved 19) sudo systemctl disable systemd-resolved 20) cat << EOF >> /etc/resolv.conf nameserver 192.168.122.199 search SAMBA EOF 21) sudo reboot 22) host -t SRV _ldap._tcp.samba-dc.example.com _ldap._tcp.samba-dc.example.com has SRV record 0 100 389 samba-dc.samba-dc.example.com. 23) $ smbclient -L localhost -N Anonymous login successful Sharename Type Comment - --- sysvol Disk netlogonDisk IPC$IPC IPC Service (Samba 4.13.17-Ubuntu) SMB1 disabled -- no workgroup available 24) $ smbclient //localhost/netlogon -UAdministrator -c 'ls' Enter SAMBA\Administrator's password: . D0 Mon Feb 28 04:23:22 2022 .. D0 Mon Feb 28 04:23:27 2022 9983232 blocks of size 1024. 7995324 blocks available 25) kinit administrator Password for administra...@samba-dc.example.com: Warning: Your password will expire in 41 days on Mon Apr 11 04:23:27 2022 26) klist Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: administra...@samba-dc.example.com Valid starting ExpiresService principal 02/28/22 04:32:47 02/28/22 14:32:47 krbtgt/samba-dc.example@samba-dc.example.com renew until 03/01/22 04:32:44 27) Create a share: 28) sudo mkdir -p /srv/samba/Demo/ 29) sudo vim /etc/samba/smb.conf [Demo] path = /srv/samba/Demo/ read only = no 30) sudo chmod 0770 /srv/samba/Demo/ Install a fresh 20.04.4 Desktop instance, and run the following: 31) sudo apt install realmd smbclient 32) sudo vim /etc/hosts Add an entry with its IP address, e.g.: 192.168.122.199samba-dc samba-dc.example.com 33) sudo realm join --user=Administrator SAMBA-DC.EXAMPLE.COM $ smbclient -U Administrator //samba-dc.example.com/demo Enter WORKGROUP\Administrator's password: Try "help" to get a list of possible commands. smb: \> ls . D0 Mon Mar 7 15:20:30 2022 .. D0 Mon Mar 7 15:20:30 2022 9983232 blocks of size 1024. 7686220 blocks available $ smbclient //samba-dc.example.com/demo -k gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in NEG_TOKEN_INIT session setup failed: NT_STATUS_INVALID_PARAMETER Now open Nautilus, add smb://samba-dc.example.com/demo as a share, and you will be faced with a dialog box asking for username / password credentials. Close Nautilus. Let's get a kerberos ticket: $ kinit administra...@samba-dc.example.com Password for administra...@samba-dc.example.com: Warning: Your password will expire in 11 days on Mon 11 Apr 2022 16:23:27 $ smbclient //samba-dc.example.com/demo -k Try "help" to get a list of possible commands. smb: \> ls . D0 Mon Mar 7 15:20:30 2022 .. D0 Mon Mar 7 15:20:30 2022 9983232 blocks of size 1024. 7616832 blocks available 34) Open Nautilus, add smb://samba-dc.example.com/demo as a share, and it will open correctly using kerberos credentials. When I look at my process list, gvfsd is where it is suppose to be, under the systemd user session: $ ps auxf ... ubuntu 1207 0.5 0.2 19008 10128 ?Ss 12:12 0:00 /lib/systemd/systemd --user ubuntu 1208 0.0 0.0 179632 3544 ?S12:12 0:00 \_ (sd-pam) ubuntu
[Desktop-packages] [Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
Hi everyone, Fady, renbag, I have been working on this bug on and off for a little while now, but I am stuck because I can't reproduce what you are all seeing. Having a reproducer will greatly speed up getting a fix created for this issue. In my client gvfsd is always started via systemd --user, so I must be configuring something differently. Can you try out my reproducer and let me know what you are configuring differently? Instructions to reproduce: You will need a 20.04 server instance, and a 20.04 Desktop instance. To set up the server: 1) Create a fresh 20.04 server instance 2) sudo apt update 3) sudo apt upgrade 4) sudo hostnamectl set-hostname samba-dc 5) sudo vim /etc/hosts Add an entry with its IP address, e.g.: 192.168.122.199samba-dc samba-dc.example.com 6) sudo apt install -y samba smbclient winbind libpam-winbind libnss-winbind krb5-kdc libpam-krb5 Note: skip config of kerberos KDC. 7) sudo rm /etc/krb5.conf 8) sudo rm /etc/samba/smb.conf 9) sudo samba-tool domain provision --server-role=dc --use-rfc2307 --dns-backend=SAMBA_INTERNAL --realm=samba-dc.EXAMPLE.COM --domain=SAMBA --adminpass=Password1 10) sudo cp /var/lib/samba/private/krb5.conf /etc/krb5.conf 11) sudo systemctl mask smbd nmbd winbind 12) sudo systemctl disable smbd nmbd winbind 13) sudo systemctl stop smbd nmbd winbind 14) sudo systemctl unmask samba-ad-dc 15) sudo systemctl start samba-ad-dc 16) sudo systemctl enable samba-ad-dc 17) sudo reboot 18) sudo systemctl stop systemd-resolved 19) sudo systemctl disable systemd-resolved 20) cat << EOF >> /etc/resolv.conf nameserver 192.168.122.199 search SAMBA EOF 21) sudo reboot 22) host -t SRV _ldap._tcp.samba-dc.example.com _ldap._tcp.samba-dc.example.com has SRV record 0 100 389 samba-dc.samba-dc.example.com. 23) $ smbclient -L localhost -N Anonymous login successful Sharename Type Comment - --- sysvol Disk netlogonDisk IPC$IPC IPC Service (Samba 4.13.17-Ubuntu) SMB1 disabled -- no workgroup available 24) $ smbclient //localhost/netlogon -UAdministrator -c 'ls' Enter SAMBA\Administrator's password: . D0 Mon Feb 28 04:23:22 2022 .. D0 Mon Feb 28 04:23:27 2022 9983232 blocks of size 1024. 7995324 blocks available 25) kinit administrator Password for administra...@samba-dc.example.com: Warning: Your password will expire in 41 days on Mon Apr 11 04:23:27 2022 26) klist Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: administra...@samba-dc.example.com Valid starting ExpiresService principal 02/28/22 04:32:47 02/28/22 14:32:47 krbtgt/samba-dc.example@samba-dc.example.com renew until 03/01/22 04:32:44 27) Create a share: 28) sudo mkdir -p /srv/samba/Demo/ 29) sudo vim /etc/samba/smb.conf [Demo] path = /srv/samba/Demo/ read only = no 30) sudo chmod 0770 /srv/samba/Demo/ Install a fresh 20.04.4 Desktop instance, and run the following: 31) sudo apt install realmd smbclient 32) sudo vim /etc/hosts Add an entry with its IP address, e.g.: 192.168.122.199samba-dc samba-dc.example.com 33) sudo realm join --user=Administrator SAMBA-DC.EXAMPLE.COM $ smbclient -U Administrator //samba-dc.example.com/demo Enter WORKGROUP\Administrator's password: Try "help" to get a list of possible commands. smb: \> ls . D0 Mon Mar 7 15:20:30 2022 .. D0 Mon Mar 7 15:20:30 2022 9983232 blocks of size 1024. 7686220 blocks available $ smbclient //samba-dc.example.com/demo -k gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in NEG_TOKEN_INIT session setup failed: NT_STATUS_INVALID_PARAMETER Now open Nautilus, add smb://samba-dc.example.com/demo as a share, and you will be faced with a dialog box asking for username / password credentials. Close Nautilus. Let's get a kerberos ticket: $ kinit administra...@samba-dc.example.com Password for administra...@samba-dc.example.com: Warning: Your password will expire in 11 days on Mon 11 Apr 2022 16:23:27 $ smbclient //samba-dc.example.com/demo -k Try "help" to get a list of possible commands. smb: \> ls . D0 Mon Mar 7 15:20:30 2022 .. D0 Mon Mar 7 15:20:30 2022 9983232 blocks of size 1024. 7616832 blocks available 34) Open Nautilus, add smb://samba-dc.example.com/demo as a share, and it will open correctly using kerberos credentials. When I look at my process list, gvfsd is where it is suppose to be, under the systemd user session: $ ps auxf ... ubuntu 1207 0.5 0.2 19008 10128 ?Ss 12:12 0:00 /lib/systemd/systemd --user ubuntu 1208 0.0 0.0 179632 3544 ?S12:12 0:00 \_ (sd-pam) ubuntu
[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
Hi everyone, Fady, renbag, I have been working on this bug on and off for a little while now, but I am stuck because I can't reproduce what you are all seeing. Having a reproducer will greatly speed up getting a fix created for this issue. In my client gvfsd is always started via systemd --user, so I must be configuring something differently. Can you try out my reproducer and let me know what you are configuring differently? Instructions to reproduce: You will need a 20.04 server instance, and a 20.04 Desktop instance. To set up the server: 1) Create a fresh 20.04 server instance 2) sudo apt update 3) sudo apt upgrade 4) sudo hostnamectl set-hostname samba-dc 5) sudo vim /etc/hosts Add an entry with its IP address, e.g.: 192.168.122.199samba-dc samba-dc.example.com 6) sudo apt install -y samba smbclient winbind libpam-winbind libnss-winbind krb5-kdc libpam-krb5 Note: skip config of kerberos KDC. 7) sudo rm /etc/krb5.conf 8) sudo rm /etc/samba/smb.conf 9) sudo samba-tool domain provision --server-role=dc --use-rfc2307 --dns-backend=SAMBA_INTERNAL --realm=samba-dc.EXAMPLE.COM --domain=SAMBA --adminpass=Password1 10) sudo cp /var/lib/samba/private/krb5.conf /etc/krb5.conf 11) sudo systemctl mask smbd nmbd winbind 12) sudo systemctl disable smbd nmbd winbind 13) sudo systemctl stop smbd nmbd winbind 14) sudo systemctl unmask samba-ad-dc 15) sudo systemctl start samba-ad-dc 16) sudo systemctl enable samba-ad-dc 17) sudo reboot 18) sudo systemctl stop systemd-resolved 19) sudo systemctl disable systemd-resolved 20) cat << EOF >> /etc/resolv.conf nameserver 192.168.122.199 search SAMBA EOF 21) sudo reboot 22) host -t SRV _ldap._tcp.samba-dc.example.com _ldap._tcp.samba-dc.example.com has SRV record 0 100 389 samba-dc.samba-dc.example.com. 23) $ smbclient -L localhost -N Anonymous login successful Sharename Type Comment - --- sysvol Disk netlogonDisk IPC$IPC IPC Service (Samba 4.13.17-Ubuntu) SMB1 disabled -- no workgroup available 24) $ smbclient //localhost/netlogon -UAdministrator -c 'ls' Enter SAMBA\Administrator's password: . D0 Mon Feb 28 04:23:22 2022 .. D0 Mon Feb 28 04:23:27 2022 9983232 blocks of size 1024. 7995324 blocks available 25) kinit administrator Password for administra...@samba-dc.example.com: Warning: Your password will expire in 41 days on Mon Apr 11 04:23:27 2022 26) klist Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: administra...@samba-dc.example.com Valid starting ExpiresService principal 02/28/22 04:32:47 02/28/22 14:32:47 krbtgt/samba-dc.example@samba-dc.example.com renew until 03/01/22 04:32:44 27) Create a share: 28) sudo mkdir -p /srv/samba/Demo/ 29) sudo vim /etc/samba/smb.conf [Demo] path = /srv/samba/Demo/ read only = no 30) sudo chmod 0770 /srv/samba/Demo/ Install a fresh 20.04.4 Desktop instance, and run the following: 31) sudo apt install realmd smbclient 32) sudo vim /etc/hosts Add an entry with its IP address, e.g.: 192.168.122.199samba-dc samba-dc.example.com 33) sudo realm join --user=Administrator SAMBA-DC.EXAMPLE.COM $ smbclient -U Administrator //samba-dc.example.com/demo Enter WORKGROUP\Administrator's password: Try "help" to get a list of possible commands. smb: \> ls . D0 Mon Mar 7 15:20:30 2022 .. D0 Mon Mar 7 15:20:30 2022 9983232 blocks of size 1024. 7686220 blocks available $ smbclient //samba-dc.example.com/demo -k gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in NEG_TOKEN_INIT session setup failed: NT_STATUS_INVALID_PARAMETER Now open Nautilus, add smb://samba-dc.example.com/demo as a share, and you will be faced with a dialog box asking for username / password credentials. Close Nautilus. Let's get a kerberos ticket: $ kinit administra...@samba-dc.example.com Password for administra...@samba-dc.example.com: Warning: Your password will expire in 11 days on Mon 11 Apr 2022 16:23:27 $ smbclient //samba-dc.example.com/demo -k Try "help" to get a list of possible commands. smb: \> ls . D0 Mon Mar 7 15:20:30 2022 .. D0 Mon Mar 7 15:20:30 2022 9983232 blocks of size 1024. 7616832 blocks available 34) Open Nautilus, add smb://samba-dc.example.com/demo as a share, and it will open correctly using kerberos credentials. When I look at my process list, gvfsd is where it is suppose to be, under the systemd user session: $ ps auxf ... ubuntu 1207 0.5 0.2 19008 10128 ?Ss 12:12 0:00 /lib/systemd/systemd --user ubuntu 1208 0.0 0.0 179632 3544 ?S12:12 0:00 \_ (sd-pam) ubuntu
[Bug 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell
Hi Daniel, I installed gnome-shell 42.0-1ubuntu1 from -proposed, along with mutter and others this morning and rebooted. I am no longer able to reproduce this issue, I can move the mouse as the screen is fading, and I can click things and enter text as normal. I will close the bug in a couple of days if I don't see it again, but I think it has been fixed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964545 Title: 42beta: moving mouse as screen is fading to screensaver prevents input to shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964545/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
