linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: linux-mips@linux-mips.org
Subject: Broadcom Swarm support
Date: Wed, 24 Jun 2009 08:34:53 +0200	[thread overview]
Message-ID: <20090624063453.GA16846@volta.aurel32.net> (raw)

Hi all,

I am still trying to get a Broadcom Swarm boot on a recent kernel. I
have made some progress, but I am now stuck on another problem.

I am using a lmo 2.6.30 kernel, using the defconfig configuration, with
minor tweaks to get the IDE and EXT3 support working.

The boot process works correctly until it reaches userland:

| hda: max request size: 128KiB
| hda: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63
| hda: cache flushes not supported
|  hda: hda1 hda2
| eth0 (sb1250-mac): not using net_device_ops yet
| sb1250-mac.0: registered as eth0
| eth0: enabling TCP rcv checksum
| eth0: SiByte Ethernet at 0x10064000, address: 00:02:4c:fe:51:e0
| eth1 (sb1250-mac): not using net_device_ops yet
| sb1250-mac.1: registered as eth1
| eth1: enabling TCP rcv checksum
| eth1: SiByte Ethernet at 0x10065000, address: 00:02:4c:fe:51:e1
| usbmon: debugfs is not available
| ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
| TCP cubic registered
| NET: Registered protocol family 17
| NET: Registered protocol family 15
| RPC: Registered udp transport module.
| RPC: Registered tcp transport module.
| kjournald starting.  Commit interval 5 seconds
| EXT3-fs: mounted filesystem with writeback data mode.
| VFS: Mounted root (ext3 filesystem) readonly on device 3:2.
| Freeing unused kernel memory: 184k freed
| Kernel panic - not syncing: Attempted to kill init!
| Rebooting in 5 seconds..Passing control back to CFE...

This is with /sbin/init, but I get the exact same problem with /bin/sh.
Also the file is found, as otherwise the message is different. The same
partition when used with an older kernel (2.6.18) works perfectly.

I have the problem with both big and little endian, and with and without
SMP support.

Does anyone is able to run a recent kernel on such a board ? If yes,
could you please share the configuration file? Thanks in advance.

Best regards,
Aurelien

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

             reply	other threads:[~2009-06-24  6:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24  6:34 Aurelien Jarno [this message]
2009-06-24 22:18 ` Broadcom Swarm support Kaz Kylheku
2009-06-24 22:18   ` Kaz Kylheku
2009-06-25  1:48   ` icache flushing (Re: Broadcom Swarm support) Atsushi Nemoto
2009-06-26 21:19   ` Broadcom Swarm support Aurelien Jarno
2009-06-26 23:24   ` Ralf Baechle
2009-06-27  5:10     ` Aurelien Jarno
2009-06-27  9:14       ` Ralf Baechle
2009-06-27 13:59     ` Atsushi Nemoto
2009-06-27 15:48       ` Ralf Baechle
2009-06-27 16:09         ` Atsushi Nemoto
2009-06-27 16:11           ` Atsushi Nemoto
2009-06-29 19:08           ` Ralf Baechle
2009-06-30 14:00             ` Atsushi Nemoto
2009-07-06 13:56               ` Atsushi Nemoto
2009-06-27 15:49   ` Ralf Baechle
2009-06-30 17:10     ` Kaz Kylheku
2009-06-30 17:10       ` Kaz Kylheku

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=20090624063453.GA16846@volta.aurel32.net \
    --to=aurelien@aurel32.net \
    --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;
as well as URLs for NNTP newsgroup(s).