From: alexmcwhirter@triadic.us
To: sparclinux@vger.kernel.org
Subject: SILO Issues on an E4900
Date: Mon, 12 Sep 2016 00:02:10 +0000 [thread overview]
Message-ID: <62477e32a682342782e652fcfdbf9fb5@triadic.us> (raw)
I was wondering if anyone has posted here about SILO failing to load on
Serengeti and Amazon machines? These would be the Sun Fire 3800, 4800,
4810, 6800, E2900, E4900, and E6900. These machines are similar in the
fact that they all use modularized system controllers running VxWorks
which in turn runs a Java implementation of the SSC software.
On an E4900 i am getting an error nearly identical to this users post
about a 6800.
I'm having trouble trying to boot off of an install CD (I don't have
networking set up at the moment, but could probably get that set up).
I'm
trying to install on a 2nd "B" domain on the machine, with a single
CPU/memory board.
When I try to issue the command to boot from the CDROM:
{14} ok boot /ssm@0,0/pci@1a,700000/pci@1/SUNW,isptwo@4/sd@6,0:f
or
{14} ok boot /ssm@0,0/pci@1a,700000/pci@1/SUNW,isptwo@4/sd@6,0
I immediately get the error message (no text between command and this):
<-------------------
ERROR: Illegal Instruction
debugger entered.
<-------------------
Looking at where the PC is and what's there in memory (seems to be same
for sd@6,0 and sd@6,0:f):
<-------------------
{14} ok %pc .
4004
{14} ok 4000 40 dump
\/ 1 2 3 4 5 6 7 8 9 A B C D E F
0123456789ABCDEF
00000004000 01 03 01 07 00 00 18 f0 00 00 00 00 00 00 01 88
................
00000004010 00 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00
......@.........
00000004020 40 00 00 02 a0 10 00 0f 33 00 00 16 b2 16 61 00
@.......3.....a.
00000004030 23 00 00 10 a2 14 60 00 b0 10 00 11 af c3 e0 c0
#.....`.........
<-------------------
I can boot a copy of Solaris installed on the disk just fine. Here's a
copy of the output from the openboot prom initialising:
<-------------------
Resetting ...
Copying IO prom to Cpu dram
.{/N0/SB5/P0} @(#) lpost 5.15.2 2003/08/04 10:27
{/N0/SB5/P0} Copyright 2001-2003 Sun Microsystems, Inc. All rights
reserved.
{/N0/SB5/P0} Use is subject to license terms.
..................................
{/N0/SB5/P0} Running PCI IO Controller Basic Tests
{/N0/SB5/P0} Jumping to memory 00000000.00000020 [00000010]
{/N0/SB5/P0} System PCI IO post code running from memory
{/N0/SB5/P0} @(#) lpost 5.15.2 2003/08/04 10:28
{/N0/SB5/P0} Copyright 2001-2003 Sun Microsystems, Inc. All rights
reserved.
{/N0/SB5/P0} Use is subject to license terms.
{/N0/SB5/P0} Subtest: PCI IO Controller Register Initialization for aid
0x1a
{/N0/SB5/P0} Running PCI IO Controller Functional Tests
{/N0/SB5/P0} Running SBBC Basic Tests
{/N0/SB5/P0} Subtest: SBBC PCI Reg Initialization for aid 0x1a
{/N0/SB5/P0} Running PCI IO Controller Basic Tests
{/N0/SB5/P0} Subtest: PCI IO Controller Register Initialization for aid
0x1b
{/N0/SB5/P0} Running PCI IO Controller Functional Tests
{/N0/SB5/P0} @(#) lpost 5.15.2 2003/08/04 10:27
{/N0/SB5/P0} Copyright 2001-2003 Sun Microsystems, Inc. All rights
reserved.
{/N0/SB5/P0} Use is subject to license terms.
{/N0/SB5/P1} @(#) lpost 5.15.2 2003/08/04 10:27
{/N0/SB5/P1} Copyright 2001-2003 Sun Microsystems, Inc. All rights
reserved.
{/N0/SB5/P1} Use is subject to license terms.
{/N0/IB7/P0} Passed
{/N0/IB7/P1} Passed
{/N0/SB5/P0} Running Domain Level Tests
{/N0/SB5/P2} @(#) lpost 5.15.2 2003/08/04 10:27
{/N0/SB5/P3} @(#) lpost 5.15.2 2003/08/04 10:27
{/N0/SB5/P2} Copyright 2001-2003 Sun Microsystems, Inc. All rights
reserved.
{/N0/SB5/P2} Use is subject to license terms.
{/N0/SB5/P3} Copyright 2001-2003 Sun Microsystems, Inc. All rights
reserved.
{/N0/SB5/P3} Use is subject to license terms.
{/N0/SB5/P0} Running Domain Basic Tests
{/N0/SB5/P0} Running Domain Advanced Tests
{/N0/SB5/P0} Running Domain Stick Sync Tests
{/N0/SB5/P0} Running Domain Verify Stick Sync Tests
{/N0/SB5/P0} DCB_DECOMP_OBP command succeeded
{/N0/SB5/P0} Committing retained memory
00000000.0096c000-00000000.0096dfff
{/N0/SB5/P0} Retaining 00000000.0096c000-00000000.0096dfff
{/N0/SB5/P0} Committing retained memory
00000000.00984000-00000000.00985fff
{/N0/SB5/P0} Retaining 00000000.00984000-00000000.00985fff
{/N0/SB5/P0} CPU 21 clearing 00000000.00000000 to 00000000.0025b000
{/N0/SB5/P0} CPU 22 clearing 00000000.0025b000 to 00000000.004b6000
{/N0/SB5/P0} CPU 23 clearing 00000000.004b6000 to 00000000.00711000
{/N0/SB5/P0} CPU 20 clearing 00000000.00711000 to 00000000.0096c000
{/N0/SB5/P0} CPU 21 clearing 00000000.0096e000 to 00000000.00973800
{/N0/SB5/P0} CPU 22 clearing 00000000.00973800 to 00000000.00979000
{/N0/SB5/P0} CPU 23 clearing 00000000.00979000 to 00000000.0097e800
{/N0/SB5/P0} CPU 20 clearing 00000000.0097e800 to 00000000.00984000
{/N0/SB5/P0} CPU 21 clearing 00000000.00986000 to 00000002.00724800
{/N0/SB5/P0} CPU 22 clearing 00000002.00724800 to 00000004.004c3000
{/N0/SB5/P0} CPU 23 clearing 00000004.004c3000 to 00000006.00261800
{/N0/SB5/P0} CPU 20 clearing 00000006.00261800 to 00000008.00000000
{/N0/SB5/P0} Decompress OBP done
{/N0/SB5/P0} DCB_ENTER_OBP command succeeded
{/N0/SB5/P1} DCB_ENTER_OBP command succeeded
{/N0/SB5/P2} DCB_ENTER_OBP command succeeded
{/N0/SB5/P3} DCB_ENTER_OBP command succeeded
Sun Fire 6800
OpenFirmware version 5.15.2 (08/04/03 10:27)
Copyright 2001-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
SmartFirmware, Copyright (C) 1996-2001. All rights reserved.
32768 MB memory installed, Serial #51339462.
Ethernet address 0:3:ba:f:60:c6, Host ID: 830f60c6.
<-------------------
Thanks for any help!
Pat
Illegal instruction is quite vague, but the OBP does enter a debugging
subsystem at the time of the error. I have seen people point fingers at
exhausting all of the trap levels causing a similar error message, but
without knowing more about what is actually happening i am not so sure.
I have relatively easy access to the machine in question if anyone has
any ideas at pin pointing the problem? This is quite a broad range of
machines that seem to be affected, so i would very much like to work on
getting at least SILO able to load a kernel. Whether or not the kernel
has issues of it's own at that point is another matter.
next reply other threads:[~2016-09-12 0:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 0:02 alexmcwhirter [this message]
2016-11-24 9:35 ` SILO Issues on an E4900 Louis Liu
2016-11-24 10:00 ` John Paul Adrian Glaubitz
2016-11-24 16:10 ` David Miller
2016-11-24 16:22 ` John Paul Adrian Glaubitz
2016-11-24 21:26 ` vincent
2016-11-24 22:04 ` Mark Cave-Ayland
2016-11-25 8:14 ` Louis Liu
2016-11-25 20:30 ` Louis Liu
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=62477e32a682342782e652fcfdbf9fb5@triadic.us \
--to=alexmcwhirter@triadic.us \
--cc=sparclinux@vger.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 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.