From: Xianghua Xiao <xiaoxianghua@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] 2.6.33.1-rt11 - BUG?
Date: Thu, 1 Apr 2010 11:55:04 -0600 [thread overview]
Message-ID: <v2se6bf505b1004011055pac588aaga825d3c674e075e1@mail.gmail.com> (raw)
In-Reply-To: <l2me6bf505b1004011042oce87e64fn94bef56c78a1b10d@mail.gmail.com>
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
next parent reply other threads:[~2010-04-01 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <l2me6bf505b1004011042oce87e64fn94bef56c78a1b10d@mail.gmail.com>
2010-04-01 17:55 ` Xianghua Xiao [this message]
2010-04-01 18:23 ` Thomas Gleixner
2010-04-01 18:46 ` Xianghua Xiao
2010-04-01 20:44 ` Xianghua Xiao
2010-04-01 21:07 ` Thomas Gleixner
2010-04-01 21:54 ` Xianghua Xiao
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=v2se6bf505b1004011055pac588aaga825d3c674e075e1@mail.gmail.com \
--to=xiaoxianghua@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®