[Bug 1969845] [NEW] grub-efi-amd64-signed does not respect grub2/update_nvram
Public bug reported: Hi, Unlike grub-efi-amd64, grub-efi-amd64-signed doesn't respect the value of "grub2/update_nvram": # debconf-show grub-efi-amd64 | grep grub2/update_nvram: * grub2/update_nvram: false # efibootmgr BootCurrent: 0002 Timeout: 1 seconds BootOrder: 0002,0003,0004,0007 Boot0002* UEFI: PXE IP4 P0 Intel(R) Ethernet Controller X550 Boot0003* UEFI: PXE IP4 P1 Intel(R) Ethernet Controller X550 Boot0004* UEFI: Built-in EFI Shell Boot0007* UEFI: PXE IP4 P0 American Megatrends Inc. # dpkg-reconfigure grub-efi-amd64-signed Installing grub to /boot/efi. Installing for x86_64-efi platform. Installation finished. No error reported. Installing grub to /var/lib/grub/esp. Installing for x86_64-efi platform. Installation finished. No error reported. # # debconf-show grub-efi-amd64 | grep grub2/update_nvram: * grub2/update_nvram: false # efibootmgr BootCurrent: 0002 Timeout: 1 seconds BootOrder: 0002,0003,0004,0007 Boot0002* UEFI: PXE IP4 P0 Intel(R) Ethernet Controller X550 Boot0003* UEFI: PXE IP4 P1 Intel(R) Ethernet Controller X550 Boot0004* UEFI: Built-in EFI Shell Boot0007* UEFI: PXE IP4 P0 American Megatrends Inc. # dpkg-reconfigure grub-efi-amd64-signed Installing grub to /boot/efi. Installing for x86_64-efi platform. Installation finished. No error reported. Installing grub to /var/lib/grub/esp. Installing for x86_64-efi platform. Installation finished. No error reported. # efibootmgr BootCurrent: 0002 Timeout: 1 seconds BootOrder: ,0001,0002,0003,0004,0007 Boot* ubuntu Boot0001* ubuntu Boot0002* UEFI: PXE IP4 P0 Intel(R) Ethernet Controller X550 Boot0003* UEFI: PXE IP4 P1 Intel(R) Ethernet Controller X550 Boot0004* UEFI: Built-in EFI Shell Boot0007* UEFI: PXE IP4 P0 American Megatrends Inc. This is especially problematic as grub-efi-amd64-signed is a dependency of shim-signed, an essential package, making its removal slightly problematic. From what I see, the postinst script is too simple: https://git.launchpad.net/~git-ubuntu- import/ubuntu/+source/grub2-signed/tree/debian/grub-efi- amd64-signed.postinst?h=import/1.180#n14 It should probably do something similar to grub-efi-amd64's postinst, i.e. run_grub_multi_install --target="$target" "$NO_EXTRA_REMOVABLE" "$NO_NVRAM" I also noticed that Debian doesn't have a postinst script for grub-efi- amd64-signed so I don't have a problem there. ** Affects: grub2 (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/1969845 Title: grub-efi-amd64-signed does not respect grub2/update_nvram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1969845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969841] Re: grub-efi-amd64: grub-efi/install_devices depends on the value of LC_COLLATE/LANG
** Description changed: Hi, As discussed with Julian Andres Klode on IRC, there are cases where the value of grub-efi/install_devices is affected by the value of LC_COLLATE. This is caused by this unique sort: https://git.launchpad.net/~ubuntu- core-dev/grub/+git/ubuntu/tree/debian/grub-multi- install?h=debian/2.06-2ubuntu7#n220 # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 From what I see, this can only happen on systems with NVMe drives: # find -L /dev/disk/by-id/ -samefile /dev/nvme0n1p1 /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1 /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 Let's assume grub-efi/install_devices has the following value: # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 This was obtained with this LANG/LC_COLLATE: # echo $LANG C.UTF-8 # dpkg-reconfigure grub-efi-amd64 - │ GRUB EFI system partitions: │ - │ │ - │[*] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ - │[*] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ + │ GRUB EFI system partitions: │ + │ │ + │[*] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ + │[*] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 We can see that the boxes are properly ticked here. However: # export LANG=en_US.UTF-8; dpkg-reconfigure grub-efi-amd64 - │ GRUB EFI system partitions: │ - │ │ - │[ ] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ + │ GRUB EFI system partitions: │ + │ │ + │[ ] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ │[ ] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000│ The boxes are not ticked, if I tick them, I get the following: # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: - * grub-efi/install_devices: /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1, /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b4466-part1 + * grub-efi/install_devices: /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1, /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b4466-part1 - - I assume the postinst script for grub-pc exhibits the same bug. + I assume the postinst script for grub-pc exhibits the same bug with the + value of grub-pc/install_devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969841 Title: grub-efi-amd64: grub-efi/install_devices depends on the value of LC_COLLATE/LANG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1969841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969841] [NEW] grub-efi-amd64: grub-efi/install_devices depends on the value of LC_COLLATE/LANG
Public bug reported: Hi, As discussed with Julian Andres Klode on IRC, there are cases where the value of grub-efi/install_devices is affected by the value of LC_COLLATE. This is caused by this unique sort: https://git.launchpad.net/~ubuntu- core-dev/grub/+git/ubuntu/tree/debian/grub-multi- install?h=debian/2.06-2ubuntu7#n220 # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 From what I see, this can only happen on systems with NVMe drives: # find -L /dev/disk/by-id/ -samefile /dev/nvme0n1p1 /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1 /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 Let's assume grub-efi/install_devices has the following value: # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 This was obtained with this LANG/LC_COLLATE: # echo $LANG C.UTF-8 # dpkg-reconfigure grub-efi-amd64 │ GRUB EFI system partitions: │ │ │ │[*] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ │[*] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 We can see that the boxes are properly ticked here. However: # export LANG=en_US.UTF-8; dpkg-reconfigure grub-efi-amd64 │ GRUB EFI system partitions: │ │ │ │[ ] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ │[ ] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ The boxes are not ticked, if I tick them, I get the following: # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1, /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b4466-part1 I assume the postinst script for grub-pc exhibits the same bug with the value of grub-pc/install_devices. ** Affects: grub2 (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/1969841 Title: grub-efi-amd64: grub-efi/install_devices depends on the value of LC_COLLATE/LANG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1969841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
** Also affects: grub2 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: grub2 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) 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/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
So testing with Fedora's boot/efi/EFI/fedora/grubx64.efi in place of the Ubuntu version solves the problem. So it is indeed the situation that you describe in comment #15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
Hi xnox, Thanks for the reply. I'll test both options and report to you here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Re: Jammy kernel does not boot when Secure Encrypted Virtualization( SEV) is enabled
Recent tests with the most recent 5.15 kernel (5.15.0-25-generic) do display the same problem, though the symptom is different. Booting w/o the swiotlb=262144 leads to the boot sequence stopping after these messages : [1.376749] i2c i2c-0: Memory type 0x07 not supported yet, not instantiating SPD [1.379840] cryptd: max_cpu_qlen set to 1000 [1.381359] scsi host1: ahci [1.384854] AVX2 version of gcm_enc/dec engaged. [1.385579] AES CTR mode by8 optimization enabled [1.386280] scsi host2: ahci [1.387162] scsi host3: ahci [1.387659] scsi host4: ahci [1.388141] scsi host5: ahci [1.388675] scsi host6: ahci [1.389091] ata1: SATA max UDMA/133 abar m4096@0x9100 port 0x91000100 irq 36 [1.389937] ata2: SATA max UDMA/133 abar m4096@0x9100 port 0x91000180 irq 36 [1.390787] ata3: SATA max UDMA/133 abar m4096@0x9100 port 0x91000200 irq 36 [1.391599] ata4: SATA max UDMA/133 abar m4096@0x9100 port 0x91000280 irq 36 [1.392417] ata5: SATA max UDMA/133 abar m4096@0x9100 port 0x91000300 irq 36 [1.393251] ata6: SATA max UDMA/133 abar m4096@0x9100 port 0x91000380 irq 36 [1.707933] ata3: SATA link down (SStatus 0 SControl 300) [1.709684] ata4: SATA link down (SStatus 0 SControl 300) [1.711379] ata5: SATA link down (SStatus 0 SControl 300) [1.712945] ata2: SATA link down (SStatus 0 SControl 300) [1.714405] ata1: SATA link down (SStatus 0 SControl 300) [1.715926] ata6: SATA link down (SStatus 0 SControl 300) [3.352937] pcieport :00:1e.0: pciehp: Slot(0): No device found [3.356935] pcieport :00:1e.2: pciehp: Slot(2): No device found [3.368942] pcieport :00:1e.1: pciehp: Slot(1): No device found [3.368958] pcieport :00:1e.3: pciehp: Slot(3): No device found [3.384970] pcieport :00:1e.4: pciehp: Slot(4): No device found [3.384991] pcieport :00:1e.6: pciehp: Slot(6): No device found [3.396926] pcieport :00:1e.5: pciehp: Slot(5): No device found [3.396957] pcieport :00:1e.7: pciehp: Slot(7): No device found And after a period of time we start seeing : [ 242.880954] INFO: task kworker/u16:0:8 blocked for more than 120 seconds. [ 242.882063] Not tainted 5.15.0-25-generic #25-Ubuntu [ 242.882895] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.884165] task:kworker/u16:0 state:D stack:0 pid:8 ppid: 2 flags:0x4000 [ 242.885520] Workqueue: events_unbound async_run_entry_fn [ 242.886383] Call Trace: [ 242.886783] [ 242.887133] __schedule+0x23d/0x590 [ 242.887716] schedule+0x4e/0xb0 [ 242.888221] async_synchronize_cookie_domain+0xcc/0x110 [ 242.889077] ? wait_woken+0x70/0x70
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
** 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/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
Here is the result of a similar bisect on the bionic kernel : https://kernel.ubuntu.com/git/ubuntu/ubuntu- bionic.git/commit/?id=091554e4a5b2a7647830a1c7beea781148b51509 091554e4a5b2a7647830a1c7beea781148b51509 is the first bad commit commit 091554e4a5b2a7647830a1c7beea781148b51509 Author: Lenny Szubowicz Date: Tue Nov 30 12:04:00 2021 +0100 efi: Support for MOK variable config table BugLink: https://bugs.launchpad.net/bugs/1928679 Because of system-specific EFI firmware limitations, EFI volatile variables may not be capable of holding the required contents of the Machine Owner Key (MOK) certificate store when the certificate list grows above some size. Therefore, an EFI boot loader may pass the MOK certs via a EFI configuration table created specifically for this purpose to avoid this firmware limitation. An EFI configuration table is a much more primitive mechanism compared to EFI variables and is well suited for one-way passage of static information from a pre-OS environment to the kernel. This patch adds initial kernel support to recognize, parse, and validate the EFI MOK configuration table, where named entries contain the same data that would otherwise be provided in similarly named EFI variables. Additionally, this patch creates a sysfs binary file for each EFI MOK configuration table entry found. These files are read-only to root and are provided for use by user space utilities such as mokutil. A subsequent patch will load MOK certs into the trusted platform key ring using this infrastructure. Signed-off-by: Lenny Szubowicz Link: https://lore.kernel.org/r/20200905013107.10457-2-lszub...@redhat.com Signed-off-by: Ard Biesheuvel (cherry picked from commit 58c909022a5a56cd1d9e89c8c5461fd1f6a27bb5) Signed-off-by: Dimitri John Ledkov Acked-by: Thadeu Lima de Souza Cascardo Acked-by: Tim Gardner Signed-off-by: Kleber Sacilotto de Souza arch/x86/kernel/setup.c | 1 + drivers/firmware/efi/Makefile | 1 + drivers/firmware/efi/arm-init.c | 1 + drivers/firmware/efi/efi.c | 9 + drivers/firmware/efi/mokvar-table.c | 360 include/linux/efi.h | 34 6 files changed, 406 insertions(+) create mode 100644 drivers/firmware/efi/mokvar-table.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title:
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
Hello @kmously, yes I am able to reproduce the same panic on 4.15.0-166. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
According to the following advisory[1] from HP, this is a known issue which is fixed upstream : "Advisory: Red Hat Enterprise Linux 8.3 - Guest Stops Responding at efi_mokvar_sysfs_init+0xa9/0x19d with AMD Secure Encrypted Virtualization (SEV) Enabled" The upstream fix cited in the article is the following : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b x86/ioremap: Map EFI-reserved memory as encrypted for SEV Adding this commit on top of kernel 5.4.0-92.103 does fix the booting issue. [1] https://support.hpe.com/hpesc/public/docDisplay?docId=a00119071en_us=en_US ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) 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/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
** Description changed: The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot when SEV is enabled. The kernel panics with the following backtrace : [1.531125] ledtrig-cpu: registered to indicate activity on CPUs [1.531760] EFI Variables Facility v0.08 2004-May-17 [1.532575] general protection fault: [#1] SMP NOPTI [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15 [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015 [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.535120] RBP: b96e4001be10 R08: R09: 0228 [1.538947] R10: 0001 R11: R12: 978437e555a0 [1.538947] R13: R14: R15: [1.538947] FS: () GS:97843f6c() knlGS: [1.538947] CS: 0010 DS: ES: CR0: 80050033 [1.538947] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.538947] Call Trace: [1.538947] ? efi_rci2_sysfs_init+0x29a/0x29a [1.538947] do_one_initcall+0x4a/0x200 [1.538947] kernel_init_freeable+0x1c0/0x263 [1.538947] ? rest_init+0xb0/0xb0 [1.538947] kernel_init+0xe/0x110 [1.538947] ret_from_fork+0x22/0x40 [1.538947] Modules linked in: [1.545871] ---[ end trace 815dc8177e65da02 ]--- [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.550617] RBP: b96e4001be10 R08: R09: 0228 [1.551337] R10: 0001 R11: R12: 978437e555a0 [1.552036] R13: R14: R15: [1.552737] FS: () GS:97843f6c() knlGS: [1.553529] CS: 0010 DS: ES: CR0: 80050033 [1.554093] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.554818] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ]--- - - - The previous kernel (linux-image-5.4.0-91-generic) boots correctly with SEV. + The previous kernel (linux-image-5.4.0-91-generic) boots correctly with + SEV. Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the following commit as the source of regresssion : # git bisect good - Bisecting: 0 revisions left to test after this (roughly 1 step) - [5f79bc17fd8d078378a9f3c8773ebcb506cb6f40] Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." + 7ca05228f713c24eb55574b36e32d9b54c5a1b76 is the first bad commit + commit 7ca05228f713c24eb55574b36e32d9b54c5a1b76 + Author: Lenny Szubowicz + Date: Fri Sep 4 21:31:05 2020 -0400 + + efi: Support for MOK variable config table + + BugLink: https://bugs.launchpad.net/bugs/1928679 + + ... Since the panic happens in very early stages of boot, no trace of the panic is present in the log files and apparently it is not possible to collect a kernel crash dump, the crashkernel has not been enabled yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
Details of the bisected commit : https://kernel.ubuntu.com/git/ubuntu/ubuntu- focal.git/commit/?id=5f79bc17fd8d078378a9f3c8773ebcb506cb6f40 Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." BugLink: https://bugs.launchpad.net/bugs/1932029 This partially reverts commit f32d73b5b9b4d8cb8e64bf51091c971d05116d48. The reverted commit fixed stray warnings, and changed get_cert_list() function prototype (return rc, pass cert-list by reference). The stray warnings fix was incomplete, and was done again in mainline with a different change of get_cert_list() function prototype (return cert-list pointer, pass EFI error status by reference), which got also cherrypicked into Ubuntu kernel ending up with passing both cert-list & efi error status by reference. Cherrypicking both get_cert_list() function prototype changes is redundant, and prevents clean cherrypicks from mainline. Revert the get_cert_list() function prototype to the one in mainline. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956575] [NEW] [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
Public bug reported: The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot when SEV is enabled. The kernel panics with the following backtrace : [1.531125] ledtrig-cpu: registered to indicate activity on CPUs [1.531760] EFI Variables Facility v0.08 2004-May-17 [1.532575] general protection fault: [#1] SMP NOPTI [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15 [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015 [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.535120] RBP: b96e4001be10 R08: R09: 0228 [1.538947] R10: 0001 R11: R12: 978437e555a0 [1.538947] R13: R14: R15: [1.538947] FS: () GS:97843f6c() knlGS: [1.538947] CS: 0010 DS: ES: CR0: 80050033 [1.538947] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.538947] Call Trace: [1.538947] ? efi_rci2_sysfs_init+0x29a/0x29a [1.538947] do_one_initcall+0x4a/0x200 [1.538947] kernel_init_freeable+0x1c0/0x263 [1.538947] ? rest_init+0xb0/0xb0 [1.538947] kernel_init+0xe/0x110 [1.538947] ret_from_fork+0x22/0x40 [1.538947] Modules linked in: [1.545871] ---[ end trace 815dc8177e65da02 ]--- [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.550617] RBP: b96e4001be10 R08: R09: 0228 [1.551337] R10: 0001 R11: R12: 978437e555a0 [1.552036] R13: R14: R15: [1.552737] FS: () GS:97843f6c() knlGS: [1.553529] CS: 0010 DS: ES: CR0: 80050033 [1.554093] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.554818] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ]--- - The previous kernel (linux-image-5.4.0-91-generic) boots correctly with SEV. Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the following commit as the source of regresssion : # git bisect good Bisecting: 0 revisions left to test after this (roughly 1 step) [5f79bc17fd8d078378a9f3c8773ebcb506cb6f40] Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." Since the panic happens in very early stages of boot, no trace of the panic is present in the log files and apparently it is not possible to collect a kernel crash dump, the crashkernel has not been enabled yet. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Summary changed: - [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enagbled + [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
Hello, The kernel panic occurs very early in the boot sequence, even before the root fs is mounted to capture the log. Here is the kenrel backtrace : [1.251773] Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer [1.253440] CPU: 2 PID: 212 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu [1.255022] Hardware name: Scaleway SCW-ENT1-S, BIOS 0.0.0 02/06/2015 [1.256228] Call Trace: [1.256697] show_stack+0x52/0x58 [1.257355] dump_stack+0x7d/0x9c [1.257989] panic+0x101/0x2e3 [1.258821] swiotlb_tbl_map_single.cold+0x57/0x7c [1.259750] swiotlb_map+0x61/0x240 [1.260428] dma_direct_map_page+0x115/0x1a0 [1.261255] dma_map_page_attrs+0x35/0x50 [1.262016] vring_map_one_sg+0x4c/0x50 [1.262787] virtqueue_add_split+0x23c/0x4a0 [1.263427] virtqueue_add_inbuf+0x48/0x50 [1.263909] virtscsi_kick_event.isra.0+0x8b/0xd0 [virtio_scsi] [1.264616] virtscsi_probe+0x31e/0x33b [virtio_scsi] [1.265216] virtio_dev_probe+0x163/0x220 [1.265683] really_probe+0x24b/0x4c0 [1.266134] driver_probe_device+0xf0/0x160 [1.266647] device_driver_attach+0xab/0xb0 [1.267188] __driver_attach+0xb2/0x140 [1.267648] ? device_driver_attach+0xb0/0xb0 [1.268163] bus_for_each_dev+0x7e/0xc0 [1.268620] driver_attach+0x1e/0x20 [1.269061] bus_add_driver+0x135/0x1f0 [1.269516] driver_register+0x95/0xf0 [1.269957] ? 0xc038e000 [1.270344] register_virtio_driver+0x20/0x30 [1.270885] init+0x8d/0x1000 [virtio_scsi] [1.271380] ? 0xc038e000 [1.271762] do_one_initcall+0x48/0x1d0 [1.272213] ? kmem_cache_alloc_trace+0xfb/0x240 [1.272759] do_init_module+0x62/0x290 [1.273199] load_module+0xa8f/0xb10 [1.273620] __do_sys_finit_module+0xc2/0x120 [1.274155] __x64_sys_finit_module+0x18/0x20 [1.274680] do_syscall_64+0x61/0xb0 [1.275118] ? syscall_exit_to_user_mode+0x27/0x50 [1.275667] ? __x64_sys_newfstatat+0x1c/0x20 [1.276177] ? do_syscall_64+0x6e/0xb0 [1.276614] ? ksys_read+0x67/0xe0 [1.277049] ? exit_to_user_mode_prepare+0x37/0xb0 [1.277614] ? syscall_exit_to_user_mode+0x27/0x50 [1.278180] ? __x64_sys_read+0x19/0x20 [1.278653] ? do_syscall_64+0x6e/0xb0 [1.279116] entry_SYSCALL_64_after_hwframe+0x44/0xae [1.279709] RIP: 0033:0x7fe040ccd94d [1.280140] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 64 0f 00 f7 d8 64 89 01 48 [1.282337] RSP: 002b:7ffe2399a6d8 EFLAGS: 0246 ORIG_RAX: 0139 [1.283252] RAX: ffda RBX: 562e8ab7a030 RCX: 7fe040ccd94d [1.284077] RDX: RSI: 7fe040e61441 RDI: 0005 [1.284910] RBP: 0002 R08: R09: 7ffe2399a810 [1.285754] R10: 0005 R11: 0246 R12: 7fe040e61441 [1.286594] R13: 562e8ab79ef0 R14: 562e8abd1c50 R15: 562e8abd4400 [1.288517] Kernel Offset: 0x25a0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.289795] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer ]--- - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
As a complement of information, here are the messages pertaining to the TLB during the log : $ grep -i tlb swiotlb_crash.out [0.003802] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB [0.037784] kvm-guest: KVM setup pv remote TLB flush [0.040674] software IO TLB: Cannot allocate buffer [0.229918] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.230877] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.322941] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.324641] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [0.799064] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.800761] software IO TLB: No low mem [1.251773] Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer [1.258821] swiotlb_tbl_map_single.cold+0x57/0x7c [1.259750] swiotlb_map+0x61/0x240 [1.289795] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549376/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549375/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549374/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549373/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549372/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549371/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549370/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549369/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549368/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549367/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] [NEW] kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
Public bug reported: While investigating LP: #1955395 by using the -generic kernel image, it appeared that it is impossible to boot the kernel unless the boot parameter swiotlb is set to 512M (swiotlb=262144). Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb it fails and later trigger a kernel panic with the following trace : $ grep TLB /tmp/console.log [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB [0.034219] kvm-guest: KVM setup pv remote TLB flush [0.037063] software IO TLB: Cannot allocate buffer [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [1.019552] software IO TLB: No low mem [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer ]--- The SWIOTLB adjustment comes from the following kernel commit : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12 For some reason, the LowMem allocation fails (as seen by the "software IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be completed. When booting with the swiotlb=262144 value, we get the following output : $ grep TLB /tmp/console.log [0.050908] kvm-guest: KVM setup pv remote TLB flush [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [1.071837] software IO TLB: mapped [mem 0x5bebe000-0x7bebe000] (512MB) [1.529804] software IO TLB: Memory encryption is active and system is using DMA bounce buffers For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without the need to set the swiotlb= value at boot time. The SWIOTLB buffer adjustment has been introduced in kernel 5.11. We can make SEV enabled resources available for testing if needed. ...Louis --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 23 13:32 seq crw-rw 1 root audio 116, 33 Dec 23 13:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Scaleway SCW-ENT1-S Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 swiotlb=262144 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-S:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku: dmi.product.name: SCW-ENT1-S dmi.product.version: pc-q35-3.0 dmi.sys.vendor: Scaleway ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected jammy uec-images ** Tags added: apport-collected jammy uec-images ** Description changed: While investigating LP: #1955395 by using the -generic kernel image, it appeared that it is impossible to boot the kernel unless the boot parameter swiotlb is set to 512M (swio
[Bug 1955395] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548709/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548710/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548708/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548707/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548706/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548705/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548704/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548703/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Re: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled
apport information ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Confirmed ** Tags added: apport-collected uec-images ** Description changed: Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm flavor of the kernel does not boot on a QEMU server with Secure Encrypted Virtualization( SEV) enabled. Using the same kernel without the -kvm optimisation does boot correctly + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Dec 20 10:41 seq + crw-rw 1 root audio 116, 33 Dec 20 10:41 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu74 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: + + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: Scaleway SCW-ENT1-XL + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 swiotlb=262144 + ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-23-generic N/A + linux-backports-modules-5.13.0-23-generic N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: jammy uec-images + Uname: Linux 5.13.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 02/06/2015 + dmi.bios.release: 0.0 + dmi.bios.vendor: EFI Development Kit II / OVMF + dmi.bios.version: 0.0.0 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-q35-3.0 + dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku: + dmi.product.name: SCW-ENT1-XL + dmi.product.version: pc-q35-3.0 + dmi.sys.vendor: Scaleway ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548701/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548702/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Re: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+attachment/5548694/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Re: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+attachment/5548693/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] [NEW] KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled
Public bug reported: Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm flavor of the kernel does not boot on a QEMU server with Secure Encrypted Virtualization( SEV) enabled. Using the same kernel without the -kvm optimisation does boot correctly ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Tags: jammy ** Also affects: linux (Ubuntu Jammy) 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/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948669] [NEW] linux-image-generic should suggest linux-firmware instead of depending on it
Public bug reported: Hello, At the moment, the only way to install linux-modules-extra and keep it up-to-date is to rely on linux-image-generic: # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy linux-image-generic linux-image-generic: Installed: (none) Candidate: 5.4.0.89.93 Version table: 5.4.0.89.93 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages # apt rdepends linux-modules-extra-5.4.0-89-generic linux-modules-extra-5.4.0-89-generic Reverse Depends: Depends: linux-image-generic However, installing linux-image-generic pulls linux-firmware: # apt depends linux-image-generic linux-image-generic Depends: linux-image-5.4.0-89-generic Depends: linux-modules-extra-5.4.0-89-generic Depends: linux-firmware Depends: intel-microcode Depends: amd64-microcode Recommends: thermald I specifically need linux-modules-extra because it contains the r8169 module which some Ethernet controllers require. The driver doesn't need any of the firmware blobs but because of the way it is packaged, I end up creating Ubuntu installations several hundred megabytes larger than necessary (in my case, these extra megabytes do matter). The initramfs also gains a few dozen megabytes. Would it please be possible to either: - mark linux-firmware as "Recommends" instead of "Depends"? - create a metapackage that pulls only the latest version of linux-modules-extra and nothing else? In addition, I'm not 100% sure linux-modules-extra should have a hard dependency on crda or wireless-crda, maybe they could also be marked as recommended instead? ** Affects: linux-meta (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/1948669 Title: linux-image-generic should suggest linux-firmware instead of depending on it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1948669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945311] [NEW] Fix for CVE-2021-40438 breaks existing configs
Public bug reported: The patches introduced for CVE-2021-40438 break existing configs. For example on Plesk: https://support.plesk.com/hc/en-us/articles/4407366133906-Website-suddenly-started-to-show-500-error-AH10292-Invalid-proxy-UDS-filename Upstream pushed some additional fixes for it: https://github.com/apache/httpd/commit/6d476a66956a6a81ac8e1f7f419ef0697b9a0b76 https://github.com/apache/httpd/commit/6d76cbb9100bf34250ffba0bded08e075380be88 In Debian I guess they will be included also according to https://salsa.debian.org/apache- team/apache2/-/commit/e36582e866cd7e87600235ff9fcd47b960899e24 So I think it might be good to include those 2 into Ubuntu as well. ** Affects: apache2 (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945311 Title: Fix for CVE-2021-40438 breaks existing configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1945311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter
Ok, thanks for the update. On Sun, Jul 4, 2021 at 5:30 PM mipser <1867...@bugs.launchpad.net> wrote: > Forgot to mention this is on a mid-2011 macbook air running Ubuntu 18.04 > LTS which I just apt upgrade'd > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1867092 > > Title: > Failed to set MokListRT: Invalid Parameter > > Status in grub2 package in Ubuntu: > Invalid > Status in mokutil package in Ubuntu: > Invalid > Status in shim package in Ubuntu: > Triaged > Status in shim-signed package in Ubuntu: > Triaged > > Bug description: > Hello, > I am testing Ubuntu 20.04 Daily built the latest version on my MacBook > pro-13inch late 2012 model Non-retina display. and I am getting the error > while I boot my MacBook using a Pendrive in which I have installed the > Ubuntu Daily 20.04 OS. > Error is as follows : > > Failed. to set MokListRT: Invalid Parameter > Could not create MokListRT: Invalid Parameter > Importing MOK states has failed: import_mok_state() failed : invalid > Parameter > Continuing boot since secure mode is disabled. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.4.0-14-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.11-0ubuntu20 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Thu Mar 12 10:40:44 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: > installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller > [106b:00fa] > InstallationDate: Installed on 2020-03-11 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 > (20200309) > MachineType: Apple Inc. MacBookPro9,2 > ProcEnviron: >LANGUAGE=en_IN:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic > root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/24/2019 > dmi.bios.vendor: Apple Inc. > dmi.bios.version: 229.0.0.0.0 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-6F01561E16C75D06 > dmi.board.vendor: Apple Inc. > dmi.board.version: MacBookPro9,2 > dmi.chassis.type: 10 > dmi.chassis.vendor: Apple Inc. > dmi.chassis.version: Mac-6F01561E16C75D06 > dmi.modalias: > dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: > dmi.product.family: MacBook Pro > dmi.product.name: MacBookPro9,2 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.100-4 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20190815-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867092 Title: Failed to set MokListRT: Invalid Parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929255] Re: update-initrd-links creates incorrect symlinks
** Also affects: linux-base (Ubuntu Bionic) 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/1929255 Title: update-initrd-links creates incorrect symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter
I certainly didn't manually change the contents of the ESP (whatever that is). Please tell me the command to update grub and re-run grub-insIstall? I was advised at one point never to upgrade but, apparently this happened anyway unattended. Is there recommended software to protect Ubuntu against malware? Thank you for your help. On Fri, May 21, 2021 at 8:20 PM Steve Langasek <1867...@bugs.launchpad.net> wrote: > Ok, that log file shows no changes to the shim-signed package version > installed. > > There is an update to grub, which would trigger re-running grub-install, > which would install the current shimx64.efi to your ESP. > > I don't know why you would not have had an up-to-date shimx64.efi on > your system previously, unless you had manually changed the contents of > the ESP. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1867092 > > Title: > Failed to set MokListRT: Invalid Parameter > > Status in grub2 package in Ubuntu: > Invalid > Status in mokutil package in Ubuntu: > Invalid > Status in shim package in Ubuntu: > Triaged > Status in shim-signed package in Ubuntu: > Triaged > > Bug description: > Hello, > I am testing Ubuntu 20.04 Daily built the latest version on my MacBook > pro-13inch late 2012 model Non-retina display. and I am getting the error > while I boot my MacBook using a Pendrive in which I have installed the > Ubuntu Daily 20.04 OS. > Error is as follows : > > Failed. to set MokListRT: Invalid Parameter > Could not create MokListRT: Invalid Parameter > Importing MOK states has failed: import_mok_state() failed : invalid > Parameter > Continuing boot since secure mode is disabled. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.4.0-14-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.11-0ubuntu20 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Thu Mar 12 10:40:44 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: > installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller > [106b:00fa] > InstallationDate: Installed on 2020-03-11 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 > (20200309) > MachineType: Apple Inc. MacBookPro9,2 > ProcEnviron: >LANGUAGE=en_IN:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic > root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/24/2019 > dmi.bios.vendor: Apple Inc. > dmi.bios.version: 229.0.0.0.0 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-6F01561E16C75D06 > dmi.board.vendor: Apple Inc. > dmi.board.version: MacBookPro9,2 > dmi.chassis.type: 10 > dmi.chassis.vendor: Apple Inc. > dmi.chassis.version: Mac-6F01561E16C75D06 > dmi.modalias: > dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: > dmi.product.family: MacBook Pro > dmi.product.name: MacBookPro9,2 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.100-4 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20190815-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867092 Title: Failed to set MokListRT: Invalid Parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions -- ubuntu-bugs mailing list
Re: [Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter
OK, Here's the history.log file. I see I had some unintended upgrades. On Fri, May 21, 2021 at 4:05 PM Steve Langasek <1867...@bugs.launchpad.net> wrote: > Please show logs (/var/log/apt/history.log) showing what versions of > shim-signed you had installed before and after the problem started. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1867092 > > Title: > Failed to set MokListRT: Invalid Parameter > > Status in grub2 package in Ubuntu: > Invalid > Status in mokutil package in Ubuntu: > Invalid > Status in shim package in Ubuntu: > Triaged > Status in shim-signed package in Ubuntu: > Triaged > > Bug description: > Hello, > I am testing Ubuntu 20.04 Daily built the latest version on my MacBook > pro-13inch late 2012 model Non-retina display. and I am getting the error > while I boot my MacBook using a Pendrive in which I have installed the > Ubuntu Daily 20.04 OS. > Error is as follows : > > Failed. to set MokListRT: Invalid Parameter > Could not create MokListRT: Invalid Parameter > Importing MOK states has failed: import_mok_state() failed : invalid > Parameter > Continuing boot since secure mode is disabled. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.4.0-14-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.11-0ubuntu20 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Thu Mar 12 10:40:44 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: > installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller > [106b:00fa] > InstallationDate: Installed on 2020-03-11 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 > (20200309) > MachineType: Apple Inc. MacBookPro9,2 > ProcEnviron: >LANGUAGE=en_IN:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic > root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/24/2019 > dmi.bios.vendor: Apple Inc. > dmi.bios.version: 229.0.0.0.0 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-6F01561E16C75D06 > dmi.board.vendor: Apple Inc. > dmi.board.version: MacBookPro9,2 > dmi.chassis.type: 10 > dmi.chassis.vendor: Apple Inc. > dmi.chassis.version: Mac-6F01561E16C75D06 > dmi.modalias: > dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: > dmi.product.family: MacBook Pro > dmi.product.name: MacBookPro9,2 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.100-4 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20190815-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions > ** Attachment added: "history.log" https://bugs.launchpad.net/bugs/1867092/+attachment/5499309/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867092 Title: Failed to set MokListRT: Invalid Parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter
I generally accept official updates (but not upgrades) to my Ubuntu version 18.04 Bionic. I don't have a record of these updates but after one recent update (about a week or two ago) I'm getting this warning "Failed to set MokListRT Invalid parameter secure mode disabled" etc. On Fri, May 21, 2021 at 2:15 PM Steve Langasek <1867...@bugs.launchpad.net> wrote: > > I am getting the same error after an update to Ubuntu 18.04 > > After updating from what to what? There have not been any updates to > the shim-signed package in 18.04 since September of last year. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1867092 > > Title: > Failed to set MokListRT: Invalid Parameter > > Status in grub2 package in Ubuntu: > Invalid > Status in mokutil package in Ubuntu: > Invalid > Status in shim package in Ubuntu: > Triaged > Status in shim-signed package in Ubuntu: > Triaged > > Bug description: > Hello, > I am testing Ubuntu 20.04 Daily built the latest version on my MacBook > pro-13inch late 2012 model Non-retina display. and I am getting the error > while I boot my MacBook using a Pendrive in which I have installed the > Ubuntu Daily 20.04 OS. > Error is as follows : > > Failed. to set MokListRT: Invalid Parameter > Could not create MokListRT: Invalid Parameter > Importing MOK states has failed: import_mok_state() failed : invalid > Parameter > Continuing boot since secure mode is disabled. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.4.0-14-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.11-0ubuntu20 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Thu Mar 12 10:40:44 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: > installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller > [106b:00fa] > InstallationDate: Installed on 2020-03-11 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 > (20200309) > MachineType: Apple Inc. MacBookPro9,2 > ProcEnviron: >LANGUAGE=en_IN:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic > root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/24/2019 > dmi.bios.vendor: Apple Inc. > dmi.bios.version: 229.0.0.0.0 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-6F01561E16C75D06 > dmi.board.vendor: Apple Inc. > dmi.board.version: MacBookPro9,2 > dmi.chassis.type: 10 > dmi.chassis.vendor: Apple Inc. > dmi.chassis.version: Mac-6F01561E16C75D06 > dmi.modalias: > dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: > dmi.product.family: MacBook Pro > dmi.product.name: MacBookPro9,2 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.100-4 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20190815-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867092 Title: Failed to set MokListRT: Invalid Parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter
I am getting the same error after an update to Ubuntu 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867092 Title: Failed to set MokListRT: Invalid Parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915509] Re: QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio driver
Hello, After much digging and searching the internet, I have found what needs to be used to get IOMMU enabled and, hence start a SEV vm using VIRTIO : -device virtio-blk-pci,drive=drive0,id=virblk0,num-queues=4,disable-modern=off,disable-legacy=on,iommu_platform=on \ -drive file=/var/lib/libvirt/images/real-qemu.qcow2,if=none,id=drive0 \ The addition of disable-modern=off,disable-legacy=on does the trick ! Thanks for your suggestions. ...Louis ** Changed in: qemu (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915509 Title: QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1915509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915509] [NEW] QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio driver
Public bug reported: When using the VIRTIO driver, starting a VM with SEV enabled on sev enabled hardware fails. The situation may be tested with the following commands : $ dd if=/dev/urandom of=/tmp/sev_key.aes bs=8 count=4 $ cp /usr/share/OVMF/OVMF_CODE.fd /tmp $ cp /usr/share/OVMF/OVMF_VARS.fd /tmp $ qemu-system-x86_64 -name real-qemu \ -machine pc-q35-3.0,accel=kvm,usb=off,vmport=off,dump-guest-core=off,memory-encryption=sev0 \ -display none \ -monitor none \ -nographic \ -nodefaults \ -m 16384.0M \ -serial mon:stdio \ -smp 2 \ -cpu host \ -device sga \ -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -netdev user,id=net0,net=192.168.100.0/24,dhcpstart=192.168.100.1 \ -device virtio-net-pci,netdev=net0,id=net0,mac=52:54:00:cc:56:90,bus=pci.1,addr=0x0,romfile=,iommu_platform=on \ -drive if=pflash,format=raw,readonly,file=/tmp/OVMF_CODE.fd \ -drive if=pflash,format=raw,file=/tmp/OVMF_VARS.fd \ -drive file=/var/lib/libvirt/images/real-qemu.qcow2,if=virtio,id=disk0 \ -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1,policy=0x3 \ -object secret,id=masterKey0,format=raw,file=/tmp/sev_key.aes The output when starting the VM shows : qemu-system-x86_64: Guest says index 53230 is available When running the same script using the 'ide' driver instead of the 'virtio' driver, the VM starts correctly : root@ubuntu:~# dmesg | grep -i sev [0.243361] AMD Secure Encrypted Virtualization (SEV) active There is a mention in the libvirt knowledge base documentation about the requirement to use IOMMU to make the virtio work (https://libvirt.org/kbase/launch_security_sev.html#virtio) so another test was to enable IOMMU : $ qemu-system-x86_64 -name real-qemu \ -machine pc-q35-3.0,accel=kvm,usb=off,vmport=off,dump-guest-core=off,memory-encryption=sev0 \ -display none \ -monitor none \ -nographic \ -nodefaults \ -m 16384.0M \ -serial mon:stdio \ -smp 2 \ -cpu host \ -device sga \ -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -netdev user,id=net0,net=192.168.100.0/24,dhcpstart=192.168.100.1 \ -device virtio-net-pci,netdev=net0,id=net0,mac=52:54:00:cc:56:90,bus=pci.1,addr=0x0,romfile=,iommu_platform=on \ -drive if=pflash,format=raw,readonly,file=/tmp/OVMF_CODE.fd \ -drive if=pflash,format=raw,file=/tmp/OVMF_VARS.fd \ -device virtio-blk-pci,drive=drive0,id=virblk0,num-queues=4,iommu_platform=on \ -drive file=/var/lib/libvirt/images/real-qemu.qcow2,if=none,id=drive0 \ -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1,policy=0x3 \ -object secret,id=masterKey0,format=raw,file=/tmp/sev_key.aes This also fails and issues the following error message : qemu-system-x86_64: -device virtio-blk-pci,drive=drive0,id=virblk0,num-queues=4,iommu_platform=on: VIRTIO_F_IOMMU_PLATFORM was supported by neither legacy nor transitional device Is it possible to use SEV in conjunction with the VIRTIO driver ? ** Affects: qemu (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/1915509 Title: QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1915509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912183] [NEW] package oscar 1.0.1-r1 failed to install/upgrade: there is no script in the new version of the package - giving up
Public bug reported: The bug popped up after upgrade from 18.04 to 20.04. Unfortunately now it also impossible to receive and install security updates for Ubuntu. Nor can I install Kernel updates. What a disaster. probably I will need to reinstall Ubuntu from scratch...pfff ProblemType: Package DistroRelease: Ubuntu 20.04 Package: oscar 1.0.1-r1 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 18 10:36:45 2021 ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2018-11-10 (799 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: oscar Title: package oscar 1.0.1-r1 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to focal on 2021-01-09 (8 days ago) ** Affects: oscar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912183 Title: package oscar 1.0.1-r1 failed to install/upgrade: there is no script in the new version of the package - giving up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oscar/+bug/1912183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm
Hello, Sorry to switch this bug back to Confirmed, but the fix that you mention is clearly not present in the latest kernel available in Focal : root@launchpad-kernel:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal root@launchpad-kernel:~# uname -a Linux launchpad-kernel 5.4.0-1030-kvm #31-Ubuntu SMP Wed Dec 9 17:27:05 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@launchpad-kernel:~# grep IP_VS /boot/config-5.4.0-1030-kvm # CONFIG_IP_VS is not set root@launchpad-kernel:~# modprobe ip_vs modprobe: FATAL: Module ip_vs not found in directory /lib/modules/5.4.0-1030-kvm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880522 Title: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm
Hello again, Sorry for the noise, I blindly reported what one of our user told me without checking. Its problem is IP_VS which has nothing to do with this bug. Thanks for your help in fixing this and, once again sorry. ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880522 Title: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905112] [NEW] installer crashes remade media and crashed again
Public bug reported: made multiple drives on windows and macos and the install keeps failing ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 20:57:45 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905112 Title: installer crashes remade media and crashed again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1905112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899365] [NEW] Upgrade error message (18.04 to 20.04)
Public bug reported: I'm on Ubuntu 18.04 and I wanted to upgrade to Ubuntu 20.04. But from the upgrade calculation, an error message occurred : Upgrade error message (18.04 to 20.04): An unsolvable problem occurred during the upgrade calculation. This was probably caused by unofficial software packages that do not come from Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 11 19:29:03 2020 InstallationDate: Installed on 2018-08-05 (797 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-11 (0 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade ** Attachment added: "error message.png" https://bugs.launchpad.net/bugs/1899365/+attachment/5420984/+files/error%20message.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899365 Title: Upgrade error message (18.04 to 20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1899365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899246] [NEW] it crashes when I upgrade from 18.04 LTS to 20.04 LTS
Public bug reported: it fails when I upgrade from 18.04 LTS to 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 10:37:22 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (1369 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-10 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2020-10-08T17:59:21.049405 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899246 Title: it crashes when I upgrade from 18.04 LTS to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1899246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891680] Re: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst
Sorry, didn't meant to change the status, I cannot revert the change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891680 Title: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1891680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891680] Re: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst
** Changed in: grub2 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891680 Title: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1891680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884981] Re: The touchpad soesn't work at all
I got another set of log after booting on mainline (appended below) and touchpad not working. The log shows up that first before the "controller timed out spamming" starts: i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration i2c_designware AMDI0010:00: controller timed out i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. Now, I found these 3 exact log messages related to a touchpad issue in this kernel commit to fix another DELL Win8 touchpad in 2015: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.8-rc2=6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095 >From this commit it seems like a similar failure occurs with the MSFT touchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884981 Title: The touchpad soesn't work at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884981] Re: The touchpad soesn't work at all
I have the same touchpad issues with the same laptop IdeaPad 5 14ARE05 As requested by You-Sheng, I have added the kernel boot parameters and got some interesting logs. Although, I am running arch linux, it looks like the journalctl logs are as relevant Some boot, the touchpad is detected but not fully working (tab click fails, two fingers motion fails, etc) Otherwise, it is not detected at all. On kernel 5.7.6: (no touchpad at all) i2c_hid i2c-MSFT0004:00: HID over i2c has not been provided an Int IRQ i2c_hid: probe of i2c-MSFT0004:00 failed with error -22 On kernel 5.8.2-rc2 mainline: (touchpad acting limited) i2c_hid i2c-MSFT0004:00: supply vdd not found, using dummy regulator i2c_hid i2c-MSFT0004:00: supply vddl not found, using dummy regulator i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input13 input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input14 hid-generic 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00 i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input16 input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input17 hid-multitouch 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00 If needed I can attached the full logs, but does not look like there is anything else relevant to this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884981 Title: The touchpad soesn't work at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884838] Re: woops-logout white page after installation from scratch on old crappy hp
This is a faulty hardware induced crash, and not a bug. I can't quite figure out how to close this. Guess "Invalid" is close enough. ** Changed in: orca (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/orca/+question/691509 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884838 Title: woops-logout white page after installation from scratch on old crappy hp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orca/+bug/1884838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884838] Re: woops-logout white page after installation from scratch on old crappy hp
This crash is not a bug. I just identified a faulty memory chip in my computer. Sorry for the noise. ** Tags removed: amd64 apport-package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884838 Title: woops-logout white page after installation from scratch on old crappy hp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orca/+bug/1884838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884838] [NEW] woops-logout white page after installation from scratch on old crappy hp
Public bug reported: Happened while doing upgrade post vanilla installation from scratch (20.04 desktop). I got a white page that said something went wrong "logout". Could not get back into interactive graphics mode (had to ctrl alt f3 to issue a reboot command) package orca 3.36.2-1ubuntu1~20.04.1 failed to install/upgrade: installed orca package post-installation script subprocess returned error exit status 1 lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy orca orca: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.2-1ubuntu1~20.04.1 Version table: *** 3.36.2-1ubuntu1~20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 3.36.1-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu focal/main i386 Packages ProblemType: Package DistroRelease: Ubuntu 20.04 Package: orca 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 23 16:37:11 2020 ErrorMessage: installed orca package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: orca Title: package orca 3.36.2-1ubuntu1~20.04.1 failed to install/upgrade: installed orca package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: orca (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884838 Title: woops-logout white page after installation from scratch on old crappy hp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orca/+bug/1884838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm
Hello Stefan, Any hint on who could check on that ? What needs to be clarified is if this is a requirement and there to stay or not. Kind regards, ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880522 Title: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880522] [NEW] CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm
Public bug reported: The NF_TABLES options are not included in the -kvm flavor of the 5.4 kernel. This package is used in the Ubuntu Cloud Image. The linux-image-5.4.0-31-generic package has the options present in the config file. ** Affects: linux (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/1880522 Title: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
At least in Firefox you can use Ctrl + L to access a location -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
I'm afraid I do have to add my voice to this particular complaint as most packages I install with snap seem to have fundamental problems accessing the file system however it's configured with multiple mount points, sim links etc. I've already removed many snap apps and reinstalled with apt which is much more reliable. Not being able to find a file path in Chromium or even be able to type in the path when you want to upload a file is a bit ridiculous to be honest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864061] Re: PCI/internal sound card not detected
On 5.3.0-46-generic had this issue on Lenovo C930. Adding "options snd-hda-intel dmic_detect=0" in the /etc/modprobe.d /alsa-base.conf got me sound again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864061 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870725] Re: artifacts appearing on gnome shell
Hey! I just upgraded to 20.04 from 19.10, and had the same issue (same GPU - Intel Graphics UHD 620). I had the same problem a few months ago using the OIBAF ppa, and I thought it was because of the Open Source driver (built twice a day from their git repo) and since removing the PPA fixed the issue. I stepped upon this bug report when searching for a reason to my screen artifacts (same problems, same symptoms and same image as the original post). I've read the last comment "Please don't use the 'intel' driver. It is old and unsupported." and remembered that I had screen tearing issues a few months ago and that I added a custom XORG config (following https://askubuntu.com/questions/1066722/intel-screen-tearing-ubuntu-18-04). I just emptied '/etc/X11/xorg.conf.d/20-intel.conf', and rebooted, and it just worked fine from this! Please check if it could fix it for you too! Sincerely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870725 Title: artifacts appearing on gnome shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1870725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Hello, Just tested the latest image in ./current and it boots fine : root@focal-ok:~# uname -a Linux focal-ok 5.4.0-1009-kvm #9-Ubuntu SMP Mon Apr 20 20:23:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@focal-ok:~# cat /etc/cloud/build.info build_name: server serial: 20200421 root@focal-ok:~# uname -r 5.4.0-1009-kvm root@focal-ok:~# grep -i ^CONFIG_EFI /boot/config-5.4.0-1009-kvm CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_EFI_MIXED=y CONFIG_EFI_VARS=y CONFIG_EFI_ESRT=y CONFIG_EFI_RUNTIME_WRAPPERS=y CONFIG_EFI_EARLYCON=y CONFIG_EFI_PARTITION=y CONFIG_EFIVAR_FS=m Thanks for the quick turnaround ! ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Hello, thanks for the quick turnaround. For the record, some EFI configs did exist in prior 5.3 images : root@focal:/boot# cat /etc/cloud/build.info build_name: server serial: 20200223 root@focal:/boot# uname -r 5.3.0-1009-kvm root@focal:/boot# grep -i ^CONFIG_EFI config-5.3.0-1009-kvm CONFIG_EFI=y CONFIG_EFI_VARS=y CONFIG_EFI_ESRT=y CONFIG_EFI_RUNTIME_WRAPPERS=y CONFIG_EFI_EARLYCON=y CONFIG_EFI_PARTITION=y CONFIG_EFIVAR_FS=m I'll be using the other image for testing in the meantime ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-bl-tutorials/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863866] [NEW] tinc missing net-tools dependency for Bionic onward
Public bug reported: net-tools is not installed by default on Bionic and after. tinc expects ifconfig to be available so it should depends on net-tools ** Affects: tinc (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/1863866 Title: tinc missing net-tools dependency for Bionic onward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tinc/+bug/1863866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607560] Re: jbd2 writing block every 5 - 10 seconds, preventing disk spin-down and making noise
I have a similar problem on a 4.15.0-20-generic kernel. Is there a new bug for this since this one has been marked invalid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/607560 Title: jbd2 writing block every 5 - 10 seconds, preventing disk spin-down and making noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855219] [NEW] grub 2 not functioning after install
Public bug reported: Installing Ubuntu 18 from USB installer, onto HP STream 13 laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 4 23:34:44 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855219 Title: grub 2 not functioning after install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1855219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635463] Re: pip freeze includes "pkg-resources==0.0.0"
Hello, for what it's worth, the problem comes from the debianized version of virtualenv which uses a debundled version of pkg_resource which gets added into the virtualenv at creation time : $ virtualenv . Running virtualenv with interpreter /usr/bin/python2 New python executable in /home/caribou/git/quividi/test/bin/python2 Also creating executable in /home/caribou/git/quividi/test/bin/python Installing setuptools, pkg_resources, pip, wheel...done. $ pip freeze pkg-resources==0.0.0 Using the pip installed version of virtualenv can be a workable workaround : $ sudo apt -y purge python3-virtualenv virtualenv tox $ pip install virtualenv $ virtualenv . pip install virtualenv Collecting virtualenv Downloading https://files.pythonhosted.org/packages/c5/97/00dd42a0fc41e9016b23f07ec7f657f636cb672fad9cf72b80f8f65c6a46/virtualenv-16.7.7-py2.py3-none-any.whl (3.4MB) 100% || 3.4MB 351kB/s Installing collected packages: virtualenv Successfully installed virtualenv-16.7.7 $ virtualenv . New python executable in /home/caribou/git/quividi/test/bin/python Installing setuptools, pip, wheel... done. $ source bin/activate $ pip freeze $ hth, ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635463 Title: pip freeze includes "pkg-resources==0.0.0" To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1635463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
Hello, Nice to see so many known and friendly faces around this bug. Let me outline a *real life* issue that we're facing following this issue. We've put block storage in private beta a while ago (https://www.scaleway.com/fr/betas/#block-storage) based on RBD storage. The same platform experienced another QEMU issue (LPl #1837869) kindly fixed and SRU by @paelzer) that we deployed on the same platform this week. So all the instances currently running that have NOT used RBD based storage during the BETA but will still be running when we go live and want to use RBD storage when it goes GA will experience this bug unless they reboot their instance. We're looking into a workaround solution to alleviate this situation but I thought I'd share the context to give a some kind of "real life" experience :-) Kind regards, Louis (aka caribou) ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852766] [NEW] Attaching RBD device after qemu upgrade fails with "Unknown protocol 'rbd'"
Public bug reported: After upgrading the following QEMU packages to latest Bionic version (1:2.11+dfsg-1ubuntu7.20) : - qemu-system-x86 - qemu-system-common - qemu-utils - qemu-block-extra:amd64 Attaching an RBD device to a VM that was running prior to the upgrade fails with "Unknown protocol 'rbd' This only happens if this is the first RBD device to be attached after the upgrade. Attaching a device, then upgrading to 1:2.11+dfsg- 1ubuntu7.20 will not generate the error message and the device will attach correctly. Attaching a device to a new VM created _AFTER_ the upgrade does not trigger the problem either. Downgrading qemu-block-extra:amd64 after the upgrade and prior to first attaching an RBD device will also not trigger the error. Here are two examples : Using : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7 ii qemu-system-common1:2.11+dfsg-1ubuntu7 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7 ii qemu-utils1:2.11+dfsg-1ubuntu7 ./qmp-shell -H /opt/vms/1/qmp.sock (QEMU) drive_add auto format=raw,cache=writeback,file=rbd:rbd/disk-086264fd-9ca4-42a9-9deb-4a8be80f2bab:rbd_cache=true:id=compute-hv:conf=/etc/ceph/ceph.conf:keyring=/etc/ceph/ceph.client.compute-hv.keyring,id=volume-8b84f816-6e11-4a17-a2ce-0cdb6f486bfe,throttling.iops-total=1,if=none OK With : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7 ii qemu-system-common1:2.11+dfsg-1ubuntu7 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7 ii qemu-utils1:2.11+dfsg-1ubuntu7 and an existing QEMU process running $ apt udpate && apt -y install qemu-utils qemu-system-x86 qemu-system-common qemu-block-extra:amd64 Using : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7.20 ii qemu-system-common1:2.11+dfsg-1ubuntu7.20 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7.20 ii qemu-utils1:2.11+dfsg-1ubuntu7.20 ./qmp-shell -H /opt/vms/1/qmp.sock (QEMU) drive_add auto format=raw,cache=writeback,file=rbd:rbd/disk-086264fd-9ca4-42a9-9deb-4a8be80f2bab:rbd_cache=true:id=compute-hv:conf=/etc/ceph/ceph.conf:keyring=/etc/ceph/ceph.client.compute-hv.keyring,id=volume-8b84f816-6e11-4a17-a2ce-0cdb6f486bfe,throttling.iops-total=1,if=none Unknown protocol 'rbd' (QEMU) Restarting the QEMU process fixes the issue. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Affects: qemu (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Also affects: qemu (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Bionic) Status: New => Confirmed ** Changed in: qemu (Ubuntu Bionic) Importance: Undecided => Medium ** Description changed: After upgrading the following QEMU packages to latest Bionic version (1:2.11+dfsg-1ubuntu7.20) : - qemu-system-x86 - qemu-system-common - qemu-utils - qemu-block-extra:amd64 Attaching an RBD device to a VM that was running prior to the upgrade fails with "Unknown protocol 'rbd' This only happens if this is the first RBD device to be attached after the upgrade. Attaching a device, then upgrading to 1:2.11+dfsg- 1ubuntu7.20 will not generate the error message and the device will attach correctly. Attaching a device to a new VM created _AFTER_ the upgrade does not trigger the problem either. Downgrading qemu-block-extra:amd64 after the upgrade and prior to first attaching an RBD device will also not trigger the error. Here are two examples : Using : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7 ii qemu-system-common1:2.11+dfsg-1ubuntu7 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7 ii qemu-utils1:2.11+dfsg-1ubuntu7 ./qmp-shell -H /opt/vms/1/qmp.sock (QEMU) drive_add auto format=raw,cache=writeback,file=rbd:rbd/disk-086264fd-9ca4-42a9-9deb-4a8be80f2bab:rbd_cache=true:id=compute-hv:conf=/etc/ceph/ceph.conf:keyring=/etc/ceph/ceph.client.compute-hv.keyring,id=volume-8b84f816-6e11-4a17-a2ce-0cdb6f486bfe,throttling.iops-total=1,if=none OK - With : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7 ii qemu-system-common1:2.11+dfsg-1ubuntu7 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7 ii qemu-utils1:2.11+dfsg-1ubuntu7 and an existing QEMU process running $ apt udpate && apt -y install qemu-utils qemu-system-x86 qemu-system-common qemu-block-extra:amd64 Using : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7.20 ii qemu-system-common1:2.11+dfsg-1ubuntu7.20 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7.20 ii qemu-utils1:2.11+dfsg-1ubuntu7.20 ./qmp-shell -H
[Bug 1425000] Re: Cannot set right monitor as primary in dual monitor configuration
> It's still the same. You can select primary monitor, but most applications will not respect it and will run only on the left monitor. If your primary monitor is on the right, everything works perfectly though. I have the same behavior with Ubuntu 18.04 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425000 Title: Cannot set right monitor as primary in dual monitor configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1425000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771158] Re: Synaptic doesn't open with administrative privileges on wayland
Fixed in 19.10 ** Changed in: synaptic (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771158 Title: Synaptic doesn't open with administrative privileges on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1771158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847247] [NEW] External dictionaries are not loaded
Public bug reported: On Ubuntu Eoan and most recent Thunderbird, the external Hunspell dictionaries are not available anymore on Thunderbird for spellcheck. The symlink is still in place: lrwxrwxrwx 1 root root20 dec 15 2017 dictionaries -> ../../share/hunspell But data doesn't get loaded for some reason. ** Affects: thunderbird (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/1847247 Title: External dictionaries are not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
Ok, I'll have a look at it; I only backported the Eoan fix to Bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845619] [NEW] Please backport bugfix for Debian Bug 838503 : mdadm should not start syncing RAID1 arrays at full speed during installation
Public bug reported: Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838503 fixes slow installation caused by RAID synchronization. This is fixed in DISCO and EOAN already. ** Affects: partman-md (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: partman-md (Ubuntu Bionic) Importance: Medium Assignee: Louis Bouchard (louis) Status: Confirmed ** Affects: partman-md (Ubuntu Disco) Importance: Undecided Status: Fix Released ** Affects: partman-md (Ubuntu Eoan) Importance: Undecided Status: Fix Released ** Also affects: partman-md (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: partman-md (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: partman-md (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: partman-md (Ubuntu Disco) Status: New => Fix Released ** Changed in: partman-md (Ubuntu Eoan) Status: New => Fix Released ** Changed in: partman-md (Ubuntu Bionic) Status: New => Confirmed ** Changed in: partman-md (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: partman-md (Ubuntu Bionic) Assignee: (unassigned) => Louis Bouchard (louis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845619 Title: Please backport bugfix for Debian Bug 838503 : mdadm should not start syncing RAID1 arrays at full speed during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-md/+bug/1845619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844523] Re: Dock hidden after lock/unlock
gnome-shell-extension-appindicator gnome-shell-extension-desktop-icons gnome-shell-extension-ubuntu-dock Those 3 are installed ** Description changed: On Eoan and Wayland the dock is hidden when you unlock your screen after having it locked. Clicking on 'Activities' brings it back. + + This seems to only happen on Wayland (unable to reproduce on X11) + AND + When xfreerdp is running in fullscreen mode on a second screen (xfreerdp /f /monitors:0 /v:x) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844523 Title: Dock hidden after lock/unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1844523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844523] [NEW] Dock hidden after lock/unlock
Public bug reported: On Eoan and Wayland the dock is hidden when you unlock your screen after having it locked. Clicking on 'Activities' brings it back. ** Affects: gnome-shell-extension-ubuntu-dock (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/1844523 Title: Dock hidden after lock/unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1844523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844467] [NEW] Ubuntu now does not restart after being suspended.
Public bug reported: When I installed UNBUNTU and was suspending my computer, it came back. Now he won't call again after I have suspended him. I had some problems with this installation due to intermittent hardware issues (power supply and bad contact on SATA hard drive connection). Will I have to reinstall Unbuntu 18.04 ?! Note: This text was translated from the original in Portuguese (below) in google translator. Quando instalei o UNBUNTU e suspendia meu computador, ele voltava. Agora ele não liga novamente após eu o ter suspendido. Tive alguns problemas com essa instalação por problemas intermitentes com o hardware (fonte de alimentação e mal contato na conexão SATA do HD ). Terei de reinstalar o Unbuntu 18.04 ?! Obs. Esse texto foi traduzido do original em português no google tradutor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Tue Sep 17 22:02:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335] InstallationDate: Installed on 2019-03-27 (174 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 24 21:29:22 2019 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844467 Title: Ubuntu now does not restart after being suspended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1844467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837869] Re: Cannot complete snapshot if read-only backing store is opened by another VM
As discussed offline, a new round of test confirms that the fix in your PPA fixes the File Lock issue. ** Changed in: qemu (Ubuntu Bionic) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837869 Title: Cannot complete snapshot if read-only backing store is opened by another VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1837869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] Profile1Prefs.txt
apport information ** Attachment added: "Profile1Prefs.txt" https://bugs.launchpad.net/bugs/1844281/+attachment/5289159/+files/Profile1Prefs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1844281/+attachment/5289153/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1844281/+attachment/5289151/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1844281/+attachment/5289160/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] Re: Opening an URL in other software tries to start new firefox instance instead of new tab
apport information ** Tags added: apport-collected eoan wayland-session ** Description changed: Since upgraded to Eoan I have issues opening an URL from within other applications. It starts: /usr/lib/firefox/firefox https://paste.ubuntu.com/p/ But while in Disco it just opened a new tab in firefox when it was already running, I now get an error message that firefox is still running and I need to close it. This while it should just open an additional tab with the URL I clicked. + --- + ProblemType: Bug + AddonCompatCheckDisabled: False + ApportVersion: 2.20.11-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: jean-louis 2554 F pulseaudio + BuildID: 2019091951 + Channel: Unavailable + CurrentDesktop: ubuntu:GNOME + DefaultProfileExtensions: extensions.sqlite corrupt or missing + DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) + DefaultProfileLocales: extensions.sqlite corrupt or missing + DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:997 + DefaultProfilePrefSources: prefs.js + DefaultProfileThemes: extensions.sqlite corrupt or missing + DistroRelease: Ubuntu 19.10 + ForcedLayersAccel: False + IfupdownConfig: + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback + InstallationDate: Installed on 2017-12-15 (640 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + IpRoute: + default via 10.10.1.1 dev enxa44cc890f4c8 proto dhcp metric 100 + default via 10.10.1.1 dev wlan0 proto dhcp metric 600 + 10.10.1.0/24 dev enxa44cc890f4c8 proto kernel scope link src 10.10.1.182 metric 100 + 10.10.1.0/24 dev wlan0 proto kernel scope link src 10.10.1.221 metric 600 + 169.254.0.0/16 dev enxa44cc890f4c8 scope link metric 1000 + Package: firefox 69.0+build2-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 + Profile1Extensions: extensions.sqlite corrupt or missing + Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) + Profile1Locales: extensions.sqlite corrupt or missing + Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:997 + Profile1PrefSources: prefs.js + Profile1Themes: extensions.sqlite corrupt or missing + Profiles: + Profile1 - LastVersion=65.0/20190128173924 (Out of date) + Profile0 (Default) - LastVersion=69.0/2019091951 (In use) + RunningIncompatibleAddons: False + Tags: eoan wayland-session + Uname: Linux 5.3.0-10-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-09-16 (0 days ago) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 07/26/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.16.0 + dmi.board.name: 0NKT5P + dmi.board.vendor: Dell Inc. + dmi.board.version: X00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd07/26/2019:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0NKT5P:rvrX00:cvnDellInc.:ct10:cvr: + dmi.product.family: Precision + dmi.product.name: Precision 5520 + dmi.product.sku: 07BF + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1844281/+attachment/5289150/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1844281/+attachment/5289157/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1844281/+attachment/5289156/+files/PciNetwork.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1844281/+attachment/5289154/+files/IpAddr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1844281/+attachment/5289158/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1844281/+attachment/5289155/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] DefaultProfilePrefs.txt
apport information ** Attachment added: "DefaultProfilePrefs.txt" https://bugs.launchpad.net/bugs/1844281/+attachment/5289152/+files/DefaultProfilePrefs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844281] [NEW] Opening an URL in other software tries to start new firefox instance instead of new tab
Public bug reported: Since upgraded to Eoan I have issues opening an URL from within other applications. It starts: /usr/lib/firefox/firefox https://paste.ubuntu.com/p/ But while in Disco it just opened a new tab in firefox when it was already running, I now get an error message that firefox is still running and I need to close it. This while it should just open an additional tab with the URL I clicked. ** Affects: firefox (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/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771158] Re: Synaptic doesn't open with administrative privileges on wayland
This is fixed in Gnome 3.34!
But, there was a message added in Synaptic, which is contra-productive now.
if [ "x${USING_WAYLAND}" = "x1" ]; then
# Running wayland; start synaptic without pkexec
zenity --warning --width=500 --text \
"You are using Wayland environment, Synaptic will continue without
administrative privileges.\\n\
To make Synaptic fully functional, please restart your session without Wayland."
exec "/usr/sbin/synaptic" "$@"
else
pkexec "/usr/sbin/synaptic" "$@"
fi
This can be removed! pkexec just works fine now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771158
Title:
Synaptic doesn't open with administrative privileges on wayland
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1771158/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392204] Re: Huge CPU usage by mount.ntfs process
In my case, many fopen() operations seems to be what is slow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/392204 Title: Huge CPU usage by mount.ntfs process To manage notifications about this bug go to: https://bugs.launchpad.net/ntfs-3g/+bug/392204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
