All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: linux-next@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linuxppc-dev@ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
	tj@kernel.org
Subject: Re: Next 10: Badness at mm/allocpercpu.c:123
Date: Wed, 11 Mar 2009 09:46:21 +0530	[thread overview]
Message-ID: <49B73B15.3040101@in.ibm.com> (raw)
In-Reply-To: <49B67552.5070307@in.ibm.com>

Sachin P. Sant wrote:
> While booting Next 20090310 on a powerpc box (Power6 9117-MMA)
> i observed the following badness :
>
> [    0.339662] ------------[ cut here ]------------
> [    0.339666] Badness at mm/allocpercpu.c:123
> [    0.339670] NIP: c0000000001129dc LR: c0000000001129b8 CTR: 
> 0000000000000000
> [    0.339676] REGS: c0000000fe1efa10 TRAP: 0700   Not tainted  
> (2.6.29-rc7-next-20090310)
> [    0.339681] MSR: 8000000000029032 <EE,ME,CE,IR,DR>  CR: 24000024  
> XER: 20000002
> [    0.339695] TASK = c0000000fe1dd3d0[1] 'swapper' THREAD: 
> c0000000fe1ec000 CPU: 0
> [    0.339701] GPR00: 0000000000000001 c0000000fe1efc90 
> c000000000948660 c0000000fe019000
> [    0.339711] GPR04: 0000000000000000 0000000000000000 
> c0000000fe019080 c00000000122e980
> [    0.339721] GPR08: 0000000000000000 c000000001467dec 
> c0000000fe0e2610 c0000000fe1dd3d0
> [    0.339732] GPR12: 0000000044000022 c000000000a22300 
> c000000000733ad0 c00000000065e0c5
> [    0.339742] GPR16: 0000000003c33a08 0000000000000000 
> c000000000733a08 0000000002f1fc90
> [    0.339752] GPR20: c000000000733a20 c000000000679b30 
> 0000000000000000 0000000002f1fc90
> [    0.339763] GPR24: 0000000000000000 0000000000000000 
> c000000000670ccd 0000000000000001
> [    0.339773] GPR28: c0000000fe019000 0000000000000080 
> c0000000008cb908 0000000000000100
> [    0.339788] NIP [c0000000001129dc] .__alloc_percpu+0x7c/0x244
> [    0.339793] LR [c0000000001129b8] .__alloc_percpu+0x58/0x244
> [    0.339798] Call Trace:
> [    0.339801] [c0000000fe1efc90] [c0000000001129b8] 
> .__alloc_percpu+0x58/0x244 (unreliable)
> [    0.339810] [c0000000fe1efdc0] [c00000000007ce84] 
> .__create_workqueue_key+0x74/0x2a0
> [    0.339819] [c0000000fe1efe70] [c000000000716990] 
> .cpuset_init_smp+0x78/0xa4
> [    0.339827] [c0000000fe1eff00] [c000000000700334] 
> .kernel_init+0x16c/0x224
> [    0.339834] [c0000000fe1eff90] [c00000000002adc8] 
> .kernel_thread+0x54/0x70
> [    0.339839] Instruction dump:
> [    0.339843] 3863007f 78630624 4bffb94d 60000000 2bbd0008 7c7c1b78 
> 40fd0030 e93e8010
> [    0.339856] 80090000 7c000034 5400d97e 78000020 <0b000000> 2fa00000 
> 41fe0010 e93e8010
>
> I have attached the dmesg log here.
>
> Next 20090306 had the same problem, while 20090305 did not.
I see that this WARN_ON was introduced by the following patch from Tejun.

http://lkml.org/lkml/2009/2/18/56

Should i be worried about this warning ?

Thanks
-Sachin


-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

WARNING: multiple messages have this Message-ID (diff)
From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: linux-next@vger.kernel.org
Cc: tj@kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>,
	LKML <linux-kernel@vger.kernel.org>,
	linuxppc-dev@ozlabs.org
Subject: Re: Next 10: Badness at mm/allocpercpu.c:123
Date: Wed, 11 Mar 2009 09:46:21 +0530	[thread overview]
Message-ID: <49B73B15.3040101@in.ibm.com> (raw)
In-Reply-To: <49B67552.5070307@in.ibm.com>

Sachin P. Sant wrote:
> While booting Next 20090310 on a powerpc box (Power6 9117-MMA)
> i observed the following badness :
>
> [    0.339662] ------------[ cut here ]------------
> [    0.339666] Badness at mm/allocpercpu.c:123
> [    0.339670] NIP: c0000000001129dc LR: c0000000001129b8 CTR: 
> 0000000000000000
> [    0.339676] REGS: c0000000fe1efa10 TRAP: 0700   Not tainted  
> (2.6.29-rc7-next-20090310)
> [    0.339681] MSR: 8000000000029032 <EE,ME,CE,IR,DR>  CR: 24000024  
> XER: 20000002
> [    0.339695] TASK = c0000000fe1dd3d0[1] 'swapper' THREAD: 
> c0000000fe1ec000 CPU: 0
> [    0.339701] GPR00: 0000000000000001 c0000000fe1efc90 
> c000000000948660 c0000000fe019000
> [    0.339711] GPR04: 0000000000000000 0000000000000000 
> c0000000fe019080 c00000000122e980
> [    0.339721] GPR08: 0000000000000000 c000000001467dec 
> c0000000fe0e2610 c0000000fe1dd3d0
> [    0.339732] GPR12: 0000000044000022 c000000000a22300 
> c000000000733ad0 c00000000065e0c5
> [    0.339742] GPR16: 0000000003c33a08 0000000000000000 
> c000000000733a08 0000000002f1fc90
> [    0.339752] GPR20: c000000000733a20 c000000000679b30 
> 0000000000000000 0000000002f1fc90
> [    0.339763] GPR24: 0000000000000000 0000000000000000 
> c000000000670ccd 0000000000000001
> [    0.339773] GPR28: c0000000fe019000 0000000000000080 
> c0000000008cb908 0000000000000100
> [    0.339788] NIP [c0000000001129dc] .__alloc_percpu+0x7c/0x244
> [    0.339793] LR [c0000000001129b8] .__alloc_percpu+0x58/0x244
> [    0.339798] Call Trace:
> [    0.339801] [c0000000fe1efc90] [c0000000001129b8] 
> .__alloc_percpu+0x58/0x244 (unreliable)
> [    0.339810] [c0000000fe1efdc0] [c00000000007ce84] 
> .__create_workqueue_key+0x74/0x2a0
> [    0.339819] [c0000000fe1efe70] [c000000000716990] 
> .cpuset_init_smp+0x78/0xa4
> [    0.339827] [c0000000fe1eff00] [c000000000700334] 
> .kernel_init+0x16c/0x224
> [    0.339834] [c0000000fe1eff90] [c00000000002adc8] 
> .kernel_thread+0x54/0x70
> [    0.339839] Instruction dump:
> [    0.339843] 3863007f 78630624 4bffb94d 60000000 2bbd0008 7c7c1b78 
> 40fd0030 e93e8010
> [    0.339856] 80090000 7c000034 5400d97e 78000020 <0b000000> 2fa00000 
> 41fe0010 e93e8010
>
> I have attached the dmesg log here.
>
> Next 20090306 had the same problem, while 20090305 did not.
I see that this WARN_ON was introduced by the following patch from Tejun.

http://lkml.org/lkml/2009/2/18/56

Should i be worried about this warning ?

Thanks
-Sachin


-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

  reply	other threads:[~2009-03-11  4:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10  8:55 linux-next: Tree for March 10 Stephen Rothwell
2009-03-10  9:33 ` Wim Van Sebroeck
2009-03-10 11:07   ` Stephen Rothwell
2009-03-10 14:12 ` Next 10: Badness at mm/allocpercpu.c:123 Sachin P. Sant
2009-03-10 14:12   ` Sachin P. Sant
2009-03-11  4:16   ` Sachin P. Sant [this message]
2009-03-11  4:16     ` Sachin P. Sant
2009-03-11  5:53     ` [GIT PATCH tj-percpu] percpu: fix spurious alignment WARN in legacy SMP percpu allocator Tejun Heo
2009-03-11  5:53       ` Tejun Heo
2009-03-11  5:54     ` [RESEND GIT " Tejun Heo
2009-03-11  5:54       ` Tejun Heo
2009-03-11  6:48       ` Sachin P. Sant
2009-03-11  6:48         ` Sachin P. Sant
2009-03-11  9:31       ` Ingo Molnar
2009-03-11  9:31         ` Ingo Molnar
2009-03-11  8:50   ` Next 10: Badness at mm/allocpercpu.c:123 AA
2009-03-11  8:50     ` AA
2009-03-11  8:53     ` where should I map 0x8000,0000 ~ 0xfc00,0000 to ? AA
2009-03-11  8:53       ` AA
2009-03-10 18:57 ` linux-next: Tree for March 10 (crypto & NLATTR) Randy Dunlap
2009-03-10 19:56   ` Geert Uytterhoeven
2009-03-10 20:08     ` Randy Dunlap
2009-03-10 20:17       ` David Miller
2009-03-11  1:07         ` Herbert Xu
2009-03-11 12:25           ` Geert Uytterhoeven
2009-03-11 16:55           ` Randy Dunlap
2009-03-10 18:59 ` [PATCH -next] staging/p9auth: fix dependency/build error Randy Dunlap

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=49B73B15.3040101@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tj@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 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.