06-03-2009
place of NVRAM
Ok, I see
That's very interesting because without SCC server shuttind down after 60 sec
I solved problem with SCC but server still can't get "ok> " prompt. It's looping in CPU test and give red exception error (RED State Exception
Error enable reg: 0000.0000.0000.0000
CPU: 0000.0000.0000.0001
TL=0000.0000.0000.0005 TT=0000.0000.0000.0010
TPC=0000.0000.f000.4200 TnPC=0000.0000.f000.4204 TSTATE=0000.0044.1500.1500)
The same result is with one, two and three CPU module(4 cpu module exist). Because of that I think this is not a CPU problem.
There are no other errors display except CPU looping and can't get ok> !!!
If a batery of nvram is low the "ok>" promt must appear.
Any advice?
Last edited by Alisher; 06-18-2009 at 05:32 AM..
10 More Discussions You Might Find Interesting
1. Solaris
Got an curious issue.
I applied 109147-39 to, oh 15 or so various systems all running Jumpstarted Solaris 8. When I hit the first two V440s, they both failed with Return code 139. All non shell commands segfaulted from then on.
The patch modified mainly the linker libraries and commands.
... (2 Replies)
Discussion started by: BOFH
2 Replies
2. Solaris
Hello,
I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Discussion started by: Tibor
1 Replies
3. Solaris
Dear All,
I am facing a specfic problem with my New SunFire T2000.Recently we bought new sunfire T2000 sparc server.When i am trying to install solaris 10 through cdrom , I get error messgae
Error:Last Trap: Instaruction Access Exception
{0} ok boot cdrom
Boot device:... (6 Replies)
Discussion started by: solaris8in
6 Replies
4. Solaris
Hello,
I am seeing error messages in V440 (OS = solaris 8). I have copied here :
The system does not reboot constantly and it is up for last 67 days. One more interesting thing I found, I see errors start appearing at 4:52AM last until 6am and again start at 16:52am on same day..
I... (5 Replies)
Discussion started by: upengan78
5 Replies
5. Solaris
Hi,
I was asked to connect a KVM screen to a Sun Fire V440 last night so I connected it up but no joy and nothing on the KVM screen. I was told that a reboot may fix the problem so connected to the ALOM and rebooted. On the plus side, the KVM screen now works but I lost the ALOM connection.
... (0 Replies)
Discussion started by: jimmy54321
0 Replies
6. Solaris
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies
7. Solaris
Dear Team,
I need some expert advice to my problem.
We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Discussion started by: sudhansu
5 Replies
8. Solaris
Hi,
I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is
Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken.
Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies
9. Solaris
Hi,
I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either.
Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies
10. Solaris
Hi,
I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error:
WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies
SCC(4) BSD Kernel Interfaces Manual SCC(4)
NAME
scc -- Zilog 8530 Serial Communications Controller interface
SYNOPSIS
scc* at ioasic? offset ?
DESCRIPTION
The scc driver provides support for the Zilog 8530 Serial Communications Controller (SCC) via the IOASIC found on DECstation 5000 models in
the /100, /20, and /240 series (supported by NetBSD/pmax).
Each SCC device has two serial ports. The DECstation 5000 model 20 provides one SCC device. Other models provide two, but one port of each
device is dedicated to mouse and keyboard input, respectively.
Input and output for each line may set to one of following baud rates: 50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800, 9600,
19200, 38400, or 57600.
Speeds up to 230400 are supported by the chip and the motherboard, but speeds higher than 57600 do not work reliably without an external
clock signal.
FILES
/dev/ttya
/dev/ttyb
/dev/ttyc
/dev/ttyd
The mapping from units to serial-hardware outlets is idiosyncratic. The even ports are wired serial connectors and the odd-numbered ports
are reserved for mouse and keyboard.
On machines with one port like Personal DECstations, the single device is ttya.
On the 5000/1xx and 5000/2xx, the first serial port (default serial console) is ttyc and the second port is ttya.
SEE ALSO
intro(4), ioasic(4), ttys(5), MAKEDEV(8)
HISTORY
The scc driver first appeared in 4.4BSD.
The scc driver was also used for the IOASIC SCC found in DEC Alpha model 3000 TurboCHANNEL based systems; NetBSD/alpha has since been con-
verted to use the machine-independent zstty(4).
BUGS
The IOASIC provides internal DMA channels that can be programmed to transfer up to 4096 bytes of data into, or out, of an SCC without further
software intervention. This feature of the IOASIC is not yet supported.
The mapping from device-special files (major and minor number) to chip and port is arguably backwards. ULTRIX tries to hide the hardware
mapping, but NetBSD does not. Users wanting to use ULTRIX compatible tty names /dev/tty0 and /dev/tty1 for the scc comm-port lines should
make links or device-special files which match their hardware setup.
BSD
April 24, 2003 BSD