public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: CKI Project <cki-project@redhat.com>
Cc: skt-results-master@redhat.com, catalin.marinas@arm.com,
	linux-arm-kernel@lists.infradead.org,
	Memory Management <mm-qe@redhat.com>,
	Jan Stancek <jstancek@redhat.com>,
	Fendy Tjahjadi <ftjahjad@redhat.com>,
	Jeff Bastian <jbastian@redhat.com>,
	robin.murphy@arm.com, mark.rutland@arm.com
Subject: Re: ❌ FAIL: Test report for kernel 5.13.0-rc7 (arm-next, 8ab9b1a9)
Date: Fri, 25 Jun 2021 09:39:19 +0100	[thread overview]
Message-ID: <20210625083918.GA2736@willie-the-truck> (raw)
In-Reply-To: <cki.6A65B499FE.46BPQ6DJTC@redhat.com>

On Thu, Jun 24, 2021 at 07:46:08PM -0000, CKI Project wrote:
> We ran automated tests on a recent commit from this kernel tree:
> 
>        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
>             Commit: 8ab9b1a98a22 - Merge branch 'for-next/core' into for-kernelci
> 
> The results of these automated tests are provided below.
> 
>     Overall result: FAILED (see details below)
>              Merge: OK
>            Compile: OK
>              Tests: FAILED
> 
> All kernel binaries, config files, and logs are available for download here:
> 
>   https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/06/24/326623253
> 
> One or more kernel tests failed:
> 
>     aarch64:
>      ❌ LTP

I think this is fixed by:

https://lore.kernel.org/lkml/YNQvB82UKfDV57eE@gmail.com/

>        🚧 ❌ Podman system integration test - as root
>        🚧 ❌ Podman system integration test - as user

These don't seem kernel related? (fails to retrieve an image afaict)

>        🚧 ✅ xfstests - btrfs
>        🚧 ✅ IPMI driver test
>        🚧 ✅ IPMItool loop stress test
>        🚧 ✅ Storage blktests
>        🚧 ✅ Storage block - filesystem fio test
>        🚧 ✅ Storage block - queue scheduler test
>        🚧 ✅ Storage nvme - tcp
>        🚧 ✅ Storage: lvm device-mapper test
>        🚧 ❌ stress: stress-ng

Oh no, this looks like another alignment fault in memcpy:

[13330.651903] Unable to handle kernel paging request at virtual address ffff8000534705ff
[13330.651914] Mem abort info:
[13330.651918]   ESR = 0x96000021
[13330.651922]   EC = 0x25: DABT (current EL), IL = 32 bits
[13330.651928]   SET = 0, FnV = 0
[13330.651931]   EA = 0, S1PTW = 0
[13330.651933]   FSC = 0x21: alignment fault
[13330.651938] Data abort info:
[13330.651940]   ISV = 0, ISS = 0x00000021
[13330.651941]   CM = 0, WnR = 0
[13330.651943] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000f3e6b000
[13330.651945] [ffff8000534705ff] pgd=1000008ffcfff003, p4d=1000008ffcfff003, pud=100000088e57d003, pmd=10000008d0aeb003, pte=006800008021370f
[13330.651956] Internal error: Oops: 96000021 [#1] SMP
[13330.651961] Modules linked in: unix_diag binfmt_misc fcrypt sm4_generic crc32_generic md4 michael_mic nhpoly1305_neon nhpoly1305 poly1305_generic libpoly1305 poly1305_neon rmd160 sha3_generic sm3_generic streebog_generic wp512 blowfish_generic blowfish_common cast5_generic des_generic libdes chacha_generic chacha_neon libchacha camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common dm_thin_pool dm_persistent_data dm_bio_prison nvme nvme_core ipmi_watchdog ipmi_poweroff loop tun af_key crypto_user scsi_transport_iscsi xt_multiport ip_gre ip_tunnel gre overlay xt_CONNSECMARK xt_SECMARK nft_counter xt_state xt_conntrack nft_compat ah6 ah4 nft_objref nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink jfs sctp ip6_udp_tunnel udp_tunnel dm_log_writes dm_flakey rfkill mlx5_ib ib_uverbs ib_core sunrpc coresight_etm4x i2c_smbus coresight_replicator coresight_tpiu coresight_tmc joydev mlx5_core acpi_ipmi psample ipmi_ssif mlxfw ipmi_devintf
[13330.652076]  ipmi_msghandler coresight_funnel thunderx2_pmu coresight vfat fat fuse zram ip_tables xfs ast crct10dif_ce i2c_algo_bit ghash_ce drm_vram_helper drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec drm_ttm_helper ttm drm gpio_xlp i2c_xlp9xx uas usb_storage aes_neon_bs [last unloaded: nvmet]
[13330.652123] CPU: 115 PID: 188446 Comm: stress-ng Tainted: G           OEL    5.13.0-rc7 #1
[13330.652129] Hardware name: HPE Apollo 70             /C01_APACHE_MB         , BIOS L50_5.13_1.15 05/08/2020
[13330.652133] pstate: 80400009 (Nzcv daif +PAN -UAO -TCO BTYPE=--)
[13330.652139] pc : __memcpy+0x168/0x250
[13330.652150] lr : memory_read_from_buffer+0x58/0x80
[13330.652161] sp : ffff800063ef3c20
[13330.652163] x29: ffff800063ef3c20 x28: ffff0008b1380000 x27: 0000000000000000
[13330.652170] x26: 0000000000000000 x25: 0000000000000000 x24: ffff00080a960fe0
[13330.652176] x23: ffff800063ef3d28 x22: 000000000000063f x21: ffff800063ef3c88
[13330.652181] x20: 000000000000063f x19: 000000000000063f x18: 0000000000000000
[13330.652186] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
[13330.652191] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
[13330.652196] x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000
[13330.652200] x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000
[13330.652206] x5 : ffff000d0fb0063f x4 : ffff80005347063f x3 : ffff000d0fb005c0
[13330.652212] x2 : ffffffffffffffef x1 : ffff800053470600 x0 : ffff000d0fb00000
[13330.652218] Call trace:
[13330.652221]  __memcpy+0x168/0x250
[13330.652225]  acpi_data_show+0x5c/0x8c
[13330.652232]  sysfs_kf_bin_read+0x78/0xa0
[13330.652238]  kernfs_file_read_iter+0x9c/0x1a4
[13330.652241]  kernfs_fop_read_iter+0x34/0x50
[13330.652244]  new_sync_read+0xdc/0x154
[13330.652253]  vfs_read+0x158/0x1e4
[13330.652260]  ksys_read+0x64/0xec
[13330.652266]  __arm64_sys_read+0x28/0x34
[13330.652273]  invoke_syscall+0x50/0x120
[13330.652280]  el0_svc_common.constprop.0+0x4c/0xd4
[13330.652284]  do_el0_svc+0x30/0x9c
[13330.652286]  el0_svc+0x2c/0x54
[13330.652294]  el0t_64_sync_handler+0x1a4/0x1b0
[13330.652296]  el0t_64_sync+0x19c/0x1a0
[13330.652303] Code: a984346c a9c4342c f1010042 54fffee8 (a97c3c8e)
[13330.652307] ---[ end trace 227d4380f57145d4 ]---

So maybe this issue isn't limited to weird modules, after all...

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-06-25  9:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 19:46 ❌ FAIL: Test report for kernel 5.13.0-rc7 (arm-next, 8ab9b1a9) CKI Project
2021-06-25  8:39 ` Will Deacon [this message]
     [not found]   ` <CA+tGwn=rP_hAMLLtoy_s90ZzBjfMggu7T2Qj8HyFfGh1BGUoRA@mail.gmail.com>
2021-06-25 11:02     ` Robin Murphy
2021-06-25 11:09       ` Catalin Marinas
2021-06-25 11:15         ` Robin Murphy
2021-06-29 11:48           ` Robin Murphy
2021-06-29 14:44             ` Lorenzo Pieralisi
2021-06-29 15:14               ` Robin Murphy
2021-06-29 16:35                 ` Catalin Marinas
2021-06-30 10:37                   ` Lorenzo Pieralisi
2021-06-30 11:17                     ` Robin Murphy
     [not found]                       ` <CAMj1kXH=Q+WNgGsbApiq94z5OpJOnNLcFk_dyoVm_-VQunv3MA@mail.gmail.com>
2021-06-30 15:49                         ` Lorenzo Pieralisi
     [not found]                           ` <CAMj1kXHgPmJV6sPO8OWYj84Ncts00fzn+gJ=+xzcXYhCxvm-aA@mail.gmail.com>
2021-07-05 16:17                             ` Lorenzo Pieralisi
     [not found]                               ` <CAMj1kXHQKKnzJUEXMMzt3D1NUodeik8FZN1OTpD9zf8ZWrp6Lw@mail.gmail.com>
2021-07-16 16:26                                 ` Lorenzo Pieralisi
     [not found]                                   ` <CA+tGwnmu-uL1v3vWO1yzH1i1ru6+EbVdEKnGOifoS6fLuTTGoQ@mail.gmail.com>
2021-07-22 13:51                                     ` Robin Murphy
     [not found]                 ` <CA+tGwn=r=BZK08CHBUkk1m5NB-W7GqC9Cwj6Qj+_MbYzqdEjDg@mail.gmail.com>
2021-06-29 17:27                   ` Robin Murphy
2022-03-04 19:31                     ` ??? " Aristeu Rozanski
2022-03-04 19:39                     ` Aristeu Rozanski
2022-03-04 20:00                       ` Robin Murphy
2022-03-07 10:19                       ` Lorenzo Pieralisi
2022-03-07 19:01                         ` Aristeu Rozanski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210625083918.GA2736@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=cki-project@redhat.com \
    --cc=ftjahjad@redhat.com \
    --cc=jbastian@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=mm-qe@redhat.com \
    --cc=robin.murphy@arm.com \
    --cc=skt-results-master@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox