Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: guenter.roeck@ericsson.com
Cc: linux-mips@linux-mips.org
Subject: Re: Linux 2.6.39 on Cavium CN38xx
Date: Thu, 09 Jun 2011 14:41:57 -0700	[thread overview]
Message-ID: <4DF13E25.2060502@caviumnetworks.com> (raw)
In-Reply-To: <1307653714.8271.130.camel@groeck-laptop>

On 06/09/2011 02:08 PM, Guenter Roeck wrote:
> Hi folks,
>
> I am trying to get Linux 2.6.39

Where did you get your 2.6.39?  Or in othe rwords, what's the SHA1 Kenneth?

And, what is your .config?

> to run on a board with Cavium CN38xx
> (pass 3, cpu ID 0x000d0003).
>
> Problem I have is that CPUs 1..15 come online, but get stuck in and
> endless interrupt handling loop as soon as interrupts are enabled. I
> attached a log generated with instrumentation code in the interrupt
> handler.
>
> Any idea what I might be doing wrong ? Note that I don't start the
> system from u-boot; the board uses OFW, so some register initialization
> may be wrong.
>

Octeon only supports the Octeon u-boot 'bootoctlinux' protocol.

You have to make sure that the octeon_bootinfo structure is filled in 
properly, and all the CPUs in the core_mask enter the kernel.


> I did see commit dbb103b243e09475c84df2b8ef17615975593761, but I have no
> idea if my problem may be related.
>

Probably not because the Ethernet driver would not be active at this point.

David Daney

> Thanks,
> Guenter
>
> ------------------------------
>
> SMP: Booting CPU09 (CoreId  9)...
> Core 9 ALIVE
>   --- waiting for CPU 9
> CPU revision is: 000d0003 (Cavium Octeon)
>   --- ### CPU 9 SR=0x100000e0
>   ---- set CPU 9 (9) callin map bit
>   ---- CPU 9 (9) call cpu_idle
> CPU 9: IRQ cause 0x0 status 0:0:0:0:0:0
> Cpu 9
> $ 0   : 0000000000000000 000000001000efe1 ffffffff81582db8
> 00000000000001ff
> $ 4   : 0000000000000009 0000000000000009 0000000000000048
> 0000000000000000
> $ 8   : 0000000000000000 0000000000000008 0000000000000000
> 0000000000000000
> $12   : 0000000000000000 ffffffff812b69bc ffffffff8140aed0
> ffffffffbfc02334
> $16   : ffffffff81582db8 0000000000000009 ffffffff815f07b0
> ffffffff81582db8
> $20   : ffffffff815e38d0 ffffffff815830f0 ffffffff815de600
> ffffffff81420000
> $24   : 0000000000000001
> ffffffff8110e870
> $28   : a80000041fe20000 a80000041fe23bf0 0000000000000003
> ffffffff8110a60c
> Hi    : 000000000b71b000
> Lo    : 000000000a037a00
> epc   : ffffffff8140d8e4 schedule+0xdc/0xde8
>      Not tainted
> ra    : ffffffff8110a60c cpu_idle+0x2fc/0x350
> Status: 1000efe3    KX SX UX KERNEL EXL IE
> Cause : 40800000
> PrId  : 000d0003 (Cavium Octeon)
> Call Trace:
> [<ffffffff8140d18c>] dump_stack+0x8/0x34
> [<ffffffff81100fbc>] plat_irq_dispatch+0x2bc/0x2c8
> [<ffffffff81107ea8>] ret_from_irq+0x0/0x4
> [<ffffffff8140d8e4>] schedule+0xdc/0xde8
> [<ffffffff8110a60c>] cpu_idle+0x2fc/0x350
>
> ---
>
> 2nd and subsequent interrupts:
>
> CPU 9: IRQ cause 0x0 status 0:0:0:0:0:0
> Call Trace:
> [<ffffffff8140d18c>] dump_stack+0x8/0x34
> [<ffffffff81100ec4>] plat_irq_dispatch+0x1c4/0x2c8
> [<ffffffff81107ea8>] ret_from_irq+0x0/0x4
> [<ffffffff8140d8e4>] schedule+0xdc/0xde8
> [<ffffffff8110a60c>] cpu_idle+0x2fc/0x350
>
>
>
>

  reply	other threads:[~2011-06-09 21:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 21:08 Linux 2.6.39 on Cavium CN38xx Guenter Roeck
2011-06-09 21:41 ` David Daney [this message]
2011-06-09 22:06   ` Guenter Roeck
2011-06-09 22:06     ` Guenter Roeck
2011-06-09 22:59     ` David Daney
2011-06-11  0:20       ` Guenter Roeck
2011-06-12 16:41         ` Guenter Roeck
2011-06-13 21:10           ` David Daney
2011-06-13 21:51             ` Guenter Roeck
2011-06-14  3:34               ` Guenter Roeck
2011-06-14 16:55                 ` David Daney
2011-06-14 18:09                   ` Guenter Roeck

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=4DF13E25.2060502@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=guenter.roeck@ericsson.com \
    --cc=linux-mips@linux-mips.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