From: Larry Finger <Larry.Finger@lwfinger.net>
To: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Kernel WARNING splat in 3.14-rc1
Date: Mon, 03 Feb 2014 14:04:40 -0600 [thread overview]
Message-ID: <52EFF658.2080001@lwfinger.net> (raw)
On my freshly built 3.14-rc1 kernel, I get the following new warning splat from
slub:
[ 69.008845] ------------[ cut here ]------------
[ 69.008861] WARNING: CPU: 0 PID: 1578 at mm/slub.c:1007
deactivate_slab+0x4bb/0x520()
[ 69.008863] Modules linked in: rfcomm nfs fscache af_packet lockd sunrpc bnep
rtl8723be arc4 rtl8723_common b43 rtl_pci rtlwifi mac80211 cfg80211 btusb bl
uetooth powernow_k8 kvm_amd kvm snd_hda_intel snd_hda_codec bcma snd_hwdep r852
sdhci_pci sdhci snd_pcm sr_mod snd_seq ssb cdrom forcedeth sm_common pcspkr s
nd_timer serio_raw snd_seq_device snd nand mtd mmc_core rfkill ata_generic
pata_amd nand_ids nand_bch bch nand_ecc 6lowpan_iphc soundcore btcoexist r592 ac v
ideo memstick button battery sg dm_mod autofs4 thermal processor thermal_sys hwmon
[ 69.008934] CPU: 0 PID: 1578 Comm: akonadi_newmail Not tainted 3.14.0-rc1-wl+ #60
[ 69.008936] Hardware name: Hewlett-Packard HP Pavilion dv2700 Notebook
PC/30D6, BIOS F.27 11/27/2008
[ 69.008939] 0000000000000009 ffff880085ab1cd0 ffffffff815ee4a0 0000000000000000
[ 69.008945] ffff880085ab1d08 ffffffff8104e768 ffffea0001ee69c0 ffff8800bb401800
[ 69.008950] 0000000000000000 ffff8800bb400c80 0000000000000002 ffff880085ab1d18
[ 69.008956] Call Trace:
[ 69.008965] [<ffffffff815ee4a0>] dump_stack+0x4d/0x6f
[ 69.008971] [<ffffffff8104e768>] warn_slowpath_common+0x78/0xa0
[ 69.008976] [<ffffffff8104e845>] warn_slowpath_null+0x15/0x20
[ 69.008980] [<ffffffff8118581b>] deactivate_slab+0x4bb/0x520
[ 69.008985] [<ffffffff81183429>] ? new_slab+0x1f9/0x300
[ 69.008989] [<ffffffff815ebe57>] __slab_alloc+0x34d/0x4f5
[ 69.008994] [<ffffffff81185a6b>] ? kmem_cache_alloc+0x18b/0x1c0
[ 69.008999] [<ffffffff810770d1>] ? prepare_creds+0x21/0x1a0
[ 69.009003] [<ffffffff810770d1>] ? prepare_creds+0x21/0x1a0
[ 69.009007] [<ffffffff81185a6b>] kmem_cache_alloc+0x18b/0x1c0
[ 69.009011] [<ffffffff810770d1>] prepare_creds+0x21/0x1a0
[ 69.009016] [<ffffffff8119f955>] SyS_access+0x35/0x1f0
[ 69.009019] [<ffffffff815fe8a2>] system_call_fastpath+0x16/0x1b
[ 69.009019] ---[ end trace c63f75644bfb030a ]---
There is a similar warning for my other CPU as well. The warning comes from
"lockdep_assert_held(&n->list_lock);".
If needed, I can bisect this issue.
Larry
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Kernel WARNING splat in 3.14-rc1
Date: Mon, 03 Feb 2014 14:04:40 -0600 [thread overview]
Message-ID: <52EFF658.2080001@lwfinger.net> (raw)
On my freshly built 3.14-rc1 kernel, I get the following new warning splat from
slub:
[ 69.008845] ------------[ cut here ]------------
[ 69.008861] WARNING: CPU: 0 PID: 1578 at mm/slub.c:1007
deactivate_slab+0x4bb/0x520()
[ 69.008863] Modules linked in: rfcomm nfs fscache af_packet lockd sunrpc bnep
rtl8723be arc4 rtl8723_common b43 rtl_pci rtlwifi mac80211 cfg80211 btusb bl
uetooth powernow_k8 kvm_amd kvm snd_hda_intel snd_hda_codec bcma snd_hwdep r852
sdhci_pci sdhci snd_pcm sr_mod snd_seq ssb cdrom forcedeth sm_common pcspkr s
nd_timer serio_raw snd_seq_device snd nand mtd mmc_core rfkill ata_generic
pata_amd nand_ids nand_bch bch nand_ecc 6lowpan_iphc soundcore btcoexist r592 ac v
ideo memstick button battery sg dm_mod autofs4 thermal processor thermal_sys hwmon
[ 69.008934] CPU: 0 PID: 1578 Comm: akonadi_newmail Not tainted 3.14.0-rc1-wl+ #60
[ 69.008936] Hardware name: Hewlett-Packard HP Pavilion dv2700 Notebook
PC/30D6, BIOS F.27 11/27/2008
[ 69.008939] 0000000000000009 ffff880085ab1cd0 ffffffff815ee4a0 0000000000000000
[ 69.008945] ffff880085ab1d08 ffffffff8104e768 ffffea0001ee69c0 ffff8800bb401800
[ 69.008950] 0000000000000000 ffff8800bb400c80 0000000000000002 ffff880085ab1d18
[ 69.008956] Call Trace:
[ 69.008965] [<ffffffff815ee4a0>] dump_stack+0x4d/0x6f
[ 69.008971] [<ffffffff8104e768>] warn_slowpath_common+0x78/0xa0
[ 69.008976] [<ffffffff8104e845>] warn_slowpath_null+0x15/0x20
[ 69.008980] [<ffffffff8118581b>] deactivate_slab+0x4bb/0x520
[ 69.008985] [<ffffffff81183429>] ? new_slab+0x1f9/0x300
[ 69.008989] [<ffffffff815ebe57>] __slab_alloc+0x34d/0x4f5
[ 69.008994] [<ffffffff81185a6b>] ? kmem_cache_alloc+0x18b/0x1c0
[ 69.008999] [<ffffffff810770d1>] ? prepare_creds+0x21/0x1a0
[ 69.009003] [<ffffffff810770d1>] ? prepare_creds+0x21/0x1a0
[ 69.009007] [<ffffffff81185a6b>] kmem_cache_alloc+0x18b/0x1c0
[ 69.009011] [<ffffffff810770d1>] prepare_creds+0x21/0x1a0
[ 69.009016] [<ffffffff8119f955>] SyS_access+0x35/0x1f0
[ 69.009019] [<ffffffff815fe8a2>] system_call_fastpath+0x16/0x1b
[ 69.009019] ---[ end trace c63f75644bfb030a ]---
There is a similar warning for my other CPU as well. The warning comes from
"lockdep_assert_held(&n->list_lock);".
If needed, I can bisect this issue.
Larry
next reply other threads:[~2014-02-03 20:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 20:04 Larry Finger [this message]
2014-02-03 20:04 ` Kernel WARNING splat in 3.14-rc1 Larry Finger
2014-02-03 20:39 ` David Rientjes
2014-02-03 20:39 ` David Rientjes
2014-02-03 22:34 ` Christoph Lameter
2014-02-03 22:34 ` Christoph Lameter
2014-02-03 23:08 ` Larry Finger
2014-02-03 23:08 ` Larry Finger
2014-02-03 23:41 ` Paul E. McKenney
2014-02-03 23:41 ` Paul E. McKenney
2014-02-03 23:44 ` [patch for-3.14] mm, slub: list_lock may not be held in some circumstances David Rientjes
2014-02-03 23:44 ` David Rientjes
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=52EFF658.2080001@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.