Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Random backtrace regarding preemptive scheduling and systemd-udevd #164

Open
lucbeaufils opened this issue Mar 1, 2023 · 1 comment
Open
Labels
bug Something isn't working Debian

Comments

@lucbeaufils
Copy link
Contributor

backtrace test didn't pass on virtu3 (SEAPATH-0080)
dump_dmesg.txt

@deribaucourt
Copy link
Member

Back trace present after the usual ------------[ cut here ]------------
Seems to be random.

At a quick glance, looks like a race condition with rt-kernel and systemd-udevd:
BUG: scheduling while atomic: systemd-udevd/651/0x00000003
Triggering another backtrace:
WARNING: CPU: 12 PID: 651 at kernel/sched/core.c:5781 preempt_count_sub+0x5e/0xa0

See attached trace for more info.

@deribaucourt deribaucourt added bug Something isn't working Debian labels Mar 1, 2023
@deribaucourt deribaucourt changed the title backtrace failed on virtu3 during CI Random backtrace regarding preemptive scheduling and systemd-udevd Mar 1, 2023
eroussy added a commit to eroussy/ci-seapath that referenced this issue Mar 20, 2023
The test "SEAPATH-00080 - no backtraces" randomly failed and block the
CI.
This commit allow the CI to pass even if this test fails.
The test will still be integrated in the test report and a warning will
be displayed in the CI logs.

An issue is open for this bug on the ansible repo :
seapath/ansible#164

Signed-off-by: Erwann Roussy <erwann.roussy@savoirfairelinux.com>
eroussy added a commit to seapath/ci that referenced this issue Mar 20, 2023
The test "SEAPATH-00080 - no backtraces" randomly failed and block the
CI.
This commit allow the CI to pass even if this test fails.
The test will still be integrated in the test report and a warning will
be displayed in the CI logs.

An issue is open for this bug on the ansible repo :
seapath/ansible#164

Signed-off-by: Erwann Roussy <erwann.roussy@savoirfairelinux.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Debian
Projects
Status: Todo
Development

No branches or pull requests

2 participants