Sponsored Content
Full Discussion: bad trap & continuous reboot
Top Forums UNIX for Dummies Questions & Answers bad trap & continuous reboot Post 56704 by forbin24 on Friday 8th of October 2004 11:21:20 AM
Old 10-08-2004
bad trap & continuous reboot

I have a system that upon boot, will declare a bad trap and reboot, whereupon it encounters the same bad trap and reboots in an endless cycle until I stop it. I can get to the ok prompt. An attempt to boot in single user mode left the box completely hung and required a power cycle to re-establish any type of communication.

This box is a piece of equipment used for remote testing of communication lines. I've replaced the CPU with a known good and the problem persists. I'm afraid I need to replace the hard drive.

My question is, would wiping the hard drive clean, reloading the software and reconfiguring the unit possibly fix the problem? Below are logs of the trap and reboot sequence.

Rebooting with command:
Boot device: /iommu/sbus/espdma@5,8400000/esp@5,8800000/sd@0,0 File and args: -r
SunOS Release 5.6 Version Generic_105181-12 [UNIX(R) System V Release 4.0]
Copyright (c) 1983-1997, Sun Microsystems, Inc.
BAD TRAP: type=2 rp=f024342c addr=0 mmu_fsr=0 rw=0
: Illegal instruction
pid=0, pc=0xf59e52ec, sp=0xf0243478, psr=0x4900cc0, context=0
g1-g7: f00f2db0, 0, f596d7bd, f006acd8, 200, 1, f0244020
Begin traceback... sp = f0243478
Called from f59e336c, fp=f02434d8, args=f59a3648 f59a3648 8 0 0 ff00
Called from f009c148, fp=f0243538, args=f59a3648 0 20 0 f592ed58 f70
Called from f00775c0, fp=f0243598, args=f59a3648 0 f59e334c 1 f597be40 f006ae1c
Called from f0077478, fp=f02435f8, args=f59a3648 f59a3648 f59e3c64 f027d5e4 f5974d74 bfc
Called from f0115fd8, fp=f0243658, args=0 f59a3648 1 f59e3c64 3b f5978408
Called from f00f2b48, fp=f02436b8, args=f59783fc f59a3648 f027d5e4 0 f59783fc 0
Called from f00f4458, fp=f0243718, args=f59e3c64 3b f5978410 f5978408 f59783fc 0
Called from f5a6c3e8, fp=f0243898, args=ffffffff 0 ffffffff 4c 3b f59a3788
Called from f0077d94, fp=f02438f8, args=f5aa5000 f025df08 20 f592ebf0 1000 f5ab1000
Called from f5a8f234, fp=f0243968, args=f5aa5000 1 20 f592ebf0 1000 f5ab1000
Called from f5a6c268, fp=f02439d8, args=f028a658 0 f028a658 0 8 c00
Called from f0077d94, fp=f0243a38, args=f027cc9c f025def8 f5a6d584 f028b3a4 f5a6d400 0
Called from f0100888, fp=f0243a98, args=f5ab0000 f028c400 1000 f5911e40 1 0
Called from f00b4740, fp=f0243af8, args=f027cc00 4400ce7 0 44000e7 f0244020 f02798f0
Called from f00411c4, fp=f0243b88, args=f026012c 4400fe0 2000 44000e0 81c52000 f005fa54
Called from 105c5c, fp=0, args=13fc00 145ef0 12b000 f7 14203c 13fe4c
End traceback...
panic: Illegal instruction
rebooting...
Resetting ...
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Building a better mouse trap, or How many lines of code does it take to trap a mouse?

Hello all, I'm hoping to get a little insight from some of the wily veterans amongst you. I've written a script to check for new outgoing files to our vendors located on our ssl server. It seems to be working ok, but the final question here, will be one of logic, and/or a better way to... (4 Replies)
Discussion started by: mph
4 Replies

2. Solaris

different between soft reboot and hard reboot

Hi Guru's Can any want here could explain to me the different between soft reboot and hard reboot . Best Regards Seelan (3 Replies)
Discussion started by: seelan3
3 Replies

3. Solaris

Panic BAD TRAP errors

One of our Sun E450 machines crashed and has this message in the /var/adm/messages after it rebooted automatically. An extract of the log is below. I suspect it is memory, but I am not sure. Can anyone give me any ideas how to diagnose this correctly? Thanks Margaret Floyd Apr 10 08:18:54... (1 Reply)
Discussion started by: floydm
1 Replies

4. Shell Programming and Scripting

Cntl+z Trap is not detecting ??? Help required to add a trap detection ???

Hi folks, I have tried to add some trap detection in the below script....this script is used to monitor database activities...in a rather awkward way :rolleyes:.... The idea behind adding trap is that....this script creates lots of temporary files in the running folder to store the count... (1 Reply)
Discussion started by: frozensmilz
1 Replies

5. Solaris

BAD TRAP: type=30 rp=2a10001b840 addr=2a000012040 mmu_fsr=0

Hello Gurus, I got a system reboot due to "unix: BAD TRAP: type=30 rp=2a10001b840 addr=2a000012040 mmu_fsr=0" on SUNW,Netra-CP2300. I guess it is caused by HW fault but not very sure, and don't know which part should be relaced incase it is HW reason really. Sincerely appreciate for your... (7 Replies)
Discussion started by: fangfang
7 Replies

6. Solaris

X2200 in reboot loop & mounting ZFS drive on other boxes

So I was patching a Solaris 10 U08 X86 X2200 box in preparation for an Oracle upgrade. Rebooted the box because the patches failed and the box will not boot successfully. I need to back up the zones on the 2 drives before going further. I pulled the drives and attempted to mount them on my Ubuntu... (0 Replies)
Discussion started by: LittleLebowski
0 Replies

7. Homework & Coursework Questions

VM trap may work differently than a pure install trap.

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: That is the last reply I received from my instructor, and I'm looking for some alternatives. When using... (2 Replies)
Discussion started by: newuser45
2 Replies

8. Shell Programming and Scripting

File Move & Sort by Name - Kick out Bad File Names & More

I have a dilemma, we have users who are copying files to "directory 1." These images have file names which include the year it was taken. I need to put together a script to do the following: Examine the file naming convention, ensuring it's the proper format (e.g. test-1983_filename-123.tif)... (8 Replies)
Discussion started by: Nvizn
8 Replies

9. Solaris

Df reporting double size of du after fsck & reboot

Solaris 8 running on a Sparcstation 5 (Aurora) with 170MHz processor and 256MB ram This is AFTER doing fsck and reboot. 820030k vs 385252k All other files in /usr/asm not in /usr/asm/sys or /usr/asm/data amount to 43k. The /usr/asm/lost+found is 8k. somehow df and other applications... (3 Replies)
Discussion started by: lcoreyl
3 Replies
trap(1)                                                            User Commands                                                           trap(1)

NAME
trap, onintr - shell built-in functions to respond to (hardware) signals SYNOPSIS
sh trap [ argument n [n2...]] csh onintr [-| label] ksh *trap [ arg sig [ sig2...]] DESCRIPTION
sh The trap command argument is to be read and executed when the shell receives numeric or symbolic signal(s) (n). (Note: argument is scanned once when the trap is set and once when the trap is taken.) Trap commands are executed in order of signal number or corresponding symbolic names. Any attempt to set a trap on a signal that was ignored on entry to the current shell is ineffective. An attempt to trap on signal 11 (memory fault) produces an error. If argument is absent all trap(s) n are reset to their original values. If argument is the null string this signal is ignored by the shell and by the commands it invokes. If n is 0 the command argument is executed on exit from the shell. The trap command with no arguments prints a list of commands associated with each signal number. csh onintr controls the action of the shell on interrupts. With no arguments, onintr restores the default action of the shell on interrupts. (The shell terminates shell scripts and returns to the terminal command input level). With the - argument, the shell ignores all inter- rupts. With a label argument, the shell executes a goto label when an interrupt is received or a child process terminates because it was interrupted. ksh trap uses arg as a command to be read and executed when the shell receives signal(s) sig. (Note that arg is scanned once when the trap is set and once when the trap is taken.) Each sig can be given as a number or as the name of the signal. trap commands are executed in order of signal number. Any attempt to set a trap on a signal that was ignored on entry to the current shell is ineffective. If arg is omitted or is -, then the trap(s) for each sig are reset to their original values. If arg is the null (the empty string, e.g., "" ) string then this signal is ignored by the shell and by the commands it invokes. If sig is ERR then arg will be executed whenever a command has a non- zero exit status. If sig is DEBUG then arg will be executed after each command. If sig is 0 or EXIT for a trap set outside any function then the command arg is executed on exit from the shell. The trap command with no arguments prints a list of commands associated with each signal number. On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways: 1. Variable assignment lists preceding the command remain in effect when the command completes. 2. I/O redirections are processed after variable assignments. 3. Errors cause a script that contains them to abort. 4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari- able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not performed. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
csh(1), exit(1), ksh(1), sh(1), attributes(5) SunOS 5.10 23 Oct 1994 trap(1)
All times are GMT -4. The time now is 03:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy