Re: Print out additional debugging advice when we hit lockdep BUGs

2013-04-25 Thread Ingo Molnar
* Dave Jones wrote: > On Wed, Apr 24, 2013 at 08:48:13AM +0200, Ingo Molnar wrote: > > > These patterns repeated in 4 places really call for a common helper > > defined as print_lockdep_off(fmt...) or so? > > > > (Can be a followup patch if that's easier for you.) > > Given there was onl

Re: Print out additional debugging advice when we hit lockdep BUGs

2013-04-25 Thread Dave Jones
On Wed, Apr 24, 2013 at 08:48:13AM +0200, Ingo Molnar wrote: > These patterns repeated in 4 places really call for a common helper > defined as print_lockdep_off(fmt...) or so? > > (Can be a followup patch if that's easier for you.) Given there was only one case which was really different,

Re: Print out additional debugging advice when we hit lockdep BUGs

2013-04-23 Thread Ingo Molnar
* Dave Jones wrote: > We occasionally get reports of these BUGs being hit, and the stack trace > doesn't necessarily always tell us what we need to know about why we are > hitting those limits. > > If users start attaching /proc/lock_stats to reports we may have more of > a clue what's going on