Messages in this thread | ![/](/images/icornerl.gif) | | Date | Thu, 1 Apr 2010 11:55:04 -0600 | Subject | Re: [ANNOUNCE] 2.6.33.1-rt11 - BUG? | From | Xianghua Xiao <> |
| |
I'm testing 2.6.33.1 on ppc 834x with rt11 patch. After system is up I keep seeing this same message from dmesg:
> BUG: sleeping function called from invalid context at kernel/rtmutex.c:684 > pcnt: 0 0 in_atomic(): 0, irqs_disabled(): 1, pid: 16, name: events/0 > Call Trace: > [cf85be80] [c00096cc] show_stack+0x6c/0x1a4 (unreliable) > [cf85beb0] [c001f928] __might_sleep+0x104/0x108 > [cf85bec0] [c03cb444] rt_spin_lock+0xa0/0xa4 > [cf85bed0] [c0270b6c] lock_tx_qs+0x40/0x68 > [cf85bef0] [c02712cc] adjust_link+0x4c/0x240 > [cf85bf20] [c026d5ec] phy_state_machine+0x3bc/0x628 > [cf85bf40] [c003e69c] worker_thread+0x148/0x1f0 > [cf85bfa0] [c0042ec0] kthread+0x84/0x88 > [cf85bff0] [c00137f8] kernel_thread+0x4c/0x68 > BUG: sleeping function called from invalid context at kernel/rtmutex.c:684 > pcnt: 0 0 in_atomic(): 0, irqs_disabled(): 1, pid: 16, name: events/0 > > #uname -a > Linux 2.6.33.1-rt11 #3 PREEMPT RT Thu Apr 1 11:58:25 CDT 2010 ppc unknown >
This does not hang/lock the system yet...google reported similar 'bug' on older kernels. Is this a bug from 2.6.33.1-rt11 patch or I have to change phy.c somehow to avoid it? This traces back to a mutex lock in phy.c.
Xianghua
| ![\](/images/icornerr.gif) |