[Bug 1956366] Re: uvt-kvm fails to create armhf VM
** Also affects: uvtool Importance: Undecided Status: New ** Changed in: uvtool Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956366 Title: uvt-kvm fails to create armhf VM To manage notifications about this bug go to: https://bugs.launchpad.net/uvtool/+bug/1956366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951280] [NEW] [Intel UHD Graphics 620] [drm] *ERROR* Fault errors on pipe B: 0x00000080
Public bug reported: Series: Impish Kernel: Linux bsg75 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 08:59:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ii linux-image-5.13.0-21-generic 5.13.0-21.21 amd64Signed kernel image generic Flavour: Generic Component: Video While running Ubuntu 21.10 on an ASUS ZenBook UX331FA_UX331FA The graphics display output will randomly become corrupt. There is no way to recover from this, unless you perform a ctrl-alt-f2 and login carefully and issue a reboot. OR you can ssh from another system. The following messages occur in the syslog. Nov 17 10:44:18 bsg75 kernel: [ 7880.792084] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe B: 0x0080 Nov 17 10:44:18 bsg75 kernel: [ 7880.792091] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe B: 0x0080 Nov 17 10:44:18 bsg75 kernel: [ 7880.792096] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe B: 0x0080 Nov 17 10:44:18 bsg75 kernel: [ 7880.792100] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe B: 0x0080 Nov 17 10:44:18 bsg75 kernel: [ 7880.792109] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe B: 0x0080 Nov 17 10:44:18 bsg75 kernel: [ 7880.792114] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe B: 0x0080 LSPCI: 00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (prog-if 00 [VGA controller]) DeviceName: VGA Subsystem: ASUSTeK Computer Inc. WhiskeyLake-U GT2 [UHD Graphics 620] Flags: bus master, fast devsel, latency 0, IRQ 139 Memory at b000 (64-bit, non-prefetchable) [size=16M] Memory at a000 (64-bit, prefetchable) [size=256M] I/O ports at 3000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 sfeole@bsg75:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 21.2.2-1ubuntu1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 21.2.2-1ubuntu1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 21.2.2-1ubuntu1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 21.2.2-1ubuntu1 amd64transitional dummy package ii libglapi-mesa:amd6421.2.2-1ubuntu1 amd64free implementation of the GL API -- shared library ii libglu1-mesa:amd64 9.0.1-1build1 amd64Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 21.2.2-1ubuntu1 amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-va-drivers:amd64 21.2.2-1ubuntu1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 21.2.2-1ubuntu1 amd64Mesa VDPAU video acceleration drivers sfeole@bsg75:~$ dpkg -l | grep xserver ii x11-xserver-utils 7.7+8build1 amd64X server utilities ii xserver-common 2:1.20.13-1ubuntu1 all common files used by various X servers ii xserver-xephyr 2:1.20.13-1ubuntu1 amd64nested X server ii xserver-xorg 1:7.7+22ubuntu2 amd64X.Org X server ii xserver-xorg-core 2:1.20.13-1ubuntu1 amd64Xorg X server - core server ii xserver-xorg-input-all 1:7.7+22ubuntu2 amd64X.Org X server -- input driver metapackage ii xserver-xorg-input-libinput1.1.0-1 amd64X.Org X server -- libinput input driver ii xserver-xorg-input-wacom 1:0.39.0-0ubuntu2 amd64X.Org X server -- Wacom input driver ii xserver-xorg-legacy2:1.20.13-1ubuntu1 amd64setuid root Xorg server wrapper ii xserver-xorg-video-all 1:7.7+22ubuntu2 amd64X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu 21.0.0-1 amd64X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati 1:19.1.0-2build1 amd64X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev 1:
[Bug 1951280] Re: [Intel UHD Graphics 620] [drm] *ERROR* Fault errors on pipe B: 0x00000080
Note: I have not had time to sort through this document and gather some additional logs: https://www.intel.com/content/www/us/en/develop/documentation/vtune- help/top/installation/set-up-system-for-gpu-analysis/rebuild-and- install-i915-module-ubuntu.html If required, I can do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951280 Title: [Intel UHD Graphics 620] [drm] *ERROR* Fault errors on pipe B: 0x0080 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1951280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946486] Re: Unable to reboot ARM64 node with 5.11.0-27-realtime
** Attachment added: "console.txt" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+attachment/5532221/+files/console.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946486 Title: Unable to reboot ARM64 node with 5.11.0-27-realtime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946486] Re: Unable to reboot ARM64 node with 5.11.0-27-realtime
After a bit of wrestling with the arm64 ampere system, I was able to reproduce the outlined issues in this bug. Console log is attached, the system will initially boot into the 5.11.0-27-realtime kernel, however, when a "reboot" command is issued, the host appears sit idle, and will not warm reset. On the console of helo-kernel, the system hang with step 3 with: [ OK ] Finished Reboot. [ OK ] Reached target Reboot. (no further update from this point) There are no other console logs that occur on the host -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946486 Title: Unable to reboot ARM64 node with 5.11.0-27-realtime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940482] Re: [thunderx2] Synchronous external abort: 96000610 [#1] SMP
After some further poking, The latest Internal Error (via kernel 5.4.0-83-generic #93-Ubuntu) has rendered the system responsive via network communication , (ICMP) requests. However, ssh itself appears to sit idle indefinitely when trying to login to the machine remotely. OpenSSH_7.6p1 Ubuntu-4ubuntu0.5, OpenSSL 1.0.2n 7 Dec 2017 debug1: Reading configuration data /home/maas/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: /etc/ssh/ssh_config line 59: Applying options for * debug1: auto-mux: Trying existing master debug2: fd 3 setting O_NONBLOCK debug2: mux_client_hello_exchange: master version 4 debug3: mux_client_forwards: request forwardings: 0 local, 0 remote debug3: mux_client_request_session: entering debug3: mux_client_request_alive: entering debug3: mux_client_request_alive: done pid = 174117 debug3: mux_client_request_session: session request sent Something else is at play, however, we can not see what it is due to this being a cloud image. Login on the CLI is not allowed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940482 Title: [thunderx2] Synchronous external abort: 96000610 [#1] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940482] Re: [thunderx2] Synchronous external abort: 96000610 [#1] SMP
Full Log Attached ** Attachment added: "thunderx2focalupdate.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940482/+attachment/5518866/+files/thunderx2focalupdate.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940482 Title: [thunderx2] Synchronous external abort: 96000610 [#1] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940482] Re: [thunderx2] Synchronous external abort: 96000610 [#1] SMP
After updating the MAAS images to use an update version of the -stable images, it now appears the ThunderX2 will boot with focal linux-generic: See Below, The Deployed kernel did not experience a "synchronous external abort: 96000610 [#1] SMP" when a reboot command was issued to power cycle. Deployed Kernel: 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:10:30 UTC 2021 After rebooting into the new -proposed kernel at this time, the Host came up , followed by the kernel panic. This did NOT render the system unusable. Upgraded Kernel: 5.4.0-83-generic #93-Ubuntu helo-kernel login: [ 139.500352] Internal error: synchronous external abort: 96000610 [#1] SMP [ 139.507134] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua joydev input_leds ipmi_ssif ipmi_devintf ipmi_msghandler thunderx2_pmu cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear i2c_smbus hid_generic usbhid hid uas ast drm_vram_helper ttm crct10dif_ce drm_kms_helper ghash_ce syscopyarea sha2_ce sysfillrect sha256_arm64 mpt3sas sysimgblt usb_storage qede sha1_ce fb_sys_fops raid_class qed drm scsi_transport_sas igb ahci i2c_algo_bit crc8 gpio_xlp i2c_xlp9xx aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 139.570639] CPU: 56 PID: 4157 Comm: landscape-sysin Not tainted 5.4.0-83-generic #93-Ubuntu [ 139.578976] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 0ACKL030 06/04/2020 [ 139.586965] pstate: 2049 (nzCv daif +PAN -UAO) [ 139.591767] pc : qed_memcpy_hw+0x98/0x140 [qed] [ 139.596295] lr : qed_memcpy_hw+0x12c/0x140 [qed] [ 139.600898] sp : 8000364131b0 [ 139.604199] x29: 8000364131b0 x28: [ 139.609497] x27: 009ee6803538 x26: [ 139.614795] x25: 1000 x24: 800036413298 [ 139.620093] x23: 01d04b68 x22: 0040 [ 139.625391] x21: 009ed9b70090 x20: 0040 [ 139.630688] x19: x18: [ 139.635986] x17: x16: [ 139.641283] x15: x14: [ 139.646581] x13: x12: 0020 [ 139.651878] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f [ 139.657176] x9 : x8 : 8000364132d8 [ 139.662473] x7 : 800036413298 x6 : 000f [ 139.667771] x5 : x4 : 0040 [ 139.673068] x3 : 01d04b68 x2 : 800025b8a000 [ 139.678366] x1 : 800025b8 x0 : 0010 [ 139.683665] Call trace: [ 139.686110] qed_memcpy_hw+0x98/0x140 [qed] [ 139.690289] qed_memcpy_from+0x64/0xc0 [qed] [ 139.694555] __qed_get_vport_mstats+0x90/0x148 [qed] [ 139.699515] _qed_get_vport_stats+0x198/0x298 [qed] [ 139.704388] qed_get_vport_stats+0x30/0x88 [qed] [ 139.708997] qede_fill_by_demand_stats+0x44/0x290 [qede] [ 139.714297] qede_get_stats64+0x30/0xd0 [qede] [ 139.718729] dev_get_stats+0x6c/0xd8 [ 139.722292] rtnl_fill_stats+0x50/0x148 [ 139.726115] rtnl_fill_ifinfo+0x510/0xd60 [ 139.730110] rtnl_dump_ifinfo+0x25c/0x528 [ 139.734108] netlink_dump+0xfc/0x330 [ 139.737671] __netlink_dump_start+0x144/0x1c0 [ 139.742013] rtnetlink_rcv_msg+0x240/0x338 [ 139.746096] netlink_rcv_skb+0x60/0x120 [ 139.749918] rtnetlink_rcv+0x2c/0x38 [ 139.753480] netlink_unicast+0x188/0x210 [ 139.757389] netlink_sendmsg+0x1c0/0x368 [ 139.761301] sock_sendmsg+0x58/0x68 [ 139.764776] __sys_sendto+0xe8/0x158 [ 139.768338] __arm64_sys_sendto+0x34/0x48 [ 139.772335] el0_svc_common.constprop.0+0xe4/0x1f0 [ 139.777112] el0_svc_handler+0x38/0xa8 [ 139.780848] el0_svc+0x10/0x2c8 [ 139.783980] Code: d37e7cc8 91001108 8b0800e8 b4000140 (b9400046) [ 139.790060] ---[ end trace f0a24c697c627870 ]--- [ 415.995884] Internal error: synchronous external abort: 96000610 [#2] SMP [ 416.002669] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua joydev input_leds ipmi_ssif ipmi_devintf ipmi_msghandler thunderx2_pmu cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear i2c_smbus hid_generic usbhid hid uas ast drm_vram_helper ttm crct10dif_ce drm_kms_helper ghash_ce syscopyarea sha2_ce sysfillrect sha256_arm64 mpt3sas sysimgblt usb_storage qede sha1_ce fb_sys_fops raid_class qed drm scsi_transport_sas igb ahci i2c_algo_bit crc8 gpio_xlp i2c_xlp9xx aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 416.066204] CPU: 0 PID: 14 Comm: kworker/0:1 Tainted: G D 5.4.0-83-generic #93-Ubuntu [ 416.075323] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 0ACKL030 06/04/2020 [ 416.083337] Workqueue: events igb_ptp_over
[Bug 1940482] [NEW] [thunderx2] Synchronous external abort: 96000610 [#1] SMP
Public bug reported:
[Impact]:
ThunderX2 will not deploy Focal, Arm64 Cloud Image - 20210811
focal": {"stable": {"content_id": "maas:v2:download", "kflavor": "generic",
"path": "ubuntu/arm64/ga-20.04/focal/20210811/boot-initrd", "product_name":
"maas:boot:ubuntu:arm64:ga-20.04:focal"
[ 286.968817] Internal error: synchronous external abort: 96000610 [#1] SMP
[ 286.975594] Modules linked in: nls_iso8859_1 bcache crc64 zfs(PO)
zunicode(PO) zlua(PO) zcommon(PO) znvpair(PO) zavl(PO) icp(PO) spl(O)
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua overlay btrfs zstd_compress
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear i2c_smbus hid_generic
ast drm_vram_helper ttm usbhid drm_kms_helper crct10dif_ce hid syscopyarea
ghash_ce sysfillrect sha2_ce qede mpt3sas sha256_arm64 ipmi_ssif sysimgblt uas
sha1_ce fb_sys_fops qed ipmi_devintf igb raid_class drm ipmi_msghandler
scsi_transport_sas ahci i2c_algo_bit crc8 gpio_xlp i2c_xlp9xx usb_storage
aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher
[ 287.040312] CPU: 1 PID: 1 Comm: shutdown Tainted: P O
5.4.0-80-generic #90-Ubuntu
[ 287.049083] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 0ACKL030
06/04/2020
[ 287.057072] pstate: 6049 (nZCv daif +PAN -UAO)
[ 287.061864] pc : igb_rd32+0x30/0xd8 [igb]
[ 287.065865] lr : __igb_shutdown+0x84/0x1d8 [igb]
[ 287.070468] sp : 80001255bb90
[ 287.073769] x29: 80001255bb90 x28: 00bf5434e900
[ 287.079067] x27: x26: 009eef029130
[ 287.084365] x25: x24: 009ed603ce08
[ 287.089663] x23: 80001255bc37 x22: 009eef029000
[ 287.094960] x21: 009ed603ce08 x20: 0008
[ 287.100258] x19: 8000301c0008 x18:
[ 287.10] x17: x16: 0032
[ 287.110853] x15: 0004 x14: 0003
[ 287.116150] x13: x12: 009ed50f3530
[ 287.121448] x11: 009ed50f3478 x10:
[ 287.126745] x9 : 0001 x8 : 00210d00
[ 287.132043] x7 : x6 : 0001
[ 287.137340] x5 : x4 : fe027b2d5c20
[ 287.142638] x3 : 00bf5434e900 x2 :
[ 287.147935] x1 : 8000301c x0 : 890491c4
[ 287.153234] Call trace:
[ 287.155673] igb_rd32+0x30/0xd8 [igb]
[ 287.159326] __igb_shutdown+0x84/0x1d8 [igb]
[ 287.163586] igb_shutdown+0x38/0x90 [igb]
[ 287.167585] pci_device_shutdown+0x48/0x88
[ 287.171670] device_shutdown+0x14c/0x298
[ 287.175582] kernel_restart_prepare+0x48/0x58
[ 287.179925] kernel_restart+0x24/0x80
[ 287.183573] __do_sys_reboot+0x100/0x228
[ 287.187482] __arm64_sys_reboot+0x30/0x40
[ 287.191480] el0_svc_common.constprop.0+0xe4/0x1f0
[ 287.196256] el0_svc_handler+0x38/0xa8
[ 287.13] el0_svc+0x10/0x2c8
[ 287.203124] Code: d503201f f94006a1 b40002c1 8b344033 (b9400273)
[ 287.209320] ---[ end trace b2addffb79e92219 ]---
[ 287.214039] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[ 287.221755] Kernel Offset: disabled
[ 287.225231] CPU features: 0x6002,62000c38
[ 287.229226] Memory Limit: none
[ 287.232296] ---[ end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b ]---
Rom...
CRC: len=0xf080, cal=0x27ff5de9, img=0x27ff5de9, match!
[Test Case]:
Deploy Focal/Arm64-Generic to a ThunderX2 in the MAAS (Metal As a Service)
provisioner. Using MAAS version: 2.9.3~beta1 (9197-g.afe92bb63) via a snap,
the daily focal image appears to be 20210811
From the kernel teams standpoint this kernel in the initrd, did pass SRU
testing before its release.
[Fix]:
N/A
[Regression]:
Probably No (From Kernel Viewpoint) this could possibly be caused by something
other than kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940482
Title:
[thunderx2] Synchronous external abort: 96000610 [#1] SMP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940482/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938299] [NEW] Unable to SSH Into Instance when deploying Impish 12.10
Public bug reported: Google Instances deployed with the Ubuntu 12.10 Daily images are inaccessible via SSH. gcloud compute instances create sf-impish-v20200720 --zone us-west1-a --network "default" --no-restart-on-failure --image-project ubuntu-os- cloud-devel --image daily-ubuntu-2110-impish-v20210720 --machine-type n1-standard-2 Will result in a successful deploy yet, inaccessible via ssh from the end users configured laptop. This appears to affect all daily images after 20210719. daily-ubuntu-2110-impish-v20210719ubuntu-os-cloud-devel ubuntu-2110 READY daily-ubuntu-2110-impish-v20210720ubuntu-os-cloud-devel ubuntu-2110 READY daily-ubuntu-2110-impish-v20210721ubuntu-os-cloud-devel ubuntu-2110 READY daily-ubuntu-2110-impish-v20210723ubuntu-os-cloud-devel ubuntu-2110 READY daily-ubuntu-2110-impish-v20210724ubuntu-os-cloud-devel ubuntu-2110 READY daily-ubuntu-2110-impish-v20210725ubuntu-os-cloud-devel ubuntu-2110 READY daily-ubuntu-2110-impish-v20210728ubuntu-os-cloud-devel ubuntu-2110 This problem also appears to be reproducible via the gcloud UI, create a new virtual machine using the daily-ubuntu-2110-impish-v20210720 or greater and instruct the virtual machine to import a ssh_pub_key in the security tab. The Instance will start, yet still be inaccessible via the users private sshkey The google-guest-agent.service appears to be responsible for adding the google project ssh keys to the instance once its deployed. Please see below when queried on the 20210719 image: google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2021-07-27 19:47:48 UTC; 18h ago Main PID: 711 (google_guest_ag) Tasks: 9 (limit: 8924) Memory: 19.7M CGroup: /system.slice/google-guest-agent.service └─711 /usr/bin/google_guest_agent Jul 27 19:47:55 sean-imp gpasswd[1469]: user google added by root to group floppy Jul 27 19:47:55 sean-imp gpasswd[1475]: user google added by root to group audio Jul 27 19:47:55 sean-imp gpasswd[1481]: user google added by root to group dip Jul 27 19:47:55 sean-imp gpasswd[1487]: user google added by root to group video Jul 27 19:47:55 sean-imp gpasswd[1493]: user google added by root to group plugdev Jul 27 19:47:55 sean-imp gpasswd[1499]: user google added by root to group netdev Jul 27 19:47:55 sean-imp gpasswd[1505]: user google added by root to group lxd Jul 27 19:47:55 sean-imp gpasswd[1511]: user google added by root to group google-sudoers Jul 27 19:47:55 sean-imp GCEGuestAgent[711]: 2021-07-27T19:47:55.1699Z GCEGuestAgent Info: Updating keys for user google. Jul 27 19:47:55 sean-imp google_guest_agent[711]: 2021/07/27 19:47:55 logging client: rpc error: code = PermissionDenied desc = Clo> lines 1-19/19 (END) ** Affects: google-guest-agent (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/1938299 Title: Unable to SSH Into Instance when deploying Impish 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1938299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4
** Tags added: hinted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926142 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1926142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866591] Re: vmx_pending_event_test failed in ubuntu_kvm_unit_tests
** Changed in: ubuntu-kernel-tests Status: Confirmed => Triaged ** Tags added: hinted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866591 Title: vmx_pending_event_test failed in ubuntu_kvm_unit_tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935684] Re: vmx_init_signal_test in ubuntu_kvm_unit_tests fails on bionic/linux amd64
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: hinted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935684 Title: vmx_init_signal_test in ubuntu_kvm_unit_tests fails on bionic/linux amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1935684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827866] Re: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure / X-aws
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: hinted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827866 Title: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure / X-aws To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923284] Re: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: hinted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923284 Title: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917616] Re: vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
** Tags added: hinted ** Changed in: ubuntu-kernel-tests Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917616 Title: vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918692] Re: ubuntu-kvm-unit-test/vmx_apic_passthrough_thread reports assertion failure
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: hinted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918692 Title: ubuntu-kvm-unit-test/vmx_apic_passthrough_thread reports assertion failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1918692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
** Tags added: hinted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932966 Title: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929925] Re: [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64
Verified fixed groovy
Verifying base install
series: groovy
arch: arm64
uname -vr: 5.8.0-55-generic #62-Ubuntu SMP Tue Jun 1 08:20:36 UTC 2021
+ SUT=bjf-test
+ SSH_KEY=/root/.ssh/id_rsa
+ SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -i /root/.ssh/id_rsa'
++ lsb_release -c
++ awk '{print$2}'
+ DISTRO=groovy
+ ARCHITECTURE=arm64
+ trap cleanup EXIT
+ '[' -z arm64 ']'
+ kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used
+ '[' 0 '!=' 0 ']'
+ '[' '!' -f /root/.ssh/id_rsa ']'
+ '[' arm64 = ppc64el ']'
++ uvt-simplestreams-libvirt query
++ grep -P 'groovy.*arm64'
+ image='release=groovy arch=arm64 label=daily (20210527)'
+ '[' -z 'release=groovy arch=arm64 label=daily (20210527)' ']'
+ uvt-kvm create bjf-test release=groovy arch=arm64
+ uvt-kvm wait bjf-test --insecure --ssh-private-key-file /root/.ssh/id_rsa
++ uvt-kvm ip bjf-test
+ ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -i /root/.ssh/id_rsa ubuntu@192.168.122.213 uname -a
Linux bjf-test 5.8.0-53-generic #60-Ubuntu SMP Thu May 6 07:47:26 UTC 2021
aarch64 aarch64 aarch64 GNU/Linux
++ cut '-d ' -f 2
+++ uvt-kvm ip bjf-test
++ ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -i /root/.ssh/id_rsa ubuntu@192.168.122.213 lsb_release -c
+ RESULT=groovy
+ '[' groovy '!=' groovy ']'
+ cleanup
+ uvt-kvm destroy bjf-test
+ '[' arm64 = ppc64el ']'
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929925
Title:
[Potential Regression] Unable to create KVM with uvtool on Groovy
ARM64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1929925/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894964] Re: Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe (blocking net test in ubuntu_kernel_selftests to build)
** Tags added: sru-20210125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894964 Title: Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe (blocking net test in ubuntu_kernel_selftests to build) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1894964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909316] Re: Unable to boot with F-gkeop kernel
** Changed in: ubuntu-kernel-tests 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/1909316 Title: Unable to boot with F-gkeop kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909316] Re: Unable to boot with F-gkeop kernel
Pushed 2 commits to internal tools to handle this problem, will update further if problem still exists. ** Changed in: linux-gkeop (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909316 Title: Unable to boot with F-gkeop kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909316] Re: Unable to boot with F-gkeop kernel
I have attempted to boot the kernel via using the kernel index in grub which has also failed at this time. The kernel does appear to boot as expected in a qemu VM. Grub appears t o be forcing the uuid partid, Panic: [0.969467] tty tty0: hash matches [0.970273] tty console: hash matches [0.971276] rtc_cmos 00:00: setting system clock to 2021-01-05T16:55:01 UTC (1609865701) [1.077316] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2 [1.079288] md: Waiting for all devices to be available before autodetect [1.080346] md: If you don't use raid, use raid=noautodetect [1.081347] md: Autodetecting RAID arrays. [1.081962] md: autorun ... [1.082359] md: ... autorun DONE. [1.082952] VFS: Cannot open root device "PARTUUID=737695f9-0fcb-48ea-acc5-48cda21d60f6" or unknown-block(0,0): error -6 [1.084735] Please append a correct "root=" boot option; here are the available partitions: [1.086158] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [1.087428] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-1008-gkeop #9-Ubuntu [1.088680] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [1.090070] Call Trace: [1.090429] dump_stack+0x6d/0x9a [1.090913] panic+0x101/0x2e3 [1.091354] mount_block_root+0x23f/0x2e8 [1.091968] mount_root+0x38/0x3a [1.092435] prepare_namespace+0x13f/0x194 [1.093003] kernel_init_freeable+0x231/0x255 [1.093679] ? rest_init+0xb0/0xb0 [1.094294] kernel_init+0xe/0x110 [1.094845] ret_from_fork+0x35/0x40 [1.095410] Kernel Offset: 0x2560 from 0x8100 (relocation range: 0x8000-0xbfff) [1.097034] ACPI MEMORY or I/O RESET_REG. In /etc/default/grub.d/40-force-partuuid.cfg the following entry exists: GRUB_FORCE_PARTUUID=737695f9-0fcb-48ea-acc5-48cda21d60f6 By removing this file, allows grub to specify the block device path for kernel root (root=/dev/sda1 vs UUID). [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1008-gkeop root=/dev/sda1 ro console=ttyS0 This appears to resolve the booting issue in the cloud. Using indexes now works, configuring /etc/default/grub ; default="1>2" boots as expected. Also using the $menu_id strings also works now: GRUB_DEFAULT="gnulinux-advanced-dc7ce673-d33f-4a3b-bce1-fff7064b9ab4>gnulinux-5.4.0-1008-gkeop-advanced-dc7ce673-d33f-4a3b-bce1-fff7064b9ab4" ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Sean Feole (sfeole) ** Changed in: ubuntu-kernel-tests Importance: Undecided => Critical ** Changed in: ubuntu-kernel-tests Status: New => 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/1909316 Title: Unable to boot with F-gkeop kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909316] Re: Unable to boot with F-gkeop kernel
See attached for full boot logs ** Attachment added: "boot.txt" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909316/+attachment/5449493/+files/boot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909316 Title: Unable to boot with F-gkeop kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905067] Re: qemu-system-riscv64 sbi_trap_error powering down VM riscv64
I have some cycles to test this, will report back hopefully by EOD today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905067 Title: qemu-system-riscv64 sbi_trap_error powering down VM riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1905067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905067] Re: qemu-system-riscv64 sbi_trap_error powering down VM riscv64
@Christian thanks for helping out, I could test both F&G versions of QEMU for you, but the one I need on our production system is Focal. Let me know where to grab it from once you have it built -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905067 Title: qemu-system-riscv64 sbi_trap_error powering down VM riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1905067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64
affects aws cloud 5.X kernels. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** No longer affects: linux (Ubuntu Disco) ** No longer affects: linux (Ubuntu Cosmic) ** Tags added: sru-20201109 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805806 Title: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1805806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed
** Tags added: affects.dgx2 sru-20201109 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829995 Title: getaddrinfo_01 from ipv6_lib test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes
** No longer affects: linux (Ubuntu Disco) ** Tags added: affects.dgx2 sru-20201109 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836167 Title: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'
affects.dgx2 in this case test-case 12 failed not 13. 11/20 14:34:51 DEBUG| utils:0153| [stdout] test_pci 700 TFAIL : tpci.c:74: PCI bus 35 slot 00 : Test-case '12' ** Tags added: affects.dgx2 bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed
** Tags added: sru-20201109 ** Tags added: affects.dgx2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822308] Re: vmx_hlt_with_rvi_test in kvm_unit_tests fails
** Tags added: affects.dgx2 ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822308 Title: vmx_hlt_with_rvi_test in kvm_unit_tests fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905067] [NEW] qemu-system-riscv64 sbi_trap_error powering down VM riscv64
Public bug reported: Host OS: Focal, 20.04(5.4.0-52-generic) QEMU: 1:4.2-3ubuntu6.8 OpenSBI: 0.8.1 Affected Series: Focal/Groovy Both 5.4/5.8 kernels Upon powering off a Groovy VM ( GNU/Linux 5.8.0-7-generic riscv64 ) an sbi_trap_error will occur halting the VM. I have not tried an older version of OSBI. root@riscv64-groovy:~# poweroff -f Powering off. [ 134.931728] reboot: Power down sbi_trap_error: hart0: trap handler failed (error -2) sbi_trap_error: hart0: mcause=0x0007 mtval=0x0010 sbi_trap_error: hart0: mepc=0x8000d4b0 mstatus=0x1822 sbi_trap_error: hart0: ra=0x800098de sp=0x80023c78 sbi_trap_error: hart0: gp=0xffe001722418 tp=0xffe1ed138b80 sbi_trap_error: hart0: s0=0x80023c88 s1=0x0040 sbi_trap_error: hart0: a0=0x a1=0x80003f66 sbi_trap_error: hart0: a2=0x80003f66 a3=0x80003f66 sbi_trap_error: hart0: a4=0x0010 a5=0x sbi_trap_error: hart0: a6=0x3f66 a7=0x000110e8 sbi_trap_error: hart0: s2=0x s3=0x80024000 sbi_trap_error: hart0: s4=0x s5=0x sbi_trap_error: hart0: s6=0x0001 s7=0x sbi_trap_error: hart0: s8=0x s9=0x sbi_trap_error: hart0: s10=0x s11=0x0008 sbi_trap_error: hart0: t0=0x t1=0x sbi_trap_error: hart0: t2=0x t3=0x sbi_trap_error: hart0: t4=0x t5=0x sbi_trap_error: hart0: t6=0x root@riscv64-groovy:~# sudo poweroff Stopping Session 1 of user root. [ OK ] Removed slice system-modprobe.slice. [ OK ] Stopped target Graphical Interface. [ OK ] Stopped target Multi-User System. [ OK ] Stopped target Login Prompts. [ OK ] Stopped target Host and Network Name Lookups. [ OK ] Stopped target Timers. [ OK ] Stopped Daily apt upgrade and clean activities. [ OK ] Stopped Daily apt download activities. [ OK ] Stopped Periodic ext4 Onli…ata Check for All Filesystems. [ OK ] Stopped Discard unused blocks once a week. [ OK ] Stopped Daily rotation of log files. [ OK ] Stopped Message of the Day. [ OK ] Stopped Daily Cleanup of Temporary Directories. [ OK ] Stopped target System Time Synchronized. [ OK ] Stopped target System Time Set. [ OK ] Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. Stopping Regular background program processing daemon... Stopping Getty on tty1... Stopping Dispatcher daemon for systemd-networkd... Stopping System Logging Service... Stopping Serial Getty on ttyS0... Stopping Load/Save Random Seed... [ OK ] Stopped Regular background program processing daemon. [ OK ] Stopped Dispatcher daemon for systemd-networkd. [ OK ] Stopped System Logging Service. [ OK ] Stopped Serial Getty on ttyS0. [ OK ] Stopped Getty on tty1. [ OK ] Stopped Load/Save Random Seed. [ OK ] Stopped Session 1 of user root. [ OK ] Removed slice system-getty.slice. [ OK ] Removed slice system-serial\x2dgetty.slice. Stopping User Login Management... Stopping User Manager for UID 0... [ OK ] Stopped User Login Management. [ OK ] Stopped User Manager for UID 0. Stopping User Runtime Directory /run/user/0... [ OK ] Unmounted /run/user/0. [ OK ] Stopped User Runtime Directory /run/user/0. [ OK ] Removed slice User Slice of UID 0. [ OK ] Reached target Unmount All Filesystems. Stopping D-Bus System Message Bus... Stopping Permit User Sessions... [ OK ] Stopped D-Bus System Message Bus. [ OK ] Stopped Permit User Sessions. [ OK ] Stopped target Basic System. [ OK ] Stopped target Network. [ OK ] Stopped target Paths. [ OK ] Stopped target Remote File Systems. [ OK ] Stopped target Slices. [ OK ] Removed slice User and Session Slice. [ OK ] Stopped target Sockets. [ OK ] Closed D-Bus System Message Bus Socket. [ OK ] Stopped target System Initialization. [ OK ] Stopped target Local Encrypted Volumes. [ OK ] Stopped Dispatch Password …ts to Console Directory Watch. [ OK ] Stopped Forward Password R…uests to Wall Directory Watch. [ OK ] Stopped target Swap. [ OK ] Closed Syslog Socket. Stopping Network Name Resolution... Stopping Network Time Synchronization... Stopping Update UTMP about System Boot/Shutdown... [ OK ] Stopped Network Time Synchronization. [ OK ] Stopped Network Name Resolution. Stopping Network Service... [ OK ] Stopped Network Service. [ OK ] Stopped Update UTMP about System Boot/Shutdown. [ OK ] Stopped Apply Kernel Variables. [ OK ] Stopped Load Kernel Modules. [ OK ] Stopped Create Volatile Files and Directories. [ OK ] Stopped target Local File Systems. [ OK ] Stopped target Local File Systems (Pre). [ OK ] Sto
[Bug 1905066] [NEW] qemu-system-riscv64 soft lockup while restarting/shutdown vm
Public bug reported: Host OS: Focal, 20.04(5.4.0-52-generic) QEMU: 1:4.2-3ubuntu6.8 OpenSBI: 0.8.1 Guest VM: Focal(5.4 Kernel) When the VM is instructed to reboot, via systemctl or without systemctl I can reproduce 100% a soft lockup. [ 107.637699] reboot: Restarting system [ 132.687087] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-shutdow:1] [ 132.687751] Modules linked in: ofpart redboot cmdlinepart cfi_cmdset_0001 cfi_probe cfi_util gen_probe physmap map_funcs chipreg mtd virtio_rng uio_pdrv_genirq uio sch_fq_codel drm drm_panel_orientation_quirks ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear virtio_net net_failover failover virtio_blk [ 132.690237] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 5.4.0-24-generic #28-Ubuntu [ 132.690777] sepc: ffeb658e ra : ffeb658e sp : ffe1f5badd30 [ 132.691226] gp : ffe000d51a40 tp : ffe1f5bb8b80 t0 : ffe000d69248 [ 132.691658] t1 : ffe0004f053c t2 : 000a s0 : ffe1f5badd50 [ 132.692085] s1 : a0 : a1 : [ 132.692530] a2 : a3 : a4 : [ 132.692945] a5 : a6 : 076d a7 : 0137 [ 132.693368] s2 : 28121969 s3 : ffe000c6abf0 s4 : fee1dead [ 132.693825] s5 : 6d07a9c2f20a9100 s6 : 003fffc539d0 s7 : 003fffc53cf8 [ 132.694271] s8 : 0fff s9 : f000 s10: [ 132.694730] s11: t3 : t4 : 0003ab28 [ 132.695177] t5 : ffe000d52928 t6 : ffe000d61588 [ 132.695519] sstatus: 0120 sbadaddr: scause: 8005 The full log is attached. Command to launch VM and utilize existing bridged network device. qemu-system-riscv64 -nographic -machine virt -m 8G -smp 8 \ -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf \ -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \ -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0 \ -append "console=ttyS0 rw root=/dev/vda1" \ -device virtio-blk-device,drive=hd0 -drive file=riscv64-focal-ubuntu.img,format=raw,id=hd0 \ -device virtio-net-device,netdev=eth0 -netdev tap,id=eth0 The Soft Lockup is also exhibited on Groovy using the 5.8.0-7 kernel Welcome to Ubuntu 20.10 (GNU/Linux 5.8.0-7-generic riscv64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage Last login: Fri Nov 20 17:29:12 UTC 2020 on ttyS0 root@galrog:~# reboot -f Rebooting. [ 45.812221] reboot: Restarting system [ 72.085848] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [reboot:404] [ 100.086371] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [reboot:404] [ 105.818281] rcu: INFO: rcu_sched self-detected stall on CPU [ 105.819258] rcu: 0-: (14998 ticks this GP) idle=f82/1/0x4002 softirq=1584/1584 fqs=7362 ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Attachment added: "riscv64-reboot.txt" https://bugs.launchpad.net/bugs/1905066/+attachment/5436395/+files/riscv64-reboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905066 Title: qemu-system-riscv64 soft lockup while restarting/shutdown vm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1905066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904243] Re: 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk
use the attached script to change the boot kernel , usage: ./script.sh generic ** Description changed: This was caught while testing a few runs in the google cloud. Steps to reproduce: 1.) deploy 21.04 in the cloud (n1-standard-1 instance type) 2.) install 5.10.0-3.4 from the canonical-kernel-team bootstrap ppa 2a.) sudo add-apt-repository ppa:canonical-kernel-team/bootstrap 3.) sudo apt install linux-generic-wip + 4.) update grub to boot the generic kernel as the default kernel will be -gcp, (use attached script) ./script.sh generic + 5.) reboot and monitor console logs Full startup logs attached: looks to be grub related, I have not looked into this any further. 1.410153] VFS: Cannot open root device "PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6 [1.411882] Please append a correct "root=" boot option; here are the available partitions: [1.413203] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [1.414356] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-3-generic #4-Ubuntu [1.415702] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [1.417180] Call Trace: [1.417710] show_stack+0x52/0x58 [1.418263] dump_stack+0x70/0x8b [1.418738] panic+0x101/0x2e3 [1.419209] mount_block_root+0x21e/0x298 [1.419778] mount_root+0x38/0x3a [1.420243] prepare_namespace+0x13f/0x18d [1.420840] kernel_init_freeable+0x156/0x17d [1.421574] ? rest_init+0xba/0xba [1.422135] kernel_init+0xe/0x116 [1.422708] ret_from_fork+0x22/0x30 [1.423858] Kernel Offset: 0x10c0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.425374] ACPI MEMORY or I/O RESET_REG. ** Attachment added: "boot-kernel-simple" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904243/+attachment/5435704/+files/boot-kernel-simple ** Description changed: This was caught while testing a few runs in the google cloud. Steps to reproduce: 1.) deploy 21.04 in the cloud (n1-standard-1 instance type) 2.) install 5.10.0-3.4 from the canonical-kernel-team bootstrap ppa 2a.) sudo add-apt-repository ppa:canonical-kernel-team/bootstrap 3.) sudo apt install linux-generic-wip - 4.) update grub to boot the generic kernel as the default kernel will be -gcp, (use attached script) ./script.sh generic + 4.) update grub to boot the generic kernel as the default kernel will be -gcp, (use attached script comment#4) ./script.sh generic 5.) reboot and monitor console logs Full startup logs attached: looks to be grub related, I have not looked into this any further. 1.410153] VFS: Cannot open root device "PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6 [1.411882] Please append a correct "root=" boot option; here are the available partitions: [1.413203] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [1.414356] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-3-generic #4-Ubuntu [1.415702] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [1.417180] Call Trace: [1.417710] show_stack+0x52/0x58 [1.418263] dump_stack+0x70/0x8b [1.418738] panic+0x101/0x2e3 [1.419209] mount_block_root+0x21e/0x298 [1.419778] mount_root+0x38/0x3a [1.420243] prepare_namespace+0x13f/0x18d [1.420840] kernel_init_freeable+0x156/0x17d [1.421574] ? rest_init+0xba/0xba [1.422135] kernel_init+0xe/0x116 [1.422708] ret_from_fork+0x22/0x30 [1.423858] Kernel Offset: 0x10c0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.425374] ACPI MEMORY or I/O RESET_REG. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904243 Title: 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904243] Re: 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk
** Description changed: - This was caught while testing a few runs in the google cloud. + This was caught while testing a few runs in the google cloud. Steps to reproduce: - 1.) deploy 21.04 in the cloud (any instance type) + 1.) deploy 21.04 in the cloud (n1-standard-1 instance type) 2.) install 5.10.0-3.4 from the canonical-kernel-team bootstrap ppa 2a.) sudo add-apt-repository ppa:canonical-kernel-team/bootstrap 3.) sudo apt install linux-generic-wip Full startup logs attached: looks to be grub related, I have not looked into this any further. -1.410153] VFS: Cannot open root device "PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6 + 1.410153] VFS: Cannot open root device "PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6 [1.411882] Please append a correct "root=" boot option; here are the available partitions: [1.413203] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [1.414356] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-3-generic #4-Ubuntu [1.415702] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [1.417180] Call Trace: [1.417710] show_stack+0x52/0x58 [1.418263] dump_stack+0x70/0x8b [1.418738] panic+0x101/0x2e3 [1.419209] mount_block_root+0x21e/0x298 [1.419778] mount_root+0x38/0x3a [1.420243] prepare_namespace+0x13f/0x18d [1.420840] kernel_init_freeable+0x156/0x17d [1.421574] ? rest_init+0xba/0xba [1.422135] kernel_init+0xe/0x116 [1.422708] ret_from_fork+0x22/0x30 [1.423858] Kernel Offset: 0x10c0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.425374] ACPI MEMORY or I/O RESET_REG. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904243 Title: 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904243] [NEW] 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk
Public bug reported: This was caught while testing a few runs in the google cloud. Steps to reproduce: 1.) deploy 21.04 in the cloud (any instance type) 2.) install 5.10.0-3.4 from the canonical-kernel-team bootstrap ppa 2a.) sudo add-apt-repository ppa:canonical-kernel-team/bootstrap 3.) sudo apt install linux-generic-wip Full startup logs attached: looks to be grub related, I have not looked into this any further. 1.410153] VFS: Cannot open root device "PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6 [1.411882] Please append a correct "root=" boot option; here are the available partitions: [1.413203] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [1.414356] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-3-generic #4-Ubuntu [1.415702] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [1.417180] Call Trace: [1.417710] show_stack+0x52/0x58 [1.418263] dump_stack+0x70/0x8b [1.418738] panic+0x101/0x2e3 [1.419209] mount_block_root+0x21e/0x298 [1.419778] mount_root+0x38/0x3a [1.420243] prepare_namespace+0x13f/0x18d [1.420840] kernel_init_freeable+0x156/0x17d [1.421574] ? rest_init+0xba/0xba [1.422135] kernel_init+0xe/0x116 [1.422708] ret_from_fork+0x22/0x30 [1.423858] Kernel Offset: 0x10c0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.425374] ACPI MEMORY or I/O RESET_REG. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Incomplete ** Tags: breezy ** Attachment added: "diske.txt" https://bugs.launchpad.net/bugs/1904243/+attachment/5434230/+files/diske.txt ** Also affects: linux (Ubuntu Hirsute) 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/1904243 Title: 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760087] Re: net test in ubuntu_kernel_selftest failed on linux-kvm
** Tags added: sru-20200921 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760087 Title: net test in ubuntu_kernel_selftest failed on linux-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1760087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896725] Re: xenial 4.4.0-191-generic in -proposed has a regression
Testing picked this up a few hours before the bug was open, looks like its affecting quite a few instances as mentioned in comment #4. Marking Confirmed, tagging appropriately. ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => Confirmed ** Changed in: ubuntu-kernel-tests Importance: Undecided => High ** Tags added: aws sru-20200921 xenial ** Tags added: kqa ** Tags removed: kqa ** Tags added: kqa-blocker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896725 Title: xenial 4.4.0-191-generic in -proposed has a regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896781] Re: lttng-modules 2.11.2-1ubuntu0.1 ADT test failure with linux 5.4.0-49.53
** Changed in: ubuntu-kernel-tests Status: New => Incomplete ** Changed in: ubuntu-kernel-tests Status: Incomplete => Confirmed ** Tags added: aws azure gcp kqa-blocker oracle sru-20200921 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896781 Title: lttng-modules 2.11.2-1ubuntu0.1 ADT test failure with linux 5.4.0-49.53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840904] Re: ubuntu_fan_smoke_test failed with enable disable fan test on GKE 4.15 with g1-small and n1-highmem-16 / B-gcp-5.3
** Changed in: ubuntu-kernel-tests Assignee: Sean Feole (sfeole) => (unassigned) ** Changed in: ubuntu-kernel-tests Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840904 Title: ubuntu_fan_smoke_test failed with enable disable fan test on GKE 4.15 with g1-small and n1-highmem-16 / B-gcp-5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856163] Re: test_maps test from ubuntu_bpf will cause OOM on Eoan s390x LPAR
Eoan is EOL and no longer in the usual round of testing. Closing bug ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: ubuntu-kernel-tests Status: Triaged => Won't Fix ** Changed in: ubuntu-z-systems 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/1856163 Title: test_maps test from ubuntu_bpf will cause OOM on Eoan s390x LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1856163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894140] Re: grub-pc 2.04-1ubuntu29 fails to install on groovy 20.10 due to pkg deps conflict
So after looking around a bit it would appear there is another version of grub2 that has been uploaded to the builders. (Version 2.04-1ubuntu30) https://launchpad.net/ubuntu/+source/grub2/2.04-1ubuntu30 Appears to have 2 fixes: * postinst.in: do not attempt to call grub-install upon fresh install of grub-pc because it it a job of installers to do that after fresh install. * grub-multi-install: fix non-interactive failures for grub-efi like it was fixed in postinst for grub-pc. Not sure if this problem would be addressed in here, however the amd64 deb has failed to build and I have notified the appropriate xnoxx ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Changed in: ubuntu-kernel-tests Importance: Undecided => High ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Sean Feole (sfeole) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894140 Title: grub-pc 2.04-1ubuntu29 fails to install on groovy 20.10 due to pkg deps conflict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1894140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894140] [NEW] grub-pc 2.04-1ubuntu29 fails to install on groovy 20.10 due to pkg deps conflict
Public bug reported:
Series: Groovy
Arch: AMD64
When attempting to deploy Groovy AMD64 images via MAAS, the deployment is
failing due to curtin attempting to install grub-pc (2.04-1ubuntu29 ) which
fails to install due to a depends issue noted below.
This has essentially broken all maas deployments at least on Groovy AMD64 at
this time.
Setting up linux-generic (5.8.0.16.18) ...
Setting up grub-pc (2.04-1ubuntu29) ...
Creating config file /etc/default/grub with new version
dpkg: error processing package grub-pc (--configure):
installed grub-pc package post-installation script subprocess returned
error exit status 1
dpkg: dependency problems prevent configuration of
grub-gfxpayload-lists:
grub-gfxpayload-lists depends on grub-pc (>= 1.99~20101210-1ubuntu2);
however:
Package grub-pc is not configured yet.
dpkg: error processing package grub-gfxpayload-lists (--configure):
dependency problems - leaving unconfigured
Processing triggers for dbus (1.12.18-1ubuntu1) ...
Processing triggers for install-info (6.7.0.dfsg.2-5) ...
No apport report written because the error message indicates its a
followup error from a previous failure.
Processing triggers for libc-bin (2.31-0ubuntu10) ...
Processing triggers for systemd (246.2-1ubuntu1) ...
Running in chroot, ignoring command 'daemon-reload'
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for linux-image-5.8.0-16-generic (5.8.0-16.17) ...
Errors were encountered while processing:
grub-pc
grub-gfxpayload-lists
E: Sub-process /usr/bin/dpkg returned an error code (1)
Running command ['udevadm', 'settle'] with allowed return codes [0]
(capture=False)
TIMED subp(['udevadm', 'settle']): 0.050
Running command ['umount', '/tmp/tmpu39p2api/target/sys'] with allowed
return codes [0] (capture=False)
Running command ['umount', '/tmp/tmpu39p2api/target/run'] with allowed
return codes [0] (capture=False)
Running command ['umount', '/tmp/tmpu39p2api/target/proc'] with allowed
return codes [0] (capture=False)
Running command ['umount', '/tmp/tmpu39p2api/target/dev'] with allowed
return codes [0] (capture=False)
finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-kernel: FAIL:
installing kernel
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin
command curthooks
Traceback (most recent call last):
File "/curtin/curtin/commands/main.py", line 202, in main
ret = args.func(args)
File "/curtin/curtin/commands/curthooks.py", line 1770, in curthooks
builtin_curthooks(cfg, target, state)
File "/curtin/curtin/commands/curthooks.py", line 1613, in
builtin_curthooks
install_kernel(cfg, target)
File "/curtin/curtin/commands/curthooks.py", line 371, in
install_kernel
distro.install_packages([kernel_package], target=target)
File "/curtin/curtin/distro.py", line 405, in install_packages
return install_cmd('install', args=pkglist, opts=opts,
target=target,
File "/curtin/curtin/distro.py", line 292, in run_apt_command
return inchroot.subp(cmd, env=env)
File "/curtin/curtin/util.py", line 708, in subp
return subp(*args, **kwargs)
File "/curtin/curtin/util.py", line 275, in subp
return _subp(*args, **kwargs)
File "/curtin/curtin/util.py", line 139, in _subp
raise ProcessExecutionError(stdout=out, stderr=err,
curtin.util.ProcessExecutionError: Unexpected error while running
command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot',
'/tmp/tmpu39p2api/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes',
'--option=Dpkg::options::=--force-unsafe-io',
'--option=Dpkg::Options::=--force-confold', 'install', 'linux-generic']
Exit code: 100
Reason: -
Stdout: ''
Stderr: ''
Unexpected error while running command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot',
'/tmp/tmpu39p2api/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes',
'--option=Dpkg::options::=--force-unsafe-io',
'--option=Dpkg::Options::=--force-confold', 'install', 'linux-generic']
Exit code: 100
Reason: -
Stdout: ''
Stderr: ''
Stderr: ''
** 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/1894140
Title:
grub-pc 2.04-1ubuntu29 fails to install on groovy 20.10 due to pkg
deps conflict
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894140/+subscrip
[Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / X-KVM / B-KVM
** Changed in: ubuntu-kernel-tests Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / X-KVM / B-KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed
** Tags added: sru-20200810 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837543 Title: crypto_user02 in crypto from ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: sru-20200810 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed
** No longer affects: linux-aws (Ubuntu Eoan) ** No longer affects: linux (Ubuntu Eoan) ** No longer affects: linux-aws (Ubuntu Disco) ** No longer affects: linux (Ubuntu Disco) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837543 Title: crypto_user02 in crypto from ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed
** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-azure (Ubuntu Disco) ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux-aws (Ubuntu Disco) ** No longer affects: linux (Ubuntu Disco) ** Tags added: sru-20200810 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834006 Title: cpuset_hotplug from controllers in ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed
** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: New => Triaged ** Tags added: sru-20200810 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890803] Re: Groovy amd64 / arm64 / PowerPC deployment seems not working
Kernel SRU is mid cycle now, someone else will have to verify this is fixed, unfortunately the kernel team is using most of the MAAS servers that would probably be used for verification. So many teams may have to wait as we can't afford to have any more delays. ** Changed in: ubuntu-kernel-tests Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890803 Title: Groovy amd64 / arm64 / PowerPC deployment seems not working To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1890803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890803] Re: Groovy amd64 / arm64 / PowerPC deployment seems not working
I would appear systemd-remount-fs is failing to complete from looking at that inital logs, not sure if I can get more information out of the system yet i will try. [ OK ] Finished Load Kernel Modules. [ 18.650374] systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE [ 18.653462] systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'. [ 18.661691] systemd[1]: Failed to start Remount Root and Kernel File Systems. [FAILED] Failed to start Remount Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. [ 18.669951] systemd[1]: Started Journal Service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890803 Title: Groovy amd64 / arm64 / PowerPC deployment seems not working To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1890803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890803] Re: Groovy amd64 / arm64 / PowerPC deployment seems not working
I happened to check this updated -daily image again this morning which includes, cloud-initramfs-tools 0.46ubuntu1 and still see that the image remains broken. I have attached the console logs from this latest deploy. Looks like we made quite a bit of headway, still missing some bits that need to be updated possibly for lack of /etc/fstab. I have worked around the problem by creating a custom focal cloud image and deploying it via maas using a bionic ephemeral. However, that is simply a hack at this stage and not a valid fix. ** Attachment added: "groovy2.txt" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1890803/+attachment/5402152/+files/groovy2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890803 Title: Groovy amd64 / arm64 / PowerPC deployment seems not working To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1890803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed
** Changed in: ubuntu-kernel-tests Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812620 Title: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853610] Re: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails
ARM64, Focal 5.4 AWS 5.4.0-1021.21-aws 07/25 09:07:09 DEBUG| utils:0153| [stdout] tag=mkfs01_ext3_sh stime=1595667930 dur=2 exit=exited stat=1 core=no cu=12 cs=29 07/25 09:07:09 DEBUG| utils:0153| [stdout] startup='Sat Jul 25 09:05:37 2020' 07/25 09:07:09 DEBUG| utils:0153| [stdout] mkfs01 1 TINFO: timeout per run is 0h 5m 0s 07/25 09:07:09 DEBUG| utils:0153| [stdout] tst_device.c:88: INFO: Found free device 4 '/dev/loop4' 07/25 09:07:09 DEBUG| utils:0153| [stdout] mkfs01 1 TPASS: 'mkfs -t ext4 /dev/loop4 ' passed. 07/25 09:07:09 DEBUG| utils:0153| [stdout] mkfs01 2 TFAIL: 'mkfs -t ext4 /dev/loop4 16000' failed, not expected. 07/25 09:07:09 DEBUG| utils:0153| [stdout] mkfs01 3 TPASS: 'mkfs -t ext4 -c /dev/loop4 ' passed. 07/25 09:07:09 DEBUG| utils:0153| [stdout] mkfs01 4 TPASS: 'mkfs -V ' passed. 07/25 09:07:09 DEBUG| utils:0153| [stdout] mkfs01 5 TPASS: 'mkfs -h ' passed. 07/25 09:07:09 DEBUG| utils:0153| [stdout] mkfs01 6 TINFO: AppArmor enabled, this may affect test results 07/25 09:07:09 DEBUG| utils:0153| [stdout] mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) 07/25 09:07:09 DEBUG| utils:0153| [stdout] mkfs01 6 TINFO: loaded AppArmor profiles: none 07/25 09:07:09 DEBUG| utils:0153| [stdout] 07/25 09:07:09 DEBUG| utils:0153| [stdout] Summary: 07/25 09:07:09 DEBUG| utils:0153| [stdout] passed 4 07/25 09:07:09 DEBUG| utils:0153| [stdout] failed 1 07/25 09:07:09 DEBUG| utils:0153| [stdout] skipped 0 07/25 09:07:09 DEBUG| utils:0153| [stdout] warnings 0 ** Summary changed: - mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails with E + mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails ** Tags added: sru-20200629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853610 Title: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed
** Tags added: arm64 sru-20200629 ** No longer affects: linux (Ubuntu Disco) ** No longer affects: linux-aws (Ubuntu Disco) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'
Focal 5.4 ARM64 07/25 09:49:58 DEBUG| utils:0153| [stdout] test_pci 44 TFAIL : tpci.c:73: PCI bus 00 slot 28 : Test-case '12' ** Tags added: arm64 sru-20200629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed with D/B/E
5.4 Focal 07/25 06:03:17 DEBUG| utils:0153| [stdout] startup='Sat Jul 25 06:01:37 2020' 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens5/stable_secret: known issue: errno=EIO(5): Input/output error 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/sysrq-trigger: is write-only. 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/task/55318/mem: known issue: errno=EIO(5): Input/output error 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/task/55318/clear_refs: is write-only. 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/task/55318/pagemap: reached maxmbytes (-m) 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/task/55318/attr/prev: known issue: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/task/55318/attr/exec: known issue: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/task/55318/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/task/55318/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/task/55318/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 1 TFAIL : proc01.c:396: read failed: /proc/self/task/55318/attr/smack/current: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 2 TFAIL : proc01.c:396: read failed: /proc/self/task/55318/attr/apparmor/prev: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 3 TFAIL : proc01.c:396: read failed: /proc/self/task/55318/attr/apparmor/exec: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/clear_refs: is write-only. 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 4 TFAIL : proc01.c:396: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 5 TFAIL : proc01.c:396: read failed: /proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 6 TFAIL : proc01.c:396: read failed: /proc/self/attr/apparmor/exec: errno=EINVAL(22): Invalid argument 07/25 06:03:17 DEBUG| utils:0153| [stdout] proc01 7 TFAIL : proc01.c:466: readproc() failed with 6 errors. 07/25 06:03:17 DEBUG| utils:0153| [stdout] tag=proc01 stime=1595656897 dur=0 exit=exited stat=1 core=no cu=8 cs=46 ** Summary changed: - proc01 in fs from ubuntu_ltp failed with D/B/E + proc01 in fs from ubuntu_ltp failed ** Tags added: 5.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs f
[Bug 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed
Focal 5.4(SRU 2020/06/29) 3367. 07/25 02:26:31 DEBUG| utils:0153| [stdout] # selftests: net: msg_zerocopy.sh 3368. 07/25 02:26:31 DEBUG| utils:0153| [stdout] # ipv4 tcp -t 1 3369. 07/25 02:26:31 DEBUG| utils:0153| [stdout] # ./msg_zerocopy: setaffinity 2 3370. 07/25 02:26:31 DEBUG| utils:0153| [stdout] # ./msg_zerocopy: setaffinity 3 3371. 07/25 02:26:31 DEBUG| utils:0153| [stdout] not ok 21 selftests: net: msg_zerocopy.sh # exit=1 ** Tags added: 5.3 ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812620 Title: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774959] Re: clock test in monotonic_time will fail on Azure Instances
monotonic-time is no longer tested in the SRU cycles ** Changed in: ubuntu-kernel-tests Status: Confirmed => Invalid ** Changed in: linux-azure (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774959 Title: clock test in monotonic_time will fail on Azure Instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781902] Re: memory hotplug test stuck on Azure BasicA1 node with X-HWE azure kernel
We no longer test with the A1 Instances due to problems like this, A1 is an extremely minimal, low resource instance. We should not be offlining cpu and memory in these VMs. ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux-signed-azure (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781902 Title: memory hotplug test stuck on Azure BasicA1 node with X-HWE azure kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1781902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765653] Re: directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and Bionic ThunderX ARM64
As the ecryptfs support has been dropped in Bionic+(https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798359) marking bug invalid ** Changed in: ecryptfs Status: Triaged => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765653 Title: directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and Bionic ThunderX ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1765653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684788] Re: extend-file-random.sh.btrfs from ubuntu_ecryptfs test-suite failed on X-hwe
Xenial 4.4.0-187.217 1. 07/22 20:20:47 DEBUG| utils:0116| Running 'tests/run_one.sh -K -t extend-file-random.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs' 2. 07/22 20:21:13 DEBUG| utils:0153| [stdout] extend-file-random pass 3. 07/22 20:21:13 DEBUG| utils:0153| [stdout] 4. 07/22 20:21:13 DEBUG| utils:0153| [stdout] Test Summary: 5. 07/22 20:21:13 DEBUG| utils:0153| [stdout] 1 passed 6. 07/22 20:21:13 DEBUG| utils:0153| [stdout] 0 failed 7. ** Changed in: ubuntu-kernel-tests Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684788 Title: extend-file-random.sh.btrfs from ubuntu_ecryptfs test-suite failed on X-hwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1684788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765653] Re: directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and Bionic ThunderX ARM64
** Changed in: ecryptfs Assignee: Tyler Hicks (tyhicks) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765653 Title: directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and Bionic ThunderX ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1765653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749427] Re: Unable to create KVM with uvtool on arm64 system
Marking this as invalid, referenced bugs are all closed and pretty sure this is not a problem on arm64 any longer. ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749427 Title: Unable to create KVM with uvtool on arm64 system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1749427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739560] Re: Trusty arm64 system will hang on libhugetlbfs shmoverride_linked test
I have not seen this occur on the -aws nitro backed arm64 instances. Giving that mcdivitt is EOL, killing off this bug. 07/09 11:08:48 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] alloc-instantiate-race shared (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] alloc-instantiate-race private (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] truncate_reserve_wraparound (2M: 64):PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] truncate_sigbus_versus_oom (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] get_huge_pages (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] shmoverride_linked (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] HUGETLB_SHM=yes shmoverride_linked (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] shmoverride_linked_static (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] HUGETLB_SHM=yes shmoverride_linked_static (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] LD_PRELOAD=libhugetlbfs.so shmoverride_unlinked (2M: 64):PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] LD_PRELOAD=libhugetlbfs.so HUGETLB_SHM=yes shmoverride_unlinked (2M: 64):PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] quota.sh (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] counters.sh (2M: 64):PASS 07/09 11:08:49 DEBUG| utils:0153| [stdout] mmap-gettest 10 20 (2M: 64): PASS 07/09 11:08:49 DEBUG| utils:0153| [stdout] mmap-cow 19 20 (2M: 64): PASS 07/09 11:08:49 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040 07/09 11:08:50 DEBUG| utils:0153| [stdout] shm-fork 10 10 (2M: 64): PASS 07/09 11:08:50 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040 07/09 11:08:52 DEBUG| utils:0153| [stdout] shm-fork 10 20 (2M: 64): PASS 07/09 11:08:52 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040 07/09 11:08:52 DEBUG| utils:0153| [stdout] shm-getraw 20 /dev/full (2M: 64):PASS 07/09 11:09:18 DEBUG| utils:0153| [stdout] fallocate_stress.sh (2M: 64): PASS 07/09 11:09:18 DEBUG| utils:0153| [stdout] ** TEST SUMMARY 07/09 11:09:18 DEBUG| utils:0153| [stdout] * 2M 07/09 11:09:18 DEBUG| utils:0153| [stdout] * 32-bit 64-bit 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Total testcases: 0 113 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Skipped: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] *PASS: 0 111 07/09 11:09:18 DEBUG| utils:0153| [stdout] *FAIL: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] *Killed by signal: 0 1 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Bad configuration: 0 1 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Expected FAIL: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Unexpected PASS: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] *Test not present: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Strange test result: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] ** ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-kernel-tests 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/1739560 Title: Trusty arm64 system will hang on libhugetlbfs shmoverride_linked test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1739560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865965] Re: kill11 from ubuntu_ltp_syscalls failed
** Changed in: ubuntu-kernel-tests Status: New => Confirmed ** Tags added: hwe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865965 Title: kill11 from ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874703] Re: ubuntu_fan_smoke_test failed with unknown underlay network format on B-GKE-5.0
** Tags added: hwe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874703 Title: ubuntu_fan_smoke_test failed with unknown underlay network format on B-GKE-5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1874703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888381] Re: net test from ubuntu_kernel_selftest will timeout on B-5.0
I was able to reproduce this with linux-gke-5.0 after another attempt and ensuring the correct packages were installed. Confirmed the modules pkg and kernel is 5.0, Linux sfgke 5.0.0-58-generic #62~18.04.1-Ubuntu SMP Tue Jul 14 03:37:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [==] Running 37 tests from 2 test cases. [ RUN ] tls.sendfile [ OK ] tls.sendfile [ RUN ] tls.send_then_sendfile [ OK ] tls.send_then_sendfile [ RUN ] tls.recv_max [ OK ] tls.recv_max [ RUN ] tls.recv_small [ OK ] tls.recv_small [ RUN ] tls.msg_more [ OK ] tls.msg_more [ RUN ] tls.sendmsg_single [ OK ] tls.sendmsg_single [ RUN ] tls.sendmsg_fragmented [ OK ] tls.sendmsg_fragmented [ RUN ] tls.sendmsg_large [ OK ] tls.sendmsg_large [ RUN ] tls.sendmsg_multiple [ OK ] tls.sendmsg_multiple [ RUN ] tls.sendmsg_multiple_stress [ OK ] tls.sendmsg_multiple_stress [ RUN ] tls.splice_from_pipe [ OK ] tls.splice_from_pipe [ RUN ] tls.splice_from_pipe2 [ OK ] tls.splice_from_pipe2 [ RUN ] tls.send_and_splice [ OK ] tls.send_and_splice [ RUN ] tls.splice_to_pipe [ OK ] tls.splice_to_pipe [ RUN ] tls.recvmsg_single [ OK ] tls.recvmsg_single [ RUN ] tls.recvmsg_single_max [ OK ] tls.recvmsg_single_max [ RUN ] tls.recvmsg_multiple [ OK ] tls.recvmsg_multiple [ RUN ] tls.single_send_multiple_recv [ OK ] tls.single_send_multiple_recv [ RUN ] tls.multiple_send_single_recv [ OK ] tls.multiple_send_single_recv [ RUN ] tls.single_send_multiple_recv_non_align Jul 21 19:33:25 sfgke kernel: [10842.325048] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 19:33:25 sfgke kernel: [10842.332940] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 19:33:25 sfgke kernel: [10842.340720] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 19:33:25 sfgke kernel: [10842.348469] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 19:33:25 sfgke kernel: [10842.356168] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 19:33:25 sfgke kernel: [10842.364229] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 19:33:25 sfgke kernel: [10842.372100] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 19:33:26 sfgke kernel: [10843.477618] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 19:33:27 sfgke kernel: [10843.529738] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 19:33:27 sfgke kernel: [10843.536771] tls_set_device_offload_rx: netdev lo with no TLS offload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888381 Title: net test from ubuntu_kernel_selftest will timeout on B-5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888381] Re: net test from ubuntu_kernel_selftest will timeout on B-5.0
I was able to reproduce this again, deploying manually. Confirmed the modules pkg and kernel is 5.0, 5.0.0-58-generic #62~18.04.1-Ubuntu SMP Tue Jul 14 03:37:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ok 1..4 selftests: net: reuseport_dualstack [PASS] selftests: net: reuseaddr_conflict Opening 127.0.0.1: Opening INADDR_ANY: bind: Address already in use Opening in6addr_any: Opening INADDR_ANY: bind: Address already in use Opening INADDR_ANY: after closing ipv6 socket bind: Address already in use Successok 1..5 selftests: net: reuseaddr_conflict [PASS] selftests: net: tls [==] Running 37 tests from 2 test cases. [ RUN ] tls.sendfile [ OK ] tls.sendfile [ RUN ] tls.send_then_sendfile [ OK ] tls.send_then_sendfile [ RUN ] tls.recv_max [ OK ] tls.recv_max [ RUN ] tls.recv_small [ OK ] tls.recv_small [ RUN ] tls.msg_more [ OK ] tls.msg_more [ RUN ] tls.sendmsg_single [ OK ] tls.sendmsg_single [ RUN ] tls.sendmsg_fragmented [ OK ] tls.sendmsg_fragmented [ RUN ] tls.sendmsg_large [ OK ] tls.sendmsg_large [ RUN ] tls.sendmsg_multiple [ OK ] tls.sendmsg_multiple [ RUN ] tls.sendmsg_multiple_stress [ OK ] tls.sendmsg_multiple_stress [ RUN ] tls.splice_from_pipe [ OK ] tls.splice_from_pipe [ RUN ] tls.splice_from_pipe2 [ OK ] tls.splice_from_pipe2 [ RUN ] tls.send_and_splice [ OK ] tls.send_and_splice [ RUN ] tls.splice_to_pipe [ OK ] tls.splice_to_pipe [ RUN ] tls.recvmsg_single [ OK ] tls.recvmsg_single [ RUN ] tls.recvmsg_single_max [ OK ] tls.recvmsg_single_max [ RUN ] tls.recvmsg_multiple [ OK ] tls.recvmsg_multiple [ RUN ] tls.single_send_multiple_recv [ OK ] tls.single_send_multiple_recv [ RUN ] tls.multiple_send_single_recv [ OK ] tls.multiple_send_single_recv [ RUN ] tls.single_send_multiple_recv_non_align In the syslog also see: the following: Jul 21 18:52:42 sfgke kernel: [ 8399.219569] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 18:52:43 sfgke kernel: [ 8400.326594] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 18:52:43 sfgke kernel: [ 8400.378602] tls_set_device_offload_rx: netdev lo with no TLS offload Jul 21 18:52:43 sfgke kernel: [ 8400.385678] tls_set_device_offload_rx: netdev lo with no TLS offload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888381 Title: net test from ubuntu_kernel_selftest will timeout on B-5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848428] Re: generic/526 from ubuntu_xfstests_btrfs failed on D
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848428 Title: generic/526 from ubuntu_xfstests_btrfs failed on D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848429] Re: generic/527 from ubuntu_xfstests_btrfs failed on D
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848429 Title: generic/527 from ubuntu_xfstests_btrfs failed on D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848439] Re: generic/562 from ubuntu_xfstests_btrfs failed on D
** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848439 Title: generic/562 from ubuntu_xfstests_btrfs failed on D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878356] Re: generic/001 from ubuntu_xfstests_btrfs / ext4 / xfs failed on F
** Tags added: sru-20200629 ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Sean Feole (sfeole) ** Changed in: ubuntu-kernel-tests Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878356 Title: generic/001 from ubuntu_xfstests_btrfs / ext4 / xfs failed on F To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846293] Re: generic/554 from ubuntu_xfstests_btrfs / ext4 failed on D
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846293 Title: generic/554 from ubuntu_xfstests_btrfs / ext4 failed on D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1846293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848423] Re: generic/260 from ubuntu_xfstests_btrfs failed on D
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848423 Title: generic/260 from ubuntu_xfstests_btrfs failed on D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878347] Re: btrfs/136 from ubuntu_xfstests_btrfs failed on Focal
** Tags added: sru-20200629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878347 Title: btrfs/136 from ubuntu_xfstests_btrfs failed on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848424] Re: generic/471 from ubuntu_xfstests_btrfs failed on D
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848424 Title: generic/471 from ubuntu_xfstests_btrfs failed on D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846308] Re: generic/228 from ubuntu_xfstests_btrfs / ext4 / xfs failed on B/D/F
** Tags added: sru-20200629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846308 Title: generic/228 from ubuntu_xfstests_btrfs / ext4 / xfs failed on B/D/F To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1846308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802474] Re: test_map in ubuntu_bpf failed on D PowerPC
** Changed in: ubuntu-kernel-tests Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802474 Title: test_map in ubuntu_bpf failed on D PowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865965] Re: kill11 from ubuntu_ltp_syscalls failed
Also passes when run directly as outlined in comment #4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865965 Title: kill11 from ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Tags added: sru-20200629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865965] Re: kill11 from ubuntu_ltp_syscalls failed
9366. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGHUP 9367. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGINT 9368. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGQUIT dumped core 9369. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGILL dumped core 9370. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGTRAP dumped core 9371. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGIOT/SIGABRT dumped core 9372. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGIOT/SIGABRT dumped core 9373. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGBUS dumped core 9374. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGFPE dumped core 9375. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGKILL 9376. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGUSR1 9377. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGSEGV dumped core 9378. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGUSR2 9379. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGPIPE 9380. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGALRM 9381. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGTERM 9382. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGSTKFLT 9383. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGXCPU dumped core 9384. 07/13 20:30:37 DEBUG| utils:0153| [stdout] Test timeouted, sending SIGKILL! 9385. 07/13 20:30:37 DEBUG| utils:0153| [stdout] tst_test.c:1286: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 9386. 07/13 20:30:37 DEBUG| utils:0153| [stdout] tst_test.c:1288: BROK: Test killed! (timeout?) ** Tags added: bionic sru-20200629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865965 Title: kill11 from ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874703] Re: ubuntu_fan_smoke_test failed with unknown underlay network format on B-GKE-5.0
** Tags added: 5.4 focal gcp ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Sean Feole (sfeole) ** Tags added: sru-20200629 ** Changed in: ubuntu-kernel-tests Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874703 Title: ubuntu_fan_smoke_test failed with unknown underlay network format on B-GKE-5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1874703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865967] Re: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
** Tags added: 5.4 ** Tags added: sru-20200629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865967 Title: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 kernels
This appears to just be a nuisance now, rather than a reliable test as it is consistently failing in clouds. Will take some time to break this down and figure out if we can fix the test. ** Changed in: ubuntu-kernel-tests Assignee: Marcelo Cerri (mhcerri) => Sean Feole (sfeole) ** Changed in: linux (Ubuntu Eoan) Assignee: Marcelo Cerri (mhcerri) => (unassigned) ** Changed in: linux (Ubuntu) Assignee: Marcelo Cerri (mhcerri) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844493 Title: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1844493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on Eoan/5.3 kernels
** Tags added: sru-20200608 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844493 Title: ubuntu_sysdig_smoke_test failed on Eoan/5.3 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1844493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866972] Re: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests
Looks like fixed in 5.3.0-1026.28~18.04.1 - aws -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866972 Title: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845860] Re: test_maps in ubuntu_bpf failed to build on B-hwe-edge 5.3 (BTF is required, but is missing or corrupted.)
** Tags added: aws -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845860 Title: test_maps in ubuntu_bpf failed to build on B-hwe-edge 5.3 (BTF is required, but is missing or corrupted.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882559] Re: ubuntu_bpf failed to build on B-5.4 GCP with "error: use of unknown builtin '__builtin_preserve_access_index'"
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: aws azure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882559 Title: ubuntu_bpf failed to build on B-5.4 GCP with "error: use of unknown builtin '__builtin_preserve_access_index'" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867596] Re: ubuntu_bpf test failed to build on Eoan 5.3.0-43.35
** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867596 Title: ubuntu_bpf test failed to build on Eoan 5.3.0-43.35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1840904] Re: ubuntu_fan_smoke_test failed with enable disable fan test on GKE 4.15 with g1-small and n1-highmem-16 / B-gcp-5.3
This test needs to be re-written, i'll try to prioritize it this week. On Mon, Jun 8, 2020 at 11:56 AM Po-Hsu Lin <1840...@bugs.launchpad.net> wrote: > Affecting B-5.4 GCP > > ** Tags added: kqa-blocker sru-20200518 > > -- > You received this bug notification because you are a member of Canonical > Kernel Team, which is subscribed to ubuntu-kernel-tests. > https://bugs.launchpad.net/bugs/1840904 > > Title: > ubuntu_fan_smoke_test failed with enable disable fan test on GKE 4.15 > with g1-small and n1-highmem-16 / B-gcp-5.3 > > Status in ubuntu-kernel-tests: > In Progress > Status in linux-signed-gke-4.15 package in Ubuntu: > Invalid > > Bug description: > This test has passed on other nodes, just these 2 are failing > Test failed with: > /usr/sbin/fanatic: bogus: unknown underlay network format > > Reproduce rate: 3/3 on these two instances. > > However, I tried to test this manually with g1-small, yes the first > attempt failed with the exact failure, but when I give it a retry > right away, test passed this time. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-1041-gke 4.15.0-1041.43 > ProcVersionSignature: Ubuntu 4.15.0-1041.43-gke 4.15.18 > Uname: Linux 4.15.0-1041-gke x86_64 > ApportVersion: 2.20.9-0ubuntu7.7 > Architecture: amd64 > Date: Wed Aug 21 09:52:32 2019 > SourcePackage: linux-signed-gke-4.15 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840904/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840904 Title: ubuntu_fan_smoke_test failed with enable disable fan test on GKE 4.15 with g1-small and n1-highmem-16 / B-gcp-5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831543] Re: Standard_A2_v2 Azure instance will have CPU in offline state
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux-azure (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831543 Title: Standard_A2_v2 Azure instance will have CPU in offline state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879752] Re: test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210
Confirmed we see this in SRU testing: http://10.246.72.4/test- results/4.4.0-180.210-lowlatency/rizzo__4.4.0-180.210__2020-05-20_05-12-00/ubuntu_bpf_jit/results/ubuntu_bpf_jit .ubuntu-bjf-jit/debug/ubuntu_bpf_jit.ubuntu-bjf-jit.DEBUG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879752 Title: test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829989] Re: memcg_use_hierarchy from controllers test suite in LTP failed
** Tags added: sru-20200427 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829989 Title: memcg_use_hierarchy from controllers test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829983] Re: memcg_stat from controllers test suite in LTP failed
** Tags added: sru-20200427 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829983 Title: memcg_stat from controllers test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854298] Re: ubuntu_unionmount_ovlfs failed on X/T-LTS-X with latest update in upstream testsuite
** Tags added: sru-20200427 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854298 Title: ubuntu_unionmount_ovlfs failed on X/T-LTS-X with latest update in upstream testsuite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833028] Re: fanotify06 from ubuntu_ltp_syscalls failed
** Tags added: sru-20200427 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833028 Title: fanotify06 from ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1833028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels
Awaiting final results for Bionic -main respin for SRU 2020.04.27 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862588 Title: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876173] [NEW] ERROR: could not get modinfo from 'da903x when installing focal oem-5.6
Public bug reported: Series: Focal Kernel: linux-oem-5.6 (linux-oem-20.04 metapkg) Problem: During installation of the linux-oem-5.6 kernel we see the following error Processing triggers for linux-image-5.6.0-1008-oem (5.6.0-1008.8) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.6.0-1008-oem modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' To Reproduce: - Install Focal - Add ppa: sudo add-apt-repository ppa:canonical-kernel-team/unstable sudo apt-get update - Install Kernel: sudo apt install linux-oem-20.04 Full output below: Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: amd64-microcode intel-microcode iucode-tool libdbus-glib-1-2 linux-firmware linux-headers-5.6.0-1008-oem linux-headers-oem-20.04 linux-image-5.6.0-1008-oem linux-image-oem-20.04 linux-modules-5.6.0-1008-oem linux-oem-5.6-headers-5.6.0-1008 thermald Suggested packages: fdutils linux-oem-5.6-tools The following NEW packages will be installed: amd64-microcode intel-microcode iucode-tool libdbus-glib-1-2 linux-firmware linux-headers-5.6.0-1008-oem linux-headers-oem-20.04 linux-image-5.6.0-1008-oem linux-image-oem-20.04 linux-modules-5.6.0-1008-oem linux-oem-20.04 linux-oem-5.6-headers-5.6.0-1008 thermald 0 upgraded, 13 newly installed, 0 to remove and 6 not upgraded. Need to get 176 MB of archives. After this operation, 903 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 iucode-tool amd64 2.3.1-1 [45.6 kB] Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 libdbus-glib-1-2 amd64 0.110-5fakssync1 [59.1 kB] Get:3 http://archive.ubuntu.com/ubuntu focal/main amd64 linux-firmware all 1.187 [98.7 MB] Get:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-oem-5.6-headers-5.6.0-1008 all 5.6.0-1008.8 [11.1 MB] Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-5.6.0-1008-oem amd64 5.6.0-1008.8 [1194 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-oem-20.04 amd64 5.6.0.1008.8 [2588 B] Get:7 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-modules-5.6.0-1008-oem amd64 5.6.0-1008.8 [53.3 MB] Get:8 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-5.6.0-1008-oem amd64 5.6.0-1008.8 [9034 kB] Get:9 http://archive.ubuntu.com/ubuntu focal/main amd64 intel-microcode amd64 3.20191115.1ubuntu3 [2408 kB] Get:10 http://archive.ubuntu.com/ubuntu focal/main amd64 amd64-microcode amd64 3.20191218.1ubuntu1 [31.8 kB] Get:11 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-oem-20.04 amd64 5.6.0.1008.8 [2676 B] Get:12 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-oem-20.04 amd64 5.6.0.1008.8 [1876 B] Get:13 http://archive.ubuntu.com/ubuntu focal/main amd64 thermald amd64 1.9.1-1build1 [197 kB] Fetched 176 MB in 38s (4658 kB/s) Selecting previously unselected package iucode-tool. (Reading database ... 63136 files and directories currently installed.) Preparing to unpack .../00-iucode-tool_2.3.1-1_amd64.deb ... Unpacking iucode-tool (2.3.1-1) ... Selecting previously unselected package libdbus-glib-1-2:amd64. Preparing to unpack .../01-libdbus-glib-1-2_0.110-5fakssync1_amd64.deb ... Unpacking libdbus-glib-1-2:amd64 (0.110-5fakssync1) ... Selecting previously unselected package linux-firmware. Preparing to unpack .../02-linux-firmware_1.187_all.deb ... Unpacking linux-firmware (1.187) ... Selecting previously unselected package linux-oem-5.6-headers-5.6.0-1008. Preparing to unpack .../03-linux-oem-5.6-headers-5.6.0-1008_5.6.0-1008.8_all.deb ... Unpacking linux-oem-5.6-headers-5.6.0-1008 (5.6.0-1008.8) ... Selecting previously unselected package linux-headers-5.6.0-1008-oem. Preparing to unpack .../04-linux-headers-5.6.0-1008-oem_5.6.0-1008.8_amd64.deb ... Unpacking linux-headers-5.6.0-1008-oem (5.6.0-1008.8) ... Selecting previously unselected package linux-headers-oem-20.04. Preparing to unpack .../05-linux-headers-oem-20.04_5.6.0.1008.8_amd64.deb ... Unpacking linux-headers-oem-20.04 (5.6.0.1008.8) ... Selecting previously unselected package linux-modules-5.6.0-1008-oem. Preparing to unpack .../06-linux-modules-5.6.0-1008-oem_5.6.0-1008.8_amd64.deb ... Unpacking linux-modules-5.6.0-1008-oem (5.6.0-1008.8) ... Selecting previously unselected package linux-image-5.6.0-1008-oem. Preparing to unpack .../07-linux-image-5.6.0-1008-oem_5.6.0-1008.8_amd64.deb ... Unpacking linux-image-5.6.0-1008-oem (5.6.0-1008.8) ... Selecting previously unselected package intel-microcode. Preparing to unpack .../08-intel-microcode_3.20191115
