ci starts bisection 2025-03-14 02:36:55.653273581 +0000 UTC m=+19292.611750909
bisecting cause commit starting from 89d75c4c67aca1573aff905e72131a10847c5fda
building syzkaller on e28266709dd2a1d1452d4a5bbf271700e10335c6
ensuring issue is reproducible on original commit 89d75c4c67aca1573aff905e72131a10847c5fda

testing commit 89d75c4c67aca1573aff905e72131a10847c5fda gcc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
kernel signature: dfe50423ea237ddf64b4a0a162ff2d7aa66583eb643e73b07f4220492429cffa
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: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #14: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #15: basic kernel testing failed: possible deadlock in lapbeth_device_event
run #16: OK
run #17: OK
run #18: OK
run #19: OK
unable to determine the verdict: 4 good runs (wanted 10), for bad wanted 10 in total, got 4
revisions tested: 1, total time: 25m49.1825341s (build: 14m12.565732019s, test: 10m0.447854819s)
error: the crash wasn't reproduced on the original commit