[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdXMsxRRMV8g6+9vTy_4o8HF49SUh2deNdFjgKwDLEWrxQ@mail.gmail.com>
Date: Mon, 12 Feb 2024 09:34:02 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org
Subject: Re: stackinit unit test failures on m68k
Hi Günter,
On Mon, Feb 12, 2024 at 12:06 AM Guenter Roeck <linux@...ck-us.net> wrote:
> I see the following stackinit unit test failures on m68k when running
> the q800 emulation.
>
> # test_char_array_zero: ASSERTION FAILED at lib/stackinit_kunit.c:333
> Expected stackinit_range_contains(fill_start, fill_size, target_start, target_size) to be true, but is false
> stack fill missed target!? (fill 16 wide, target offset by -12)
>
> # test_char_array_none: ASSERTION FAILED at lib/stackinit_kunit.c:343
> Expected stackinit_range_contains(fill_start, fill_size, target_start, target_size) to be true, but is false
> stack fill missed target!? (fill 16 wide, target offset by -12)
>
> Do you happen to know if this a problem with the test, with m68k, or maybe
> with the configuration ? My configuration is based on mac_defconfig with
> various test options enabled. I use gcc 11.4 to build the image. I tried
> with qemu v8.1 and v8.2.
Thanks, I see the same failures in the logs of my last testrun on ARAnyM, too.
I haven't looked into the details yet.
Only two failures does look like a nice improvement, compared to the
previous time I ran that test ;-)
https://lore.kernel.org/all/CAMuHMdX_g1tbiUL9PUQdqaegrEzCNN3GtbSvSBFYAL4TzvstFg@mail.gmail.com
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68korg
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists