[Bug 1920202] Re: Updated to kernel 5.4.0-67-generic and Xen DomU stoped working
Possibly related (if 3499ba8198ca ("xen: Fix event channel callback via
INTX/GSI") was backported to 5.4.0-67 ):
https://gitlab.alpinelinux.org/alpine/aports/-/issues/12373
https://lore.kernel.org/xen-devel/4c9af052a6e0f6485d1de43f2c38b1461996db99.ca...@infradead.org/
** Bug watch added: gitlab.alpinelinux.org/alpine/aports/-/issues #12373
https://gitlab.alpinelinux.org/alpine/aports/-/issues/12373
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920202
Title:
Updated to kernel 5.4.0-67-generic and Xen DomU stoped working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1920202/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901311] [NEW] Fort segfaults after multiple "doesn't have files with extension '.slurm'" events
Public bug reported: Fort segfaults after multiple "doesn't have files with extension '.slurm'" events Also see upstream report: https://github.com/NICMx/FORT-validator/issues/41 This is fixed in v1.4.1 Debian already ships v1.4.1: https://packages.debian.org/bullseye/fort-validator Please upgrade groovy from 1.4.0-1 to 1.4.1-1 (Debian). Please also upgrade focal to 1.4.1-1 (Debian). ** Affects: fort-validator (Ubuntu) Importance: Undecided Status: New ** Description changed: Fort segfaults after multiple "doesn't have files with extension '.slurm'" events Also see upstream report: https://github.com/NICMx/FORT-validator/issues/41 This is fixed in v1.4.1 - Debian already ships v1.4.1: https://packages.debian.org/bullseye/fort-validator - - Please upgrade from groovy from 1.4.0-1 to 1.4.1-1 (Debian). + Please upgrade groovy from 1.4.0-1 to 1.4.1-1 (Debian). Please also upgrade focal to 1.4.1-1 (Debian). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901311 Title: Fort segfaults after multiple "doesn't have files with extension '.slurm'" events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fort-validator/+bug/1901311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889669] Re: Focal update: v5.4.54 upstream stable release
Would probably fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890951 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889669 Title: Focal update: v5.4.54 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890951] Re: btrfs not writable when mounted without "skip_balance"
Also see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889669 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641429] Re: tcpdump capture filter for vlans incorrect
The kernel now longer passes vlan tag information as-is to libpcap, instead BPF needs to access ancillary data. That is the reason "vlan 114" works (because it does the right thing), and a manual filter doesn't, because libpcap never actually sees this. Offsets are negative because this is the way to access this ancillary data (like vlan tags) in the Linux kernel: https://github.com/torvalds/linux/blob/6f0d349d922ba44e4348a17a78ea51b7135965b1/include/uapi/linux/filter.h#L60 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641429 Title: tcpdump capture filter for vlans incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcpdump/+bug/1641429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525724] Re: boot hangs with more than 1 luks device in crypttab
I tried Xenial. Yes it does fix the simplified test case in this bug (when booting doesn't require the second encrypted volume to be open), but it doesn't fix my real issue, which is encrypting multiple devices and putting btrfs on top of it. Adding initramfs doesn't help. So whenever you try booting from multiple encrypted devices it will fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525724 Title: boot hangs with more than 1 luks device in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1525724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525724] [NEW] boot hangs with more than 1 luks device in crypttab
Public bug reported: When /etc/crypttab has more than one luks device, the boot process locks up (hangs) after the decryption of the first luks device. A password prompt for the second luks device never appears. Affected: Ubuntu 15.04 (vivid) Ubuntu 15.10 (wily) Works fine in: Ubuntu 14.10 (utopic) When upgrading utopic to vivid in the affected configuration, the bug is triggered as well (first boot into vivid). Testcase: - install (text mode) from ubuntu-15.10-server-amd64.iso - manually partition the disk (see attached installer-partitions.png): -> sda1: 512mb ext2 for /boot/ (unencrypted) -> sda2: 4GB encrypted (luks) -> sda2_crypt -> sda3: 2GB encrypted (luks) -> sda3_crypt -> sda2_crypt: ext4 for / -> sda3_crypt: ext4 for /tmp boot will hang (boot-hang.png) after decrypting sda2. My real use-case is to encrypt multiple physical hard drivers, which fails exactly the same way (the test config doesn't make much sense, but its simple to reproduce). Commenting sda3_crypt in /etc/fstab and adding a the option nofail to sda3_crypt in /etc/crypttab makes the OS boot. # cat /etc/crypttab sda2_crypt UUID=b41558ee-eb5b-463a-a1a5-34e1cc6b05e9 none luks,discard sda3_crypt UUID=c1c660d3-2e70-4761-85a2-6f635719f8cd none luks,discard # cat /etc/fstab # /dev/mapper/sda2_crypt / ext4errors=remount-ro 0 1 # /boot was on /dev/sda1 during installation UUID=56e38284-0cef-4e8a-b933-c82f70ef4588 /boot ext2defaults 0 2 #/dev/mapper/sda3_crypt /tmpext4defaults0 2 # blkid /dev/mapper/sda2_crypt: UUID="8413bc48-13e7-4b19-aabc-42b6b19101a5" TYPE="ext4" /dev/sda1: UUID="56e38284-0cef-4e8a-b933-c82f70ef4588" TYPE="ext2" PARTUUID="ec85536d-0bb5-44c8-a3ba-93ae539e4ef1" /dev/sda2: UUID="b41558ee-eb5b-463a-a1a5-34e1cc6b05e9" TYPE="crypto_LUKS" PARTUUID="4f76f8cb-b170-4a07-a412-832ba2964377" /dev/sda3: UUID="c1c660d3-2e70-4761-85a2-6f635719f8cd" TYPE="crypto_LUKS" PARTUUID="ef6c816c-71d3-4d36-88e7-eb2ddae2a06a" ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Attachment added: "boot-hang.png" https://bugs.launchpad.net/bugs/1525724/+attachment/4534337/+files/boot-hang.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525724 Title: boot hangs with more than 1 luks device in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1525724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525724] Re: boot hangs with more than 1 luks device in crypttab
** Attachment added: "installer-partitions.png" https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1525724/+attachment/4534338/+files/installer-partitions.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525724 Title: boot hangs with more than 1 luks device in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1525724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
