bisecting fixing commit since 614124bea77e452aa6df7a8714e8bc820b489922
building syzkaller on e59537be40a9ad863e953e187c14dbde57caf1b1
testing commit 614124bea77e452aa6df7a8714e8bc820b489922 with gcc (GCC) 10.2.1 20210217
kernel signature: c83abe1efc5170f17dc13d85c2aa6e9d5abc4c495911029397a1ed0541e8294a
all runs: crashed: WARNING in vmk80xx_auto_attach/usb_submit_urb
testing current HEAD f55966571d5eb2876a11e48e798b4592fa1ffbb7
testing commit f55966571d5eb2876a11e48e798b4592fa1ffbb7 with gcc (GCC) 10.2.1 20210217
kernel signature: 207b7ffd0c40aee109f2b377a4f54420709b7ba41d3c2cc48df7419020a75be7
run #0: boot failed: kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
run #1: boot failed: BUG: sleeping function called from invalid context in stack_depot_save
run #2: boot failed: kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
run #3: boot failed: kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
run #4: boot failed: kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
run #5: boot failed: BUG: sleeping function called from invalid context in stack_depot_save
run #6: boot failed: BUG: sleeping function called from invalid context in stack_depot_save
run #7: boot failed: kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
run #8: boot failed: possible deadlock in get_page_from_freelist
run #9: boot failed: kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
revisions tested: 2, total time: 30m30.923331663s (build: 15m30.7635182s, test: 14m26.243938154s)
bisection is inconclusive, the first good commit could be any of:
614124bea77e452aa6df7a8714e8bc820b489922
f55966571d5eb2876a11e48e798b4592fa1ffbb7