All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luk Claes <luk@debian.org>
To: linux-mips@linux-mips.org
Subject: Re: kernel for a Broadcom Swarm board
Date: Fri, 01 May 2009 00:36:42 +0200	[thread overview]
Message-ID: <49FA27FA.3070408@debian.org> (raw)

Hi

 > | [    0.000000] Broadcom SiByte BCM1250 B2 @ 800 MHz (SB1 rev 2)
 > | [    0.000000] Board type: SiByte BCM91250A (SWARM)
 > | [    0.000000] This kernel optimized for board runs with CFE
 > | [    0.000000] Determined physical RAM map:
 > | [    0.000000]  memory: 000000000fe47e00 @ 0000000000000000 (usable)
 > | [    0.000000] Initrd not found or empty - disabling initrd
 > | [    0.000000] Zone PFN ranges:
 > | [    0.000000]   DMA32    0x00000000 -> 0x00100000
 > | [    0.000000]   Normal   0x00100000 -> 0x00100000
 > | [    0.000000] Movable zone start PFN for each node
 > | [    0.000000] early_node_map[1] active PFN ranges
 > | [    0.000000]     0: 0x00000000 -> 0x0000fe47
 > | [    0.000000] Detected 1 available secondary CPU(s)
 > | [    0.000000] Built 1 zonelists in Zone order, mobility grouping 
on.  Total
 > pages: 64205
 > | [    0.000000] Kernel command line: root=/dev/hdc1 console=duart0
 > | [    0.000000] Primary instruction cache 32kB, VIVT, 4-way, 
linesize 32 bytes.
 > | [    0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, 
linesize 32
 > bytes
 > | [    0.000000] PID hash table entries: 1024 (order: 10, 8192 bytes)
 >
 > And then it hangs...

The zeros look like there are no timing interrupts happening. It's a 
pity we don't have hardware to test which kernel version introduced the 
bug (for instance with git-bisect and reboots).

Cheers

Luk

             reply	other threads:[~2009-04-30 22:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 22:36 Luk Claes [this message]
2009-05-01  7:57 ` kernel for a Broadcom Swarm board Aurelien Jarno
2009-05-01 13:54   ` Ralf Baechle
2009-05-01 15:16 ` Jon Fraser
  -- strict thread matches above, loose matches on Subject: below --
2009-04-22 13:16 Aurelien Jarno

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=49FA27FA.3070408@debian.org \
    --to=luk@debian.org \
    --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 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.