Messages in this thread | | | Date | Fri, 8 Aug 2008 02:23:41 +0530 | From | Rabin Vincent <> | Subject | Re: Oops when accessing /proc/lockdep_chains |
| |
On Wed, Aug 06, 2008 at 02:41:34PM +0200, Eric Sesterhenn wrote: > * Eric Sesterhenn (snakebyte@gmx.de) wrote: > > hi, > > > > with current -git (aka -rc2) i sometime get the following oops > > when doing a cat /proc/lockdep_chains > > The other /proc/lockdep* files dont cause any errors > > > > I dont get it after a fresh reboot :| But was able to reproduce it when > > running my testscripts, I'll try to narrow it down. > > I can easily reproduce this with > > modprobe rcutorture; sleep 10s; rmmod rcutorture; cat > /proc/lockdep_chains > /dev/null
Indeed, it oopses after any module which creates a lock is unloaded. I'll send a patch for this shortly.
Rabin
| |