Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-11 Thread Alexey Dobriyan
On Fri, Aug 10, 2007 at 12:55:17AM -0700, Andrew Morton wrote: > On Fri, 10 Aug 2007 09:40:00 +0200 Ingo Molnar <[EMAIL PROTECTED]> wrote: > > > > > * Andrew Morton <[EMAIL PROTECTED]> wrote: > > > > > We seem to have made a mess in there. timer_list_show() ends up > > > calling

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-11 Thread Alexey Dobriyan
On Fri, Aug 10, 2007 at 12:55:17AM -0700, Andrew Morton wrote: On Fri, 10 Aug 2007 09:40:00 +0200 Ingo Molnar [EMAIL PROTECTED] wrote: * Andrew Morton [EMAIL PROTECTED] wrote: We seem to have made a mess in there. timer_list_show() ends up calling lookup_module_symbol_name(),

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-10 Thread Andrew Morton
On Fri, 10 Aug 2007 09:40:00 +0200 Ingo Molnar <[EMAIL PROTECTED]> wrote: > > * Andrew Morton <[EMAIL PROTECTED]> wrote: > > > We seem to have made a mess in there. timer_list_show() ends up > > calling lookup_module_symbol_name(), which takes a mutex. However > > print_symbol() (which is

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-10 Thread Ingo Molnar
* Andrew Morton <[EMAIL PROTECTED]> wrote: > We seem to have made a mess in there. timer_list_show() ends up > calling lookup_module_symbol_name(), which takes a mutex. However > print_symbol() (which is called at oops time, interrupt time, etc) > calls module_address_lookup(), which is

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-10 Thread Mariusz Kozlowski
> >>This probably doesn't have great impact ;) but ... > >> To reproduce: run torture tests for RCU and then sysrq+q. > >> > >> SysRq : Show Pending Timers > >> Timer List Version: v0.3 > >> HRTIMER_MAX_CLOCK_BASES: 2 > >> now at 1764338760370 nsecs > >> > >> cpu: 0 > >> clock 0: > >>

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-10 Thread Mariusz Kozlowski
This probably doesn't have great impact ;) but ... To reproduce: run torture tests for RCU and then sysrq+q. SysRq : Show Pending Timers Timer List Version: v0.3 HRTIMER_MAX_CLOCK_BASES: 2 now at 1764338760370 nsecs cpu: 0 clock 0: .index: 0 .resolution: 1

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-10 Thread Ingo Molnar
* Andrew Morton [EMAIL PROTECTED] wrote: We seem to have made a mess in there. timer_list_show() ends up calling lookup_module_symbol_name(), which takes a mutex. However print_symbol() (which is called at oops time, interrupt time, etc) calls module_address_lookup(), which is basically

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-10 Thread Andrew Morton
On Fri, 10 Aug 2007 09:40:00 +0200 Ingo Molnar [EMAIL PROTECTED] wrote: * Andrew Morton [EMAIL PROTECTED] wrote: We seem to have made a mess in there. timer_list_show() ends up calling lookup_module_symbol_name(), which takes a mutex. However print_symbol() (which is called at oops

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-09 Thread Josh Triplett
Andrew Morton wrote: > On Fri, 10 Aug 2007 01:23:07 +0200 > Mariusz Kozlowski <[EMAIL PROTECTED]> wrote: > >> Hello, >> >> This probably doesn't have great impact ;) but ... >> To reproduce: run torture tests for RCU and then sysrq+q. >> >> SysRq : Show Pending Timers >> Timer List Version:

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-09 Thread Andrew Morton
On Fri, 10 Aug 2007 01:23:07 +0200 Mariusz Kozlowski <[EMAIL PROTECTED]> wrote: > Hello, > > This probably doesn't have great impact ;) but ... > To reproduce: run torture tests for RCU and then sysrq+q. > > SysRq : Show Pending Timers > Timer List Version: v0.3 > HRTIMER_MAX_CLOCK_BASES:

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-09 Thread Mariusz Kozlowski
Hello, This probably doesn't have great impact ;) but ... To reproduce: run torture tests for RCU and then sysrq+q. SysRq : Show Pending Timers Timer List Version: v0.3 HRTIMER_MAX_CLOCK_BASES: 2 now at 1764338760370 nsecs cpu: 0 clock 0: .index: 0 .resolution: 1 nsecs

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-09 Thread Mariusz Kozlowski
Hello, This probably doesn't have great impact ;) but ... To reproduce: run torture tests for RCU and then sysrq+q. SysRq : Show Pending Timers Timer List Version: v0.3 HRTIMER_MAX_CLOCK_BASES: 2 now at 1764338760370 nsecs cpu: 0 clock 0: .index: 0 .resolution: 1 nsecs

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-09 Thread Andrew Morton
On Fri, 10 Aug 2007 01:23:07 +0200 Mariusz Kozlowski [EMAIL PROTECTED] wrote: Hello, This probably doesn't have great impact ;) but ... To reproduce: run torture tests for RCU and then sysrq+q. SysRq : Show Pending Timers Timer List Version: v0.3 HRTIMER_MAX_CLOCK_BASES: 2 now at

Re: 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86

2007-08-09 Thread Josh Triplett
Andrew Morton wrote: On Fri, 10 Aug 2007 01:23:07 +0200 Mariusz Kozlowski [EMAIL PROTECTED] wrote: Hello, This probably doesn't have great impact ;) but ... To reproduce: run torture tests for RCU and then sysrq+q. SysRq : Show Pending Timers Timer List Version: v0.3