From: "Daniel K." <daniel@cluded.net>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: BUG: when using 'brctl stp'
Date: Fri, 10 Aug 2007 22:15:28 +0000 [thread overview]
Message-ID: <46BCE380.60508@cluded.net> (raw)
I get this on the latest GIT, it was also present shortly after -rc1.
I have not tested with earlier kernels.
# brctl stp br0 on
[ 169.672008] BUG: sleeping function called from invalid context at kernel/mutex.c:86
[ 169.672532] in_atomic():1, irqs_disabled():0
[ 169.672832]
[ 169.672832] Call Trace:
[ 169.673406] [<ffffffff8125db3a>] mutex_lock+0x19/0x2f
[ 169.673696] [<ffffffff81067135>] __alloc_pages+0x71/0x2d3
[ 169.673996] [<ffffffff881e0abc>] :bridge:set_stp_state+0x12/0x37
[ 169.674293] [<ffffffff881e0a0a>] :bridge:store_bridge_parm+0x5f/0x79
[ 169.674587] [<ffffffff810ceb24>] sysfs_write_file+0xf2/0x134
[ 169.674879] [<ffffffff8108b3ad>] vfs_write+0xce/0x177
[ 169.675170] [<ffffffff8108b970>] sys_write+0x45/0x6e
[ 169.675463] [<ffffffff8100bc8e>] system_call+0x7e/0x83
[ 169.675769]
[ 169.676139] br0: starting userspace STP failed, staring kernel STP
# brctl stp br0 off
[ 171.774500] BUG: sleeping function called from invalid context at kernel/mutex.c:86
[ 171.775040] in_atomic():1, irqs_disabled():0
[ 171.775327]
[ 171.775328] Call Trace:
[ 171.775906] [<ffffffff8125db3a>] mutex_lock+0x19/0x2f
[ 171.776195] [<ffffffff81067135>] __alloc_pages+0x71/0x2d3
[ 171.776496] [<ffffffff881e0abc>] :bridge:set_stp_state+0x12/0x37
[ 171.776792] [<ffffffff881e0a0a>] :bridge:store_bridge_parm+0x5f/0x79
[ 171.777086] [<ffffffff810ceb24>] sysfs_write_file+0xf2/0x134
[ 171.777378] [<ffffffff8108b3ad>] vfs_write+0xce/0x177
[ 171.777669] [<ffffffff8108b970>] sys_write+0x45/0x6e
[ 171.777958] [<ffffffff8100bc8e>] system_call+0x7e/0x83
[ 171.778250]
Daniel K.
next reply other threads:[~2007-08-10 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 22:15 Daniel K. [this message]
[not found] ` <20070812012037.0195b610.akpm@linux-foundation.org>
2007-08-14 13:11 ` BUG: when using 'brctl stp' Stephen Hemminger
2007-08-14 13:18 ` Lennert Buytenhek
2007-08-14 13:50 ` [PATCH] bridge: sysfs locking fix Stephen Hemminger
2007-08-14 20:21 ` David Miller
2007-08-24 8:18 ` Daniel Lezcano
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=46BCE380.60508@cluded.net \
--to=daniel@cluded.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).