From: Masopust Christian (christian.masopust@siemens.com)
Date: Mon Jun 06 2005 - 09:09:45 EDT
The following message is shown at the console when running with "boot
-srvd":
sd1 is /pci@1c,600000/scsi@2/sd@1,0
pseudo-device: fssnap0
fssnap0 is /pseudo/fssnap@0
pseudo-device: ramdisk1024
ramdisk1024 is /pseudo/ramdisk@1024
pseudo-device: winlock0
winlock0 is /pseudo/winlock@0
pseudo-device: lockstat0
lockstat0 is /pseudo/lockstat@0
pseudo-device: llc10
llc10 is /pseudo/llc1@0
WARNING:
SC Alert: CRITICAL ALARM is set
pcisch1 (pci@1e,600000): PCI fault log start:
PCI SERR
pcisch1 (pci@1e,600000): PBM AFSR=0x0.00000000 dwordmask=0 bytemask=0
pcisch1 (pci@1e,600000): PCI primary error (0):
pcisch1 (pci@1e,600000): PCI secondary error (0):
pcisch1 (pci@1e,600000): PBM AFAR 0.00010005:WARNING: pcisch1: PCI config
space CSR=0x2a0
pcisch1 (pci@1e,600000): PCI fault log end.
panic[cpu0]/thread=30001dc8fe0: pcisch-1: PCI bus 1 error(s)!
000002a100077ea0 pcisch:pbm_error_intr+15c (30000270dd0, 7b2, 1400418,
1400000, f640, 125ae08)
%l0-3: 000003000007d8a0 0000000000000003 0000000000000001 000003000029d400
%l4-7: 0000000000000000 0000000000000368 0000000001443ac0 000000000144d668
000002a100077f50 unix:current_thread+104 (2a100290df0, 1, 0, 0, 0, b)
any idea what happens? hardware-defect?
thanks a lot,
christian
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:49 EDT