My Oracle Support Banner

Netbackup Windriver Jungo causes server to panic with Error " Fatal Error Has Occured In: PCIe Fabric.(0x40)(0x41)" (Doc ID 1922112.1)

Last updated on OCTOBER 05, 2022

Applies to:

Qlogic FC HBA - Version All Versions and later
Information in this document applies to any platform.



WinDriver v9.01 Jungo (c) 1997 - 2007 Build Date: Jun 17 2007 Sparc 64bit unloaded <===========
WinDriver v9.01 Jungo (c) 1997 - 2007 Build Date: Jun 17 2007 Sparc 64bit loaded <=========
WDsolarisAttach: entered, name pciex1077,2432, instance 4, cmd 0
PCIE-device: QLGC,qlc@0, windrvr64
windrvr64 is /pci@0/pci@0/pci@8/pci@0/pci@8/QLGC,qlc@0
WDsolarisAttach: entered, name pciex1077,2432, instance 5, cmd 0
PCIE-device: QLGC,qlc@0,1, windrvr65
windrvr65 is /pci@0/pci@0/pci@8/pci@0/pci@8/QLGC,qlc@0,1
WDsolarisAttach: entered, name windrvr6, instance 60, cmd 0
pseudo-device: windrvr660
windrvr660 is /pseudo/windrvr6@60
st30 at fp4: unit-address w500104f0009cf350,0: 19100
st30 is /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/st@w500104f0009cf350,0
/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/st@w500104f0009cf350,0 (st30):
       <HP      Ultrium 5-SCSI  >
st31 at fp4: unit-address w500104f0009cf353,0: 11100
st31 is /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/st@w500104f0009cf353,0
/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/st@w500104f0009cf353,0 (st31):
st29 at fp4: unit-address w500104f0009cf34d,0: 14100
st29 is /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/st@w500104f0009cf34d,0
/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/st@w500104f0009cf34d,0 (st29):
       <HP      Ultrium 5-SCSI  >
st33 at fp4: unit-address w500104f0009cf356,0: 15700
st33 is /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/st@w500104f0009cf356,0
/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/st@w500104f0009cf356,0 (st33):
       <HP      Ultrium 5-SCSI  >
st26 at fp5: unit-address w500104f0009cf359,0: 29000
st26 is /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/st@w500104f0009cf359,0
/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/st@w500104f0009cf359,0 (st26):
       <HP      Ultrium 5-SCSI  >
st32 at fp4: unit-address w500104f0009cf365,0: 1f100
st32 is /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/st@w500104f0009cf365,0
/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/st@w500104f0009cf365,0 (st32):
       <HP      Ultrium 5-SCSI  >
st24 at fp5: unit-address w500104f0009cf35c,0: 21100
st24 is /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/st@w500104f0009cf35c,0
/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/st@w500104f0009cf35c,0 (st24):
st27 at fp5: unit-address w500104f0009cf362,0: 28000
st27 is /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/st@w500104f0009cf362,0
/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/st@w500104f0009cf362,0 (st27):
       <HP      Ultrium 5-SCSI  >
st28 at fp5: unit-address w500104f0009cf368,0: 2f100
st28 is /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/st@w500104f0009cf368,0
/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/st@w500104f0009cf368,0 (st28):
st25 at fp5: unit-address w500104f0009cf35f,0: 29100
st25 is /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/st@w500104f0009cf35f,0
/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/st@w500104f0009cf35f,0 (st25):
Symantec SCSA Generic Revision: 3.7
pseudo-device: devinfo0
devinfo0 is /pseudo/devinfo@0
pseudo-device: fcsm0
fcsm0 is /pseudo/fcsm@0

SUNW-MSG-ID: SUNOS-8000-0G, TYPE: Error, VER: 1, SEVERITY: Major
EVENT-TIME: 0x53bd21e1.0x1efea63d (0x13925ad83f50b1)
PLATFORM: SUNW,SPARC-Enterprise-T5220, CSN: -, HOSTNAME: melsmpmednbu01
SOURCE: SunOS, REV: 5.10 Generic_150400-11
DESC: Errors have been detected that require a reboot to ensure system
integrity. See 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

panic[cpu56]/thread=2a102301c80: Fatal error has occured in: PCIe fabric.(0x40)(0x41)

000002a102369d50 px:px_err_panic+1cc (1a72800, 13e7400, 41, 2a102369e00, 40, 0)
  %l0-3: 0000030002c4a2f8 0000000001a72800 0000000000000000 0000000000000001
  %l4-7: 0000000000000034 0000000001a72800 ffffffffffffffff 0000000000000000
000002a102369e60 px:px_err_intr+1a4 (2, 2, 21, 40, 30000586a40, 40)
  %l0-3: 0000030002c62980 0000030002c54380 0000000000000001 0000030000586a98
  %l4-7: 0000030000586a98 0000000000000004 0000000000000001 0000000000000001
000002a102369f50 unix:current_thread+260 (16, 1, 7, 200, 100010101010101, 12)
  %l0-3: 0000000001009964 000002a102300fe1 000000000000000e 000000007008c180
  %l4-7: 0000000000000000 0000000000000000 0000000000000000 000002a102301890
000002a102301930 unix:cpu_halt+110 (30004436000, 38, 198baf0, 198b9c0, 30004436000, 1)
  %l0-3: 00000600348a6384 0000000000000000 0000000000000016 0000000000000001
  %l4-7: 0000000000000000 0000000000000000 0000000000000000 000000000000001b
000002a1023019e0 unix:idle+128 (1866c00, 0, 30004436000, ffffffffffffffff, 39, 1865800)
  %l0-3: 00000600348a6360 000000000000001b 0000000000000000 ffffffffffffffff
  %l4-7: 00000600348a6360 ffffffffffffffff 000000000198b9c0 00000000010464c0

syncing file systems... 3 done




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.