[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+G9fYvC3b9YwXjeAUBKbgWCgip7KioBRxH=GGNPSpyPqDy2dQ@mail.gmail.com>
Date: Tue, 29 Mar 2022 23:16:25 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Shuah Khan <shuah@...nel.org>,
Shuah Khan <skhan@...uxfoundation.org>,
"David S. Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK <linux-kselftest@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>, lkft-triage@...ts.linaro.org,
Netdev" <netdev@...r.kernel.org>
Subject: Re: kselftest: net: tls: hangs
Hi Jakub,
On Tue, 29 Mar 2022 at 22:56, Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Tue, 29 Mar 2022 20:19:10 +0530 Naresh Kamboju wrote:
> > > > But I can't repro the hung, and we have a timer at the hardness level
> > > > IIUC so IDK how this could "hang"?
> >
> > Did you get a chance to build and test with the config file that I
> > have provided ?
> > I am using kselftest-merge configs for my daily CI system [1] on gitlab.
> >
> > If you think the Kconfig is a test
>
> I have not used the exact config, just a config with TLS=n.
> I also have a different GCC version (11.1).
> Unfortunately I don't have access to docker or podman on the machines
> I'm using.
>
> > > > Naresh, is there any stack trace in the logs? Can you repro on Linus's
> > > > tree?
> >
> > There is no stack trace print, it was only hung.
>
> Can you check where the process is stuck and it's state?
> /proc/$pid/stack and run that thru scripts/decode_stacktrace
I generally use remote devices. which have single serial connection only.
However, I will try your suggestions tomorrow and get back to you.
> > > I couldn't reproduce this either - I have TLS=m
> >
> > If you want to reproduce the same build or re-use the bzImage /
> > vmlinux / System.map
> > you may check the provided link [1].
> >
> > Step to reproduce [1]:
> >
> > # TuxMake supports the concept of runtimes.
> > # See https://docs.tuxmake.org/runtimes/, for that to work it requires
> > # that you install podman or docker on your system.
> > #
> > # To install tuxmake on your system globally:
> > # sudo pip3 install -U tuxmake
> > #
> > # See https://docs.tuxmake.org/ for complete documentation.
> > # Original tuxmake command with fragments listed below.
> >
> > tuxmake --runtime podman --target-arch x86_64 --toolchain gcc-11
> > --kconfig defconfig --kconfig-add
> > https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft.config
> > --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft-crypto.config
> > --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/distro-overrides.config
> > --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/systemd.config
> > --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/virtio.config
> > --kconfig-add CONFIG_IGB=y --kconfig-add
> > CONFIG_UNWINDER_FRAME_POINTER=y cpupower headers kernel kselftest
> > kselftest-merge modules
> >
> >
> > [1] https://builds.tuxbuild.com/26mKij4yB5Q6WUpOyHHEoHLstVJ/
>
> I only see build logs here, are there logs for the run?
Yes. Those are only build logs.
The test log is here but not very useful.
https://lkft.validation.linaro.org/scheduler/job/4770773#L2700
- Naresh
Powered by blists - more mailing lists