This works with ARM64 ThunderX node "starmie" on 18.04 with 4.15 kernel
It looks like since 4.18 kernel, this SyS_write has been changed into ksys_write Test result from 5.0.0 ARM64 ThunderX node "wright" # grep ksys_write ftrace.log |grep dd | tail dd-1389 [002] .... 801.332505: vfs_write <-ksys_write dd-1389 [002] .... 801.333108: ksys_write <-__arm64_sys_write dd-1389 [002] .... 801.333108: __fdget_pos <-ksys_write dd-1389 [002] .... 801.333109: vfs_write <-ksys_write dd-1389 [002] .... 801.333154: ksys_write <-__arm64_sys_write dd-1389 [002] .... 801.333154: __fdget_pos <-ksys_write dd-1389 [002] .... 801.333155: vfs_write <-ksys_write dd-1389 [002] .... 801.333162: ksys_write <-__arm64_sys_write dd-1389 [002] .... 801.333162: __fdget_pos <-ksys_write dd-1389 [002] .... 801.333163: vfs_write <-ksys_write # uname -a Linux ms10-34-mcdivittB0-kernel 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:27:27 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux Test result from 4.18.0 AMD64 node "onibi": # grep ksys_write ftrace.log | grep dd | tail dd-2036 [001] .... 325.866508: vfs_write <-ksys_write dd-2036 [001] .... 325.866722: ksys_write <-__x64_sys_write dd-2036 [001] .... 325.866722: __fdget_pos <-ksys_write dd-2036 [001] .... 325.866722: vfs_write <-ksys_write dd-2036 [001] .... 325.866747: ksys_write <-__x64_sys_write dd-2036 [001] .... 325.866747: __fdget_pos <-ksys_write dd-2036 [001] .... 325.866747: vfs_write <-ksys_write dd-2036 [001] .... 325.866750: ksys_write <-__x64_sys_write dd-2036 [001] .... 325.866750: __fdget_pos <-ksys_write dd-2036 [001] .... 325.866750: vfs_write <-ksys_write # uname -a Linux onibi 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Disco) ** Tags added: disco -- 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/1818612 Title: ubuntu_ftrace_smoke_test failed with 0 SyS_write traces found Status in ubuntu-kernel-tests: New Bug description: ubuntu_ftrace_smoke_test failed on AMD64 / ARM64 PASSED (CONFIG_FUNCTION_TRACER=y in /boot/config-4.18.0-15-generic) PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in /boot/config-4.18.0-15-generic) PASSED (CONFIG_STACK_TRACER=y in /boot/config-4.18.0-15-generic) PASSED (CONFIG_DYNAMIC_FTRACE=y in /boot/config-4.18.0-15-generic) PASSED all expected /sys/kernel/debug/tracing files exist PASSED (function_graph in /sys/kernel/debug/tracing/available_tracers) PASSED (function in /sys/kernel/debug/tracing/available_tracers) PASSED (nop in /sys/kernel/debug/tracing/available_tracers) PASSED (function can be enabled) FAILED (SyS_write traces found must be > 32, got 0) PASSED (function_graph can be enabled) PASSED (vfs_write traces found must be > 32, got 181) PASSED (tracer hwlat can be enabled (got 9 lines of tracing output)) PASSED (tracer blk can be enabled (got 2 lines of tracing output)) PASSED (tracer mmiotrace can be enabled (got 9 lines of tracing output)) PASSED (tracer function_graph can be enabled (got 107012 lines of tracing output)) PASSED (tracer wakeup_dl can be enabled (got 2 lines of tracing output)) PASSED (tracer wakeup_rt can be enabled (got 47 lines of tracing output)) PASSED (tracer wakeup can be enabled (got 2 lines of tracing output)) PASSED (tracer function can be enabled (got 102228 lines of tracing output)) TIMEOUT 13299 KILLING 13299 FAILED: aborting, timeout, took way too long to complete END ERROR ubuntu_ftrace_smoke_test.ftrace-smoke-test ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1551758051 localtime=Mar 05 03:54:11 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-15-generic 4.18.0-15.16 ProcVersionSignature: User Name 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Mar 4 04:44 seq crw-rw---- 1 root audio 116, 33 Mar 4 04:44 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.2 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: Tue Mar 5 03:54:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ded56b2d-3057-4d58-a1e5-422853291ffd ro console=ttyS0,1152008n1 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-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: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1818612/+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