All of lore.kernel.org
 help / color / mirror / Atom feed
From: w90p710@gmail.com (wyang)
To: kernelnewbies@lists.kernelnewbies.org
Subject: MPC8641 based custom board kernel Bug
Date: Thu, 26 Dec 2013 17:07:23 +0800	[thread overview]
Message-ID: <52BBF1CB.3070006@gmail.com> (raw)
In-Reply-To: <CAERE9PrGaOJS3YTBv61=JCEGyPxGnqr_8j=eKrnn7Y9vi8dMug@mail.gmail.com>

On 12/26/2013 01:09 PM, Ashish Khetan wrote:
> Hi,
> I was trying to port Linux-3.12 for MPC8641 based custom designed 
> board for evaluation purpose. I have been facing a kernel bug at mpic 
> initialization. Is somebody have faced this kind of bugs or can give 
> me any pointer for further steps how to solve kernel bugs will be 
> really helpful. here is the snapshot for the bug that may be helpful 
> to address the bug.
> Using MPC86xx HPCN machine description
> Total memory = 512MB; using 1024kB for hash table (at cff00000)
> Linux version 3.12.0 (ashish at ashish-VirtualBox) (gcc version 4.7.2 
> (GCC) ) #2 We
> d Dec 25 16:04:36 IST 2013
> Found initrd at 0xde975000:0xdfec428a
> bootconsole [udbg0] enabled
> setup_arch: bootmem
> mpc86xx_hpcn_setup_arch()
> MPC86xx HPCN board from Freescale Semiconductor
> arch: exit
> Zone ranges:
>   DMA      [mem 0x00000000-0x1fffffff]
>   Normal   empty
>   HighMem  empty
> Movable zone start for each node
> Early memory node ranges
>   node   0: [mem 0x00000000-0x1fffffff]
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
> Kernel command line: root=/dev/ram0 rw rootfs console=ttyS0,115200
> PID hash table entries: 2048 (order: 1, 8192 bytes)
> Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> Sorting __ex_table...
> Memory: 424980K/524288K available (4172K kernel code, 208K rwdata, 
> 1304K rodata,
>  196K init, 149K bss, 99308K reserved, 0K highmem)
> Kernel virtual memory layout:
>   * 0xfffcf000..0xfffff000  : fixmap
>   * 0xff800000..0xffc00000  : highmem PTEs
>   * 0xff7fe000..0xff800000  : early ioremap
>   * 0xe1000000..0xff7fe000  : vmalloc & ioremap
> SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
> NR_IRQS:512 nr_irqs:512 16
> ------------[ cut here ]------------
> kernel BUG at arch/powerpc/platforms/86xx/pic.c:42!

It hints that mpic_alloc() fails. Maybe, you should spend some time 
investigating why it fails.:-)

Thanks
Wei
> Oops: Exception in kernel mode, sig: 5 [#1]
> MPC86xx HPCN
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper Not tainted 3.12.0 #2
> task: c05903e0 ti: c05b4000 task.ti: c05b4000
> NIP: c0567438 LR: c0567430 CTR: c0567400
> REGS: c05b5ee0 TRAP: 0700   Not tainted  (3.12.0)
> MSR: 00021032 <ME,IR,DR,RI>  CR: 24000042  XER: 20000000
>
> GPR00: c0567430 c05b5f90 c05903e0 00000000 c04e4ff8 c051e588 0000008f 
> 00000002
> GPR08: c042789c 00000001 0000006f 00000000 22000048 bebffffd 11a7b4e5 
> 200c8000
> GPR16: ffbeffff ffffffff 00000000 00000024 00000000 1fec56f8 1fec59a7 
> 00000000
> GPR24: 00000000 1fff97e8 40000000 1ffcc6a0 c0bff080 c05c2490 c05c2628 
> c0585b60
> NIP [c0567438] mpc86xx_init_irq+0x38/0x108
> LR [c0567430] mpc86xx_init_irq+0x30/0x108
> Call Trace:
> [c05b5f90] [c0567430] mpc86xx_init_irq+0x30/0x108 (unreliable)
> [c05b5fb0] [c0562784] init_IRQ+0x24/0x38
> [c05b5fc0] [c055fde4] start_kernel+0x1bc/0x2ec
> [c05b5ff0] [00003444] 0x3444
> Instruction dump:
> 3d00c04f 38800000 38a01002 38c00000 38e00100 39088f8c 38600000 90010024
> bfa10014 4bffec35 7c690034 5529d97e <0f090000> 3fa0c04f 4bfff391 38600000
> ---[ end trace 31fd0ba7d8756001 ]---
>
> Kernel panic - not syncing: Attempted to kill the idle task!
> Rebooting in 180 seconds..
>
>
> Thanks & Regards
> Ashish Khetan
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20131226/4a1b873b/attachment-0001.html 

WARNING: multiple messages have this Message-ID (diff)
From: wyang <w90p710@gmail.com>
To: Ashish Khetan <curieux.khetan@gmail.com>,
	kernelnewbies@kernelnewbies.org, linuxppc-dev@lists.ozlabs.org
Cc: scottwood@freescale.com
Subject: Re: MPC8641 based custom board kernel Bug
Date: Thu, 26 Dec 2013 17:07:23 +0800	[thread overview]
Message-ID: <52BBF1CB.3070006@gmail.com> (raw)
In-Reply-To: <CAERE9PrGaOJS3YTBv61=JCEGyPxGnqr_8j=eKrnn7Y9vi8dMug@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3504 bytes --]

On 12/26/2013 01:09 PM, Ashish Khetan wrote:
> Hi,
> I was trying to port Linux-3.12 for MPC8641 based custom designed 
> board for evaluation purpose. I have been facing a kernel bug at mpic 
> initialization. Is somebody have faced this kind of bugs or can give 
> me any pointer for further steps how to solve kernel bugs will be 
> really helpful. here is the snapshot for the bug that may be helpful 
> to address the bug.
> Using MPC86xx HPCN machine description
> Total memory = 512MB; using 1024kB for hash table (at cff00000)
> Linux version 3.12.0 (ashish@ashish-VirtualBox) (gcc version 4.7.2 
> (GCC) ) #2 We
> d Dec 25 16:04:36 IST 2013
> Found initrd at 0xde975000:0xdfec428a
> bootconsole [udbg0] enabled
> setup_arch: bootmem
> mpc86xx_hpcn_setup_arch()
> MPC86xx HPCN board from Freescale Semiconductor
> arch: exit
> Zone ranges:
>   DMA      [mem 0x00000000-0x1fffffff]
>   Normal   empty
>   HighMem  empty
> Movable zone start for each node
> Early memory node ranges
>   node   0: [mem 0x00000000-0x1fffffff]
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
> Kernel command line: root=/dev/ram0 rw rootfs console=ttyS0,115200
> PID hash table entries: 2048 (order: 1, 8192 bytes)
> Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> Sorting __ex_table...
> Memory: 424980K/524288K available (4172K kernel code, 208K rwdata, 
> 1304K rodata,
>  196K init, 149K bss, 99308K reserved, 0K highmem)
> Kernel virtual memory layout:
>   * 0xfffcf000..0xfffff000  : fixmap
>   * 0xff800000..0xffc00000  : highmem PTEs
>   * 0xff7fe000..0xff800000  : early ioremap
>   * 0xe1000000..0xff7fe000  : vmalloc & ioremap
> SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
> NR_IRQS:512 nr_irqs:512 16
> ------------[ cut here ]------------
> kernel BUG at arch/powerpc/platforms/86xx/pic.c:42!

It hints that mpic_alloc() fails. Maybe, you should spend some time 
investigating why it fails.:-)

Thanks
Wei
> Oops: Exception in kernel mode, sig: 5 [#1]
> MPC86xx HPCN
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper Not tainted 3.12.0 #2
> task: c05903e0 ti: c05b4000 task.ti: c05b4000
> NIP: c0567438 LR: c0567430 CTR: c0567400
> REGS: c05b5ee0 TRAP: 0700   Not tainted  (3.12.0)
> MSR: 00021032 <ME,IR,DR,RI>  CR: 24000042  XER: 20000000
>
> GPR00: c0567430 c05b5f90 c05903e0 00000000 c04e4ff8 c051e588 0000008f 
> 00000002
> GPR08: c042789c 00000001 0000006f 00000000 22000048 bebffffd 11a7b4e5 
> 200c8000
> GPR16: ffbeffff ffffffff 00000000 00000024 00000000 1fec56f8 1fec59a7 
> 00000000
> GPR24: 00000000 1fff97e8 40000000 1ffcc6a0 c0bff080 c05c2490 c05c2628 
> c0585b60
> NIP [c0567438] mpc86xx_init_irq+0x38/0x108
> LR [c0567430] mpc86xx_init_irq+0x30/0x108
> Call Trace:
> [c05b5f90] [c0567430] mpc86xx_init_irq+0x30/0x108 (unreliable)
> [c05b5fb0] [c0562784] init_IRQ+0x24/0x38
> [c05b5fc0] [c055fde4] start_kernel+0x1bc/0x2ec
> [c05b5ff0] [00003444] 0x3444
> Instruction dump:
> 3d00c04f 38800000 38a01002 38c00000 38e00100 39088f8c 38600000 90010024
> bfa10014 4bffec35 7c690034 5529d97e <0f090000> 3fa0c04f 4bfff391 38600000
> ---[ end trace 31fd0ba7d8756001 ]---
>
> Kernel panic - not syncing: Attempted to kill the idle task!
> Rebooting in 180 seconds..
>
>
> Thanks & Regards
> Ashish Khetan
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev


[-- Attachment #2: Type: text/html, Size: 5970 bytes --]

  reply	other threads:[~2013-12-26  9:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26  5:09 MPC8641 based custom board kernel Bug Ashish Khetan
2013-12-26  5:09 ` Ashish Khetan
2013-12-26  9:07 ` wyang [this message]
2013-12-26  9:07   ` wyang
2013-12-26 11:48   ` Ashish Khetan
2013-12-26 11:48     ` Ashish Khetan
2013-12-26 22:51     ` Sri Ram Vemulpali
2013-12-26 22:51       ` Sri Ram Vemulpali
2013-12-27  5:20       ` Ashish Khetan
2013-12-27  5:20         ` Ashish Khetan
2013-12-27  6:40         ` Sri Ram Vemulpali
2013-12-27  6:40           ` Sri Ram Vemulpali
2014-03-27 10:34         ` MPC8641 based custom board Kernel stuck at 1000Mhz core clock Ashish
2014-03-27 10:34           ` Ashish
2014-03-27 16:31           ` Valdis.Kletnieks at vt.edu
2014-03-27 16:31             ` Valdis.Kletnieks
2014-04-03  3:25             ` sanjeev sharma
2014-04-03  3:25               ` sanjeev sharma
2014-04-04  7:42               ` Ashish
2014-04-04  7:42                 ` Ashish
2014-05-02  3:52                 ` sanjeev sharma
2014-05-02  3:52                   ` sanjeev sharma
     [not found]     ` <5311987F.3080504@gmail.com>
2014-03-07  5:05       ` SRIO gen2 switch Ashish

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=52BBF1CB.3070006@gmail.com \
    --to=w90p710@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.