From: Eric Sesterhenn <snakebyte@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, mingo@redhat.com
Subject: Re: Oops when accessing /proc/lockdep_chains
Date: Wed, 6 Aug 2008 14:41:34 +0200 [thread overview]
Message-ID: <20080806124134.GA3615@alice> (raw)
In-Reply-To: <20080806121650.GA3119@alice>
* 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
Greetings, Eric
next prev parent reply other threads:[~2008-08-06 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 12:16 Oops when accessing /proc/lockdep_chains Eric Sesterhenn
2008-08-06 12:41 ` Eric Sesterhenn [this message]
2008-08-07 20:53 ` Rabin Vincent
2008-08-07 20:57 ` [PATCH] lockdep: handle chains involving classes defined in modules Rabin Vincent
2008-08-08 3:24 ` Huang Ying
2008-08-08 22:25 ` Rabin Vincent
2008-08-11 6:38 ` Huang Ying
2008-08-08 7:57 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080806124134.GA3615@alice \
--to=snakebyte@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox