From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jiri Pirko <jpirko@redhat.com>, Meelis Roos <mroos@linux.ee>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Boot lockups triggered by 'net: restore the original spinlock to protect unicast list'
Date: Wed, 5 Aug 2009 14:36:59 +0100 [thread overview]
Message-ID: <20090805133659.GA3740@rakim.wolfsonmicro.main> (raw)
I'm experiencing lockups at boot in -next with the loopback interface on
my SMDK6410. These appear to be triggered by commit
a6ac65db2329e7685299666f5f7b6093c7b0f3a0 (net: restore the original
spinlock to protect unicast list) - the code change is suspicious and
reverting the change allows my system to boot. I've not yet tried to
understand the failure, I'm just reporting it.
The console trace I get on failure is:
[ 1.830000] BUG: spinlock bad magic on CPU#0, swapper/1
[ 1.830000] lock: c7852508, .magic: 00000000, .owner: <none>/-1, .owner_cpu0
[ 1.840000] [<c002fdc8>] (unwind_backtrace+0x0/0xe0) from [<c01679fc>] (_raw)
[ 1.850000] [<c01679fc>] (_raw_spin_lock+0x20/0x98) from [<c020ac40>] (dev_u)
[ 1.860000] [<c020ac40>] (dev_unicast_init+0x18/0x3c) from [<c020ebf8>] (all)
[ 1.860000] [<c020ebf8>] (alloc_netdev_mq+0xbc/0x13c) from [<c001b210>] (loo)
[ 1.870000] [<c001b210>] (loopback_net_init+0x1c/0x70) from [<c02096e4>] (re)
[ 1.880000] [<c02096e4>] (register_pernet_operations+0x20/0x2c) from [<c0209)
[ 1.890000] [<c0209778>] (register_pernet_device+0x20/0x54) from [<c001cbbc>)
[ 1.900000] [<c001cbbc>] (net_dev_init+0xd0/0x15c) from [<c0029274>] (do_one)
[ 1.910000] [<c0029274>] (do_one_initcall+0x4c/0x174) from [<c0008640>] (do_)
[ 1.920000] [<c0008640>] (do_initcalls+0x1c/0x38) from [<c0008a04>] (kernel_)
[ 1.930000] [<c0008a04>] (kernel_init+0x3c/0x8c) from [<c002ac98>] (kernel_t)
[ 9.930000] BUG: spinlock lockup on CPU#0, swapper/1, c7852508
[ 9.930000] [<c002fdc8>] (unwind_backtrace+0x0/0xe0) from [<c01679c8>] (__sp)
[ 9.940000] [<c01679c8>] (__spin_lock_debug+0x88/0x9c) from [<c0167a54>] (_r)
[ 9.940000] [<c0167a54>] (_raw_spin_lock+0x78/0x98) from [<c020ac40>] (dev_u)
[ 9.950000] [<c020ac40>] (dev_unicast_init+0x18/0x3c) from [<c020ebf8>] (all)
[ 9.960000] [<c020ebf8>] (alloc_netdev_mq+0xbc/0x13c) from [<c001b210>] (loo)
[ 9.970000] [<c001b210>] (loopback_net_init+0x1c/0x70) from [<c02096e4>] (re)
[ 9.980000] [<c02096e4>] (register_pernet_operations+0x20/0x2c) from [<c0209)
[ 9.990000] [<c0209778>] (register_pernet_device+0x20/0x54) from [<c001cbbc>)
[ 10.000000] [<c001cbbc>] (net_dev_init+0xd0/0x15c) from [<c0029274>] (do_one)
[ 10.010000] [<c0029274>] (do_one_initcall+0x4c/0x174) from [<c0008640>] (do_)
[ 10.020000] [<c0008640>] (do_initcalls+0x1c/0x38) from [<c0008a04>] (kernel_)
[ 10.030000] [<c0008a04>] (kernel_init+0x3c/0x8c) from [<c002ac98>] (kernel_t)
next reply other threads:[~2009-08-05 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 13:36 Mark Brown [this message]
2009-08-05 13:40 ` Boot lockups triggered by 'net: restore the original spinlock to protect unicast list' Jiri Pirko
2009-08-05 13:49 ` Mark Brown
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=20090805133659.GA3740@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=davem@davemloft.net \
--cc=jpirko@redhat.com \
--cc=mroos@linux.ee \
--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).