From: Jean-Francois Guilmard (jfguilmard@easyplanet.com)
Date: Mon Jul 21 2003 - 15:48:59 EDT
Hi,
Thx a lot for the answers I received !
I managed to boot the system once thanks to the advice you gave me. I
have edited the /etc/system file BUT:
A problem remains: The server boot only sometimes, if not it is looping
on trying to boot.
Here is what I get when the system is not booting:
Executing last command: boot
Boot device: disk File and args:
SunOS Release 5.8 Version Generic_108528-12 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights
reserved.
|
panic[cpu0]/thread=10408000: BAD TRAP: type=31
rp=10407590 addr=310007e959e mmu_
fsr=0
: trap type = 0x31
addr=0x310007e959e
pid=0, pc=0x1002d04c, sp=0x10406e31,
tstate=0x9980001605, context=0x0
g1-g7: 10418000, 9e, 310007e9500, 7, 13c00, 0, 10408000
00000000104071b0 unix:die+a4 (31, 10407590, 310007e959e,
0, 10407590, c8488003)
%l0-3: 0000000000000001 7fffffffffffffd8
8000000000000000 0800000000000000
%l4-7: 0000000000000009 0000000000000002
0000000000000000 0000000000001638
0000000010407290 unix:trap+8b8 (300007e8000, 1, 6, 0,
10407590, 0)
%l0-3: 0000000000000001 000003000004bf88
0000000010423a00 0000000000000000
%l4-7: 0000000000000031 000000001041c730
0000000000010000 0000000000000000
00000000104073d0 unix:sfmmu_tsb_miss+640 (104286c8, 0,
3000004bf88, 0, 3000004bf
88, 19)
%l0-3: 00000300007e8000 0000000000000004
0000000000000000 000003100007f120
%l4-7: 00000300007e8000 000003000007c8f2
0000000000000000 0000030000400003
00000000104074e0 unix:prom_rtt+0 (10, 10418270,
10418270, 0, 0, 3000007ca61)
%l0-3: 0000000000000006 0000000000001400
0000009980001605 0000000010018de4
%l4-7: 0000000000000000 0000000010407717
000000000000000d 0000000010407590
0000000010407630 unix:page_ctr_sub+38 (13c00, 1, 0,
10418200, 4, 310007ea700)
%l0-3: 000003000007c8d8 000003000007c8e9
000003000007f800 0000000000000011
%l4-7: 00000300000815d8 00000000000002c0
000003000007f780 000000001045c0e8
00000000104076e0 unix:page_promote+268 (200, 0, 0,
1040f5f8, 1041bc70, 1041bd60)
%l0-3: 000000001040f600 000000001040f5f8
000000001041bd18 0000000000000001
%l0-3: 000000001040f600 000000001040f5f8
000000001041bd18 0000000000000001
00000000104077b0 unix:page_freelist_coalesce+e8
(1041c1d4, 10050990, 0, 10418210
, 0, 10418210)
%l0-3: 0000000000000003 0000000000000000
0000000000000000 0000000010418268
%l4-7: 0000000010418258 0000000000000003
00000000000001a0 000000000000009f
0000000010407870 unix:startup_vm+1b8 (0, 1041d578, 0,
2000, 2000, 0)
%l0-3: 000000001041a800 0000000010423400
0000000000000000 00000310014f8000
%l4-7: 0000000010418000 000000001041c800
000000001041bc00 000000001041a800
0000000010407970 unix:startup+2c (10428400, 0, 0,
66000000, 2000, ffffffffffffff
ff)
%l0-3: 0000000010024120 000000000000cf48
0000000000001638 0000000000000000
%l4-7: 0000000010462470 00000000002f1224
00000000000b7638 0000000000001638
0000000010407a20 genunix:main+4 (1040d400, 2000,
10407ec0, 10408030, fff2, 1004e
bcc)
%l0-3: 0000000010408000 0000000000000001
0000000000000015 0000000000000e99
%l4-7: 0000000010428c20 0000000010462470
00000000000cd578 0000000000000540
skipping system dump - no dump device configured
rebooting...
Res
LOM event: +0h53m24s host reset
During this loop, if I press during 5 sec the shutting down button on
the back of the server, and then send a poweron from the console, the
server is boot well with the following results:
Executing last command: boot
Boot device: disk File and args:
SunOS Release 5.8 Version Generic_108528-12 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
WARNING: invalid vector intr: number 0x7de, pil 0x0
configuring IPv4 interfaces: dmfe0.
Hostname: ep1jfs3.easyplanet.net
NOTICE: dmfe0: PHY 1 link up 100 Mbps Full-Duplex
NOTICE: dmfe1: PHY 1 link down
The system is coming up. Please wait.
checking ufs filesystems
/dev/rdsk/c0t0d0s7: is stable.
So, I guess there is a problem somewhere, but I don't know where ...
Maybe I didn't edit well the /etc/system file? Here is it:
*ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
*
* SYSTEM SPECIFICATION FILE
*
* moddir:
*
* Set the search path for modules. This has a format similar to
the
* csh path variable. If the module isn't found in the first
directory
* it tries the second and so on. The default is /kernel
/usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules
* root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
*
* (Swap device configuration should be specified in /etc/vfstab.)
* exclude:
*
* Modules appearing in the moddir path which are NOT to be loaded,
* even if referenced. Note that `exclude' accepts either a module
name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys
* forceload:
*
* Cause these modules to be loaded at boot time, (just before
mounting
* the root filesystem) rather than at first reference. Note that
* forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it
will
* be installed.
*
* Example:
* forceload: drv/foo
* set:
*
* Set an integer variable in the kernel or a module to a new
value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named
'test_module'
*
* set test_module:debug = 0x13
Thx for everything !!!
Jef
PS: follow the history of the message I sent:
Hi,
I'm a newbie with sun Netra X1, and I've inherited a configuration that
doesn't work: The last administrator has edited the /etc/system and put
a wrong line in it. The system refused to boot again, so he made plenty
of things to make it boot again whitout any success.
Nowadays, whatever I do, i always have a timeout waiting for RARP/ARP
packet. So I guess the server is trying to boot on the net ?? What can I
do to stop that? Is it linked to the problem in /etc/system? What is
your advice about that last problem? Without any cdrom reader, nor
floppy, I can't manage to make it boot in order to edit the etc system
...
THX a lot,
Jef
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:47 EDT