From: "Vegard Nossum" <vegard.nossum@gmail•com>
To: Mariusz Kozlowski <m.kozlowski@tuxland•pl>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
kernel-testers@vger•kernel.org, linux-next@vger•kernel.org,
LKML <linux-kernel@vger•kernel.org>,
Pekka Enberg <penberg@cs•helsinki.fi>
Subject: Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller
Date: Sat, 19 Jul 2008 11:55:14 +0200 [thread overview]
Message-ID: <19f34abd0807190255x304173d4wf2bfabb2d5bce511@mail.gmail.com> (raw)
In-Reply-To: <200807190928.33978.m.kozlowski@tuxland.pl>
On Sat, Jul 19, 2008 at 9:28 AM, Mariusz Kozlowski
<m.kozlowski@tuxland•pl> wrote:
> Hello,
>
> I get this on my x86_32 laptop.
>
> ------------[ cut here ]------------
> WARNING: at /home/mako/linux/lkt/sources/linux-next/kernel/lockdep.c:2068 trace_hardirqs_on_caller+0xdc/0x128()
> Modules linked in:
> Pid: 0, comm: swapper Not tainted 2.6.26-next-20080718 #1
> [<c011d5ca>] warn_on_slowpath+0x4e/0x68
> [<c0132600>] ? init_srcu_struct+0x17/0x3b
> [<c011de86>] ? release_console_sem+0x1c2/0x1e8
> [<c0139818>] ? trace_hardirqs_off+0xb/0xd
> [<c02b95cb>] ? _spin_unlock_irqrestore+0x39/0x60
> [<c011de9a>] ? release_console_sem+0x1d6/0x1e8
> [<c01326be>] ? up+0x23/0x30
> [<c011de86>] ? release_console_sem+0x1c2/0x1e8
> [<c01326be>] ? up+0x23/0x30
> [<c011de86>] ? release_console_sem+0x1c2/0x1e8
> [<c013b83b>] ? __lock_acquire+0x365/0x1151
> [<c013b048>] trace_hardirqs_on_caller+0xdc/0x128
> [<c013b09f>] trace_hardirqs_on+0xb/0xd
> [<c016a40b>] __slab_alloc+0x329/0x61e
> [<c011665f>] ? kmemcheck_memset+0x24/0xe5
> [<c016a7a0>] kmem_cache_alloc+0xa0/0xb6
> [<c01dedb4>] ? kobject_init+0x3b/0xdd
> [<c01dedb4>] ? kobject_init+0x3b/0xdd
> [<c01dedb4>] kobject_init+0x3b/0xdd
> [<c025997f>] firmware_map_add_entry+0x2a/0x4b
> [<c03b8e0c>] firmware_map_add_early+0x32/0x56
> [<c03a3faf>] e820_reserve_resources+0x10a/0x14e
> [<c03a1965>] setup_arch+0x375/0x540
> [<c0136e81>] ? clockevents_register_notifier+0x28/0x2d
> [<c011e477>] ? printk+0x1b/0x1d
> [<c03a09df>] start_kernel+0x67/0x278
> [<c03a0304>] i386_start_kernel+0x64/0x70
> =======================
> ---[ end trace 4eaa2a86a8e2da22 ]---
>
What I don't get here is how SLUB can be used this early in the boot
process. Notice that this is still miles away from the
SLUB: Genslabs=12, HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
line, which comes much later. And that kobject_init() _is_ calling
kzalloc() via verify_dynamic_kobject_allocation(). Isn't this an
error?
(Unfortunately, my "git log" doesn't turn up any recent changes for
any of the affected code paths here.)
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-07-19 9:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 9:53 linux-next: Tree for July 18 Stephen Rothwell
2008-07-19 7:28 ` linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller Mariusz Kozlowski
2008-07-19 9:55 ` Vegard Nossum [this message]
[not found] ` <19f34abd0807190255x304173d4wf2bfabb2d5bce511-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-19 12:56 ` Pekka Enberg
2008-07-19 12:59 ` Vegard Nossum
[not found] ` <19f34abd0807190559y2fe5ebf9h7095793e82de3122-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-19 13:22 ` Stephen Rothwell
2008-07-19 22:17 ` Greg KH
2008-07-19 22:27 ` Vegard Nossum
[not found] ` <19f34abd0807191527u61c5ed61kffe2279c8d46915d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-19 22:41 ` Greg KH
2008-07-19 22:44 ` Vegard Nossum
[not found] ` <19f34abd0807191544nfd73be5nf7dde4b61992a7e8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-19 22:58 ` Greg KH
2008-07-19 23:11 ` Vegard Nossum
[not found] ` <19f34abd0807191611y7cabf405iad307ba79591e04f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-19 23:20 ` Greg KH
2008-07-20 12:51 ` Bernhard Walle
2008-07-20 9:01 ` Dave Hansen
2008-07-20 9:35 ` Thomas Meyer
2008-07-20 13:03 ` Bernhard Walle
[not found] ` <20080720150341.7cd381c2-Hxm9IJOWyO+kWa+peg0mPg@public.gmane.org>
2008-07-20 15:44 ` Bernhard Walle
2008-07-21 13:17 ` Vivek Goyal
[not found] ` <20080721131721.GB4451-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-07-21 13:25 ` Bernhard Walle
2008-07-21 13:39 ` Vivek Goyal
[not found] ` <20080721133937.GC4451-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-07-21 15:00 ` Bernhard Walle
[not found] ` <20080721170037.1a0046b1-oJhqVyG5NZ9bpigZmTR7Iw@public.gmane.org>
2008-07-22 6:15 ` Yasunori Goto
2008-07-20 12:48 ` Bernhard Walle
[not found] ` <20080718195352.e562a00f.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-07-19 7:39 ` linux-next: Tree for July 18: nfs problems Mariusz Kozlowski
2008-07-19 9:35 ` linux-next: Tree for July 18: powerpc g3 hangs Mariusz Kozlowski
2008-07-19 15:31 ` linux-next: Tree for July 18 (very early crash on x86_32) Bartlomiej Zolnierkiewicz
2008-07-20 0:20 ` linux-next: Tree for July 18: sky2 WOL broken Rafael J. Wysocki
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=19f34abd0807190255x304173d4wf2bfabb2d5bce511@mail.gmail.com \
--to=vegard.nossum@gmail$(echo .)com \
--cc=kernel-testers@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=m.kozlowski@tuxland$(echo .)pl \
--cc=penberg@cs$(echo .)helsinki.fi \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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