ci starts bisection 2025-05-07 22:40:00.96082834 +0000 UTC m=+109.672574470
bisecting fixing commit since 89d75c4c67aca1573aff905e72131a10847c5fda
building syzkaller on e28266709dd2a1d1452d4a5bbf271700e10335c6
ensuring issue is reproducible on original commit 89d75c4c67aca1573aff905e72131a10847c5fda

testing commit 89d75c4c67aca1573aff905e72131a10847c5fda gcc
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
kernel signature: 47d3a210a039ca46a12d9adee150f3aac40ade9a17cce03c473c0991b7976759
run #0: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #1: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #2: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #3: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #4: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #5: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #6: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #7: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #8: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #9: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #10: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #11: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #12: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #13: OK
run #14: OK
run #15: OK
run #16: OK
run #17: OK
run #18: OK
run #19: OK
unable to determine the verdict: 7 good runs (wanted 10), for bad wanted 10 in total, got 7
revisions tested: 1, total time: 2h52m12.740684914s (build: 22m47.507754599s, test: 10m19.398626145s)
error: the crash wasn't reproduced on the original commit