[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUWXpaXi9GwB37hLaPbZaAi2aOMXez1f79DDtb_22ZY1jQ@mail.gmail.com>
Date: Tue, 23 Apr 2013 17:49:35 +0200
From: Sedat Dilek <sedat.dilek@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
Paul McKenney <paul.mckenney@...aro.org>
Subject: Re: linux-next: Tree for Apr 23 [ Call-Traces: lib/debugobjects.c |
kernel/rcupdate.c | kernel/rcutree.c ]
On Tue, Apr 23, 2013 at 10:00 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> Changes since 20130422:
>
> The net-next tree lost its build failure but gained another for which I
> applied a patch.
>
> The akpm tree gained a conflict against the tip tree.
>
> ----------------------------------------------------------------------------
>
Can't say this is related to the ipc-sem-next issue I have seen or the
real trouble-causer.
[ 168.609273] WARNING: at lib/debugobjects.c:260 debug_print_object+0x8e/0xb0()
[ 168.609492] WARNING: at kernel/rcupdate.c:309
rcuhead_fixup_activate+0x5a/0x70()
[ 168.609672] WARNING: at lib/debugobjects.c:260 debug_print_object+0x8e/0xb0()
[ 168.784401] WARNING: at kernel/rcutree.c:2105
rcu_process_callbacks+0x54d/0x5b0()
For details see attached dmesg and kernel-config files.
Paul?
- Sedat -
View attachment "dmesg_3.9.0-rc8-next20130423-1-iniza-small_BROKEN.txt" of type "text/plain" (77072 bytes)
Download attachment "config-3.9.0-rc8-next20130423-1-iniza-small" of type "application/octet-stream" (112457 bytes)
Powered by blists - more mailing lists