PCI errors on ultra80.

[POPKORN]

Hello Guys and thans for your help in advance.


I installed another network card besides the built in card that the ultra 80 brings because I wanted gbit on this file server.

Never the less, I have been running into some really weird pci errors.

I went as far as performing a full reinstall and I have not applied the latest patch cluster which I would if the server would not crash.

Funny thing is, I pulled all the cards out, meaning fibre channel card, gbit card, video card, sunpci Pro card and I rebooted the system and I still got the same error.




Here is some debug info.





{0} ok test-all
Testing /SUNW,afb@1e,0

Starting AFB Selftest
(This will take an estimated
2-4 minutes for the full test)

AFB Command Register Test ......... pass
AFB Float Microcode Test .......... pass
AFB Passthru Packet Test .......... pass
AFB RAMDAC Register Test .......... pass
AFB General Initialization Test ... pass
AFB RAMDAC Sync Generator Test .... pass
AFB Memory Fixed-Value Test ....... pass
AFB Memory Sequenced-Value Test ... pass
AFB Rectangle/Scroll Test ......... pass

AFB Selftest Completed: No Errors Detected
Testing /pci@1f,4000/scsi@3,1
No targets found
Selftest failed. Return code = -1
Testing /pci@1f,4000/scsi@3
Testing /pci@1f,4000/network@1,1
Hme register test --- succeeded.
Internal loopback test -- succeeded.
Transceiver check -- Using Onboard Transceiver - Link Up.
passed
----------------------------------------------------------


Software Power ON
Master CPU : 0000.0000.0023.11a0
Slave CPU : 0000.0001.0023.1120
Slave CPU : 0000.0002.0023.1120
Slave CPU : 0000.0003.0023.1120
Master E$ : 0000.0000.0040.0000
Slave E$ : 0000.0000.0040.0000
Slave E$ : 0000.0000.0040.0000
Slave E$ : 0000.0000.0040.0000

@(#) UPA/PCI 3.31 Version 0 created 2001/07/25 20:35
Clearing DTAGS Done
Probing Memory
CONFIG = 0000.0000.0000.0010
MEM BASE = 0000.0000.0000.0000
MEM SIZE = 0000.0000.4000.0000
MMUs ON
Copy Done
PC = 0000.01ff.f000.2b30
PC = 0000.0000.0000.2b74
Decompressing into Memory Done
Size = 0000.0000.0006.ee80
ttya initialized
SC Control: EWP:0 IAP:0 FATAL:0 WAKEUP:0 BXIR:0 BPOR:0 SXIR:0 SPOR:1 POR:0
Probing Memory Bank #0 256 256 256 256 : 1 Gigabytes
Probing Memory Bank #1 0 0 0 0 : 0 Megabytes
Probing Memory Bank #2 0 0 0 0 : 0 Megabytes
Probing Memory Bank #3 0 0 0 0 : 0 Megabytes
Probing Floppy: No drives detected
Probing EBUS SUNW,CS4231
Probing UPA Slot at 1e,0 SUNW,afb
Probing UPA Slot at 1d,0 Nothing there
Probing /pci@1f,4000 at Device 1 pci108e,1000 network
Probing /pci@1f,4000 at Device 3 scsi disk tape scsi disk tape
Probing /pci@1f,4000 at Device 2 Nothing there
Probing /pci@1f,4000 at Device 4 fibre-channel
Probing /pci@1f,4000 at Device 5 pci108e,5043
Probing /pci@1f,2000 at Device 1 ethernet
SC Control: EWP:0 IAP:0 FATAL:0 WAKEUP:0 BXIR:0 BPOR:0 SXIR:0 SPOR:1 POR:0
Probing Memory Bank #0 256 256 256 256 : 1 Gigabytes
Probing Memory Bank #1 0 0 0 0 : 0 Megabytes
Probing Memory Bank #2 0 0 0 0 : 0 Megabytes
Probing Memory Bank #3 0 0 0 0 : 0 Megabytes
Probing Floppy: No drives detected
Probing EBUS SUNW,CS4231
Probing UPA Slot at 1e,0 SUNW,afb
Probing UPA Slot at 1d,0 Nothing there
Probing /pci@1f,4000 at Device 1 pci108e,1000 network
Probing /pci@1f,4000 at Device 3 scsi disk tape scsi disk tape
Probing /pci@1f,4000 at Device 2 Nothing there
Probing /pci@1f,4000 at Device 4 fibre-channel
Probing /pci@1f,4000 at Device 5 pci108e,5043
Probing /pci@1f,2000 at Device 1 ethernet

Sun Ultra 80 UPA/PCI (4 X UltraSPARC-II 336MHz), No Keyboard
OpenBoot 3.31, 1024 MB memory installed, Serial #13761336.
Ethernet address 8:0:20:d1:fb:38, Host ID: 80d1fb38.



Rebooting with command: boot
Boot device: net File and args:
Using Onboard Transceiver - Timeout waiting for AutoNegotiation Status to be updated.
Timeout reading Link status. Check cable and try again.
Timeout waiting for AutoNegotiation Status to be updated.

{0} ok boot disk
Boot device: /pci@1f,4000/scsi@3/disk@0,0 File and args:
Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
FCode UFS Reader 1.12 00/07/17 15:48:16.
Loading: /platform/SUNW,Ultra-80/ufsboot
Loading: /platform/sun4u/ufsboot
SunOS Release 5.10 Version Generic_118833-33 64-bit
Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: solaris
checking ufs filesystems
/dev/rdsk/c0t0d0s7: is logging.

solaris console login: root
Password:
Last login: Sun Mar 11 19:53:05 on console
bSun Microsystems Inc. SunOS 5.10 Generic January 2005
as# h
Mar 11 19:58:32 solaris sendmail[360]: My unqualified host name (solaris) unknown; sleeping for retry
Mar 11 19:58:32 solaris sendmail[361]: My unqualified host name (solaris) unknown; sleeping for retry





bash-3.00#
bash-3.00#
bash-3.00#
bash-3.00#
bash-3.00#
bash-3.00# ping

SUNW-MSG-ID: SUNOS-8000-0G, TYPE: Error, VER: 1, SEVERITY: Major
EVENT-TIME: 0x45f497b9.0x2c1b9674 (0x31b7af855e)
PLATFORM: SUNW,Ultra-80, CSN: -, HOSTNAME: solaris
SOURCE: SunOS, REV: 5.10 Generic_118833-33
DESC: Errors have been detected that require a reboot to ensure system
integrity. See

http://www.sun.com/msg/SUNOS-8000-0G

for more information.
AUTO-RESPONSE: Solaris will attempt to save and diagnose the error telemetry
IMPACT: The system will sync files, save a crash dump if needed, and reboot
REC-ACTION: Save the error summary below in case telemetry cannot be saved

ereport.io.pci.dpe ena=31b7abc2c500c01 detector=[ version=0 scheme="dev"
device-path="/pci@1f,2000" ] pci-status=c2a0 pci-command=146 pci-pa=0

ereport.io.pci.sserr ena=31b7abc2c500c01 detector=[ version=0 scheme="dev"
device-path="/pci@1f,2000" ] pci-status=c2a0 pci-command=146 pci-pa=0

ereport.io.pci.rserr ena=31b7abc2c500c01 detector=[ version=0 scheme="dev"
device-path="/pci@1f,2000" ] pci-status=c2a0 pci-command=146 pci-pa=0


panic[cpu3]/thread=2a1003e3cc0: pcipsy-1: Fatal PCI bus error(s)


000002a100459e70 pcipsybm_error_intr+158 (300015cbcc0, 1298000, 300000dfce8, 300000dfce8, 0, 300015cb7c0)
%l0-3: 0000004480001604 0000000000000000 00000000018d1800 00000000018d1800
%l4-7: 0000000000000001 00000000018d1800 00000300000ef838 0000000000000001
000002a100459f50 unix:current_thread+170 (0, 1843dd8, 30001992000, 1b, 0, 1813400)
%l0-3: 00000000010076e4 000002a1003e30d1 000000000000000e 00000000000007f0
%l4-7: 0000030000389a80 0000000000000000 0000000000000000 000002a1003e3980
000002a1003e3a20 unix:idle+128 (1813400, 0, 30001992000, ffffffffffffffff, 4, 1812000)
%l0-3: 0000030001401b48 000000000000001b 0000000000000000 ffffffffffffffff
%l4-7: 0000030001401b48 ffffffffffffffff 0000000001843dd8 0000000001053b98

syncing file systems... 43 12 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 done (not all i/o completed)
dumping to /dev/dsk/c0t0d0s1, offset 107741184, content: kernel
100% done: 16268 pages dumped, compression ratio 3.32, dump succeeded
----------------------------------------------------------


This time I did not even get to use ping.


{0} ok boot disk
Boot device: /pci@1f,4000/scsi@3/disk@0,0 File and args:
Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
FCode UFS Reader 1.12 00/07/17 15:48:16.
Loading: /platform/SUNW,Ultra-80/ufsboot
Loading: /platform/sun4u/ufsboot
SunOS Release 5.10 Version Generic_118833-33 64-bit
Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: solaris
checking ufs filesystems
/dev/rdsk/c0t0d0s7: is logging.

solaris console login: Mar 11 20:16:09 solaris sendmail[360]: My unqualified host name (solaris) unknown; sleeping for retry
Mar 11 20:16:09 solaris sendmail[361]: My unqualified host name (solaris) unknown; sleeping for retry

SUNW-MSG-ID: SUNOS-8000-0G, TYPE: Error, VER: 1, SEVERITY: Major
EVENT-TIME: 0x45f49bcb.0x157528e5 (0xe7ddcf2ee4)
PLATFORM: SUNW,Ultra-80, CSN: -, HOSTNAME: solaris
SOURCE: SunOS, REV: 5.10 Generic_118833-33
DESC: Errors have been detected that require a reboot to ensure system
integrity. See

http://www.sun.com/msg/SUNOS-8000-0G

for more information.
AUTO-RESPONSE: Solaris will attempt to save and diagnose the error telemetry
IMPACT: The system will sync files, save a crash dump if needed, and reboot
REC-ACTION: Save the error summary below in case telemetry cannot be saved

ereport.io.pci.dpe ena=e7ddcb874400c01 detector=[ version=0 scheme="dev"
device-path="/pci@1f,2000" ] pci-status=c2a0 pci-command=146 pci-pa=0

ereport.io.pci.sserr ena=e7ddcb874400c01 detector=[ version=0 scheme="dev"
device-path="/pci@1f,2000" ] pci-status=c2a0 pci-command=146 pci-pa=0

ereport.io.pci.rserr ena=e7ddcb874400c01 detector=[ version=0 scheme="dev"
device-path="/pci@1f,2000" ] pci-status=c2a0 pci-command=146 pci-pa=0


panic[cpu3]/thread=300068789c0: pcipsy-1: Fatal PCI bus error(s)


000002a100459e70 pcipsybm_error_intr+158 (3000209e1c0, 1298000, 300000dfce8, 300000dfce8, 0, 30002469b80)
%l0-3: 0000000000000006 0000000000000000 00000000018d1800 00000000018d1800
%l4-7: 0000000000000001 00000000018d1800 00000300000ef838 0000000000000001
000002a100459f50 unix:current_thread+170 (0, 1, 6, 2420, 1883a68, 0)
%l0-3: 00000000010076e4 000002a100a67091 000000000000000e 00000000000007f0
%l4-7: 0000000000000100 00000300010f8040 0000000000000000 000002a100a67940
000002a100a679e0 genunixwrite+154 (6, 100110bb0, 3000598c6d8, 7fffffffffffffff, 2000, 4880000)
%l0-3: 0000030005a4cf00 0000000004882000 00000000e22a0000 0000000000002302
%l4-7: 0000030002030020 7fffffffffffffff 0000000000000000 0000000000000000

syncing file systems... [2] 102 [2] 76 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 [2] 49 done (not all i/o completed)
dumping to /dev/dsk/c0t0d0s1, offset 107741184, content: kernel
100% done: 16930 pages dumped, compression ratio 3.39, dump succeeded


-----------------------------------------------------------

Any help suggestions are trully appreciated.


PopK0rn

 

[laytrotter]

Hi

ereport.io.pci.dpe ena=e7ddcb874400c01 detector=[ version=0 scheme="dev"
device-path="/pci@1f,2000" ] pci-status=c2a0 pci-command=146

As pci@1f,2000 is pci slot 3 I would remove the card from there and leave it out for the time being. You need to see if the machine is stable with slot 3 empty. Run POST several times and do from the OK prompt 'show-post-results'. If okay then boot to Solaris and check 'prtdiag'. If you have SunVTS then install and run that for a couple of hours.

Don't go putting the card into another slot for the time being, you might end up with a system that has just crashed too many times.

If you have another network card then put that into slot 3 and see what happenes.

Hope this is of some help.

 

[laytrotter]

A liitle more info:-

Slot 3 is 33/66Mhz 64bit 3.3v - is your card compatible?

 

[laytrotter]

Sorry, Sorry, Sorry - IGNORE the last post!

Slot 3 on the Ultra80 = 33Mhz only 32/64bit 5volt.

You card may be a 66Mz card.

Laytrotter.

 

[POPKORN]

Ohh, you know what.

I just checked the box and there is nothing and there has never been anything on slot 3.

I am using this as a reference.

http://www.sunshack.org/data/sh/2.1...yshbk/Devices/System_Board/SYSBD_Ultra80.html

slot 1 has the Gige Pci 32bit 3.3 card.
slot 2 has an emulex 64bit 5 volts lp8000 card.
slot 3 is empty
slot 4 has a sunpci pro card

Of course, this is using the above drawing in the link as a reference. So my question is, Is pci@1f,2000 really pci slot 3? I mean, I don't mean to question you but I am rather confused since I know I dont have anything in slot 3.

Please advise.


PopKorn

 

[laytrotter]

Hi Popkorn - looks like I was having a bad day yesterday, rushing around doing too many things Ooops!.

1f,2000 is Slot 1 -my apologies.

Here is a list of device paths for the Ultra80:-

Ultra 80, 420R, NETRA t 1400/1405

PCI Slot 1 /pci@1f,2000/<device>@1,*

PCI Slot 2 /pci@1f,4000/<device>@4,*

PCI Slot 3 /pci@1f,4000/<device>@2,*

PCI Slot 4 /pci@1f,4000/<device>@5,*

Disk 1 /pci@1f,4000/scsi@3/sd@0,0

CDROM /pci@1f,4000/scsi@3/sd@6,0

External SCSI Port /pci@1f,4000/scsi@3,1/<device>

I think I'll get to bed earlier tonight. lol.

 

[POPKORN]

OK, now that makes perfect sense....
Thank you so much for the clarification.
So in other words looks like the MOBO does not like the Realtek Gige card on that slot.

questions.

By the looks of it, slot 1 is the only 3.3v slot. So I am asuming that the only slot I can put that card in is on slot 1 or, will the other slots work even though they are 5volts. I mean if I put the card on another slot, will it not fry my gige card?


PopKorn

Much appreciated!!!

 

[POPKORN]

Update.

My ultra 80 really does not like the non sun branded hardware. I tried drifferent slots and the problem just followed the card. Same error on different slot.

I have opted to change the gbit card with a sun QFE quad ethernet interface and use trunking to establish a 400mbit link using the same cisco switch which supports trunkinbg as well. I got a hold of the Sun Trunnking 1.3 software and I found some good info in here as well that will help me configure this.

Never the less, much appreciated the help of those that gave feedback

Thank you.

P0Pk0rn

 

[POPKORN]

Update.

If you own a sparc machine and you would like to use gbit ethernet. Please by all means stay away from the Hawkings HGA32T, this card is not compatible at all on sun hardware even though it says it is on HCL on Sun website.

This card uses Realtek RTL8169-S32 chipset, the problem is not the chip, I can tell you that much because I purchased a NETGEAR G311 and this card has the same chipset and its currently working with no issues. I did not even had to use the Gani drivers. The default rge drivers work fine.

bash-3.00# dladm show-dev
hme0 link: unknown speed: 0 Mbps duplex: unknown
rge0 link: up speed: 1000 Mbps duplex: full


This is for informational purpose only and I am only expressing the fact that the Hawking card did not worked on my ultra80 and that the NETGEAR did. I am not trying to degrade any company in any way. It is only my personal opinion.


PS. The card working right now is the NETGEAR.


P0Pk0rn