[Kernel-packages] [Bug 1864140] Re: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC
** Changed in: ubuntu-kernel-tests Status: In Progress => Confirmed ** Changed in: ubuntu-kernel-tests Assignee: Sean Feole (sfeole) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864140 Title: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Issue found on PowerPC nodes across different kernels. (It works on other arches in different MAAS server, so it looks like some network config issue) Running in the Canonical CI environment Testing Fan Networking (pre-0.13.0 API) docker pull ppc64le/ubuntu: PASSED enable disable fan test: PASSED fanctl show test: PASSED fanctl check bridge config test: PASSED fanatic docker test: FAILED: (docker run returned 100) stderr: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease Unable to connect to ports.ubuntu.com:http: W: Some index files failed to download. They have been ignored, or old ones used instead. E: Unable to locate package iputils-ping ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 21 03:32 seq crw-rw 1 root audio 116, 33 Feb 21 03:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Feb 21 03:47:15 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=faf7d4a6-6836-4496-bc64-15f33ec9e43d ro console=hvc0 ProcLoadAvg: 1.28 1.27 0.97 1/1305 17149 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-174-generic (buildd@bos02-ppc64el-008) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.12) ) #204-Ubuntu SMP Wed Jan 29 06:41:38 UTC 2020 RelatedPackageVersions: linux-restricted-modules-4.4.0-174-generic N/A linux-backports-modules-4.4.0-174-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 120) max: 3.694 GHz (cpu 37) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946486 Title: Unable to reboot ARM64 node with 5.11.0-27-realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Confirmed Bug description: It looks like this issue is affecting some ARM64 bare metal node: * helo-kernel 2 failed out of 2 attempts * kuzzle 11 failed out of 13 attempts (as far as I can recall 2 deployments failed early, the system was not deployed at all, so probably we can call it 9 failed) The boot test will fail, the system was unable to reboot with the 5.11.0-27-realtime kernel, here is the steps (integrated with the deployment script) 1. Deploy this node with Hirsute 2. Install the 5.11.0-27-realtime kernel and set to boot with this kernel by using the boot-kernel-simple in ckct. Reboot 3. System can boot with 5.11.0-27-realtime, reboot again to make sure it's OK It seem the system will stuck at the last reboot attempt in step 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946486 Title: Unable to reboot ARM64 node with 5.11.0-27-realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Confirmed Bug description: It looks like this issue is affecting some ARM64 bare metal node: * helo-kernel 2 failed out of 2 attempts * kuzzle 11 failed out of 13 attempts (as far as I can recall 2 deployments failed early, the system was not deployed at all, so probably we can call it 9 failed) The boot test will fail, the system was unable to reboot with the 5.11.0-27-realtime kernel, here is the steps (integrated with the deployment script) 1. Deploy this node with Hirsute 2. Install the 5.11.0-27-realtime kernel and set to boot with this kernel by using the boot-kernel-simple in ckct. Reboot 3. System can boot with 5.11.0-27-realtime, reboot again to make sure it's OK It seem the system will stuck at the last reboot attempt in step 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940482
Title:
[thunderx2] Synchronous external abort: 96000610 [#1] SMP
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Incomplete
Bug description:
[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
[Kernel-packages] [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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940482
Title:
[thunderx2] Synchronous external abort: 96000610 [#1] SMP
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Incomplete
Bug description:
[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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940482/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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
[Kernel-packages] [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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940482
Title:
[thunderx2] Synchronous external abort: 96000610 [#1] SMP
Status in linux package in Ubuntu:
New
Status in linux source package in Focal:
New
Bug description:
[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
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1926142 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 Status in ubuntu-kernel-tests: New Status in linux-hwe package in Ubuntu: New Status in linux-hwe-5.4 package in Ubuntu: New Status in linux-hwe source package in Bionic: New Status in linux-hwe-5.4 source package in Bionic: New Bug description: Test build on B-5.4 (5.4.0-73.82~18.04.1) failed with: error: ‘F_SEAL_FUTURE_WRITE’ undeclared Build log: $ sudo make TARGETS=memfd make --no-builtin-rules ARCH=x86 -C ../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd' gcc -D_FILE_OFFSET_BITS=64 -I../../../../include/uapi/ -I../../../../include/ -I../../../../usr/include/memfd_test.c common.o -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test memfd_test.c: In function ‘test_seal_future_write’: memfd_test.c:749:27: error: ‘F_SEAL_FUTURE_WRITE’ undeclared (first use in this function); did you mean ‘F_SEAL_WRITE’? mfd_assert_add_seals(fd, F_SEAL_FUTURE_WRITE); ^~~ F_SEAL_WRITE memfd_test.c:749:27: note: each undeclared identifier is reported only once for each function it appears in ../lib.mk:141: recipe for target '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test' failed make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test] Error 1 make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd' Makefile:143: recipe for target 'all' failed make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1926142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866591 Title: vmx_pending_event_test failed in ubuntu_kvm_unit_tests Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: Issue found on bare-metal node r5.metal, i3.metal, c5.metal timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.132aLPLaXz -smp 1 -cpu host,+vmx -append vmx_pending_event_test # -initrd /tmp/tmp.nWvh3t6ooD enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_pending_event_test FAIL: x86/vmx_tests.c:2184: Assertion failed: (expected) == (actual) LHS: 0x0012 - ''''''''''''''0001'0010 - 18 RHS: 00 - ''''''''''''''' - 0 Expected VMX_VMCALL, got VMX_EXC_NMI. STACK: 405e1c 405e46 4060e4 4061a1 401556 4039f1 400312 SUMMARY: 4 tests, 1 unexpected failures FAIL vmx_pending_event_test (4 tests, 1 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935684 Title: vmx_init_signal_test in ubuntu_kvm_unit_tests fails on bionic/linux amd64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: Issue found on node akis, with bionic/linux 4.15.0-150.155. This is not a regression as the failure can be found on previous releases. Error: filter = vmx_init_signal_test, test = vmx_init_signal_test Test suite: vmx_init_signal_test FAIL: INIT signal blocked when CPU in VMX operation filter = vmx_init_signal_test, test = vmx_sipi_signal_test Full log: Running 'kvm-ok' [stdout] INFO: /dev/kvm exists [stdout] KVM acceleration can be used Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_init_signal_test' [stdout] BUILD_HEAD=90a7d30e [stdout] timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.BwMoFCX0Fv -smp 2 -cpu max,+vmx -m 2048 -append vmx_init_signal_test # -initrd /tmp/tmp.9wCF3rz6vO [stdout] enabling apic [stdout] enabling apic [stdout] paging enabled [stdout] cr0 = 80010011 [stdout] cr3 = 107f000 [stdout] cr4 = 20 [stdout] filter = vmx_init_signal_test, test = test_vmx_feature_control [stdout] filter = vmx_init_signal_test, test = test_vmxon [stdout] filter = vmx_init_signal_test, test = test_vmptrld [stdout] filter = vmx_init_signal_test, test = test_vmclear [stdout] filter = vmx_init_signal_test, test = test_vmptrst [stdout] filter = vmx_init_signal_test, test = test_vmwrite_vmread [stdout] filter = vmx_init_signal_test, test = test_vmcs_high [stdout] filter = vmx_init_signal_test, test = test_vmcs_lifecycle [stdout] filter = vmx_init_signal_test, test = test_vmx_caps [stdout] filter = vmx_init_signal_test, test = test_vmread_flags_touch [stdout] filter = vmx_init_signal_test, test = test_vmwrite_flags_touch [stdout] filter = vmx_init_signal_test, test = null [stdout] filter = vmx_init_signal_test, test = vmenter [stdout] filter = vmx_init_signal_test, test = preemption timer [stdout] filter = vmx_init_signal_test, test = control field PAT [stdout] filter = vmx_init_signal_test, test = control field EFER [stdout] filter = vmx_init_signal_test, test = CR shadowing [stdout] filter = vmx_init_signal_test, test = I/O bitmap [stdout] filter = vmx_init_signal_test, test = instruction intercept [stdout] filter = vmx_init_signal_test, test = EPT A/D disabled [stdout] filter = vmx_init_signal_test, test = EPT A/D enabled [stdout] filter = vmx_init_signal_test, test = PML [stdout] filter = vmx_init_signal_test, test = VPID [stdout] filter = vmx_init_signal_test, test = interrupt [stdout] filter = vmx_init_signal_test, test = nmi_hlt [stdout] filter = vmx_init_signal_test, test = debug controls [stdout] filter = vmx_init_signal_test, test = MSR switch [stdout] filter = vmx_init_signal_test, test = vmmcall [stdout] filter = vmx_init_signal_test, test = disable RDTSCP [stdout] filter = vmx_init_signal_test, test = int3 [stdout] filter = vmx_init_signal_test, test = into [stdout] filter = vmx_init_signal_test, test = exit_monitor_from_l2_test [stdout] filter = vmx_init_signal_test, test = invalid_msr [stdout] filter = vmx_init_signal_test, test = v2_null_test [stdout] filter = vmx_init_signal_test, test = v2_multiple_entries_test [stdout] filter = vmx_init_signal_test, test = fixture_test_case1 [stdout] filter = vmx_init_signal_test, test = fixture_test_case2 [stdout] filter = vmx_init_signal_test, test = invvpid_test_v2 [stdout] filter = vmx_init_signal_test, test = vmx_controls_test [stdout] filter = vmx_init_signal_test, test = vmx_host_state_area_test [stdout] filter = vmx_init_signal_test, test = vmx_guest_state_area_test [stdout] filter = vmx_init_signal_test, test = vmentry_movss_shadow_test [stdout] filter = vmx_init_signal_test, test = vmentry_unrestricted_guest_test [stdout] filter = vmx_init_signal_test, test = vmx_eoi_bitmap_ioapic_scan_test [stdout] filter = vmx_init_signal_test, test = vmx_hlt_with_rvi_test [stdout] filter = vmx_init_signal_test, test = apic_reg_virt_test [stdout] filter = vmx_init_signal_test, test = virt_x2apic_mode_test [stdout] filter = vmx_init_signal_test, test = vmx_apic_passthrough_test [stdout] filter = vmx_init_signal_test, test = vmx_apic_passthrough_thread_test [stdout] filter = vmx_init_signal_test, test = vmx_apic_passthrough_tpr_threshold_test [stdout] filter = vmx_init_signal_test, test = vmx_init_signal_test
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-kvm in 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 Status in ubuntu-kernel-tests: Triaged Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Xenial: New Status in linux-kvm source package in Xenial: New Status in linux-oracle source package in Xenial: New Status in linux-azure source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux-oracle source package in Bionic: New Bug description: vmx_apicv_test from ubuntu_kvm_unit_tests failed on X-KVM: FAIL vmx_apicv_test (timeout; duration=10) the test was terminated with return code 124: # TESTNAME=vmx_apicv_test TIMEOUT=10 ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "apic_reg_virt_test virt_x2apic_mode_test" timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,+vmx -append apic_reg_virt_test virt_x2apic_mode_test # -initrd /tmp/tmp.K6b7rjmgp8 enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: apic_reg_virt_test --- Virtualize APIC accesses test --- PASS: xapic - reading 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - writing 0x12345678 to 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - reading 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - writing 0x12345678 to 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - reading 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - writing 0x12345678 to 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - reading 0x030: got APIC access exit @ page offset 0x030, want 0x030 PASS: xapic - writing 0x12345678 to 0x380: non-virtualized write; val is 0x12345678, want 0x12345678 PASS: xapic - reading 0x390: read 0x12345678, expected 0x12345678. PASS: xapic - writing 0x12345678 to 0x390: non-virtualized writqemu-system-x86_64: terminating on signal 15 from pid 1327 # echo $? 124 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1044-kvm 4.4.0-1044.50 ProcVersionSignature: Ubuntu 4.4.0-1044.50-kvm 4.4.177 Uname: Linux 4.4.0-1044-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon May 6 10:47:17 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in 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 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test fails with timeout on Bionic 4.15.0-141.145 host rizzo this failed on the previous version of bionic 4.15.0-140.144 as well, so not a regression. vmx_host_state_area has an error before giving timeout: 04/10 01:29:18 DEBUG| utils:0153| [stderr] KVM: entry failed, hardware error 0x8021 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:18 DEBUG| utils:0153| [stderr] If you're running a guest on an Intel machine without unrestricted mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] support, the failure can be most likely due to the guest entering an invalid 04/10 01:29:18 DEBUG| utils:0153| [stderr] state for Intel VT. For example, the guest maybe running in big real mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] which is not supported on less recent Intel processors. 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:47 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 21956 (timeout) 04/10 01:29:47 DEBUG| utils:0153| [stdout] FAIL vmx_host_state_area (timeout; duration=30) vmx_intr_window_test / vmx_nmi_window_test shows passing until the timeout: 28. 04/10 01:29:49 DEBUG| utils:0153| [stdout] PASS: interrupt-window: active, RFLAGS.IF = 0: Activity state (0) is 'ACTIVE' 29. 04/10 01:30:19 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22161 (timeout) 30. 04/10 01:30:19 DEBUG| utils:0153| [stdout] FAIL vmx_intr_window_test (timeout; duration=30) 31. 04/10 01:30:19 ERROR| test:0414| Exception escaping from test: -- 26. 04/10 01:30:24 DEBUG| utils:0153| [stdout] PASS: NMI-window: active, blocking by NMI: #UD handler executed once (actual 1 times) 27. 04/10 01:30:53 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22570 (timeout) 28. 04/10 01:30:53 DEBUG| utils:0153| [stdout] FAIL vmx_nmi_window_test (timeout; duration=30) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917616
Title:
vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
Status in ubuntu-kernel-tests:
Triaged
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
Appearing in bionic 5.4.0-67.75~18.04.1 affecting lowlatency and hwe
flavors.
2538. 02/25 00:10:11 DEBUG| utils:0153| [stdout] Unhandled exception 13 #GP
at ip 004071a3
2539. 02/25 00:10:11 DEBUG| utils:0153| [stdout] error_code=
rflags=00010006 cs=0008
2540. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rax=0078
rcx=0809 rdx= rbx=0009
2541. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rbp=0047efdf
rsi=0042568d rdi=0042568d
2542. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r8=000a
r9=03f8 r10=000d r11=
2543. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r12=
r13= r14=00403dcc r15=
2544. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr0=80010031
cr2=e000 cr3=00477000 cr4=2020
2545. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr8=0007
2546. 02/25 00:10:11 DEBUG| utils:0153| [stdout] STACK: @4071a3 40170b 4004dd
2547. 02/25 00:10:11 DEBUG| utils:0153| [stdout] FAIL vmx
2548. 02/25 00:10:11 ERROR| test:0414| Exception escaping from test:
2549. Traceback (most recent call last):
2550. File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
2551. _call_test_function(self.execute, *p_args, **p_dargs)
2552. File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
2553. return func(*args, **dargs)
2554. File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
2555. postprocess_profiled_run, args, dargs)
2556. File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
2557. self.run_once(*args, **dargs)
2558. File
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
line 80, in run_once
2559. raise error.TestError("Test failed for {}".format(test_name))
2560. TestError: Test failed for vmx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917616/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918692 Title: ubuntu-kvm-unit-test/vmx_apic_passthrough_thread reports assertion failure Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: Running the ubuntu_kvm_unit_test/vmx_apic_passthrough_thread subtest on rumford shows the following failure: 14. 03/03 06:44:40 DEBUG| utils:0153| [stdout] Test suite: vmx_apic_passthrough_thread_test 15. 03/03 06:44:40 DEBUG| utils:0153| [stdout] FAIL: x86/vmx_tests.c:7705: Assertion failed: (0) == ((int)ioapic_read_redir(0xf).remote_irr) 16. 03/03 06:44:40 DEBUG| utils:0153| [stdout] LHS: 00 - ''''''''''''''' - 0 17. 03/03 06:44:40 DEBUG| utils:0153| [stdout] RHS: 0x0001 - '''''''''''''''0001 - 1 18. 03/03 06:44:40 DEBUG| utils:0153| [stdout] IOAPIC pass-through: remote_irr=0 after EOI 19. 03/03 06:44:40 DEBUG| utils:0153| [stdout] STACK: 4083de 40841a 40158a 403a60 400312 20. 03/03 06:44:40 DEBUG| utils:0153| [stdout] SUMMARY: 5 tests, 1 unexpected failures This sounds like some hardware related setup issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1918692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1932966
Title:
kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
Confirmed
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-kvm source package in Bionic:
Confirmed
Bug description:
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991
RBP=0051b440 RSP=0051b420
18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8
R10=000d R11=
18:27:11 DEBUG| [stderr] R12=e000 R13=
R14=d000 R15=
18:27:11 DEBUG| [stderr] RIP=00400a0c RFL=00010006 [-P-] CPL=0
II=0 A20=1 SMM=0 HLT=0
18:27:11 DEBUG| [stderr] ES =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] CS =0008 00a09b00 DPL=0
CS64 [-RA]
18:27:11 DEBUG| [stderr] SS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] DS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] FS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] GS =0010 0051a4d0 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] LDT= 8200 DPL=0 LDT
18:27:11 DEBUG| [stderr] TR =0080 0041207a 8b00 DPL=0
TSS64-busy
18:27:11 DEBUG| [stderr] GDT= 0041100a 106f
18:27:11 DEBUG| [stderr] IDT= 0041 0fff
18:27:11 DEBUG| [stderr] CR0=80010011 CR2=
CR3=01007000 CR4=0220
18:27:11 DEBUG| [stderr] DR0= DR1=
DR2= DR3=
18:27:11 DEBUG| [stderr] DR6=0ff0 DR7=0400
18:27:11 DEBUG| [stderr] EFER=0500
18:27:11 DEBUG| [stderr] Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66
0f 6f 45 e0 <0f> 11 03 48 89 de 48 8d 7d e0 e8 f8 f9 ff ff 0f b6 f8 be a1 8f 41
00 b8 00 00 00 00 e8 05
18:28:40 DEBUG| [stderr] qemu-system-x86_64: terminating on signal 15 from
pid 13634 (timeout)
18:28:40 DEBUG| [stdout] FAIL emulator (timeout; duration=90s)
[...]
TestError: Test failed for emulator
18:28:40 ERROR| child process failed
18:28:40 DEBUG| Traceback (most recent call last):
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/parallel.py", line 25,
in fork_start
18:28:40 DEBUG| l()
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/job.py", line 505, in
18:28:40 DEBUG| l = lambda: test.runtest(self, url, tag, args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/test.py", line 125, in
runtest
18:28:40 DEBUG| job.sysinfo.log_after_each_iteration)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
913, in runtest
18:28:40 DEBUG| mytest._exec(args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
411, in _exec
18:28:40 DEBUG| _call_test_function(self.execute, *p_args, **p_dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
823, in _call_test_function
18:28:40 DEBUG| return func(*args, **dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
291, in execute
18:28:40 DEBUG| postprocess_profiled_run, args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
212, in _call_run_once
18:28:40 DEBUG| self.run_once(*args, **dargs)
18:28:40 DEBUG| File
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
line 82, in run_once
18:28:40 DEBUG| raise error.TestError("Test failed for
{}".format(test_name))
18:28:40 DEBUG| TestError: Test failed for emulator
18:28:41 INFO | ERROR ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1624040921localtime=Jun 18
18:28:41 Test failed for emulator
18:28:41 INFO | END ERROR ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1624040921localtime=Jun 18
18:28:41
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932966/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1929925
Title:
[Potential Regression] Unable to create KVM with uvtool on Groovy
ARM64
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Groovy:
Fix Committed
Bug description:
Issue found on 5.8.0-54-generic proposed ARM64 kernel with node
"helo", "wright"
This issue does not exist in 5.8.0-53.60 so this might be a
regression.
Test case:
1. Deploy Groovy on an ARM64 node
2. Create a KVM with the following command:
uvt-kvm create bjf-test release=groovy arch=arm64
Or you can run the ubuntu_kvm_smoke_test with autotest:
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
-b master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
sudo apt-get install git python-minimal -y || sudo apt install python2 -y
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E
autotest/client/autotest-local --verbose
autotest/client/tests/ubuntu_kvm_smoke_test/control
3. Install just the proposed kernel and reboot
4. Repeat step 2
This is 100% reproducible on ARM64, 4 out of 4 attempts (twice on each
nodes).
Test log:
+ SUT=bjf-test
+ SSH_KEY=/home/ubuntu/.ssh/id_rsa
+ SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
++ lsb_release -c
++ awk '{print$2}'
+ DISTRO=groovy
+ ARCHITECTURE=arm64
+ trap cleanup EXIT
+ '[' -z arm64 ']'
+ kvm-ok
+ '[' 0 '!=' 0 ']'
+ '[' '!' -f /home/ubuntu/.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: error: libvirt: unsupported configuration: Emulator
'/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'
syslog:
May 28 08:01:07 helo-kernel kernel: [ 1030.945560] mpt3sas :8d:00.0:
invalid short VPD tag 00 at offset 1
May 28 08:01:08 helo-kernel kernel: [ 1031.238058] sr 3:0:0:0: [sr0] CDROM
not ready. Make sure there is a disc in the drive.
May 28 08:01:08 helo-kernel kernel: [ 1031.242304] sr 3:0:0:0: [sr0] CDROM
not ready. Make sure there is a disc in the drive.
May 28 08:01:08 helo-kernel kernel: [ 1031.245430] sr 3:0:0:1: [sr1] CDROM
not ready. Make sure there is a disc in the drive.
May 28 08:01:08 helo-kernel kernel: [ 1031.248810] sr 3:0:0:1: [sr1] CDROM
not ready. Make sure there is a disc in the drive.
May 28 08:01:08 helo-kernel kernel: [ 1031.252678] sr 3:0:0:2: [sr2] CDROM
not ready. Make sure there is a disc in the drive.
May 28 08:01:08 helo-kernel kernel: [ 1031.255678] sr 3:0:0:2: [sr2] CDROM
not ready. Make sure there is a disc in the drive.
May 28 08:01:08 helo-kernel kernel: [ 1031.258811] sr 3:0:0:3: [sr3] CDROM
not ready. Make sure there is a disc in the drive.
May 28 08:01:08 helo-kernel kernel: [ 1031.272678] sr 3:0:0:3: [sr3] CDROM
not ready. Make sure there is a disc in the drive.
May 28
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in 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) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: Issue found on 5.8.0-1001.1 - kvm Test build failed with: Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' In file included from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:5, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/kernel.h:8, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.h:10, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:8: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c: In function ‘__func_get_name’: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:38: warning: nested extern declaration of ‘__compiletime_assert_0’ [-Wnested-externs] 37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:16:15: note: in definition of macro ‘__compiletime_assert’ 16 | extern void prefix ## suffix(void) __compiletime_error(msg); \ | ^~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:2: note: in expansion of macro ‘_compiletime_assert’ 37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:39:37: note: in expansion of macro ‘compiletime_assert’ 39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg) | ^~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:50:2: note: in expansion of macro ‘BUILD_BUG_ON_MSG’ 50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition) | ^~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:20:2: note: in expansion of macro ‘BUILD_BUG_ON’ 20 | BUILD_BUG_ON(ARRAY_SIZE(func_id_str) != __BPF_FUNC_MAX_ID); | ^~~~ libbpf: failed to open format: No such file or directory Error: failed to load BTF from format: No such file or directory make[1]: *** [Makefile:190: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h] Error 2 make[1]: *** Deleting file '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h' make: *** [Makefile:157: all] Error 2 Please find attachment for the complete build log. As the ubuntu_kernel_selftests needs bpf to be built first, this will block the ubuntu_kernel_selftests/net to build as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1894964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805806 Title: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Invalid Bug description: This issue can be found on 2 different ARM64 node, TunderX Cavium node "starmie" and Moonshot "ms10-34-mcdivittB0-kernel" Running test_maps bpf test.. Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Failed sockmap unexpected timeout ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836167 Title: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: <<>> incrementing stop Name: cpuhotplug03 Date: Thu Jul 11 08:31:48 UTC 2019 Desc: Do tasks get scheduled to a newly on-lined CPU? CPU is 1 sh: echo: I/O error cpuhotplug03 1 TBROK: CPU1 cannot be offlined USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 4642 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4643 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4644 0.0 0.0 2020 468 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4645 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4646 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4647 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4648 0.0 0.0 2020 456 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4649 0.0 0.0 2020 508 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4650 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4651 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4652 0.0 0.0 2020 484 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4653 0.0 0.0 2020 496 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4654 0.0 0.0 2020 464 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4655 0.0 0.0 2020 492 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4656 0.0 0.0 2020 448 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4657 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4661 0.0 0.0 7540 648 pts/0S08:31 0:00 grep cpuhotplug_do_spin_loop cpuhotplug03 1 TINFO: Onlining CPU 1 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found onCPU1 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=2 corefile=no cutime=1060 cstime=9 <<>> Test passed on ThunderX ARM64, probably a test case issue. Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug03 cpuhotplug03.sh -c 1 -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
[Kernel-packages] [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 Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1829995
Title:
getaddrinfo_01 from ipv6_lib test suite in LTP failed
Status in ubuntu-kernel-tests:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in linux-aws package in Ubuntu:
New
Status in linux source package in Bionic:
Incomplete
Status in linux-aws source package in Bionic:
New
Status in linux source package in Eoan:
New
Status in linux-aws source package in Eoan:
New
Bug description:
startup='Wed May 22 08:02:52 2019'
getaddrinfo_011 TPASS : getaddrinfo IPv4 basic lookup
getaddrinfo_012 TFAIL : getaddrinfo_01.c:140: getaddrinfo IPv4
canonical name ("curly.maas") doesn't match hostname ("curly")
getaddrinfo_013 TFAIL : getaddrinfo_01.c:578: getaddrinfo IPv6 basic
lookup ("curly") returns -5 ("No address associated with hostname")
tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-50-generic 4.15.0-50.54
ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 22 02:57 seq
crw-rw 1 root audio 116, 33 May 22 02:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Wed May 22 08:04:30 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
RelatedPackageVersions:
linux-restricted-modules-4.15.0-50-generic N/A
linux-backports-modules-4.15.0-50-generic N/A
linux-firmware 1.173.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias:
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829995/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Bug description: With bug 1868707 fixed, the tpci test can finish now, and it's reporting another issue here: test_pci 489 TFAIL : tpci.c:73: PCI bus 01 slot 01 : Test-case '13' Please find attachment for dmesg log and the full test log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 10:08 seq crw-rw 1 root audio 116, 33 May 13 10:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed May 13 10:19:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Triaged Status in linux-azure package in Ubuntu: Triaged Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/prev:
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1822308 Title: vmx_hlt_with_rvi_test in kvm_unit_tests fails Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_hlt_with_rvi_test' BUILD_HEAD=e2c275c4 timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.Jo9XTMTiTj -smp 1 -cpu host,+vmx -append vmx_hlt_with_rvi_test # -initrd /tmp/tmp.Y9HtqW5t9P enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_hlt_with_rvi_test qemu-system-x86_64: terminating on signal 15 from pid 24517 FAIL vmx_hlt_with_rvi_test (timeout; duration=10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904243 Title: 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Incomplete Bug description: 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 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]
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904243 Title: 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Incomplete Bug description: 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 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904243 Title: 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Incomplete Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760087 Title: net test in ubuntu_kernel_selftest failed on linux-kvm Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Steps: 1. Deploy a KVM node with Xenial, install linux-kvm on it. 2. git clone --depth 1 https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial linux 3. Run the "net" sub set in the kernel_selftest Result: * test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory * test_bpf: [FAIL] * selftests: test_bpf.sh [FAIL] Output: $ sudo make -C linux/tools/testing/selftests/net all run_tests make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make: Nothing to be done for 'all'. running socket test [PASS] selftests: run_netsocktests [PASS] running psock_fanout test test: control single socket test: control multiple sockets test: datapath 0x0 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,5, expect=20,5 test: datapath 0x1000 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,15, expect=20,15 test: datapath 0x1 info: count=0,0, expect=0,0 info: count=10,10, expect=10,10 info: count=18,17, expect=18,17 test: datapath 0x3 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,15, expect=20,15 test: datapath 0x6 info: count=0,0, expect=0,0 info: count=5,15, expect=15,5 info: count=20,15, expect=15,20 test: datapath 0x7 bpf: Function not implemented bpf verifier: ���ߟ [FAIL] running psock_tpacket test test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory [FAIL] selftests: run_afpackettests [PASS] test_bpf: [FAIL] selftests: test_bpf.sh [FAIL] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 30 12:12:46 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1760087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896725 Title: xenial 4.4.0-191-generic in -proposed has a regression Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: [Impact] The new xenial kernel in -proposed, 4.4.0-191-generic, and its derivatives, such as 4.4.0-1115-aws suffer a kernel panic on boot on AWS. I tested t2.micro and t2.medium, it happens every time. Simply install the kernel from -proposed and reboot, we get the following oops: [0.549557] BUG: unable to handle kernel paging request at ff5f3000 [0.552000] IP: [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] PGD 1e0f067 PUD 1e11067 PMD 1e12067 PTE 0 [0.552000] Oops: 0002 [#1] SMP [0.552000] Modules linked in: [0.552000] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-191-generic #221-Ubuntu [0.552000] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [0.552000] task: 88010a0f ti: 88010a0f8000 task.ti: 88010a0f8000 [0.552000] RIP: 0010:[] [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] RSP: :88010a0fbc48 EFLAGS: 00010086 [0.552000] RAX: 0086 RBX: 88010a1df480 RCX: [0.552000] RDX: ff5f3000 RSI: 0001 RDI: 0020c000 [0.552000] RBP: 88010a0fbc50 R08: 81ebdfd0 R09: [0.552000] R10: 0011 R11: 0009 R12: 88010ad95400 [0.552000] R13: 0001 R14: 0009 R15: 88010a1fc480 [0.552000] FS: () GS:88010b24() knlGS: [0.552000] CS: 0010 DS: ES: CR0: 80050033 [0.552000] CR2: ff5f3000 CR3: 01e0a000 CR4: 00160670 [0.552000] DR0: DR1: DR2: [0.552000] DR3: DR6: fffe0ff0 DR7: 0400 [0.552000] Stack: [0.552000] 88010ac0ba58 88010a0fbc70 810ea644 88010ac0ba00 [0.552000] 88010ac0ba58 88010a0fbca0 810e6d88 810e1009 [0.552000] 88010ac0ba00 88010ac0baa0 88010a1fc480 88010a0fbd38 [0.552000] Call Trace: [0.552000] [] irq_domain_activate_irq+0x44/0x50 [0.552000] [] irq_startup+0x38/0x90 [0.552000] [] ? vprintk_default+0x29/0x40 [0.552000] [] __setup_irq+0x5a2/0x650 [0.552000] [] ? kmem_cache_alloc_trace+0x1d4/0x1f0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] request_threaded_irq+0xfb/0x1a0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] ? acpi_ev_sci_dispatch+0x64/0x64 [0.552000] [] acpi_os_install_interrupt_handler+0xaa/0x100 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] acpi_ev_install_sci_handler+0x23/0x25 [0.552000] [] acpi_ev_install_xrupt_handlers+0x1c/0x6c [0.552000] [] acpi_enable_subsystem+0x8f/0x93 [0.552000] [] acpi_init+0x8b/0x2c4 [0.552000] [] ? kasprintf+0x4e/0x70 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] do_one_initcall+0xb5/0x200 [0.552000] [] ? parse_args+0x29a/0x4a0 [0.552000] [] kernel_init_freeable+0x177/0x218 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] [] kernel_init+0xe/0xe0 [0.552000] [] ret_from_fork+0x55/0x80 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] Code: 8d 1c d2 8d ba 0b 02 00 00 44 8d 51 11 42 8b 14 dd 74 ec 10 82 c1 e7 0c 48 63 ff 81 e2 ff 0f 00 00 48 81 ea 00 10 80 00 48 29 fa <44> 89 12 89 72 10 42 8b 14 dd 74 ec 10 82 83 c1 10 81 e2 ff 0f [0.552000] RIP [] mp_irqdomain_activate+0x5f/0xa0 [0.996006] RSP [0.996006] CR2: ff5f3000 [0.996006] ---[ end trace 1d0c3bd610d641a0 ]--- [1.012018] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856163 Title: test_maps test from ubuntu_bpf will cause OOM on Eoan s390x LPAR Status in ubuntu-kernel-tests: Won't Fix Status in Ubuntu on IBM z Systems: Invalid Status in linux package in Ubuntu: Won't Fix Status in linux source package in Eoan: Won't Fix Bug description: This issue can be reproduced with 5.3.0-24, so this is not a regression in this cycle. Reproduce rate: 3/3 On the s390x LPAR (s2lp4), the test_maps test from ubuntu_bpf will cause OOM and the following tests will be aborted. [ 591.755446] test_maps invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 [ 591.755451] CPU: 1 PID: 19054 Comm: test_maps Tainted: PW O 5.3.0-25-generic #27-Ubuntu [ 591.755452] Hardware name: IBM 2964 N63 400 (LPAR) [ 591.755453] Call Trace: [ 591.755460] ([<00023d11b98e>] show_stack+0x8e/0xd0) [ 591.755464] [<00023d995f6a>] dump_stack+0x8a/0xb8 [ 591.755469] [<00023d30e082>] dump_header+0x62/0x250 [ 591.755470] [<00023d30d152>] oom_kill_process+0x172/0x178 [ 591.755472] [<00023d30d322>] out_of_memory.part.0+0x1ca/0x4e0 [ 591.755473] [<00023d30df1e>] out_of_memory+0x6e/0xf8 [ 591.755477] [<00023d36af02>] __alloc_pages_slowpath+0xda2/0xeb0 [ 591.755478] [<00023d36b2b6>] __alloc_pages_nodemask+0x2a6/0x318 [ 591.755481] [<00023d387d6c>] alloc_pages_vma+0x104/0x1d8 [ 591.755482] [<00023d372ca4>] __read_swap_cache_async+0x18c/0x268 [ 591.755483] [<00023d372daa>] read_swap_cache_async+0x2a/0x60 [ 591.755485] [<00023d37300c>] swap_cluster_readahead+0x22c/0x2e8 [ 591.755486] [<00023d3734f8>] swapin_readahead+0x2d0/0x408 [ 591.755488] [<00023d34a14c>] do_swap_page+0x1f4/0x880 [ 591.755489] [<00023d34bf2c>] __handle_mm_fault+0x7f4/0x910 [ 591.755491] [<00023d34c10e>] handle_mm_fault+0xc6/0x1a0 [ 591.755492] [<00023d12c2bc>] do_exception+0x12c/0x3e0 [ 591.755494] [<00023d12d122>] do_dat_exception+0x2a/0x58 [ 591.755497] [<00023d9b67f0>] pgm_check_handler+0x1cc/0x220 [ 591.755497] Mem-Info: [ 591.755501] active_anon:0 inactive_anon:33 isolated_anon:6 active_file:59 inactive_file:93 isolated_file:3 unevictable:6786 dirty:0 writeback:2 unstable:0 slab_reclaimable:27072 slab_unreclaimable:44918 mapped:3670 shmem:0 pagetables:12555 bounce:0 free:19327 free_pcp:356 free_cma:0 [ 591.755505] Node 0 active_anon:0kB inactive_anon:132kB active_file:236kB inactive_file:372kB unevictable:27144kB isolated(anon):24kB isolated(file):12kB mapped:14680kB dirty:0kB writeback:8kB shmem:0kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no [ 591.755505] Node 0 DMA free:57800kB min:2876kB low:4944kB high:7012kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:2097152kB managed:2097056kB mlocked:0kB kernel_stack:496kB pagetables:4964kB bounce:0kB free_pcp:620kB local_pcp:248kB free_cma:0kB [ 591.755509] lowmem_reserve[]: 0 13806 13806 [ 591.755511] Node 0 Normal free:19508kB min:19648kB low:33784kB high:47920kB active_anon:0kB inactive_anon:132kB active_file:0kB inactive_file:576kB unevictable:27144kB writepending:8kB present:14680064kB managed:14141200kB mlocked:27144kB kernel_stack:25040kB pagetables:45256kB bounce:0kB free_pcp:804kB local_pcp:120kB free_cma:0kB [ 591.755515] lowmem_reserve[]: 0 0 0 [ 591.755516] Node 0 DMA: 1*4kB (M) 5*8kB (UME) 6*16kB (UME) 2*32kB (M) 4*64kB (UME) 4*128kB (ME) 5*256kB (UME) 4*512kB (ME) 52*1024kB (UM) = 57548kB [ 591.755525] Node 0 Normal: 244*4kB (UME) 198*8kB (UMEH) 94*16kB (UMEH) 149*32kB (MEH) 31*64kB (UME) 10*128kB (UMEH) 2*256kB (MH) 2*512kB (MH) 5*1024kB (UM) = 18752kB [ 591.755534] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1024kB [ 591.755535] 3724 total pagecache pages [ 591.755536] 74 pages in swap cache [ 591.755537] Swap cache stats: add 98390, delete 98316, find 11531/42289 [ 591.755538] Free swap = 935816kB [ 591.755538] Total swap = 1001096kB [ 591.755539] 4194304 pages RAM [ 591.755540] 0 pages HighMem/MovableOnly [ 591.755540] 134740 pages reserved [ 591.755541] 0 pages cma reserved [ 591.755542] Unreclaimable slab info: [ 591.755542] Name
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-signed-oracle in 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 Status in ubuntu-kernel-tests: New Status in linux-signed-oracle package in Ubuntu: New Bug description: This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test' BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.h2DFw8L0AF enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_nm_test client_loop: send disconnect: Broken pipe (node disconnected here) Before the test started, this can be found in syslog: Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. After that, noting was printed and node disconnected. If you try to run this case manually, it will stop at: # ./vmx_nm_test BUILD_HEAD=4671e4ba ready!!! timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM enabling ap (stopped here, even the "enabling apic" string was not printed) It looks like this is a new test case added since the cycle of 4.15.0-1037.41~16.04.1-oracle [1] https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1867623/comments/2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1 ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18 Uname: Linux 4.15.0-1031-oracle x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Apr 13 05:18:03 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Bug description: With bug 1868707 fixed, the tpci test can finish now, and it's reporting another issue here: test_pci 489 TFAIL : tpci.c:73: PCI bus 01 slot 01 : Test-case '13' Please find attachment for dmesg log and the full test log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 10:08 seq crw-rw 1 root audio 116, 33 May 13 10:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed May 13 10:19:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1837543 Title: crypto_user02 in crypto from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: Confirmed Bug description: This is a new test, test will fail with: <<>> tag=crypto_user02 stime=1563881396 cmdline="crypto_user02" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s crypto_user02.c:59: INFO: Starting crypto_user larval deletion test. May crash buggy kernels. crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Nothing interesting in syslog: Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu. Jul 23 11:29:56 amaura kernel: [ 619.646330] LTP: starting crypto_user02 Jul 23 11:30:23 amaura kernel: [ 646.554403] cfg80211: Loading compiled-in X.509 certificates for regulatory database Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "crypto_user02 crypto_user02" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 23 11:19 seq crw-rw 1 root audio 116, 33 Jul 23 11:19 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 23 11:30:15 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1837543 Title: crypto_user02 in crypto from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: Confirmed Bug description: This is a new test, test will fail with: <<>> tag=crypto_user02 stime=1563881396 cmdline="crypto_user02" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s crypto_user02.c:59: INFO: Starting crypto_user larval deletion test. May crash buggy kernels. crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Nothing interesting in syslog: Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu. Jul 23 11:29:56 amaura kernel: [ 619.646330] LTP: starting crypto_user02 Jul 23 11:30:23 amaura kernel: [ 646.554403] cfg80211: Loading compiled-in X.509 certificates for regulatory database Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "crypto_user02 crypto_user02" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 23 11:19 seq crw-rw 1 root audio 116, 33 Jul 23 11:19 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 23 11:30:15 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834006 Title: cpuset_hotplug from controllers in ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Bug description: Issue found on node amaura: <<>> tag=cpuset_hotplug stime=1561372131 cmdline="cpuset_hotplug_test.sh" contacts="" analysis=exit <<>> incrementing stop cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, Expect: 0-7). cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded. <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=19 cstime=81 <<>> Test script: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 24 10:25 seq crw-rw 1 root audio 116, 33 Jun 24 10:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jun 24 10:30:59 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Triaged Status in linux-azure package in Ubuntu: Triaged Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current:
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1812620 Title: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Disco: Won't Fix Status in linux-aws source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-azure source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Bug description: == SRU Justification [ FOCAL ] == The msg_zerocopy.sh kernel self test will fail on machines that don't have 2 or 3 CPUs such as 1 CPU cloud instances since the C test program tries to set CPU affinity to CPUs 2 and 3 and bails out if it fails. == Fix == Upstream linux-next commit commit 16f6458f2478b55e2b628797bc81a4455045c74e Author: Willem de Bruijn Date: Wed Aug 5 04:40:45 2020 -0400 selftests/net: relax cpu affinity requirement in msg_zerocopy test The fix now just emits a warning that CPU affinity can't be set rather than cause an exit(1) termination. == Test cast == Run the msg_zerocopy.sh test from the kernel net selftest on a 1 CPU system. Without the fix the test fails. With the fix it runs successfully as expected. == Regression Potential == The original test pinned the CPUs for a benchmarking metric, for our testing we are using this to test to see if the operations in the test work successfully. There is a potential that users using this test will not notice the warning if they are using this test as a benchmark on a 1 CPU system and may get more jittery timing in their benchmarks rather than a test failing and complaining they are not running it on a suitable multi-CPU system. However, the likelyhood of a user using this test on a single CPU system for benchmarking is small and as it stands the test will now run and produce potentially jittery benchmarks on a 1 CPU system compared to previously where it never ran. This test will return 1 $ sudo ./msg_zerocopy.sh ipv4 tcp -t 1 ./msg_zerocopy: setaffinity 2 ./msg_zerocopy: setaffinity 3 $ echo $? 1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 21 07:41 seq crw-rw 1 root audio 116, 33 Jan 21 07:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 21 07:50:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853610 Title: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Series: E Problem: commands test in ubuntu_ltp fails on E, test cases listed below: * mkfs01_ext3_sh * mkfs01_ext4_sh * nm01_sh startup='Fri Dec 6 02:30:45 2019' mkfs01 1 TINFO: timeout per run is 0h 5m 0s tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2' mkfs01 1 TPASS: 'mkfs -t ext3 /dev/loop2 ' passed. mkfs01 2 TFAIL: 'mkfs -t ext3 /dev/loop2 16000' failed, not expected. mkfs01 3 TPASS: 'mkfs -t ext3 -c /dev/loop2 ' passed. mkfs01 4 TPASS: 'mkfs -V ' passed. mkfs01 5 TPASS: 'mkfs -h ' passed. mkfs01 6 TINFO: AppArmor enabled, this may affect test results mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) mkfs01 6 TINFO: loaded AppArmor profiles: none Summary: passed 4 failed 1 skipped 0 warnings 0 tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 cs=12 tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 cs=12 startup='Fri Dec 6 02:30:52 2019' mkfs01 1 TINFO: timeout per run is 0h 5m 0s tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2' mkfs01 1 TPASS: 'mkfs -t ext4 /dev/loop2 ' passed. mkfs01 2 TFAIL: 'mkfs -t ext4 /dev/loop2 16000' failed, not expected. mkfs01 3 TPASS: 'mkfs -t ext4 -c /dev/loop2 ' passed. mkfs01 4 TPASS: 'mkfs -V ' passed. mkfs01 5 TPASS: 'mkfs -h ' passed. mkfs01 6 TINFO: AppArmor enabled, this may affect test results mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) mkfs01 6 TINFO: loaded AppArmor profiles: none Summary: passed 4 failed 1 skipped 0 warnings 0 tag=mkfs01_ext4_sh stime=1575599452 dur=2 exit=exited stat=1 core=no cu=4 cs=1 startup='Fri Dec 6 02:28:44 2019' nm01 1 TINFO: timeout per run is 0h 5m 0s nm01 1 TPASS: nm -f posix -A lib.a > nm.out passed as expected nm01 1 TPASS: Got correct listing nm01 1 TPASS: nm -f posix -A dir/lib.a > nm.out passed as expected nm01 1 TPASS: Got correct listing nm01 2 TPASS: nm -f posix -g /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 2 TPASS: Got only external symbols with -g nm01 3 TPASS: nm -f posix -t o /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 3 TPASS: Got an octal symbol values with -f nm01 4 TPASS: nm -f sysv /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 4 TPASS: Got SysV format with -f sysv nm01 5 TPASS: nm -f bsd /opt/ltp/testcases/data/nm01/f1 > nm_bsd.out passed as expected nm01 5 TPASS: nm -f posix /opt/ltp/testcases/data/nm01/f1 > nm_posix.out passed as expected nm01 5 TFAIL: Got wrong format with -f bsd 3dc8 d _DYNAMIC 3fb8 d _GLOBAL_OFFSET_TABLE_
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 06:50:45 2019' cpuacct 1 TINFO: timeout per run is 0h 5m 0s cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: /opt/ltp/testcases/bin/cpuacct.sh: Cannot fork tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 cs=53 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 06:59:27 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: With bug 1868707 fixed, the tpci test can finish now, and it's reporting another issue here: test_pci 489 TFAIL : tpci.c:73: PCI bus 01 slot 01 : Test-case '13' Please find attachment for dmesg log and the full test log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 10:08 seq crw-rw 1 root audio 116, 33 May 13 10:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed May 13 10:19:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829849
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1812620 Title: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Disco: Won't Fix Status in linux-aws source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Eoan: New Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Bug description: This test will return 1 $ sudo ./msg_zerocopy.sh ipv4 tcp -t 1 ./msg_zerocopy: setaffinity 2 ./msg_zerocopy: setaffinity 3 $ echo $? 1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 21 07:41 seq crw-rw 1 root audio 116, 33 Jan 21 07:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 21 07:50:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1774959 Title: clock test in monotonic_time will fail on Azure Instances Status in ubuntu-kernel-tests: Invalid Status in linux-azure package in Ubuntu: Invalid Bug description: Among all of the Azure node, this test only failed on these two nodes: Seen on the following instances: Basic_A2 Standard_D2_v3 Standard_D2s_v3 Standard_E4s_v3 Standard_E64-16s Standard_F2s_v2 Steps to reproduce: 1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 2. make -C autotest-client-tests/monotonic_time/src 3. sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc Results: $ sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc Running 'make ' cc -O -std=gnu99 -Wall -c -o time_test.o time_test.c cc -O -std=gnu99 -Wall -c -o cpuset.o cpuset.c cc -O -std=gnu99 -Wall -c -o threads.o threads.c cc -O -std=gnu99 -Wall -c -o logging.o logging.c cc -o time_test time_test.o cpuset.o threads.o logging.o -lpthread -lrt Running '/home/azure/autotest/client/tmp/monotonic_time/src/time_test --duration 300 clock' Time test command exit status: 1 Exception escaping from test: Traceback (most recent call last): File "/home/azure/autotest/client/shared/test.py", line 411, in _exec_call_test_function(self.execute, *p_args, **p_dargs) File "/home/azure/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/azure/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/azure/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/azure/autotest/client/tests/monotonic_time/monotonic_time.py", line 53, in run_once raise error.TestFail(line) TestFail: FAIL: clock-worst-warp=-100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774959/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1781902 Title: memory hotplug test stuck on Azure BasicA1 node with X-HWE azure kernel Status in ubuntu-kernel-tests: Invalid Status in linux-signed-azure package in Ubuntu: Invalid Bug description: The memory hotplug test stuck on Azure Basic A1 node, with kernel 4.15.0-1017-azure #17~16.04.1-Ubuntu Running 'sudo make -C linux/tools/testing/selftests/memory-hotplug all run_tests' make: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memory-hotplug' make: Nothing to be done for 'all'. ./mem-on-off-test.sh -r 2 || echo "selftests: memory-hotplug [FAIL]" Test scope: 2% hotplug memory online all hot-pluggable memory in offline state: SKIPPED - no hot-pluggable memory in offline state offline 2% hot-pluggable memory in online state trying to offline 1 out of 1 memory block(s): online->offline memory39 Some traces could be found in dmesg: [ 605.156847] INFO: task kworker/0:0:3 blocked for more than 120 seconds. [ 605.165522] Not tainted 4.15.0-1017-azure #17~16.04.1-Ubuntu [ 605.171822] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 605.182439] kworker/0:0 D0 3 2 0x8000 [ 605.182450] Workqueue: cgroup_destroy css_free_work_fn [ 605.182452] Call Trace: [ 605.182460] __schedule+0x3d6/0x8b0 [ 605.182464] ? enqueue_entity+0x112/0x670 [ 605.182467] schedule+0x36/0x80 [ 605.182470] rwsem_down_read_failed+0x10a/0x170 [ 605.182473] call_rwsem_down_read_failed+0x18/0x30 [ 605.182474] ? call_rwsem_down_read_failed+0x18/0x30 [ 605.182477] __percpu_down_read+0x54/0x80 [ 605.182481] get_online_mems+0x32/0x40 [ 605.182485] memcg_destroy_kmem_caches+0x14/0x90 [ 605.182488] mem_cgroup_css_free+0x144/0x180 [ 605.182491] css_free_work_fn+0x4c/0x370 [ 605.182494] process_one_work+0x14d/0x410 [ 605.182495] worker_thread+0x4b/0x460 [ 605.182499] kthread+0x105/0x140 [ 605.182500] ? process_one_work+0x410/0x410 [ 605.182503] ? kthread_associate_blkcg+0xa0/0xa0 [ 605.182504] ret_from_fork+0x35/0x40 [ 725.984133] INFO: task kworker/0:0:3 blocked for more than 120 seconds. [ 725.996091] Not tainted 4.15.0-1017-azure #17~16.04.1-Ubuntu [ 726.012768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.030221] kworker/0:0 D0 3 2 0x8000 [ 726.030232] Workqueue: cgroup_destroy css_free_work_fn [ 726.030234] Call Trace: [ 726.030242] __schedule+0x3d6/0x8b0 [ 726.030246] ? enqueue_entity+0x112/0x670 [ 726.030249] schedule+0x36/0x80 [ 726.030252] rwsem_down_read_failed+0x10a/0x170 [ 726.030255] call_rwsem_down_read_failed+0x18/0x30 [ 726.030256] ? call_rwsem_down_read_failed+0x18/0x30 [ 726.030259] __percpu_down_read+0x54/0x80 [ 726.030264] get_online_mems+0x32/0x40 [ 726.030268] memcg_destroy_kmem_caches+0x14/0x90 [ 726.030271] mem_cgroup_css_free+0x144/0x180 [ 726.030273] css_free_work_fn+0x4c/0x370 [ 726.030276] process_one_work+0x14d/0x410 [ 726.030278] worker_thread+0x4b/0x460 [ 726.030281] kthread+0x105/0x140 [ 726.030283] ? process_one_work+0x410/0x410 [ 726.030285] ? kthread_associate_blkcg+0xa0/0xa0 [ 726.030287] ret_from_fork+0x35/0x40 [ 846.820680] INFO: task kworker/0:0:3 blocked for more than 120 seconds. [ 846.831583] Not tainted 4.15.0-1017-azure #17~16.04.1-Ubuntu [ 846.842013] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 846.851811] kworker/0:0 D0 3 2 0x8000 [ 846.851822] Workqueue: cgroup_destroy css_free_work_fn [ 846.851823] Call Trace: [ 846.851831] __schedule+0x3d6/0x8b0 [ 846.851835] ? enqueue_entity+0x112/0x670 [ 846.851838] schedule+0x36/0x80 [ 846.851841] rwsem_down_read_failed+0x10a/0x170 [ 846.851844] call_rwsem_down_read_failed+0x18/0x30 [ 846.851845] ? call_rwsem_down_read_failed+0x18/0x30 [ 846.851848] __percpu_down_read+0x54/0x80 [ 846.851852] get_online_mems+0x32/0x40 [ 846.851856] memcg_destroy_kmem_caches+0x14/0x90 [ 846.851859] mem_cgroup_css_free+0x144/0x180 [ 846.851862] css_free_work_fn+0x4c/0x370 [ 846.851865] process_one_work+0x14d/0x410 [ 846.851867] worker_thread+0x4b/0x460 [ 846.851870] kthread+0x105/0x140 [ 846.851872] ? process_one_work+0x410/0x410 [ 846.851874]
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765653 Title: directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and Bionic ThunderX ARM64 Status in eCryptfs: Invalid Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Invalid Bug description: This directory-concurrent.sh.ext4 test will fail with 4.13 and 4.15 kernel on a ThunderX ARM64 node (passed on the other Moonshot node): Steps: 1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next 2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest 3. rm -fr autotest/client/tests 4. ln -sf ~/autotest-client-tests autotest/client/tests 5. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_ecryptfs/control Output: Running 'tests/run_one.sh -K -t directory-concurrent.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f ext4' Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1684788 Title: extend-file-random.sh.btrfs from ubuntu_ecryptfs test-suite failed on X-hwe Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This test has failed on both amd64, i386 and arm64 X-hwe kernel 04/15 05:13:07 DEBUG| utils:0116| Running 'apt-get install --yes --force-yes build-essential libglib2.0-dev intltool keyutils libkeyutils-dev libpam0g-dev libnss3-dev libtool acl xfsprogs btrfs-tools libattr1-dev gcc-multilib' 04/15 05:13:07 DEBUG| utils:0153| [stdout] Reading package lists... 04/15 05:13:07 DEBUG| utils:0153| [stdout] Building dependency tree... 04/15 05:13:07 DEBUG| utils:0153| [stdout] Reading state information... 04/15 05:13:08 DEBUG| utils:0153| [stdout] acl is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] build-essential is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] gcc-multilib is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] intltool is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] keyutils is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libattr1-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libkeyutils-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libtool is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] xfsprogs is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] btrfs-tools is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libglib2.0-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libnss3-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libpam0g-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 04/15 05:13:08 DEBUG| utils:0116| Running 'which gcc' 04/15 05:13:08 DEBUG| utils:0153| [stdout] /usr/bin/gcc 04/15 05:13:08 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' 04/15 05:13:21 ERROR| utils:0153| [stderr] size should be > 0 04/15 05:13:22 DEBUG| utils:0153| [stdout] extend-file-random FAIL 04/15 05:13:22 DEBUG| utils:0153| [stdout] 04/15 05:13:22 DEBUG| utils:0153| [stdout] Test Summary: 04/15 05:13:22 DEBUG| utils:0153| [stdout] 0 passed 04/15 05:13:22 DEBUG| utils:0153| [stdout] 1 failed 04/15 05:13:22 ERROR| test:0414| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_ecryptfs/ubuntu_ecryptfs.py", line 45, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: tests/run_one.sh -K -t extend-file-random.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs Exit status: 1 Duration: 14.147703886 stdout: extend-file-random FAIL Test Summary: 0 passed 1 failed stderr: size should be > 0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-74-generic 4.4.0-74.95~14.04.1 ProcVersionSignature: User Name
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765653 Title: directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and Bionic ThunderX ARM64 Status in eCryptfs: Triaged Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Invalid Bug description: This directory-concurrent.sh.ext4 test will fail with 4.13 and 4.15 kernel on a ThunderX ARM64 node (passed on the other Moonshot node): Steps: 1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next 2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest 3. rm -fr autotest/client/tests 4. ln -sf ~/autotest-client-tests autotest/client/tests 5. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_ecryptfs/control Output: Running 'tests/run_one.sh -K -t directory-concurrent.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f ext4' Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749427 Title: Unable to create KVM with uvtool on arm64 system Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Bug description: Not sure if this is related to bug 1452016, or just a HW issue: With the uvt-kvm create command on this Artful system, it returns: uvt-kvm: error: libvirt: unsupported configuration: ACPI requires UEFI on this architecture With the same command running on a Xenail system + Artful kernel, it returns: qemu-system-aarch64: Cirrus VGA not available ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 14 11:01 seq crw-rw 1 root audio 116, 33 Feb 14 11:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Feb 14 11:09:44 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1749427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739560 Title: Trusty arm64 system will hang on libhugetlbfs shmoverride_linked test Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Bug description: Steps: 1. Deploy an ARM64 system with Trusty 2. Install necessary packages 3. git clone --depth=1 -b next https://github.com/libhugetlbfs/libhugetlbfs.git 4. make BUILDTYPE=NATIVEONLY 5. execute the run_test.py in tests directory Results: * you will see it stuck at shmoverride_linked test, no output for this test in syslog truncate_reserve_wraparound (2M: 64): PASS truncate_sigbus_versus_oom (2M: 64): PASS get_huge_pages (2M: 64): PASS shmoverride_linked (2M: 64): This issue can be reproduced in 3.13.0-137 and 3.13.0-138 in proposed. As we didn't run any regression-test on this node between 3.13.0-135 ~ 3.13.0-136 (this node was broken). This test cannot be built on ARM64 before (till 3.13.0-133, we have changed to use the upstream repo since then) therefore I think this can be considered as not a regression. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-137-generic 3.13.0-137.186 ProcVersionSignature: User Name 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic aarch64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865965 Title: kill11 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: startup='Tue Mar 3 15:46:25 2020' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s kill11.c:97: PASS: signal SIGHUP kill11.c:97: PASS: signal SIGINT kill11.c:97: PASS: signal SIGQUIT dumped core kill11.c:97: PASS: signal SIGILL dumped core kill11.c:97: PASS: signal SIGTRAP dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGBUS dumped core kill11.c:97: PASS: signal SIGFPE dumped core kill11.c:97: PASS: signal SIGKILL kill11.c:97: PASS: signal SIGUSR1 kill11.c:97: PASS: signal SIGSEGV dumped core kill11.c:97: PASS: signal SIGUSR2 kill11.c:97: PASS: signal SIGPIPE kill11.c:97: PASS: signal SIGALRM kill11.c:97: PASS: signal SIGTERM kill11.c:97: PASS: signal SIGSTKFLT kill11.c:97: PASS: signal SIGXCPU dumped core Test timeouted, sending SIGKILL! tst_test.c:1269: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1270: BROK: Test killed! (timeout?) Summary: passed 18 failed 0 skipped 0 warnings 0 tag=kill11 stime=1583250385 dur=302 exit=exited stat=2 core=no cu=0 cs=0 Need to see if bump the timeout threshold can help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848429 Title: generic/527 from ubuntu_xfstests_btrfs failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: Issue found on node amd64 node "kili" generic/527- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad) --- tests/generic/527.out 2019-10-16 10:51:13.160701040 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad 2019-10-16 12:22:10.315449210 + @@ -1,4 +1,9 @@ QA output created by 527 -File fname1 data after power failure: bar -File fname2 data after power failure: foo -File fname3 data after power failure: foo +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) system call failed: File exists. +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such file or directory +File fname1 data after power failure: ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad' to see the entire diff) $ diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad --- /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out 2019-10-16 10:51:13.160701040 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad 2019-10-16 12:22:10.315449210 + @@ -1,4 +1,9 @@ QA output created by 527 -File fname1 data after power failure: bar -File fname2 data after power failure: foo -File fname3 data after power failure: foo +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) system call failed: File exists. +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such file or directory +File fname1 data after power failure: +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname2: No such file or directory +File fname2 data after power failure: +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname3: No such file or directory +File fname3 data after power failure: +umount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: not mounted. Syslog: Oct 16 12:22:09 kili ubuntu: run xfstest generic/527 Oct 16 12:22:09 kili kernel: [ 6068.948341] run fstests generic/527 at 2019-10-16 12:22:09 Oct 16 12:22:09 kili kernel: [ 6069.125238] BTRFS info (device sdb1): disk space caching is enabled Oct 16 12:22:09 kili kernel: [ 6069.125240] BTRFS info (device sdb1): has skinny extents Oct 16 12:22:09 kili kernel: [ 6069.132427] BTRFS info (device sdb1): enabling ssd optimizations Oct 16 12:22:09 kili kernel: [ 6069.246264] BTRFS: device fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 transid 5 /dev/sdb2 Oct 16 12:22:09 kili multipathd[1484]: dm-0: remove map (uevent) Oct 16 12:22:09 kili kernel: [ 6069.353749] BTRFS info (device dm-0): disk space caching is enabled Oct 16 12:22:09 kili kernel: [ 6069.353751] BTRFS info (device dm-0): has skinny extents Oct 16 12:22:09 kili kernel: [ 6069.353752] BTRFS info (device dm-0): flagging fs with big metadata feature Oct 16 12:22:09 kili kernel: [ 6069.358172] BTRFS info (device dm-0): enabling ssd optimizations Oct 16 12:22:09 kili kernel: [ 6069.359885] BTRFS info (device dm-0): checking UUID tree Oct 16 12:22:09 kili kernel: [ 6069.677202] BTRFS info (device dm-0): device fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved old:/dev/mapper/flakey-test new:/dev/dm-0 Oct 16 12:22:09 kili kernel: [ 6069.677914] BTRFS info (device dm-0): device fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved old:/dev/dm-0 new:/dev/mapper/flakey-test Oct 16 12:22:09 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 12:22:09 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 12:22:10 kili kernel: [ 6069.781083] BTRFS info (device dm-0): disk space caching is enabled Oct 16 12:22:10 kili kernel: [ 6069.781085] BTRFS info (device dm-0): has
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848439 Title: generic/562 from ubuntu_xfstests_btrfs failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: Issue found on node amd64 node "kili" generic/562_check_dmesg: something found in dmesg (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.dmesg) - output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad) --- tests/generic/562.out 2019-10-16 10:51:13.164700997 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad 2019-10-16 12:35:45.694630398 + @@ -1,5 +1,102404 @@ QA output created by 562 +XFS_IOC_CLONE: No space left on device File foo data after cloning and remount: -000 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 +000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +* +0004096 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/562.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad' to see the entire diff) Syslog with kernel traces: BTRFS info (device sdb2): checking UUID tree [ cut here ] BTRFS: Transaction aborted (error -28) WARNING: CPU: 52 PID: 53560 at fs/btrfs/ioctl.c:3350 clone_finish_inode_update+0x102/0x130 [btrfs] Modules linked in: dm_thin_pool dm_persistent_data dm_bio_prison dm_snapshot dm_bufio btrfs zstd_compress dm_flakey dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ioatdma irqbypass mei_me mei ipmi_si crct10dif_pclmul crc32_pclmul ghash_clmulni_intel joydev input_leds ipmi_devintf intel_cstate ipmi_msghandler intel_rapl_perf mac_hid acpi_pad acpi_power_meter sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid aesni_intel mgag200 aes_x86_64 crypto_simd i2c_algo_bit cryptd ttm glue_helper drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ixgbe ahci lpc_ich xfrm_algo i2c_i801 libahci dca mdio wmi [last unloaded: scsi_debug] CPU: 52 PID: 53560 Comm: xfs_io Tainted: G I 5.0.0-31-generic #33-Ubuntu Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS SE5C610.86B.01.01.1008.031920151331 03/19/2015 RIP: 0010:clone_finish_inode_update+0x102/0x130 [btrfs] Code: ff ff ff 49 8b 45 50 f0 48 0f ba a8 40 ce 00 00 02 72 19 83 fb fb 0f 84 86 3a 05 00 89 de 48 c7 c7 48 08 ad c0 e8 90 18 03 e4 <0f> 0b 4c 89 ef 89 d9 ba 16 0d 00 00 48 c7 c6 90 30 ac c0 e8 2e d9 RSP: 0018:bcf6e4017b60 EFLAGS: 00010286 RAX: RBX: ffe4 RCX: 0006 RDX: 0007 RSI: 0082 RDI: 9ec45fa16440 RBP: bcf6e4017b90 R08: 0001 R09: 3827 R10: 0004 R11: R12: 9ec455442a60 R13: 9ec4533992d8 R14: 0a40 R15: 9ec1cb06c800 FS: 7f34c46f3800() GS:9ec45fa0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f34c46f1ef8 CR3: 000d124f6003 CR4: 001606e0 Call Trace: btrfs_clone+0xa18/0x1080 [btrfs] btrfs_clone_files+0xfe/0x160 [btrfs] btrfs_remap_file_range+0x321/0x410 [btrfs] do_clone_file_range+0x12b/0x260 vfs_clone_file_range+0x3a/0xb0 ioctl_file_clone+0x93/0xc0 do_vfs_ioctl+0x495/0x640 ? putname+0x47/0x50 ksys_ioctl+0x67/0x90 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x5a/0x110 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f34c4a5e417 Code: 00 00 90 48 8b 05 79 0a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 49 0a 0d 00 f7 d8 64 89 01 48 RSP: 002b:7fff6c7b9e98 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 0012 RCX: 7f34c4a5e417 RDX: 0012 RSI: 40049409 RDI: 0008 RBP: R08: 7fff6c7de0a0 R09: 7fff6c7de080
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848428 Title: generic/526 from ubuntu_xfstests_btrfs failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: Issue found on node amd64 node "kili" generic/526- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad) --- tests/generic/526.out 2019-10-16 10:51:13.160701040 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad 2019-10-16 12:22:09.159460024 + @@ -1,5 +1,11 @@ QA output created by 526 -File fname1 data after power failure: bar -File fname2 data after power failure: foo -File fname3 data after power failure: foo -File fname4 data after power failure: hello +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) system call failed: File exists. +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such file or directory ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad' to see the entire diff) $ diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad --- /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out 2019-10-16 10:51:13.160701040 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad 2019-10-16 12:22:09.159460024 + @@ -1,5 +1,11 @@ QA output created by 526 -File fname1 data after power failure: bar -File fname2 data after power failure: foo -File fname3 data after power failure: foo -File fname4 data after power failure: hello +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) system call failed: File exists. +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such file or directory +File fname1 data after power failure: +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname2: No such file or directory +File fname2 data after power failure: +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname3: No such file or directory +File fname3 data after power failure: +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname4: No such file or directory +File fname4 data after power failure: +umount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: not mounted. Syslog: Oct 16 12:22:07 kili ubuntu: run xfstest generic/526 Oct 16 12:22:07 kili kernel: [ 6067.439549] run fstests generic/526 at 2019-10-16 12:22:07 Oct 16 12:22:07 kili kernel: [ 6067.619112] BTRFS info (device sdb1): disk space caching is enabled Oct 16 12:22:07 kili kernel: [ 6067.619114] BTRFS info (device sdb1): has skinny extents Oct 16 12:22:07 kili kernel: [ 6067.623160] BTRFS info (device sdb1): enabling ssd optimizations Oct 16 12:22:07 kili kernel: [ 6067.740396] BTRFS: device fsid 25391e30-6097-48bd-8db6-b92d0184c072 devid 1 transid 5 /dev/sdb2 Oct 16 12:22:08 kili kernel: [ 6067.845454] BTRFS info (device dm-0): disk space caching is enabled Oct 16 12:22:08 kili kernel: [ 6067.845456] BTRFS info (device dm-0): has skinny extents Oct 16 12:22:08 kili kernel: [ 6067.845458] BTRFS info (device dm-0): flagging fs with big metadata feature Oct 16 12:22:08 kili kernel: [ 6067.851055] BTRFS info (device dm-0): enabling ssd optimizations Oct 16 12:22:08 kili kernel: [ 6067.851555] BTRFS info (device dm-0): checking UUID tree Oct 16 12:22:08 kili kernel: [ 6068.206539] BTRFS info (device dm-0): device fsid 25391e30-6097-48bd-8db6-b92d0184c072 devid 1 moved old:/dev/mapper/flakey-test new:/dev/dm-0 Oct 16 12:22:08 kili kernel: [ 6068.207207] BTRFS info (device dm-0): device fsid 25391e30-6097-48bd-8db6-b92d0184c072 devid 1 moved old:/dev/dm-0 new:/dev/mapper/flakey-test Oct 16 12:22:08 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 12:22:08 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 12:22:08 kili kernel: [ 6068.292235]
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878356 Title: generic/001 from ubuntu_xfstests_btrfs / ext4 / xfs failed on F Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Focal (5.4.0-31.35, 5.4.0-26.30): generic/001 - output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/001.out.bad) --- tests/generic/001.out 2020-05-09 00:34:22.099406165 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/001.out.bad 2020-05-09 01:24:51.034988549 + @@ -1,9 +1,14 @@ QA output created by 001 cleanup setup -iter 1 chain ... check -iter 2 chain ... check -iter 3 chain ... check -iter 4 chain ... check ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/001.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/001.out.bad' to see the entire diff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848423 Title: generic/260 from ubuntu_xfstests_btrfs failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: Issue found on node amd64 node "kili" generic/260[failed, exit status 1]- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad) --- tests/generic/260.out 2019-10-16 10:51:13.136701298 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad 2019-10-16 11:46:46.002804112 + @@ -1,14 +1,15 @@ QA output created by 260 [+] Start beyond the end of fs (should fail) -fstrim: SCRATCH_MNT: FITRIM ioctl failed: Invalid argument + [+] Start beyond the end of fs with len set (should fail) -fstrim: SCRATCH_MNT: FITRIM ioctl failed: Invalid argument + ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/260.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad' to see the entire diff) Syslog: Oct 16 11:46:26 kili ubuntu: run xfstest generic/260 Oct 16 11:46:26 kili kernel: [ 3925.966035] run fstests generic/260 at 2019-10-16 11:46:26 Oct 16 11:46:26 kili kernel: [ 3926.146996] BTRFS info (device sdb1): disk space caching is enabled Oct 16 11:46:26 kili kernel: [ 3926.146998] BTRFS info (device sdb1): has skinny extents Oct 16 11:46:26 kili kernel: [ 3926.150850] BTRFS info (device sdb1): enabling ssd optimizations Oct 16 11:46:26 kili kernel: [ 3926.233032] BTRFS: device fsid 38d9a8f4-3115-4a21-adaa-a1a68be4d42c devid 1 transid 5 /dev/sdb2 Oct 16 11:46:26 kili kernel: [ 3926.252529] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:46:26 kili kernel: [ 3926.252530] BTRFS info (device sdb2): has skinny extents Oct 16 11:46:26 kili kernel: [ 3926.252531] BTRFS info (device sdb2): flagging fs with big metadata feature Oct 16 11:46:26 kili kernel: [ 3926.257694] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:46:26 kili kernel: [ 3926.259525] BTRFS info (device sdb2): checking UUID tree Oct 16 11:46:33 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:33 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:33 kili kernel: [ 3933.374556] BTRFS: device fsid cd6d9b8b-abdd-4c38-b9bb-c97b36cb3117 devid 1 transid 5 /dev/sdb2 Oct 16 11:46:33 kili kernel: [ 3933.394698] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:46:33 kili kernel: [ 3933.394700] BTRFS info (device sdb2): has skinny extents Oct 16 11:46:33 kili kernel: [ 3933.394701] BTRFS info (device sdb2): flagging fs with big metadata feature Oct 16 11:46:33 kili kernel: [ 3933.399463] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:46:33 kili kernel: [ 3933.401342] BTRFS info (device sdb2): checking UUID tree Oct 16 11:46:41 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:41 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:41 kili kernel: [ 3941.143873] BTRFS: device fsid f10eab55-8c80-402c-84d2-002a6a1339de devid 1 transid 5 /dev/sdb2 Oct 16 11:46:41 kili kernel: [ 3941.162874] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:46:41 kili kernel: [ 3941.162876] BTRFS info (device sdb2): has skinny extents Oct 16 11:46:41 kili kernel: [ 3941.162876] BTRFS info (device sdb2): flagging fs with big metadata feature Oct 16 11:46:41 kili kernel: [ 3941.170124] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:46:41 kili kernel: [ 3941.172812] BTRFS info (device sdb2): checking UUID tree Oct 16 11:46:42 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:42 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:43 kili kernel: [ 3942.718482] BTRFS: device fsid 030f6bb2-f009-4cf6-91f0-75ea33b909c6 devid 1 transid 5 /dev/sdb2 Oct 16 11:46:43 kili kernel: [ 3942.737021] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:46:43 kili kernel: [ 3942.737022] BTRFS info (device sdb2): has skinny extents Oct 16 11:46:43 kili kernel: [ 3942.737023] BTRFS info (device
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846293 Title: generic/554 from ubuntu_xfstests_btrfs / ext4 failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: Issue found on node amd64 node "gonzo" generic/554- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/554.out.bad) --- tests/generic/554.out 2019-10-01 07:38:07.096386372 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/554.out.bad 2019-10-01 14:01:59.541113516 + @@ -1,3 +1,2 @@ QA output created by 554 swap files return ETXTBUSY -copy_range: Text file busy ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/tests/generic/554.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/554.out.bad' to see the entire diff) $ cat /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/554.out.bad QA output created by 554 swap files return ETXTBUSY ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-29-generic 5.0.0-29.31 ProcVersionSignature: User Name 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 1 11:07 seq crw-rw 1 root audio 116, 33 Oct 1 11:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Oct 2 06:03:41 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R415 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 08WNM9 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R415 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1846293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848424 Title: generic/471 from ubuntu_xfstests_btrfs failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: Issue found on node amd64 node "kili" generic/471- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad) --- tests/generic/471.out 2019-10-16 10:51:13.156701083 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad 2019-10-16 12:16:10.594841128 + @@ -2,12 +2,10 @@ pwrite: Resource temporarily unavailable wrote 8388608/8388608 bytes at offset 0 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) -RWF_NOWAIT time is within limits. +pwrite: Resource temporarily unavailable +(standard_in) 1: syntax error +RWF_NOWAIT took seconds ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad' to see the entire diff) $ diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad --- /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out 2019-10-16 10:51:13.156701083 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad 2019-10-16 12:16:10.594841128 + @@ -2,12 +2,10 @@ pwrite: Resource temporarily unavailable wrote 8388608/8388608 bytes at offset 0 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) -RWF_NOWAIT time is within limits. +pwrite: Resource temporarily unavailable +(standard_in) 1: syntax error +RWF_NOWAIT took seconds : aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa * -0020: bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb -* -0030: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa -* read 8388608/8388608 bytes at offset 0 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) Syslog: Oct 16 12:16:09 kili ubuntu: run xfstest generic/471 Oct 16 12:16:09 kili kernel: [ 5708.949736] run fstests generic/471 at 2019-10-16 12:16:09 Oct 16 12:16:10 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded. Oct 16 12:16:10 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded. Oct 16 12:16:10 kili kernel: [ 5710.290570] BTRFS info (device sdb1): disk space caching is enabled Oct 16 12:16:10 kili kernel: [ 5710.290573] BTRFS info (device sdb1): has skinny extents Oct 16 12:16:10 kili kernel: [ 5710.294454] BTRFS info (device sdb1): enabling ssd optimizations ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33 ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 16 10:41 seq crw-rw 1 root audio 116, 33 Oct 16 10:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Oct 17 04:55:08 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S2600WTT PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=72dbdd83-0e2a-4fdd-99ca-70869e30b925 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C610.86B.01.01.1008.031920151331 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name:
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878347 Title: btrfs/136 from ubuntu_xfstests_btrfs failed on Focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Focal (5.4.0-31.35, 5.4.0-26.30): btrfs/136 [failed, exit status 1]- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/136.out.bad) --- tests/btrfs/136.out 2020-05-09 00:34:22.075405127 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/136.out.bad 2020-05-09 01:14:37.317409196 + @@ -1,2 +1,4 @@ QA output created by 136 -Silence is golden +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error. +Could not mount new btrfs fs +(see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/136.full for details) ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/136.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/136.out.bad' to see the entire diff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846308 Title: generic/228 from ubuntu_xfstests_btrfs / ext4 / xfs failed on B/D/F Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux source package in Focal: New Bug description: Issue found on node amd64 node "gonzo" generic/228- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad) --- tests/generic/228.out 2019-10-01 07:38:07.060386413 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad 2019-10-01 12:27:44.465549241 + @@ -1,6 +1,6 @@ QA output created by 228 File size limit is now set to 100 MB. Let us try to preallocate 101 MB. This should fail. -File size limit exceeded +fallocate: File too large Let us now try to preallocate 50 MB. This should succeed. Test over. ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/tests/generic/228.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad' to see the entire diff) $ cat /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad QA output created by 228 File size limit is now set to 100 MB. Let us try to preallocate 101 MB. This should fail. fallocate: File too large Let us now try to preallocate 50 MB. This should succeed. Test over. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-29-generic 5.0.0-29.31 ProcVersionSignature: User Name 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 1 11:07 seq crw-rw 1 root audio 116, 33 Oct 1 11:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [68184.314209] cfg80211: Loading compiled-in X.509 certificates for regulatory database [68184.315939] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed Oct 2 07:45:38 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R415 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 08WNM9 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R415 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1846308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802474 Title: test_map in ubuntu_bpf failed on D PowerPC Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: The test_map test will fail with the following error on powerpc boxes: $ sudo ./test_maps libbpf: object file doesn't contain bpf program Failed to load SK_SKB parse prog ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-11.12~18.04.1-generic 4.18.12 Uname: Linux 4.18.0-11-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.4 Architecture: ppc64el Date: Fri Nov 9 08:37:46 2018 ProcLoadAvg: 0.18 0.51 0.47 1/1615 14440 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.18.0-11-generic (buildd@bos02-ppc64el-012) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #12~18.04.1-Ubuntu SMP Thu Oct 25 12:58:39 UTC 2018 SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 159) max: 3.695 GHz (cpu 1) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865965 Title: kill11 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: startup='Tue Mar 3 15:46:25 2020' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s kill11.c:97: PASS: signal SIGHUP kill11.c:97: PASS: signal SIGINT kill11.c:97: PASS: signal SIGQUIT dumped core kill11.c:97: PASS: signal SIGILL dumped core kill11.c:97: PASS: signal SIGTRAP dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGBUS dumped core kill11.c:97: PASS: signal SIGFPE dumped core kill11.c:97: PASS: signal SIGKILL kill11.c:97: PASS: signal SIGUSR1 kill11.c:97: PASS: signal SIGSEGV dumped core kill11.c:97: PASS: signal SIGUSR2 kill11.c:97: PASS: signal SIGPIPE kill11.c:97: PASS: signal SIGALRM kill11.c:97: PASS: signal SIGTERM kill11.c:97: PASS: signal SIGSTKFLT kill11.c:97: PASS: signal SIGXCPU dumped core Test timeouted, sending SIGKILL! tst_test.c:1269: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1270: BROK: Test killed! (timeout?) Summary: passed 18 failed 0 skipped 0 warnings 0 tag=kill11 stime=1583250385 dur=302 exit=exited stat=2 core=no cu=0 cs=0 Need to see if bump the timeout threshold can help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865965 Title: kill11 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: startup='Tue Mar 3 15:46:25 2020' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s kill11.c:97: PASS: signal SIGHUP kill11.c:97: PASS: signal SIGINT kill11.c:97: PASS: signal SIGQUIT dumped core kill11.c:97: PASS: signal SIGILL dumped core kill11.c:97: PASS: signal SIGTRAP dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGBUS dumped core kill11.c:97: PASS: signal SIGFPE dumped core kill11.c:97: PASS: signal SIGKILL kill11.c:97: PASS: signal SIGUSR1 kill11.c:97: PASS: signal SIGSEGV dumped core kill11.c:97: PASS: signal SIGUSR2 kill11.c:97: PASS: signal SIGPIPE kill11.c:97: PASS: signal SIGALRM kill11.c:97: PASS: signal SIGTERM kill11.c:97: PASS: signal SIGSTKFLT kill11.c:97: PASS: signal SIGXCPU dumped core Test timeouted, sending SIGKILL! tst_test.c:1269: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1270: BROK: Test killed! (timeout?) Summary: passed 18 failed 0 skipped 0 warnings 0 tag=kill11 stime=1583250385 dur=302 exit=exited stat=2 core=no cu=0 cs=0 Need to see if bump the timeout threshold can help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865967 Title: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification == The fill_fs test for XFS in fallocate06 from ubuntu_ltp_syscalls will fail on X/B/D/E: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 8192) fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Fix == * e093c4be (xfs: Fix tail rounding in xfs_alloc_file_space()) This patch can be cherry-picked in D/E and needs some minor context adjustmest on X/B. == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1865967-xfs-fallocate06/ All patched kernels are working as expected, this issue will no longer exist on XFS: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop5 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Regression Potential == Low, this ensures all the blocks are properly allocated and it's only affecting the allocation on XFS.
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1844493 Title: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 kernels Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux source package in Eoan: Incomplete Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux-gcp source package in Eoan: New Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Status in linux-gcp source package in Focal: New Bug description: Test failed with: FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Steps: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_sysdig_smoke_test/control Test output: == sysdig smoke test to trace dd, cat, read and writes == Limiting raw capture file to 16384 blocks Try 1 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 18 Mbytes Try 2 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 22 Mbytes Try 3 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 4 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 5 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 6 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 7 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 8 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 9 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 10 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Found: 279845 sysdig events 29882 context switches 0 reads from /dev/zero by dd 0 writes to /dev/null by dd PASSED (trace at least 25 context switches) FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Summary: 1 passed, 2 failed ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: User Name 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 18 08:10 seq crw-rw 1 root audio 116, 33 Sep 18 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Sep 18 08:18:54 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 RfKill: Error: [Errno 2] No such file or directory
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1844493 Title: ubuntu_sysdig_smoke_test failed on Eoan/5.3 kernels Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux source package in Eoan: Incomplete Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux-gcp source package in Eoan: New Bug description: Test failed with: FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Steps: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_sysdig_smoke_test/control Test output: == sysdig smoke test to trace dd, cat, read and writes == Limiting raw capture file to 16384 blocks Try 1 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 18 Mbytes Try 2 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 22 Mbytes Try 3 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 4 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 5 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 6 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 7 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 8 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 9 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 10 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Found: 279845 sysdig events 29882 context switches 0 reads from /dev/zero by dd 0 writes to /dev/null by dd PASSED (trace at least 25 context switches) FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Summary: 1 passed, 2 failed ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: User Name 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 18 08:10 seq crw-rw 1 root audio 116, 33 Sep 18 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Sep 18 08:18:54 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias:
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866972 Title: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Committed Bug description: [Impact] kernel selftest ftrace will fail with: [42] Register/unregister many kprobe events [FAIL] [Test case] Run that selftest with: cd tools/testing/selftests/ftrace/ sudo make run_tests [Regression potential] The suggested fix only change the test, not the ftrace code. From the nature of the test, the change would hardly prevent us from detecting other hard failures besides that we do not return EEXIST currently for duplicate probes. = Issue found on c4.large with 5.0.0-1027.30-aws Test failed with: [42] Register/unregister many kprobe events [FAIL] selftests: ftrace: ftracetest === Ftrace unit tests === [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] [3] Basic trace clock test [PASS] [4] Basic event tracing check[PASS] [5] Change the ringbuffer size [PASS] [6] Snapshot and tracing setting [PASS] [7] trace_pipe and trace_marker [PASS] [8] Generic dynamic event - add/remove kprobe events [PASS] [9] Generic dynamic event - add/remove synthetic events [PASS] [10] Generic dynamic event - selective clear (compatibility) [PASS] [11] Generic dynamic event - generic clear event [PASS] [12] event tracing - enable/disable with event level files [PASS] [13] event tracing - restricts events based on pid [PASS] [14] event tracing - enable/disable with subsystem level files [PASS] [15] event tracing - enable/disable with top level files [PASS] [16] Test trace_printk from module [UNRESOLVED] [17] ftrace - function graph filters with stack tracer [PASS] [18] ftrace - function graph filters [PASS] [19] ftrace - function pid filters [PASS] [20] ftrace - stacktrace filter command [PASS] [21] ftrace - function trace with cpumask[PASS] [22] ftrace - test for function event triggers [PASS] [23] ftrace - function trace on module [UNRESOLVED] [24] ftrace - function profiling [PASS] [25] ftrace - function profiler with function tracing[PASS] [26] ftrace - test reading of set_ftrace_filter [PASS] [27] ftrace - test for function traceon/off triggers [PASS] [28] Test creation and deletion of trace instances while setting an event [PASS] [29] Test creation and deletion of trace instances [PASS] [30] Kprobe dynamic event - adding and removing [PASS] [31] Kprobe dynamic event - busy event check [PASS] [32] Kprobe dynamic event with arguments [PASS] [33] Kprobe event with comm arguments[PASS] [34] Kprobe event string type argument [PASS] [35] Kprobe event symbol argument[PASS] [36] Kprobe event argument syntax[PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer [PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events [FAIL] [43] Kprobe dynamic event - adding and removing [PASS] [44] test for the preemptirqsoff tracer [UNSUPPORTED] [45] Test wakeup tracer [PASS] [46] Test wakeup RT tracer [PASS] [47] event trigger - test extended error support [PASS] [48] event trigger - test field variable support [PASS] [49] event trigger - test multiple actions on hist trigger [PASS] [50] event trigger - test inter-event histogram trigger onmatch action [PASS] [51] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] [52] event trigger - test inter-event histogram trigger onmax action [PASS] [53] event trigger - test synthetic_events syntax parser [PASS] [54] event trigger - test event enable/disable trigger [PASS] [55] event trigger - test trigger filter [PASS] [56] event trigger - test histogram modifiers[PASS] [57] event trigger - test multiple histogram triggers[PASS] [58] event trigger - test snapshot-trigger [PASS] [59] event trigger - test stacktrace-trigger [PASS] [60] trace_marker trigger - test snapshot trigger[PASS] [61] trace_marker trigger - test histogram with synthetic event against kernel event [PASS] [62] trace_marker trigger - test histogram with synthetic event [PASS] [63] event
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in 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.) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: Issue found on 5.3 Bionic hwe: Running './test_maps' libbpf: BTF is required, but is missing or corrupted. Failed to load SK_SKB verdict prog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867596 Title: ubuntu_bpf test failed to build on Eoan 5.3.0-43.35 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Bug description: Issue found on Eoan with tip b864ec039 (UBUNTU: Ubuntu-5.3.0-43.35) Caused by 3769128 (selftests/bpf: Skip perf hw events test if the setup disabled it) $ sudo make run_tests TARGETS=bpf make --no-builtin-rules ARCH=x86 -C ../../.. headers_install make[1]: Entering directory '/home/ubuntu/ubuntu-eoan' SYSTBL arch/x86/include/generated/asm/syscalls_32.h SYSHDR arch/x86/include/generated/uapi/asm/unistd_32.h HDRINST usr/include/linux/btf.h HDRINST usr/include/linux/input.h HDRINST usr/include/linux/netfilter/xt_sctp.h REMOVE usr/include/rdma/nes-abi.h HDRINST usr/include/asm/unistd_32.h INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/ubuntu-eoan' make[1]: Entering directory '/home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf' /bin/sh: 1: llvm-readelf: not found make -C ../../../lib/bpf OUTPUT=/home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/ make[2]: Entering directory '/home/ubuntu/ubuntu-eoan/tools/lib/bpf' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' CC /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/libbpf.o CC /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/bpf.o CC /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/btf.o CC /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/bpf_prog_linfo.o LD /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/libbpf-in.o LINK /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/libbpf.a LINK /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/libbpf.so.0.0.4 LINK /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/test_libbpf make[2]: Leaving directory '/home/ubuntu/ubuntu-eoan/tools/lib/bpf' gcc -g -Wall -O2 -I../../../include/uapi -I../../../lib -I../../../lib/bpf -I../../../../include/generated -I../../../include -Dbpf_prog_load=bpf_prog_test_load -Dbpf_load_program=bpf_test_load_program -I. -I/home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf -Iverifier test_verifier.c /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/test_stub.o /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/libbpf.a -lcap -lelf -lrt -lpthread -o /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/test_verifier gcc -g -Wall -O2 -I../../../include/uapi -I../../../lib -I../../../lib/bpf -I../../../../include/generated -I../../../include -Dbpf_prog_load=bpf_prog_test_load -Dbpf_load_program=bpf_test_load_program test_tag.c /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/test_stub.o /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/libbpf.a -lcap -lelf -lrt -lpthread -o /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/test_tag gcc -g -Wall -O2 -I../../../include/uapi -I../../../lib -I../../../lib/bpf -I../../../../include/generated -I../../../include -Dbpf_prog_load=bpf_prog_test_load -Dbpf_load_program=bpf_test_load_program -I. -I/home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpftest_maps.c /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/test_stub.o /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/libbpf.a map_tests/sk_storage_map.c -lcap -lelf -lrt -lpthread -o /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/test_maps gcc -g -Wall -O2 -I../../../include/uapi -I../../../lib -I../../../lib/bpf -I../../../../include/generated -I../../../include -Dbpf_prog_load=bpf_prog_test_load -Dbpf_load_program=bpf_test_load_program test_lru_map.c /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/test_stub.o /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/libbpf.a -lcap -lelf -lrt -lpthread -o /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/test_lru_map gcc -g -Wall -O2 -I../../../include/uapi -I../../../lib -I../../../lib/bpf -I../../../../include/generated -I../../../include -Dbpf_prog_load=bpf_prog_test_load -Dbpf_load_program=bpf_test_load_program test_lpm_map.c /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/test_stub.o /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/libbpf.a -lcap -lelf -lrt -lpthread -o /home/ubuntu/ubuntu-eoan/tools/testing/selftests/bpf/test_lpm_map gcc -g -Wall -O2 -I../../../include/uapi -I../../../lib
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1831543 Title: Standard_A2_v2 Azure instance will have CPU in offline state Status in ubuntu-kernel-tests: Won't Fix Status in linux-azure package in Ubuntu: Won't Fix Bug description: This needs to be investigated to see if it's been disabled intentionally. The cpu-hot-plug test shows there are 126 offlined CPUs. selftests: cpu-on-off-test.sh pid 9824's current affinity mask: 3 pid 9824's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 2-127 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 not ok 1..1 selftests: cpu-on-off-test.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20200520_161352_2051b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20200520_160450_cdd7c@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20200520_152728_5aa07@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200520_151052_5aa07@/log.gz The test_bpf testcase what it does is only loading the test_bpf module, which reports the following error: May 20 16:57:21 autopkgtest kernel: [ 88.143826] test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop jited:1 ret -12 != 3055 FAIL (1 times) This is cased by upstream commit 636c2628086e "net: skbuff: Remove errornous length validation in skb_vlan_pop()" which we applied from stable upstream v4.4.223. The fix is upstream commit 0d906b1e8d40 "bpf, test: fix ld_abs + vlan push/pop stress test". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829983 Title: memcg_stat from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: memcg_stat_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168 memcg_stat_test 1 TINFO: Warming up pid: 31352 memcg_stat_test 1 TINFO: Process is still here after warm up: 31352 memcg_stat_test 1 TPASS: cache is 135168 as expected memcg_stat_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168 memcg_stat_test 2 TINFO: Warming up pid: 31380 memcg_stat_test 2 TINFO: Process is still here after warm up: 31380 memcg_stat_test 2 TPASS: mapped_file is 135168 as expected memcg_stat_test 3 TINFO: Starting test 3 sh: echo: I/O error memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096 memcg_stat_test 3 TINFO: Warming up pid: 31409 memcg_stat_test 3 TINFO: Process is still here after warm up: 31409 memcg_stat_test 3 TPASS: unevictable is 4096 as expected memcg_stat_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096 memcg_stat_test 4 TINFO: Warming up pid: 31434 memcg_stat_test 4 TINFO: Process is still here after warm up: 31434 memcg_stat_test 4 TPASS: unevictable is 4096 as expected memcg_stat_test 5 TINFO: Starting test 5 sh: echo: I/O error memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected memcg_stat_test 6 TINFO: Starting test 6 sh: echo: I/O error memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed sh: echo: I/O error memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected memcg_stat_test 7 TINFO: Starting test 7 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled memcg_stat_test 7 TINFO: Starting test 8 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version:
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829989 Title: memcg_use_hierarchy from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:07 2019' memcg_use_hierarchy_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_use_hierarchy_test 1 TPASS: process 31577 is killed memcg_use_hierarchy_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_use_hierarchy_test 2 TFAIL: echo 1 > memory.use_hierarchy passed unexpectedly memcg_use_hierarchy_test 3 TINFO: Starting test 3 sh: echo: I/O error memcg_use_hierarchy_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_use_hierarchy_test 3 TPASS: echo 0 > subgroup/memory.use_hierarchy failed as expected tag=memcg_use_hierarchy stime=1558504747 dur=1 exit=exited stat=1 core=no cu=5 cs=5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:33:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 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 Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854298 Title: ubuntu_unionmount_ovlfs failed on X/T-LTS-X with latest update in upstream testsuite Status in ubuntu-kernel-tests: Triaged Status in linux-signed package in Ubuntu: Confirmed Bug description: A bisect shows this test is failing since commit 2104e51db38 (Simplify initialization of __upper) The test will fail with: *** *** ./run --ov --ts=0 rmtree *** TEST rmtree.py:4: Recursive remove populated lower dir with lower files - rmtree /mnt/a/dir100 *** *** ./run --ov --ts=0 rmtree-new *** TEST rmtree-new.py:4: Recursive remove populated lower dir with new subdir ./run --mkdir /mnt/a/dir100/b 0755 - rmtree /mnt/a/dir100 *** *** ./run --ov --ts=0 hard-link *** TEST hard-link.py:10: Hard link file ./run --link /mnt/a/foo100 /mnt/a/no_foo100 stderr: /mnt/a/foo100: File unexpectedly on upper layer For the complete test log, please refer the attachment. HEAD now is 1724ef2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-169-generic 4.4.0-169.198 ProcVersionSignature: User Name 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Nov 28 04:21:52 2019 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833028] Re: fanotify06 from ubuntu_ltp_syscalls failed
** Tags added: sru-20200427 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833028 Title: fanotify06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in linux source package in Disco: Fix Released Bug description: == SRU Justification == fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for overlayfs has received more than one expected event: <<>> tag=fanotify06 stime=1560747299 cmdline="fanotify06" contacts="" analysis=exit <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15 fanotify06.c:230: PASS: group 8 got no event fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24) fanotify06.c:220: FAIL: group 3 got event fanotify06.c:220: FAIL: group 4 got event fanotify06.c:220: FAIL: group 5 got event fanotify06.c:220: FAIL: group 6 got event fanotify06.c:220: FAIL: group 7 got event fanotify06.c:220: FAIL: group 8 got event Summary: passed 9 failed 9 skipped 0 warnings 0 This duplicated event was generated with operations on files with "fake" path. == Fix == * d9899030 (ovl: do not generate duplicate fsnotify events for "fake" path) This patch can be cherry-picked into Disco. Older kernels are not affected by this issue (without commit d1d04ef8) == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1833028-fanotify06-ovl/ Verified on a KVM node, the fanotify06 test will pass with this patched disco kernel: fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=5997 fd=30 fanotify06.c:230: PASS: group 3 got no event fanotify06.c:230: PASS: group 4 got no event fanotify06.c:230: PASS: group 5 got no event fanotify06.c:230: PASS: group 6 got no event fanotify06.c:230: PASS: group 7 got no event fanotify06.c:230: PASS: group 8 got no event == Regression Potential == Low, fix limited to the overlayfs and just corrects the flag behaviour with "fake" path. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 17 04:37 seq crw-rw 1 root audio 116, 33 Jun 17 04:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Mon Jun 17 04:40:18 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to:
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862588 Title: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-signed-oracle-5.0 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-aws source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux-signed-oracle-5.0 source package in Bionic: New Status in linux source package in Disco: Fix Committed Status in linux-aws source package in Disco: New Status in linux-gcp source package in Disco: New Status in linux-signed-oracle-5.0 source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in linux-aws source package in Eoan: New Status in linux-gcp source package in Eoan: New Status in linux-signed-oracle-5.0 source package in Eoan: New Bug description: [Impact] Running seccomp kernel selftests will fail. [Test case] Run linux/tools/testing/selftests/seccomp/seccomp_bpf. On failure: seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 (18446744073709551615) == ret (0) seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == errno (0) global.user_notification_basic: Test failed at step #3 [ FAIL ] global.user_notification_basic On success: [ RUN ] global.user_notification_basic [ OK ] global.user_notification_basic [Regression potential] The test is checking that the given structure which the kernel will write to is all zeroes. It's doing it because it wants userspace to have the possibility in the future to give data there indicating support for an extension that might be developed in the future. As the test is there right now, not applying the breaking uABI fix might cause us to miss applications that would break in future kernels. As the backport for that is prone for more regression potential, we are deciding to revert the new test. == Issue found on Oracle Bionic 5.0 (oracle : 5.0.0-1011.16 : amd64) [ RUN ] global.user_notification_basic seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 (18446744073709551615) == ret (0) seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == errno (0) global.user_notification_basic: Test failed at step #3 [ FAIL ] global.user_notification_basic This cannot be reproduced with the kselftest in older kernel, probably a test case issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1011-oracle 5.0.0-1011.16 ProcVersionSignature: User Name 5.0.0-1011.16-oracle 5.0.21 Uname: Linux 5.0.0-1011-oracle x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Mon Feb 10 05:17:54 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle-5.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873054] Re: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests
** Tags added: s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873054 Title: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments[PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument[PASS] 04/12 03:26:18 DEBUG| utils:0153| [stdout] # [37] Kprobe event argument syntax[PASS] 04/12 03:26:20 DEBUG| utils:0153| [stdout] # [38] Kprobes event
[Kernel-packages] [Bug 1865406] Re: Add support to test 5.0 Bionic kernel
Sam, linux-image-virtual-gkeop-5.0 has been testing in the GKE cloud on baremetal and virtual instances. This package does not need to consume resources in the metal labs. I would prefer it not be tested in any of the MAAS clouds. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865406 Title: Add support to test 5.0 Bionic kernel Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: For Bionic-5.0 hwe kernel, the requested meta package "linux-generic- hwe-18.04-5.0" from the test request is not available: sudo DEBIAN_FRONTEND=noninteractive UCF_FORCE_CONFFNEW=1 apt-get install --yes linux-generic-hwe-18.04-5.0 ShellError Raised Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package linux-generic-hwe-18.04-5.0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-76-generic 4.15.0-76.86 ProcVersionSignature: User Name 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 2 03:09 seq crw-rw 1 root audio 116, 33 Mar 2 03:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Mar 2 03:12:05 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872526] Re: dbgsym package for linux-image-4.15.0-1065-aws missing
Package is now in -updates: linux-image-4.15.0-1065-aws-dbgsym: Installed: (none) Candidate: 4.15.0-1065.69 Version table: 4.15.0-1065.69 500 500 http://ddebs.ubuntu.com bionic-updates/main amd64 Packages Thanks. ** Changed in: linux-aws (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1872526 Title: dbgsym package for linux-image-4.15.0-1065-aws missing Status in linux-aws package in Ubuntu: Fix Released Bug description: On April 6th, a new linux-aws was released, targeting linux- image-4.15.0-1065-aws. However it's been over a week and the linux- image-4.15.0-1065-aws-dbgsym is still not available on http://ddebs.ubuntu.com/ubuntu "bionic-updates". It does seem to be there on "bionic-proposed", but I think it should be there on "bionic- updates" as well given that "linux-image-4.15.0-1065-aws" is there on bionic-updates. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1065-aws (not installed) ProcVersionSignature: User Name 4.15.0-1051.53-aws 4.15.18 Uname: Linux 4.15.0-1051-aws x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Mon Apr 13 19:00:32 2020 Ec2AMI: ami-096bb69690a48bcc9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1872526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866972] Re: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests
Was observed on the linux-gcp 5.3 kernel: 04/14 09:54:08 DEBUG| utils:0153| [stdout] # [45] Register/unregister many kprobe events [FAIL] 5.3.0-1018.19~18.04.1 linux-gcp-5.3 ** Tags added: gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866972 Title: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Eoan: New Bug description: Issue found on c4.large with 5.0.0-1027.30-aws Test failed with: [42] Register/unregister many kprobe events [FAIL] selftests: ftrace: ftracetest === Ftrace unit tests === [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] [3] Basic trace clock test [PASS] [4] Basic event tracing check[PASS] [5] Change the ringbuffer size [PASS] [6] Snapshot and tracing setting [PASS] [7] trace_pipe and trace_marker [PASS] [8] Generic dynamic event - add/remove kprobe events [PASS] [9] Generic dynamic event - add/remove synthetic events [PASS] [10] Generic dynamic event - selective clear (compatibility) [PASS] [11] Generic dynamic event - generic clear event [PASS] [12] event tracing - enable/disable with event level files [PASS] [13] event tracing - restricts events based on pid [PASS] [14] event tracing - enable/disable with subsystem level files [PASS] [15] event tracing - enable/disable with top level files [PASS] [16] Test trace_printk from module [UNRESOLVED] [17] ftrace - function graph filters with stack tracer [PASS] [18] ftrace - function graph filters [PASS] [19] ftrace - function pid filters [PASS] [20] ftrace - stacktrace filter command [PASS] [21] ftrace - function trace with cpumask[PASS] [22] ftrace - test for function event triggers [PASS] [23] ftrace - function trace on module [UNRESOLVED] [24] ftrace - function profiling [PASS] [25] ftrace - function profiler with function tracing[PASS] [26] ftrace - test reading of set_ftrace_filter [PASS] [27] ftrace - test for function traceon/off triggers [PASS] [28] Test creation and deletion of trace instances while setting an event [PASS] [29] Test creation and deletion of trace instances [PASS] [30] Kprobe dynamic event - adding and removing [PASS] [31] Kprobe dynamic event - busy event check [PASS] [32] Kprobe dynamic event with arguments [PASS] [33] Kprobe event with comm arguments[PASS] [34] Kprobe event string type argument [PASS] [35] Kprobe event symbol argument[PASS] [36] Kprobe event argument syntax[PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer [PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events [FAIL] [43] Kprobe dynamic event - adding and removing [PASS] [44] test for the preemptirqsoff tracer [UNSUPPORTED] [45] Test wakeup tracer [PASS] [46] Test wakeup RT tracer [PASS] [47] event trigger - test extended error support [PASS] [48] event trigger - test field variable support [PASS] [49] event trigger - test multiple actions on hist trigger [PASS] [50] event trigger - test inter-event histogram trigger onmatch action [PASS] [51] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] [52] event trigger - test inter-event histogram trigger onmax action [PASS] [53] event trigger - test synthetic_events syntax parser [PASS] [54] event trigger - test event enable/disable trigger [PASS] [55] event trigger - test trigger filter [PASS] [56] event trigger - test histogram modifiers[PASS] [57] event trigger - test multiple histogram triggers[PASS] [58] event trigger - test snapshot-trigger [PASS] [59] event trigger - test stacktrace-trigger [PASS] [60] trace_marker trigger - test snapshot trigger[PASS] [61] trace_marker trigger - test histogram with synthetic event against kernel event [PASS] [62] trace_marker trigger - test histogram with synthetic event [PASS] [63] event trigger - test traceon/off trigger[PASS] [64] (instance) Basic test for tracers [PASS] [65] (instance) Basic trace clock test [PASS] [66] (instance) Change the ringbuffer size [PASS] [67] (instance) Snapshot and tracing setting [PASS] [68] (instance) trace_pipe and trace_marker [PASS] [69] (instance) event tracing - enable/disable with event level
[Kernel-packages] [Bug 1872526] Re: dbgsym package for linux-image-4.15.0-1065-aws missing
I have checked the status of the pkg, it's still in the queue just wanted to update the bug, hopefully we should see it in updates by Sat EOD. ** Changed in: linux-aws (Ubuntu) Importance: High => Medium ** Changed in: linux-aws (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1872526 Title: dbgsym package for linux-image-4.15.0-1065-aws missing Status in linux-aws package in Ubuntu: In Progress Bug description: On April 6th, a new linux-aws was released, targeting linux- image-4.15.0-1065-aws. However it's been over a week and the linux- image-4.15.0-1065-aws-dbgsym is still not available on http://ddebs.ubuntu.com/ubuntu "bionic-updates". It does seem to be there on "bionic-proposed", but I think it should be there on "bionic- updates" as well given that "linux-image-4.15.0-1065-aws" is there on bionic-updates. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1065-aws (not installed) ProcVersionSignature: User Name 4.15.0-1051.53-aws 4.15.18 Uname: Linux 4.15.0-1051-aws x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Mon Apr 13 19:00:32 2020 Ec2AMI: ami-096bb69690a48bcc9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1872526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864140] Re: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC
Here is the problem. Fanatic test-local-docker, creates a local docker container and imports local DNS via systemd-resolv.conf , it tries to install "Ping" and can't do that because of our firewall, well... the firewall in the lab. It's blocking access to ports.ubuntu.com.. 2 ways we can fix this.. Need to install docker manually, prior to running the teest and preseed docker templates to add Acquire::http::Proxy "http://:3128"; so that it imports to /etc/apt/apt.conf OR we update the firewall rules to allow access to ports.ubuntu.com from all machines in this lab. Giving we don't own that network it may require some haggling. updating our test may be the least invasive, but it's a pain in the rear. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864140 Title: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Bug description: Issue found on PowerPC nodes across different kernels. (It works on other arches in different MAAS server, so it looks like some network config issue) Running in the Canonical CI environment Testing Fan Networking (pre-0.13.0 API) docker pull ppc64le/ubuntu: PASSED enable disable fan test: PASSED fanctl show test: PASSED fanctl check bridge config test: PASSED fanatic docker test: FAILED: (docker run returned 100) stderr: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease Unable to connect to ports.ubuntu.com:http: W: Some index files failed to download. They have been ignored, or old ones used instead. E: Unable to locate package iputils-ping ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 21 03:32 seq crw-rw 1 root audio 116, 33 Feb 21 03:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Feb 21 03:47:15 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=faf7d4a6-6836-4496-bc64-15f33ec9e43d ro console=hvc0 ProcLoadAvg: 1.28 1.27 0.97 1/1305 17149 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-174-generic (buildd@bos02-ppc64el-008) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.12) ) #204-Ubuntu SMP Wed Jan 29 06:41:38 UTC 2020 RelatedPackageVersions: linux-restricted-modules-4.4.0-174-generic N/A linux-backports-modules-4.4.0-174-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 120) max: 3.694 GHz (cpu 37) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864140] Re: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC
Marking the linux package invalid as this is clearly a busted test ** Changed in: ubuntu-kernel-tests Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864140 Title: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Bug description: Issue found on PowerPC nodes across different kernels. (It works on other arches in different MAAS server, so it looks like some network config issue) Running in the Canonical CI environment Testing Fan Networking (pre-0.13.0 API) docker pull ppc64le/ubuntu: PASSED enable disable fan test: PASSED fanctl show test: PASSED fanctl check bridge config test: PASSED fanatic docker test: FAILED: (docker run returned 100) stderr: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease Unable to connect to ports.ubuntu.com:http: W: Some index files failed to download. They have been ignored, or old ones used instead. E: Unable to locate package iputils-ping ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 21 03:32 seq crw-rw 1 root audio 116, 33 Feb 21 03:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Feb 21 03:47:15 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=faf7d4a6-6836-4496-bc64-15f33ec9e43d ro console=hvc0 ProcLoadAvg: 1.28 1.27 0.97 1/1305 17149 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-174-generic (buildd@bos02-ppc64el-008) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.12) ) #204-Ubuntu SMP Wed Jan 29 06:41:38 UTC 2020 RelatedPackageVersions: linux-restricted-modules-4.4.0-174-generic N/A linux-backports-modules-4.4.0-174-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 120) max: 3.694 GHz (cpu 37) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864140] Re: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC
After looking @ lp#1840904 This looks like its nameresolv issue in the lab in which the power machine resides. I'll have to deploy one in order to fix this and find out whats causing it. ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Sean Feole (sfeole) ** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864140 Title: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Bug description: Issue found on PowerPC nodes across different kernels. (It works on other arches in different MAAS server, so it looks like some network config issue) Running in the Canonical CI environment Testing Fan Networking (pre-0.13.0 API) docker pull ppc64le/ubuntu: PASSED enable disable fan test: PASSED fanctl show test: PASSED fanctl check bridge config test: PASSED fanatic docker test: FAILED: (docker run returned 100) stderr: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease Unable to connect to ports.ubuntu.com:http: W: Some index files failed to download. They have been ignored, or old ones used instead. E: Unable to locate package iputils-ping ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 21 03:32 seq crw-rw 1 root audio 116, 33 Feb 21 03:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Feb 21 03:47:15 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=faf7d4a6-6836-4496-bc64-15f33ec9e43d ro console=hvc0 ProcLoadAvg: 1.28 1.27 0.97 1/1305 17149 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-174-generic (buildd@bos02-ppc64el-008) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.12) ) #204-Ubuntu SMP Wed Jan 29 06:41:38 UTC 2020 RelatedPackageVersions: linux-restricted-modules-4.4.0-174-generic N/A linux-backports-modules-4.4.0-174-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 120) max: 3.694 GHz (cpu 37) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed
** Changed in: ubuntu-kernel-tests Status: New => Confirmed ** Tags added: sru-20200406 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Status in linux source package in Disco: New Status in linux-aws source package in Disco: New Bug description: startup='Wed May 22 06:50:45 2019' cpuacct 1 TINFO: timeout per run is 0h 5m 0s cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: /opt/ltp/testcases/bin/cpuacct.sh: Cannot fork tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 cs=53 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 06:59:27 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on Eoan/5.3 kernels
** Tags added: sru-20200406 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1844493 Title: ubuntu_sysdig_smoke_test failed on Eoan/5.3 kernels Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux source package in Eoan: Incomplete Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux-gcp source package in Eoan: New Bug description: Test failed with: FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Steps: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_sysdig_smoke_test/control Test output: == sysdig smoke test to trace dd, cat, read and writes == Limiting raw capture file to 16384 blocks Try 1 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 18 Mbytes Try 2 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 22 Mbytes Try 3 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 4 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 5 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 6 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 7 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 8 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 9 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 10 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Found: 279845 sysdig events 29882 context switches 0 reads from /dev/zero by dd 0 writes to /dev/null by dd PASSED (trace at least 25 context switches) FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Summary: 1 passed, 2 failed ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: User Name 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 18 08:10 seq crw-rw 1 root audio 116, 33 Sep 18 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Sep 18 08:18:54 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias:
[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed with D/B/E
** Tags added: sru-20200406 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed with D/B/E Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Triaged Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 18 TFAIL : proc01.c:397: read
[Kernel-packages] [Bug 1873054] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1873054/+attachment/5354791/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873054 Title: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments[PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument[PASS] 04/12 03:26:18 DEBUG| utils:0153| [stdout]
[Kernel-packages] [Bug 1873054] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1873054/+attachment/5354788/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873054 Title: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments[PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument[PASS] 04/12 03:26:18 DEBUG| utils:0153|
[Kernel-packages] [Bug 1873054] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1873054/+attachment/5354790/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873054 Title: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments[PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument[PASS] 04/12 03:26:18 DEBUG| utils:0153| [stdout] # [37]
[Kernel-packages] [Bug 1873054] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1873054/+attachment/5354789/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873054 Title: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments[PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument[PASS] 04/12 03:26:18 DEBUG| utils:0153|
[Kernel-packages] [Bug 1873054] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1873054/+attachment/5354783/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873054 Title: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments[PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument[PASS] 04/12 03:26:18 DEBUG| utils:0153|
[Kernel-packages] [Bug 1873054] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1873054/+attachment/5354784/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873054 Title: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments[PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument[PASS] 04/12 03:26:18 DEBUG| utils:0153| [stdout] # [37]
[Kernel-packages] [Bug 1873054] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1873054/+attachment/5354787/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873054 Title: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments[PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument[PASS] 04/12 03:26:18 DEBUG|
[Kernel-packages] [Bug 1873054] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1873054/+attachment/5354786/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873054 Title: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments[PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument[PASS] 04/12 03:26:18 DEBUG| utils:0153| [stdout] #
[Kernel-packages] [Bug 1873054] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1873054/+attachment/5354785/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873054 Title: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments[PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument[PASS] 04/12 03:26:18 DEBUG| utils:0153| [stdout] #
[Kernel-packages] [Bug 1873054] Re: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests
apport information ** Tags added: apport-collected uec-images ** Description changed: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments[PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument[PASS] 04/12 03:26:18 DEBUG| utils:0153| [stdout] # [37] Kprobe event argument syntax[PASS] 04/12 03:26:20 DEBUG| utils:0153| [stdout] # [38] Kprobes event arguments with types [PASS] 04/12 03:26:20 DEBUG| utils:0153| [stdout] # [39] Kprobe event user-memory access [PASS] 04/12 03:26:21 DEBUG| utils:0153| [stdout] # [40] Kprobe event auto/manual naming [PASS] 04/12 03:26:23 DEBUG| utils:0153| [stdout] # [41] Kprobe dynamic event with function tracer
[Kernel-packages] [Bug 1873054] Re: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests
Also exhibited on ARM64: non-xgene systems. 04/12 03:48:06 DEBUG| utils:0153| [stdout] # [50] Meta-selftest [PASS] 04/12 03:48:17 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:48:40 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:48:55 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions [XFAIL] 04/12 03:49:16 DEBUG| utils:0153| [stdout] # [54] event trigger - test field variable support [PASS] We do not see these Ftrace Failures on AWS-Nitro backed ARM64 instances. ** Tags added: arm64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873054 Title: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions[XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command [PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask[PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing[PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event[PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32]
[Kernel-packages] [Bug 1873054] [NEW] Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests
Public bug reported: In Focal, The following tests fail on baremetal/amd64: 04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer [FAIL] 04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer [FAIL] 04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test inter-event histogram trigger expected fail actions [XFAIL] Full output below. 04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker[PASS] 04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - add/remove kprobe events [PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - add/remove synthetic events[PASS] 04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - selective clear (compatibility) [PASS] 04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - generic clear event [PASS] 04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - enable/disable with event level files [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts events based on pid [PASS] 04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with subsystem level files [PASS] 04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - enable/disable with top level files [PASS] 04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from module [PASS] 04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph filters with stack tracer [PASS] 04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph filters [PASS] 04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid filters [PASS] 04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace filter command[PASS] 04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace with cpumask [PASS] 04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for function event triggers [PASS] 04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace on module [PASS] 04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function profiling [PASS] 04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function profiler with function tracing [PASS] 04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of set_ftrace_filter[PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for function traceon/off triggers [PASS] 04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing error log support [PASS] 04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and deletion of trace instances while setting an event [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and deletion of trace instances [PASS] 04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - adding and removing[PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - busy event check [PASS] 04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm arguments [PASS] 04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type argument [PASS] 04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol argument [PASS] 04/12 03:26:18 DEBUG| utils:0153| [stdout] # [37] Kprobe event argument syntax [PASS] 04/12 03:26:20 DEBUG| utils:0153| [stdout] # [38] Kprobes event arguments with types[PASS] 04/12 03:26:20 DEBUG| utils:0153| [stdout] # [39] Kprobe event user-memory access [PASS] 04/12 03:26:21 DEBUG| utils:0153| [stdout] # [40] Kprobe event auto/manual naming [PASS] 04/12 03:26:23 DEBUG| utils:0153| [stdout] # [41] Kprobe dynamic event with function tracer [PASS] 04/12 03:26:24 DEBUG| utils:0153| [stdout] # [42] Create/delete multiprobe on kprobe event [PASS] 04/12 03:26:25 DEBUG| utils:0153| [stdout] # [43] Kprobe
[Kernel-packages] [Bug 1866972] Re: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests on B-AWS-5.0 / E
** Changed in: ubuntu-kernel-tests Status: Invalid => Triaged ** Summary changed: - ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests on B-AWS-5.0 / E + ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests on Metal / E ** Summary changed: - ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests on Metal / E + ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests ** Tags removed: 5.0 aws ** Tags added: sru-20200406 ** Changed in: linux (Ubuntu) Status: Invalid => Triaged ** No longer affects: linux (Ubuntu Disco) ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866972 Title: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Eoan: New Bug description: Issue found on c4.large with 5.0.0-1027.30-aws Test failed with: [42] Register/unregister many kprobe events [FAIL] selftests: ftrace: ftracetest === Ftrace unit tests === [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] [3] Basic trace clock test [PASS] [4] Basic event tracing check[PASS] [5] Change the ringbuffer size [PASS] [6] Snapshot and tracing setting [PASS] [7] trace_pipe and trace_marker [PASS] [8] Generic dynamic event - add/remove kprobe events [PASS] [9] Generic dynamic event - add/remove synthetic events [PASS] [10] Generic dynamic event - selective clear (compatibility) [PASS] [11] Generic dynamic event - generic clear event [PASS] [12] event tracing - enable/disable with event level files [PASS] [13] event tracing - restricts events based on pid [PASS] [14] event tracing - enable/disable with subsystem level files [PASS] [15] event tracing - enable/disable with top level files [PASS] [16] Test trace_printk from module [UNRESOLVED] [17] ftrace - function graph filters with stack tracer [PASS] [18] ftrace - function graph filters [PASS] [19] ftrace - function pid filters [PASS] [20] ftrace - stacktrace filter command [PASS] [21] ftrace - function trace with cpumask[PASS] [22] ftrace - test for function event triggers [PASS] [23] ftrace - function trace on module [UNRESOLVED] [24] ftrace - function profiling [PASS] [25] ftrace - function profiler with function tracing[PASS] [26] ftrace - test reading of set_ftrace_filter [PASS] [27] ftrace - test for function traceon/off triggers [PASS] [28] Test creation and deletion of trace instances while setting an event [PASS] [29] Test creation and deletion of trace instances [PASS] [30] Kprobe dynamic event - adding and removing [PASS] [31] Kprobe dynamic event - busy event check [PASS] [32] Kprobe dynamic event with arguments [PASS] [33] Kprobe event with comm arguments[PASS] [34] Kprobe event string type argument [PASS] [35] Kprobe event symbol argument[PASS] [36] Kprobe event argument syntax[PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer [PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events [FAIL] [43] Kprobe dynamic event - adding and removing [PASS] [44] test for the preemptirqsoff tracer [UNSUPPORTED] [45] Test wakeup tracer [PASS] [46] Test wakeup RT tracer [PASS] [47] event trigger - test extended error support [PASS] [48] event trigger - test field variable support [PASS] [49] event trigger - test multiple actions on hist trigger [PASS] [50] event trigger - test inter-event histogram trigger onmatch action [PASS] [51] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] [52] event trigger - test inter-event histogram trigger onmax action [PASS] [53] event trigger - test synthetic_events syntax parser [PASS] [54] event trigger - test event enable/disable trigger [PASS] [55] event trigger - test trigger filter [PASS] [56] event trigger - test histogram modifiers[PASS] [57] event trigger - test multiple histogram triggers[PASS] [58] event trigger - test snapshot-trigger [PASS] [59] event trigger - test stacktrace-trigger [PASS] [60] trace_marker trigger - test snapshot trigger[PASS]
[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_selftests ftrace fails
** Changed in: ubuntu-kernel-tests Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1830084 Title: ubuntu_kernel_selftests ftrace fails Status in ubuntu-kernel-tests: Invalid Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: Confirmed Status in linux-gcp source package in Disco: Confirmed Status in linux-oracle source package in Disco: New Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux-gcp source package in Eoan: New Status in linux-oracle source package in Eoan: New Bug description: Cloud: Azure Series: Disco Kernel: 5.0.0-1007.7 linux-azure Instance: Standard_D2_v3 and others. 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > /proc/sys/net/ipv4/conf/all/accept_local'' 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done for 'all'. 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13 05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest 05/20 14:24:27 DEBUG| utils:0153| [stdout] 05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal number: 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests === 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file check 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for tracers 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock test 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing check 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the ringbuffer size 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing setting 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and trace_marker 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic event - add/remove kprobe events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic event - add/remove synthetic events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic event - selective clear (compatibility) 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic event - generic clear event 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - enable/disable with event level files 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - restricts events based on pid 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - enable/disable with subsystem level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - enable/disable with top level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [16] Test
