Sun Fire v880 when booting shows the following:
Takes too much to boo then shows the following WARNINGS: pcisch1 : ino 0x4 has been blocked
WARNING : qlc0 : interrupt has been blocked
WARNING : pcisch1 : ino 0x4 has been blocked
then the machine writes messages which i could not get hold of and reboots .
It is recycling betwee rebooting and panicing .
Thank you for your help
Debbol
Next time the server boots stop it at the ok prompt and set auto-boot? to false. Then pass the server through maximum diagnostics 3 or 4 times, making sure you are on the console to catch any errors.
If these pass ok, try and see if the server will boot from CD into single user mode.
You beat me to it Stuart! and as always very detailed!
This may be helpful:
<a href="http://sunsolve8.sun.com/search/document.do?assetkey=1-26-57160-1& ;searchclause=" target="_blank"> http://sunsolve8.sun.com/search/document.do?assetkey=1-26-57 160-1&searchclause=</a>
Thanks for your reply ,
I did try the the workaround on the link. The customer has told me that they did not do any thing .
It is not only that the machine panics and displays the WARNINGs , it takes about an hour to show the WARNINGs
any help is highly appreciated
Debbol
stumoor,
It does boot from a cdrom into single mode. I have even installed on it Solaris 8 , but same problem comes when it reboots ,
I have done setenv auto-boot? false , reset-all, and reboot!
it also takes to show
WARNING : qlc0 : interrupt has been blocked
WARNING : pcisch1 : ino 0x4 has been blocked
Thank your for your help
Hi there,
It did pass the diagnostic.
0:0>Basic Memory Test....Done
0:0>Full CPU Test....Done
0:0>Memory Block....Done
0:0>IO-Bridge Tests....Done
0:0>Full Memory Test....Done
0:0>Enable Errors....Done
0:0>INFO:
0:0>POST Passed all devices.
0:0>POST:Return to OBP.
POST Reset
Enabling system bus....... Done
Probing Memory............ Done
Initializing CPUs......... Done
Initializing boot memory.. Done
Initializing OpenBoot
Probing system devices
Probing I/O buses
Probing system devices
Probing I/O buses
Sun Fire 880, Keyboard Present
Copyright 1998-2004 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.15.1, 4096 MB memory installed, Serial #52536809.
Ethernet address 0:3:ba:21:a5:e9, Host ID: 8321a5e9.
Running diagnostic script obdiag/normal
Testing /<a href="mailto:pci@8" target="_blank">pci@8</a>,600000/<a href="mailto:network@1" target="_blank">network@1</a>
Testing /<a href="mailto:pci@8" target="_blank">pci@8</a>,600000/SUNW,<a href="mailto:qlc@2" target="_blank">qlc@2</a>
Testing /<a href="mailto:pci@9" target="_blank">pci@9</a>,700000/<a href="mailto:ebus@1" target="_blank">ebus@1</a>/<a href="mailto:i2c@1" target="_blank">i2c@1</a>,2e
Testing /<a href="mailto:pci@9" target="_blank">pci@9</a>,700000/<a href="mailto:ebus@1" target="_blank">ebus@1</a>/<a href="mailto:i2c@1" target="_blank">i2c@1</a>,30
Testing /<a href="mailto:pci@9" target="_blank">pci@9</a>,700000/<a href="mailto:ebus@1" target="_blank">ebus@1</a>/<a href="mailto:i2c@1" target="_blank">i2c@1</a>,50002e
Testing /<a href="mailto:pci@9" target="_blank">pci@9</a>,700000/<a href="mailto:ebus@1" target="_blank">ebus@1</a>/<a href="mailto:i2c@1" target="_blank">i2c@1</a>,500030
Testing /<a href="mailto:pci@9" target="_blank">pci@9</a>,700000/<a href="mailto:ebus@1" target="_blank">ebus@1</a>/<a href="mailto:bbc@1" target="_blank">bbc@1</a>,0
Testing /<a href="mailto:pci@9" target="_blank">pci@9</a>,700000/<a href="mailto:ebus@1" target="_blank">ebus@1</a>/<a href="mailto:bbc@1" target="_blank">bbc@1</a>,500000
Testing /<a href="mailto:pci@8" target="_blank">pci@8</a>,700000/<a href="mailto:scsi@1" target="_blank">scsi@1</a>
Testing /<a href="mailto:pci@9" target="_blank">pci@9</a>,700000/<a href="mailto:network@1" target="_blank">network@1</a>,1
Testing /<a href="mailto:pci@9" target="_blank">pci@9</a>,700000/<a href="mailto:usb@1" target="_blank">usb@1</a>,3
Testing /<a href="mailto:pci@9" target="_blank">pci@9</a>,700000/<a href="mailto:ebus@1" target="_blank">ebus@1</a>/<a href="mailto:gpio@1" target="_blank">gpio@1</a>,300600
Testing /<a href="mailto:pci@9" target="_blank">pci@9</a>,700000/<a href="mailto:ebus@1" target="_blank">ebus@1</a>/<a href="mailto:pmc@1" target="_blank">pmc@1</a>,300700
Testing /<a href="mailto:pci@9" target="_blank">pci@9</a>,700000/<a href="mailto:ebus@1" target="_blank">ebus@1</a>/<a href="mailto:rtc@1" target="_blank">rtc@1</a>,300070
Resetting ...
Enabling system bus....... Done
Initializing CPUs......... Done
Initializing boot memory.. Done
Initializing OpenBoot
Probing system devices
Probing I/O buses
Probing system devices
Probing I/O buses
Sun Fire 880, Keyboard Present
Copyright 1998-2004 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.15.1, 4096 MB memory installed, Serial #52536809.
Ethernet address 0:3:ba:21:a5:e9, Host ID: 8321a5e9.
Rebooting with command: boot
Boot device: /<a href="mailto:pci@8" target="_blank">pci@8</a>,600000/SUNW,<a href="mailto:qlc@2" target="_blank">qlc@2</a>/<a href="mailto:fp@0" target="_blank">fp@0</a>,0/<a href="mailto:disk@w21000004cfb398ab" target="_blank">disk@w21000004cfb398ab</a>,0:a File an
d args:
SunOS Release 5.8 Version Generic_108528-13 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
...Here it just hungs for hours
Hiv stumoor ,Thanks a lot.
I have done . your steps
now another error is comming !
syncing file systems...
panic[cpu0] /thread=30002502c00:BAD TRAP:Type=10 rp=10423260 addr=7813c2f8 mmu_fsr=0
dumping to /dev/dsk/c1t0d0s1,offset 839909376
92% done
94% done] /thread=2a100071d20:
panic[cpu2]/thread=2a100071d20
my usual appreciation for your helps
Sorry I have not replied in a while I have been not been on shift for 3 or 4 days. I know you said that you are now seeing the server panicing.
Is the server still panicing?
Is it able to boot now from disk?
At this stage if you have not already done so I would open a Sun Support Case. Any update or feedback you could give to finish the thread would be good.
Hi Looks like a bit of a problem...
The best way to prove the hardware would be minimum config the box
1 cpu/mem board no cards , connect serial port to terminal/pc and run extended diags.
if it passes try a single user mode boot.
add more hardware 1 item at a time and repeat test.
if passes add more .
if it falls over then the last bit of hardware you added is probably fault.
