[Bug 1897860] Re: flash-kernel does not generate initramfs on SolidRun MACCHIATObin
I have repeated the installation procedure and captured logging. flash- kernel exits with exit code 3: 2020-09-30 07:28:57,452 DEBUG subiquitycore.utils:83 arun_command ['systemd-cat', '--level-prefix=false', '--identifier=curtin_log.2566', '/snap/subiquity/1972/usr/bin/python3', '-m', 'curtin', '--showtrace', '-c', '/var/log/installer/subiquity-curtin-install.conf', 'install'] exited with code 3 2020-09-30 07:28:57,453 ERROR root:39 finish: subiquity/InstallProgress/install/curtin_install: FAIL: Command '['systemd-cat', '--level-prefix=false', '--identifier=curtin_log.2566', '/snap/subiquity/1972/usr/bin/python3', '-m', 'curtin', '--showtrace', '-c', '/var/log/installer/subiquity-curtin-install.conf', 'install']' returned non-zero exit status 3. subprocess.CalledProcessError: Command '['systemd-cat', '--level-prefix=false', '--identifier=curtin_log.2566', '/snap/subiquity/1972/usr/bin/python3', '-m', 'curtin', '--showtrace', '-c', '/var/log/installer/subiquity-curtin-install.conf', 'install']' returned non-zero exit status 3. 2020-09-30 07:28:57,452 DEBUG subiquitycore.utils:83 arun_command ['systemd-cat', '--level-prefix=false', '--identifier=curtin_log.2566', '/snap/subiquity/1972/usr/bin/python3', '-m', 'curtin', '--showtrace', '-c', '/var/log/installer/subiquity-curtin-install.conf', 'install'] exited with code 3 2020-09-30 07:28:57,453 ERROR root:39 finish: subiquity/InstallProgress/install/curtin_install: FAIL: Command '['systemd-cat', '--level-prefix=false', '--identifier=curtin_log.2566', '/snap/subiquity/1972/usr/bin/python3', '-m', 'curtin', '--showtrace', '-c', '/var/log/installer/subiquity-curtin-install.conf', 'install']' returned non-zero exit status 3. subprocess.CalledProcessError: Command '['systemd-cat', '--level-prefix=false', '--identifier=curtin_log.2566', '/snap/subiquity/1972/usr/bin/python3', '-m', 'curtin', '--showtrace', '-c', '/var/log/installer/subiquity-curtin-install.conf', 'install']' returned non-zero exit status 3. and that gives the following logging in curtin: 2020-09-30 07:19:55,807 DEBUG root:39 start: subiquity/InstallProgress/install/curtin_install/cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-kernel: installing kernel 2020-09-30 07:28:56,459 DEBUG root:39 finish: subiquity/InstallProgress/install/curtin_install/cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-kernel: SUCCESS: Status.FAIL 2020-09-30 07:28:56,480 DEBUG root:39 finish: subiquity/InstallProgress/install/curtin_install/cmd-install/stage-curthooks/builtin: SUCCESS: Status.FAIL 2020-09-30 07:28:56,483 DEBUG root:39 finish: subiquity/InstallProgress/install/curtin_install/cmd-install/stage-curthooks: SUCCESS: Status.FAIL 2020-09-30 07:28:57,452 DEBUG subiquitycore.utils:83 arun_command ['systemd-cat', '--level-prefix=false', '--identifier=curtin_log.2566', '/snap/subiquity/1972/usr/bin/python3', '-m', 'curtin', '--showtrace', '-c', '/var/log/installer/subiquity-curtin-install.conf', 'install'] exited with code 3 2020-09-30 07:28:57,453 DEBUG subiquity.lockfile:44 unlocking exclusive /run/subiquity/installing 2020-09-30 07:28:57,453 ERROR root:39 finish: subiquity/InstallProgress/install/curtin_install: FAIL: Command '['systemd-cat', '--level-prefix=false', '--identifier=curtin_log.2566', '/snap/subiquity/1972/usr/bin/python3', '-m', 'curtin', '--showtrace', '-c', '/var/log/installer/subiquity-curtin-install.conf', 'install']' returned non-zero exit status 3. 2020-09-30 07:28:57,455 ERROR subiquitycore.controller.installprogress:145 curtin_error Traceback (most recent call last): File "/snap/subiquity/1972/lib/python3.6/site-packages/subiquity/controllers/installprogress.py", line 304, in install await self.curtin_install(context=context) File "/snap/subiquity/1972/lib/python3.6/site-packages/subiquitycore/context.py", line 142, in decorated_async return await meth(self, **kw) File "/snap/subiquity/1972/lib/python3.6/site-packages/subiquity/controllers/installprogress.py", line 281, in curtin_install self.logged_command(curtin_cmd), check=True) File "/snap/subiquity/1972/lib/python3.6/site-packages/subiquitycore/utils.py", line 85, in arun_command raise subprocess.CalledProcessError(proc.returncode, cmd) subprocess.CalledProcessError: Command '['systemd-cat', '--level-prefix=false', '--identifier=curtin_log.2566', '/snap/subiquity/1972/usr/bin/python3', '-m', 'curtin', '--showtrace', '-c', '/var/log/installer/subiquity-curtin-install.conf', 'install']' returned non-zero exit status 3. 2020-09-30 07:28:57,458 DEBUG subiquity.core:470 generating crash report 2020-09-30 07:28:57,462 INFO subiquity.core:487 saving crash report 'install failed crashed with CalledProcessError' to /var/crash/1601450937.461412191.install_fail.crash 2020-09-30 07:28:57,465 DEBUG subiquity.core:511 show_error_report '1601450937.461412191.install_fail' This time, the initrd image _is_ created:
[Bug 1897860] [NEW] flash-kernel does not generate initramfs on SolidRun MACCHIATObin
Public bug reported: Ubuntu Focal installer hits the following in the installation process when flash-kernel gets triggerd: Using DTB: marvell/armada-8040-mcbin.dtb Couldn't find DTB armada-8040-mcbin.dtb on the following paths: /etc/flash-kernel/dtbs /usr/lib/linux-image- /lib/firmware//device-tree/ Installing into /boot/dtbs//marvell/armada-8040-mcbin.dtb cp: cannot stat '': No such file or directory the DTB _is_ actually installed in "/boot/dtbs//marvell/armada-8040-mcbin.dtb". However, the initramfs is never created, maybe because of exit 1 code in the aforementioned output. Invoking "/usr/sbin/update-initramfs.curtin-disabled -u -k all" by hand does create a initramfs for all available kernels, and the system is able to boot fine afterwards. I *think* this also prevents the Focal installer (curtin) to complete succesfully, but it reboots almost immediately after hitting an error, so I don't know for sure. ** Affects: flash-kernel (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/1897860 Title: flash-kernel does not generate initramfs on SolidRun MACCHIATObin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1897860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] Re: kernel warning in epyc2 nested virtualization
apport-collect info has been collected ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] Re: kernel warning in epyc2 nested virtualization
apport information ** Tags added: apport-collected ** Description changed: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 18 18:55 seq + crw-rw 1 root audio 116, 33 Jun 18 18:55 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.3 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + HibernationDevice: RESUME=none + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' +
[Bug 1884058] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385060/+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/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385056/+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/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385051/+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/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385054/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385059/+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/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385050/+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/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385053/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385058/+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/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385049/+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/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385052/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385055/+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/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385057/+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/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] Re: kernel warning in epyc2 nested virtualization
I've gdb and debug symbols installed ... so let me know if you need more info -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] [NEW] kernel warning in epyc2 nested virtualization
Public bug reported: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- ** Affects: ubuntu Importance: Undecided Status: New ** Tags: kvm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] Re: kernel warning in epyc2 nested virtualization
Description:Ubuntu 20.04 LTS Release:20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884058] Re: kernel warning in epyc2 nested virtualization
This bug gets triggered when VM (L1 with L2 guest) is live migrated from one hypervisor to another. This bug does not get triggered on a Intel CPU with the same kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1884058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853614] [NEW] System stuck in reboot loop on AMD EPYC 7542 32-Core Processor
Public bug reported: After installing latest microcode update: version 3.20191021.1ubuntu0.18.04.2, the system is stuck in a reboot loop. De- installing the amd64-microcode package fixes the issue. CPU details vendor_id : AuthenticAMD cpu family : 23 model : 49 model name : AMD EPYC 7542 32-Core Processor stepping: 0 microcode : 0x830101c <- 3.20180524.1ubuntu1 version is the newest one known to work ** Affects: amd64-microcode (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/1853614 Title: System stuck in reboot loop on AMD EPYC 7542 32-Core Processor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1853614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1794766] Re: nbd device size not updated correctly
On Tue, Oct 02, 2018 at 03:01:13PM -, Joseph Salisbury wrote: > Bionic already has commit 639812a1ed9b since it was added to mainline as > of v4.14-rc6: > > 639812a1ed9b nbd: don't set the device size until we're connected > > Can you confirm Bionic has this bug after applying all the latest > updates? If it does, we can perform a "Reverse" bisect, since you > confirm this bug is fixed in 4.19-rc5. Just tested again against kernel 4.15.0-36-generic #39-Ubuntu SMP (linux-image-generic: Installed: 4.15.0.36.38) but a "rbd resize" on the ceph cluster does *not* propagate to the rbd-nbd session. Bug is still present. Gr. Stefan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794766 Title: nbd device size not updated correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794766] Re: nbd device size not updated correctly
Unable to send logs as this host is ipv6 only, and bugs.launchpad.net does not have a quad A record published (ERROR: connecting to Launchpad failed: [Errno 101] Network is unreachable). Logs are not relevant IMHO as the fix is clear and only needs to get applied to the kernels affacted (at least Ubuntu Bionic with 4.15 kernel). ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794766 Title: nbd device size not updated correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794766] Re: Apply upstream bugfix for "nbd device size" not updated correctly
** Summary changed: - Apply upstream kernel fix to relevant Ubuntu kernels + Apply upstream bugfix for "nbd device size" not updated correctly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794766 Title: Apply upstream bugfix for "nbd device size" not updated correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794766] [NEW] Apply upstream kernel fix to relevant Ubuntu kernels
Public bug reported: nbd does not handle a disk resize correctly. This has been fixed upstream: https://github.com/torvalds/linux/commit/639812a1ed9bf49ae2c026086fbf975339cd1eef On Ubuntu Bionic with a "4.15.0-34-generic #37-Ubuntu" kernel a resize of a (Ceph) rbd image does not propagate to a "rbd-nbd" mapped disk, until it's unmapped / remapped. See https://tracker.ceph.com/issues/23137. Other "nbd" mapped disks might suffer from the same behaviour (not tested). Ubuntu mainline kernel (4.19-rc5) works correct with regards to this rbd resize rbd-nbd mapped image. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: nbd rbd-nbd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794766 Title: Apply upstream kernel fix to relevant Ubuntu kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723127] Re: Intel i40e PF reset due to incorrect MDD detection (continues...)
Hi there. I can confirm this problem still exists in newest kernels and with the latest intel drivers as of today: Jan 19 16:05:19 osd9 kernel: [511271.581413] i40e :02:00.1: TX driver issue detected, PF reset issued Jan 19 16:09:08 osd9 kernel: [511500.919380] i40e :02:00.0: TX driver issue detected, PF reset issued driver: i40e-2.4.3 (and xenial / 4.13 shipped driver: 2.1.14-k) kernel: 4.13.0-25-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 12:16:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Kernel loaded with nopti noibrs noibpb (Meltdown / Spetre mitigation disabled). We can trigger the issue with high load (benchmarking Ceph cluster with fio: 4 clients, 8 threads, iodepth 256, 100% random write, 64K block size). Only when we use relatively large block size (64K) do we hit this problem. With 4K blocks we do not hit this issue. We haven't tested large random reads (that test is still to be done). When using openvswitch port-channel (as we do) with jumbo frames ... this port-channel will not come back online after the reset. rmmod i40e / modprobe i40e does the trick though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723127 Title: Intel i40e PF reset due to incorrect MDD detection (continues...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713553] Re: Intel i40e PF reset due to incorrect MDD detection
H there. I can confirm this problem still exists in newest kernels and with the latest intel drivers as of today: Jan 19 16:05:19 osd9 kernel: [511271.581413] i40e :02:00.1: TX driver issue detected, PF reset issued Jan 19 16:09:08 osd9 kernel: [511500.919380] i40e :02:00.0: TX driver issue detected, PF reset issued driver: i40e-2.4.3 (and xenial / 4.13 shipped driver: 2.1.14-k) kernel: 4.13.0-25-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 12:16:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Kernel loaded with nopti noibrs noibpb (Meltdown / Spetre mitigation disabled). We can trigger the issue with high load (benchmarking Ceph cluster with fio: 4 clients, 8 threads, iodepth 256, 100% random write, 64K block size). Only when we use relatively large block size (64K) do we hit this problem. With 4K blocks we do not hit this issue. We haven't tested large random reads (that test is still to be done). When using openvswitch port-channel (as we do) with jumbo frames ... this port-channel will not come back online after the reset. rmmod i40e / modprobe i40e does the trick though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713553 Title: Intel i40e PF reset due to incorrect MDD detection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448269] Re: qemu guest hangs on nested kvm startup with host kernel oops
I had this issue (kernel oops) when I explicitly disabled ignore_msrs (Ubuntu Trusty, 3.13.0-54-generic): cat /etc/modprobe.d/qemu-system-x86.conf options kvm-intel nested=y ept=y options kvm ignore_msrs=1 Removing the option kvm ignore_msrs=1 made the guest (L2) run but give a KVM: entry failed, hardware error 0x7 when the L1 guest (guest hypervisor) was booted with these cpu flags (libvirt): cpu archx86_64/arch modelNehalem/model vendorIntel/vendor topology sockets='1' cores='2' threads='2'/ feature name='rdtscp'/ feature name='dca'/ feature name='pdcm'/ feature name='xtpr'/ feature name='tm2'/ feature name='est'/ feature name='vmx'/ feature name='ds_cpl'/ feature name='monitor'/ feature name='dtes64'/ feature name='pbe'/ feature name='tm'/ feature name='ht'/ feature name='ss'/ feature name='acpi'/ feature name='ds'/ feature name='vme'/ /cpu Guest VM (L2) running fine with these cpu flags (libvirt) for guest VM (L1): cpu match='exact' cpu mode='host-passthrough'/ modelNehalem/model feature policy='require' name='vmx'/ /cpu @Serge Hallyn: I wonder what cpu parameters you have defined for your L1 guest (guest hypervisor) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448269 Title: qemu guest hangs on nested kvm startup with host kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321449] [NEW] Output not supressed when quiet mode is set
Public bug reported: If a non nodeset action is performed with -q option, for example: xpath -e 'count(VM/TEMPLATE/NIC)' -q $xml the output is not surpressed: Query didn't return a nodeset. Value: 2 In quiet mode this should return only 2 This bug has been fixed already in upstream, see: https://rt.cpan.org/Public/Bug/Display.html?id=68932 ** Affects: libxml-xpath-perl (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/1321449 Title: Output not supressed when quiet mode is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml-xpath-perl/+bug/1321449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296271] [NEW] ceph-deploy purge node_name gives ERROR
Public bug reported: ceph-deploy purge ceph1 ceph2 ceph3 ceph4 ceph5 [ceph_deploy.cli][INFO ] Invoked (1.3.5): /usr/bin/ceph-deploy purge ceph1 ceph2 ceph3 ceph4 ceph5 [ceph_deploy.install][DEBUG ] Purging from cluster ceph hosts ceph1 ceph2 ceph3 ceph4 ceph5 [ceph_deploy.install][DEBUG ] Detecting platform for host ceph1 ... [ceph1][DEBUG ] connected to host: ceph1 [ceph1][DEBUG ] detect platform information from remote host [ceph1][DEBUG ] detect machine type [ceph_deploy.install][INFO ] Distro info: Ubuntu 14.04 trusty [ceph1][INFO ] purging host ... ceph1 [ceph1][INFO ] Running command: sudo apt-get -q remove -f -y --force-yes --purge -- ceph ceph-mds ceph-common ceph-fs-common [ceph1][WARNIN] E: Command line option 'f' [from -f] is not known. [ceph1][ERROR ] RuntimeError: command returned non-zero exit status: 100 [ceph_deploy][ERROR ] RuntimeError: Failed to execute command: apt-get -q remove -f -y --force-yes --purge -- ceph ceph-mds ceph-common ceph-fs-common ** Affects: ceph-deploy (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/1296271 Title: ceph-deploy purge node_name gives ERROR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-deploy/+bug/1296271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1084028] [NEW] openvswitch based interfaces not started in time during boot
Public bug reported: If you create network interfaces (access ports) in openvswitch, and configure them in /etc/network/interfaces, failsafe.conf will kick in and the interfaces get configured after failsafe.conf exits. This adds two minutes to boot time. openvswitch config: ovs-vsctl show 93e6b401-214b-4089-ac51-27ca43009cce Bridge br0 Port br0 Interface br0 type: internal Port vlan128 tag: 128 Interface vlan128 type: internal Port bond0 trunks: [128] Interface eth0 Interface eth5 Bridge br1 Port bond1 trunks: [143, 145] Interface eth1 Interface eth4 Port phy-br1 Interface phy-br1 Port br1 Interface br1 type: internal Port int-br1 Interface int-br1 ovs_version: 1.4.3 cat /etc/network/interfaces: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto eth1 iface eth1 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto eth4 iface eth4 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto eth5 iface eth5 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto vlan128 iface vlan128 inet static address 172.17.128.102 netmask 255.255.255.0 I expected openvswitch (interfaces/ports/bonds/trunks) to be up-and- running before /etc/network/interfaces gets evaluated. Clint Byrum (Ubuntu) reported me the following: failsafe.conf will exit when all interfaces marked as 'auto' are up. The only time you get a 2 minute delay is when it takes that long to bring those interfaces up. Since you have these vlanXXX interfaces listed, the system is waiting for them to come up. It seems to me that openvswitch needs to be brought up before runlevel 2, and so probably needs an upstart job. This sounds like a clear bug. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1084028] [NEW] openvswitch based interfaces not started in time during boot
Public bug reported: If you create network interfaces (access ports) in openvswitch, and configure them in /etc/network/interfaces, failsafe.conf will kick in and the interfaces get configured after failsafe.conf exits. This adds two minutes to boot time. openvswitch config: ovs-vsctl show 93e6b401-214b-4089-ac51-27ca43009cce Bridge br0 Port br0 Interface br0 type: internal Port vlan128 tag: 128 Interface vlan128 type: internal Port bond0 trunks: [128] Interface eth0 Interface eth5 Bridge br1 Port bond1 trunks: [143, 145] Interface eth1 Interface eth4 Port phy-br1 Interface phy-br1 Port br1 Interface br1 type: internal Port int-br1 Interface int-br1 ovs_version: 1.4.3 cat /etc/network/interfaces: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto eth1 iface eth1 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto eth4 iface eth4 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto eth5 iface eth5 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto vlan128 iface vlan128 inet static address 172.17.128.102 netmask 255.255.255.0 I expected openvswitch (interfaces/ports/bonds/trunks) to be up-and- running before /etc/network/interfaces gets evaluated. Clint Byrum (Ubuntu) reported me the following: failsafe.conf will exit when all interfaces marked as 'auto' are up. The only time you get a 2 minute delay is when it takes that long to bring those interfaces up. Since you have these vlanXXX interfaces listed, the system is waiting for them to come up. It seems to me that openvswitch needs to be brought up before runlevel 2, and so probably needs an upstart job. This sounds like a clear bug. ** Affects: openvswitch (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/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
