Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Failing to boot - DMVA problem Post 102409 by RTM on Friday 17th of March 2006 01:57:41 PM
Old 03-17-2006
Quote:
The system did a watchdog reset.

Watchdog resets are usually hardware related. They occur when a processor
gets a second trap while in the middle of initial processing of a first trap,
during the period when trap handling is disabled. During this period, the
system does not know what to do with the second trap, so it just stops.
Software can cause this, but most Solaris bugs in this vein have been fixed.
A problematic piece of hardware, on the other hand, could cause spurious traps to be sent, some in the middle of processing of legitimate traps.

The system leaves no messages when it reboots.

This could be a watchdog reset on a system with its obprom "watchdog-reboot?"
flag set to true.
OS reload probably won't help you at all.
 

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
WATCHDOG(9)						   BSD Kernel Developer's Manual					       WATCHDOG(9)

NAME
watchdog -- software and hardware watchdog facility SYNOPSIS
#include <sys/watchdog.h> void watchdog_fn(void *private, u_int cmd, int *error); EVENTHANDLER_REGISTER(watchdog_list, watchdog_fn, private, 0); EVENTHANDLER_DEREGISTER(watchdog_list, eventhandler_tag); DESCRIPTION
To implement a watchdog in software or hardware, only a single function needs to be written and registered on the global watchdog_list. The function must examine the cmd argument and act on it as follows: If cmd is zero, the watchdog must be disabled and the error argument left untouched. If the watchdog cannot be disabled, the error argument must be set to EOPNOTSUPP. Else the watchdog should be reset and configured to a timeout of (1 << (cmd & WD_INTERVAL)) nanoseconds or larger and the error argument be set to zero to signal arming of a watchdog. If the watchdog cannot be configured to the proposed timeout, it must be disabled and the error argument left as is (to avoid hiding the arm- ing of another watchdog). There is no specification of what the watchdog should do when it times out, but a hardware reset or similar ``drastic but certain'' behaviour is recommended. SEE ALSO
watchdog(4) AUTHORS
The watchdog facility and this manual page was written Poul-Henning Kamp <phk@FreeBSD.org>. BSD
February 28, 2004 BSD
All times are GMT -4. The time now is 01:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy