Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Failing to boot - DMVA problem Post 102398 by forbin24 on Friday 17th of March 2006 12:55:46 PM
Old 03-17-2006
Failing to boot - DMVA problem

SunOS 5.6

I have a remote test system (test T1/T3, etc) that runs SunOS 5.6. I rebooted the system for no other reason than that it had been up for over 300 days. It failed to boot completely.

I have an ok prompt and when I type boot, I see the following messages..
Boot device: /iommu/sbus/espdma@5,8400000/esp@5,8800000/sd@0,0 File and args: -r
Short read. 0x2000 chars read
Short read. 0x2000 chars read
Short read. 0x2000 chars read
Short read. 0x2000 chars read
|
Watchdog Reset

There are some diagnostic tools that pointed me to the problem:
CS4231 ASIC SelfTest Passed.
Error: DVMA failure internal loopback
expected 2 received 0
Error: DVMA failure internal loopback
expected 4 received 0
Error: DVMA failure internal loopback
expected 8 received 0
Error: DVMA failure internal loopback
expected 10 received 0
Error: DVMA failure internal loopback
expected 20 received 0
Error: DVMA failure internal loopback
expected 40 received 0
Error: DVMA failure internal loopback
expected 80 received 0
Selftest failed. Return code = 7
ok

Based on this output, I used another diag tool to check the memory map and got the following results:
Virtual : 0000.0002
Context : @ 0.01ff.f000 001f.eec1 # 0
Region : @ 0.01fe.ec00 001f.ee71
Segment : @ 0.01fe.e700 001f.ee61
Page : @ 0.01fe.e600 0000.001c Invalid
Stack Underflow

So it appears to me that the system can't find the pages it's looking for. I'm in very short supply of CPUs so will probably attempt to reload the OS/software. This is a bit of a hassle because it's a remote site.

What I'm looking for is opinions on what the most likely cause of the problem is and if there is some way to possibly fix this without a CPU replacement or OS/software reload. I've already reseated the CPU and I get the same results.

Thanks for you time!
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Boot problem

we have a problem with a server UNIX SUN OS 5.7 : we tried to reboot it and we have the following error message : "boot load failed the file just loaded does not appear to be executable " we booted the server in single user mode with the cdrom we made the mirrored disk bootable we tried... (2 Replies)
Discussion started by: farzolito
2 Replies

2. UNIX for Advanced & Expert Users

Boot Problem

Hi All. Yesterday my pc worked fine. Today when booting the sequence gets just past mounting the root filesystem - it then says ' Module dependencies up to date (no new kernel modules found).' At this point it hangs and goes no further! Does this sound familiar to anyone? I am running... (2 Replies)
Discussion started by: silvaman
2 Replies

3. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

4. UNIX for Advanced & Expert Users

unix server failing to boot

i have unix 5.4 running on team server hs failing to boot. when i turn it on, it prints the following lines on the screen and just stops: module ID 01: (0011) Main power supply ok module ID 01: (0012) checks ok module ID 01: (0020) test of SCSI device 0 x 0 in progress module ID 01:... (4 Replies)
Discussion started by: ronst
4 Replies

5. Solaris

Boot problem

Hi everyone, I have sun fire280R machine before i it is installed with solaris5.9 now i want to upgrade it but it not booting from the cd rom ....OK prompt also not comming i dont have solaris keyboard to press stop-A key...i have a intel supported keyboard ...what may be the problem it is... (1 Reply)
Discussion started by: alakshmanrao
1 Replies

6. Solaris

flar restore with svm mirrors failing to create boot image

In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies

7. UNIX for Dummies Questions & Answers

boot problem

hello i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message: Enabling system bus....... Done Initializing CPUs......... Done Initializing boot memory.. RAM-Copy CRC failure!Can't start: No image found FATAL: Can't find/decompress... (0 Replies)
Discussion started by: bahjatm
0 Replies

8. Solaris

boot problem

hello i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message: Enabling system bus....... Done Initializing CPUs......... Done Initializing boot memory.. RAM-Copy CRC failure!Can't start: No image found FATAL: Can't find/decompress... (12 Replies)
Discussion started by: bahjatm
12 Replies

9. Solaris

Boot problem

Hi all, I have the the following SCSI diagnostic codes shown in the attached photo I suspect disk drive failure what can I do further to diagnose the disk. and if possible to boot into OS again. (5 Replies)
Discussion started by: h@foorsa.biz
5 Replies

10. Solaris

Problem boot Solaris

Hi I have a problem on a server, when he boot I have this type of message loop, do you know what it corresponds to ? ( requesting internet Adress for 0:3:ba:fa:33:91 ) Regards Sun Fire V240, No Keyboard Copyright 2007 Sun Microsystems, INC. All rights reserved. openboot 4.22.33,... (10 Replies)
Discussion started by: yoyo-tns
10 Replies
syncloop(1M)						  System Administration Commands					      syncloop(1M)

NAME
syncloop - synchronous serial loopback test program SYNOPSIS
/usr/sbin/syncloop [-cdlstv] device DESCRIPTION
The syncloop command performs several loopback tests that are useful in exercising the various components of a serial communications link. Before running a test, syncloop opens the designated port and configures it according to command line options and the specified test type. It announces the names of the devices being used to control the hardware channel, the channel number (ppa) corresponding to the device argument, and the parameters it has set for that channel. It then runs the loopback test in three phases. The first phase is to listen on the port for any activity. If no activity is seen for at least four seconds, syncloop proceeds to the next phase. Otherwise, the user is informed that the line is active and that the test cannot proceed, and the program exits. In the second phase, called the "first-packet" phase, syncloop attempts to send and receive one packet. The program will wait for up to four seconds for the returned packet. If no packets are seen after five attempts, the test fails with an excoriating message. If a packet is returned, the result is compared with the original. If the length and content do not match exactly, the test fails. The final phase, known as the "multiple-packet" phase, attempts to send many packets through the loop. Because the program has verified the integrity of the link in the first-packet phase, the test will not fail after a particular number of timeouts. If a packet is not seen after four seconds, a message is displayed. Otherwise, a count of the number of packets received is updated on the display once per second. If it becomes obvious that the test is not receiving packets during this phase, the user may wish to stop the program manually. The number and size of the packets sent during this phase is determined by default values, or by command line options. Each returned packet is com- pared with its original for length and content. If a mismatch is detected, the test fails. The test completes when the required number of packets have been sent, regardless of errors. After the multiple-packet phase has completed, the program displays a summary of the hardware event statistics for the channel that was tested. The display takes the following form: CRC errors Aborts Overruns Underruns In<-Drops-> Out 0 0 0 0 0 0 This is followed by an estimated line speed, which is an approximation of the bit rate of the line, based on the number of bytes sent and the actual time that it took to send them. OPTIONS
The options for syncloop are described in the following table: Option Parameter Default Description -c packet_count 100 Specifies the number of pack- ets to be sent in the multi- ple-packet phase. -d hex_data_byte random Specifies that each packet will be filled with bytes with the value of hex_data_byte. -l packet_length 100 Specifies the length of each packet in bytes. -s line_speed 9600 Bit rate in bits per second. -v Sets verbose mode. If data errors occur, the expected and received data is dis- played. -t test_type none A number, from 1 to 4, that specifies which test to per- form. The values for test_type are as follows: 1: Internal loopback test. Port loopback is on. Transmit and receive clock sources are internal (baud rate genera- tor). 2: External loopback test. Port loopback is off. Transmit and receive clock sources are internal. Requires a loopback plug suitable to the port under test. 3: External loopback test. Port loopback is off. Transmit and receive clock sources are external (modem). Requires that one of the local modem, the remote modem, or the remote system be set in a loopback configu- ration. 4: Test using prede- fined parameters. User defines hardware configura- tion and may select port parameters using the syncinit(1M) command. All numeric options except -d are entered as decimal numbers (for example, -s 19200). If you do not provide the -t test_type option, syn- cloop prompts for it. EXAMPLES
Example 1: A sample display of using the syncloop command. In the following command syncloop uses a packet length of 512 bytes over the first CPU port: example# syncloop -l 512 zsh0 In response to the above command, syncloop prompts you for the test option you want. The following command performs an internal loopback test on the first CPU port, using 5000 packets and a bit rate of 56Kbps: example# syncloop -t 1 -s 56000 -c 5000 zsh0 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
syncinit(1M), syncstat(1M), attributes(5), zsh(7D) DIAGNOSTICS
device missing minor device number The name device does not end in a decimal number that can be used as a minor device number. invalid packet length: nnn The packet length was specified to be less than zero or greater than 4096. poll: nothing to read poll: nothing to read or write. The poll(2) system call indicates that there is no input pending and/or that output would be blocked if attempted. len xxx should be yyy The packet that was sent had a length of yyy, but was received with a length of xxx. nnn packets lost in outbound queueing nnn packets lost in inbound queueing A discrepancy has been found between the number of packets sent by syncloop and the number of packets the driver counted as transmit- ted, or between the number counted as received and the number read by the program. WARNINGS
To allow its tests to run properly, as well as prevent disturbance of normal operations, syncloop should only be run on a port that is not being used for any other purpose at that time. SunOS 5.10 9 Mar 1993 syncloop(1M)
All times are GMT -4. The time now is 09:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy