❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc3, arm-next, fec50db7)

❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc3, arm-next, fec50db7)

[cki-project]

Hi, we tested your kernel and here are the results:

    Overall result: FAILED
             Merge: OK
           Compile: OK
              Test: FAILED


Kernel information:
    Commit message: Linux 6.9-rc3

You can find all the details about the test run at
    https://datawarehouse.cki-project.org/kcidb/checkouts/139776

One or more kernel tests failed:
    Unrecognized or new issues:
        Boot test
             aarch64
                   Logs: https://datawarehouse.cki-project.org/kcidb/tests/11963290
                   Non-passing ran subtests:
                       ❌ FAIL distribution/kpkginstall/journalctl-check
        Reboot test
             aarch64
                   Logs: https://datawarehouse.cki-project.org/kcidb/tests/11963296
                   Non-passing ran subtests:
                       ❌ FAIL misc/reboot-test/journalctl-check

    We also see the following known issues which are not related to your changes:
        Issue: [upstream] blktests tests/zbd/010 failed (WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51)
            URL: https://lore.kernel.org/linux-block/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/T/#u
            Affected tests:
                Storage - blktests - blk - upstream [aarch64]
        Issue: [upstream] stress-ng: avc denial on secretmemory
            URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/1752
            Affected tests:
                stress: stress-ng - memory [aarch64]


Tests that were not ran because of internal issues: 
    Memory function: memfd_create [aarch64]


If you find a failure unrelated to your changes, please ask the test maintainer to review it.
This will prevent the failures from being incorrectly reported in the future.

Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.

        ,-.   ,-.
       ( C ) ( K )  Continuous
        `-',-.`-'   Kernel
          ( I )     Integration
           `-'
______________________________________________________________________________


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

Re: ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc3, arm-next, fec50db7)

[Will Deacon]

On Tue, Apr 09, 2024 at 06:01:06PM -0000, cki-project@redhat.com wrote:
> Hi, we tested your kernel and here are the results:
> 
>     Overall result: FAILED
>              Merge: OK
>            Compile: OK
>               Test: FAILED
> 
> 
> Kernel information:
>     Commit message: Linux 6.9-rc3
> 
> You can find all the details about the test run at
>     https://datawarehouse.cki-project.org/kcidb/checkouts/139776
> 
> One or more kernel tests failed:
>     Unrecognized or new issues:
>         Boot test
>              aarch64
>                    Logs: https://datawarehouse.cki-project.org/kcidb/tests/11963290
>                    Non-passing ran subtests:
>                        ❌ FAIL distribution/kpkginstall/journalctl-check

This is just with a vanilla -rc3 kernel to get a baseline result before
queuing patches for 6.10, but the failure seems to stem from a GFP_DMA32
allocation failure in the mellanox driver:

 | (udev-worker): page allocation failure: order:0, mode:0xcc4(GFP_KERNEL|GFP_DMA32), nodemask=(null),cpuset=/,mems_allowed=0
 | CPU: 24 PID: 927 Comm: (udev-worker) Not tainted 6.9.0-rc3 #1
 | Hardware name: Lenovo HR330A            7X33CTO1WW    /FALCON     , BIOS hve104r-1.15 02/26/2021
 | Call trace:
 |  dump_backtrace+0xdc/0x140
 |  show_stack+0x20/0x40
 |  dump_stack_lvl+0x60/0x80
 |  dump_stack+0x18/0x28
 |  warn_alloc+0x138/0x1c8
 |  __alloc_pages_slowpath.constprop.0+0x89c/0x958
 |  __alloc_pages+0x2cc/0x360
 |  __dma_direct_alloc_pages.isra.0+0x118/0x290
 |  dma_direct_alloc+0x21c/0x318
 |  dma_alloc_attrs+0x90/0x110
 |  mlx4_create_eq+0x160/0x4c8 [mlx4_core]
 |  mlx4_init_eq_table+0x46c/0x5c0 [mlx4_core]
 |  mlx4_setup_hca+0xf0/0x7a0 [mlx4_core]
 |  mlx4_load_one+0x56c/0xe80 [mlx4_core]
 |  __mlx4_init_one+0x388/0x408 [mlx4_core]
 |  mlx4_init_one+0x278/0x300 [mlx4_core]
 |  local_pci_probe+0x48/0xc0
 |  pci_call_probe+0x5c/0x1b0
 |  pci_device_probe+0x88/0x160
 |  really_probe+0xc8/0x3a0
 |  __driver_probe_device+0x84/0x160
 |  driver_probe_device+0x44/0x130
 |  __driver_attach+0xcc/0x208
 |  bus_for_each_dev+0x84/0x100
 |  driver_attach+0x2c/0x40
 |  bus_add_driver+0x11c/0x238
 |  driver_register+0x70/0x138
 |  __pci_register_driver+0x54/0x68
 |  mlx4_init+0x144/0xff8 [mlx4_core]
 |  do_one_initcall+0x60/0x318
 |  do_init_module+0x68/0x260
 |  load_module+0x62c/0x760
 |  init_module_from_file+0x90/0xe0
 |  idempotent_init_module+0x18c/0x2b8
 |  __arm64_sys_finit_module+0x6c/0xe0
 |  invoke_syscall+0x74/0x100
 |  el0_svc_common.constprop.0+0xc8/0xf0
 |  do_el0_svc+0x24/0x38
 |  el0_svc+0x3c/0x158
 |  el0t_64_sync_handler+0x120/0x138
 |  el0t_64_sync+0x194/0x198

Will

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

Re: ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc3, arm-next, fec50db7)

[Catalin Marinas]

On Wed, Apr 10, 2024 at 02:54:39PM +0100, Will Deacon wrote:
> On Tue, Apr 09, 2024 at 06:01:06PM -0000, cki-project@redhat.com wrote:
> > Hi, we tested your kernel and here are the results:
> > 
> >     Overall result: FAILED
> >              Merge: OK
> >            Compile: OK
> >               Test: FAILED
> > 
> > 
> > Kernel information:
> >     Commit message: Linux 6.9-rc3
> > 
> > You can find all the details about the test run at
> >     https://datawarehouse.cki-project.org/kcidb/checkouts/139776
> > 
> > One or more kernel tests failed:
> >     Unrecognized or new issues:
> >         Boot test
> >              aarch64
> >                    Logs: https://datawarehouse.cki-project.org/kcidb/tests/11963290
> >                    Non-passing ran subtests:
> >                        ❌ FAIL distribution/kpkginstall/journalctl-check
> 
> This is just with a vanilla -rc3 kernel to get a baseline result before
> queuing patches for 6.10, but the failure seems to stem from a GFP_DMA32
> allocation failure in the mellanox driver:
> 
>  | (udev-worker): page allocation failure: order:0, mode:0xcc4(GFP_KERNEL|GFP_DMA32), nodemask=(null),cpuset=/,mems_allowed=0
>  | CPU: 24 PID: 927 Comm: (udev-worker) Not tainted 6.9.0-rc3 #1
>  | Hardware name: Lenovo HR330A            7X33CTO1WW    /FALCON     , BIOS hve104r-1.15 02/26/2021
>  | Call trace:
>  |  dump_backtrace+0xdc/0x140
>  |  show_stack+0x20/0x40
>  |  dump_stack_lvl+0x60/0x80
>  |  dump_stack+0x18/0x28
>  |  warn_alloc+0x138/0x1c8
>  |  __alloc_pages_slowpath.constprop.0+0x89c/0x958
>  |  __alloc_pages+0x2cc/0x360
>  |  __dma_direct_alloc_pages.isra.0+0x118/0x290
>  |  dma_direct_alloc+0x21c/0x318
>  |  dma_alloc_attrs+0x90/0x110
>  |  mlx4_create_eq+0x160/0x4c8 [mlx4_core]
[...]

If I read the rest of the log correctly [1], there's plenty of memory in
ZONE_DMA:

| Node 0 DMA free:1035920kB boost:0kB min:452kB low:1752kB high:3052kB
| reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB
| active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB
| present:1835008kB managed:1301248kB mlocked:0kB bounce:0kB
| free_pcp:3144kB local_pcp:3144kB free_cma:1035920kB 

For some reason the GFP_DMA32 allocation doesn't fall through to
ZONE_DMA.

[1] https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/1245911266/test_aarch64/6582401556/artifacts/run.done.01/results_0001/console.log

-- 
Catalin

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