linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: Tejun Heo <tj@kernel.org>
Cc: David Miller <davem@davemloft.net>,
	Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: 2.6.31-git5 kernel boot hangs on powerpc
Date: Thu, 17 Sep 2009 22:11:19 +0530	[thread overview]
Message-ID: <4AB266AF.9080705@in.ibm.com> (raw)
In-Reply-To: <4AB25B61.9020609@kernel.org>

Tejun Heo wrote:
> Ah... sorry about that.  Sachin, is it possible for you to build the
> kernel with debug info and ask gdb where the stalling NIP is in the c
> file?
>   
<6>NET: Registered protocol family 10
<3>BUG: soft lockup - CPU#2 stuck for 61s! [modprobe:1865]
<4>Modules linked in: ipv6(+) fuse loop dm_mod sg sd_mod crc_t10dif ibmvscsic scsi_transport_srp scsi_tgt scsi_mod
<4>NIP: c00000000004198c LR: c00000000015dac8 CTR: 0000000000000040
<4>REGS: c0000000fbdbb6f0 TRAP: 0901   Not tainted  (2.6.31-git5)
<4>MSR: 8000000000009032 <EE,ME,IR,DR>  CR: 44224420  XER: 20000001
<4>TASK = c0000000fbd57840[1865] 'modprobe' THREAD: c0000000fbdb8000 CPU: 2
<4>GPR00: 0000000000000040 c0000000fbdbb970 c000000000a96d08 d00007fffff00000
<4>GPR04: 0000000000000000 0000000000000000 d00007fffff00000 d00007fffff00000
<4>GPR08: 0000000000000000 c000000001020180 c000000000b6b4e8 00000000000003c0
<4>GPR12: 0000000048224428 c000000000b82a00
<4>NIP [c00000000004198c] .memset+0x60/0xfc
<4>LR [c00000000015dac8] .pcpu_alloc+0x758/0x960
<4>Call Trace:
<4>[c0000000fbdbb970] [c00000000015da58] .pcpu_alloc+0x6e8/0x960 (unreliable)
<4>[c0000000fbdbba90] [c000000000565664] .snmp_mib_init+0x34/0x9c
<4>[c0000000fbdbbb20] [d00000000212e130] .ipv6_add_dev+0x1cc/0x3dc [ipv6]
<4>[c0000000fbdbbbc0] [d0000000021598ac] .addrconf_init+0x6c/0x194 [ipv6]
<4>[c0000000fbdbbc50] [d00000000215967c] .inet6_init+0x1bc/0x34c [ipv6]
<4>[c0000000fbdbbce0] [c0000000000097a4] .do_one_initcall+0x88/0x1bc
<4>[c0000000fbdbbd90] [c0000000000c84dc] .SyS_init_module+0x11c/0x29c
<4>[c0000000fbdbbe30] [c0000000000085b4] syscall_exit+0x0/0x40
<4>Instruction dump:
<4>98860000 38c60001 409e000c b0860000 38c60002 409d000c 90860000 38c60004
<4>78a0d183 78a506a0 7c0903a6 4182002c <f8860000> f8860008 f8860010 f8860018
2:mon> r
R00 = 0000000000000040   R07 = d00007fffff00000
R01 = c0000000fbdbb970   R08 = 0000000000000000
R02 = c000000000a96d08   R09 = c000000001020180
R03 = d00007fffff00000   R10 = c000000000b6b4e8
R04 = 0000000000000000   R11 = 00000000000003c0
R05 = 0000000000000000   R12 = 0000000048224428
R06 = d00007fffff00000   R13 = c000000000b82a00
pc  = c00000000004198c .memset+0x60/0xfc
lr  = c00000000015dac8 .pcpu_alloc+0x758/0x960
msr = 8000000000009032   cr  = 44224420
ctr = 0000000000000040   xer = 0000000020000001   trap =  501
2:mon>

The corresponding c code is :

pcpu_populate_chunk():
/home/sachin/work/linux-2.6.31/mm/percpu.c:978

        /* commit new bitmap */
        bitmap_copy(chunk->populated, populated, pcpu_unit_pages);
clear:
        for_each_possible_cpu(cpu)
                memset((void *)pcpu_chunk_addr(chunk, cpu, 0) + off, 0, size);
    1aa0:       e9 3f 00 38     ld      r9,56(r31)
    1aa4:       7b a0 1f 24     rldicr  r0,r29,3,60
    1aa8:       e8 7b 00 18     ld      r3,24(r27)
    1aac:       38 80 00 00     li      r4,0
    1ab0:       e8 a1 00 88     ld      r5,136(r1)
    1ab4:       7c 09 00 2a     ldx     r0,r9,r0
    1ab8:       7c 63 02 14     add     r3,r3,r0
    1abc:       7c 63 b2 14     add     r3,r3,r22
    1ac0:       48 00 00 01     bl      1ac0 <.pcpu_alloc+0x754>
    1ac4:       60 00 00 00     nop

Thanks
-Sachin


-- 

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

  reply	other threads:[~2009-09-17 16:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 12:25 2.6.31-git5 kernel boot hangs on powerpc Sachin Sant
2009-09-17 10:51 ` Sachin Sant
2009-09-17 11:13   ` Benjamin Herrenschmidt
2009-09-17 15:53     ` Tejun Heo
2009-09-17 16:41       ` Sachin Sant [this message]
2009-09-19  8:54         ` Sachin Sant
2009-09-23  8:23           ` Sachin Sant
2009-09-23  8:34             ` Tejun Heo
2009-09-23 14:17               ` Tejun Heo
2009-09-24  7:58                 ` Sachin Sant
2009-09-24 12:59                   ` Tejun Heo
2009-09-24 13:23                     ` Sachin Sant
2009-09-24 21:05                       ` Benjamin Herrenschmidt
2009-09-25  3:22                         ` Tejun Heo
2009-09-25  3:40                           ` Benjamin Herrenschmidt
2009-09-25  7:15                           ` Sachin Sant
2009-09-25  7:39                             ` Tejun Heo
2009-09-25  7:43                               ` Tejun Heo
2009-09-25  8:03                                 ` Sachin Sant
2009-09-25  9:01                                   ` Tejun Heo
2009-09-25  9:48                                     ` Benjamin Herrenschmidt
2009-10-05  6:54                                       ` Sachin Sant
2009-09-25  8:31                               ` Benjamin Herrenschmidt

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=4AB266AF.9080705@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linuxppc-dev@ozlabs.org \
    --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 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).