I have now been running the debug config kernel since posting this
bug. There has been no lockdep or slab debug reports in kernel log
since. That makes me wonder what is possible cause of the twice
produced oops in __d_shrink.

I have been using suspend multiple times per day. I have applied all
normal stress to dentry cache through normal use and background file
system scan operations like security checks and defragmentation. Also
log rotation has been done multiple times if that could be original
cause somehow.

If anyone has any ideas how dentry cache could be stressed to
reproduce the issue I would be happy to try it.


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: 
http://lists.debian.org/CAB_=Lzu4e_4MCXkomNSAJ=bbwkbxdmppcjmdcmfec-iyu4p...@mail.gmail.com

Reply via email to