On Tue, 2019-03-26 at 08:35 +0800, shenghui wrote:
> My test steps:
> --------------
> 1) bootup the system, and check the calltrace in dmesg. Just warning and
> ignore it.
> 2) cat /proc/lockdep # everything is well
> 3) rmmod some module which provides lock_class in lockdep
> In my system, module bcache is used: ('grep bcache /proc/lockdep' prints
> something)
> * stop bcache set
> * rmmod bcache
> I have tried other module, e.g: rmmod iwldvm
> 4) cat /proc/lockdep # system crash
Hi shenghui,
Thank you for having shared your test steps. I ran a slightly different test
myself:
while true; do cat /proc/lockdep >/dev/null; done &
(cd blktests && while ./check -q; do :; done)
This test reads /proc/lockdep in a loop while running a test that stresses
lockdep and also that loads and unloads kernel modules. Since this test
passed on my setup I suggest that you have a close look at your setup. The
vboxdrv kernel driver or an out-of-tree patch may be what is making your
system unstable.
Bart.
