| Title: | AlphaServer 4100 |
| Moderator: | MOVMON::DAVIS S |
| Created: | Tue Apr 16 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 648 |
| Total number of notes: | 3158 |
We do get fatal machine-checks on an Alpha Server 4100. The CPU has
been replaced yesterday but that didn't solve the problem. All entries
are the same. Below I have included one entry and an output of CLUE
CONFIG to show the configuration. Anyone an idea, all help is welcome.
best regards Ton Drummen
This is DECEVENT 2.4 output
******************************** ENTRY 36 ********************************
Logging OS 1. OpenVMS
System Architecture 2. Alpha
OS version V7.1
Event sequence number 1015.
Timestamp of occurrence 14-MAY-1997 11:35:31
Time since reboot 0 Day(s) 21:50:16
Host name DNAHES
System Model AlphaServer 4100 5/300 2MB
Entry type 38. Time Stamp Entry
SWI Minor class 7. Timestamp
******************************** ENTRY 37 ********************************
Logging OS 1. OpenVMS
System Architecture 2. Alpha
OS version V7.1
Event sequence number 1016.
Timestamp of occurrence 14-MAY-1997 11:42:29
Time since reboot 0 Day(s) 21:57:14
Host name DNAHES
System Model AlphaServer 4100 5/300 2MB
Entry type 2. Machine Check
CPU Minor class 1. Machine check (670 entry)
Software Flags x0000000300000000
IOD 0 Register Subpkt Pres
IOD 1 Register Subpkt Pres
Active CPUs x00000001
Hardware Rev x00000000
System Serial Number AY70209473
Module Serial Number
Module Type x0000
System Revision x00000000
* MCHK 670 Regs *
Flags: x00000000
PCI Mask x0002
Machine Check Reason x0098 Fatal Alpha Chip Detected Hard Error
PAL SHADOW REG 0 x0000000000000000
PAL SHADOW REG 1 x0000000000000000
PAL SHADOW REG 2 x0000000000000000
PAL SHADOW REG 3 x0000000000000000
PAL SHADOW REG 4 x00004B3300000000
PAL SHADOW REG 5 x0000000000000000
PAL SHADOW REG 6 x0000000000000000
PAL SHADOW REG 7 x0000000000000000
PALTEMP0 x0000000000000001
PALTEMP1 x0000000000000008
PALTEMP2 xFFFFFFFF80C2B740
PALTEMP3 x0000000000004400
PALTEMP4 xFFFFFFFF80CECF00
PALTEMP5 xFFFFFFFF80CED280
PALTEMP6 x0000000000000010
PALTEMP7 x0000000000000015
PALTEMP8 x0000000000000004
PALTEMP9 x0000000000000004
PALTEMP10 xFFFFFFFF8005E1A8
PALTEMP11 x0000000000000000
PALTEMP12 x000000000000000A
PALTEMP13 x0000000000006E80
PALTEMP14 x0000000000000000
PALTEMP15 x00000000000F0000
PALTEMP16 x0000009806700001
PALTEMP17 x0000158E2FD6014B
PALTEMP18 xFFFFFFFF80C12000
PALTEMP19 x000000007FFA2000
PALTEMP20 x00000000001F2000
PALTEMP21 xFFFFFFFC00000000
PALTEMP22 x0000000000354000
PALTEMP23 x0000000000C12080
Exception Address Reg xFFFFFFFF8005E1A8
Native-mode Instruction
Exception PC x3FFFFFFFE001786A
Exception Summary Reg x0000000000000000
Exception Mask Reg x0000000000000000
PAL Base Address Reg x0000000000008000
Base Addr for PALcode: x0000000000000002
Interrupt Summary Reg x0000000000200000
External HW Interrupt at IPL21
AST Requests 3-0: x0000000000000000
IBOX Ctrl and Status Reg x000000C140000000
Timeout Counter Bit Clear.
IBOX Timeout Counter Enabled.
Floating Point Instructions will Cause
FEN Exceptions.
PAL Shadow Registers Enabled.
Correctable Error Interrupts Enabled.
ICACHE BIST (Self Test) Was Successful.
TEST_STATUS_H Pin Asserted
Icache Par Err Stat Reg x0000000000000000
Dcache Par Err Stat Reg x0000000000000000
Virtual Address Reg xFFFFFFFF832E6000
Memory Mgmt Flt Sts Reg x0000000000005E90
If Err, Reference Resulted in DTB Miss
Fault Inst RA Field: x000000000000001A
Fault Inst Opcode: x000000000000000B
Scache Address Reg xFFFFFF000000F42F
Scache Status Reg x0000000000000000
Bcache Tag Address Reg xFFFFFF80034DCFFF
Last Bcache Access Resulted in a Miss.
Value of Parity Bit for Tag Control Status
Bits Dirty, Shared & Valid is Clear.
Value of Tag Control Dirty Bit is Set.
Value of Tag Control Shared Bit is Set.
Value of Tag Control Valid Bit is Set.
Value of Parity Bit Covering Tag Store
Address Bits is Clear.
Tag Address<38:20> Is: x0000000000000034
Ext Interface Address Reg xFFFFFF000E0004FF
Fill Syndrome Reg x000000000000FF00
Ext Interface Status Reg xFFFFFFF004FFFFFF
Error Occurred During D-ref Fill
LD LOCK xFFFFFF0008D2C07F
** IOD SUBPACKET -> ** IOD 0 Register Subpacket
WHOAMI x00002F7A MID 2.
GID 7.
Ref Err Fail Addr 7A XXXXXXXX
This Bus Bridge Phy Addr x000000F9E0000000
IOD# 0
Dev Type & Rev Register x06008032 CAP Chip Revision: x00000002
B3040 Module Revision: x00000003
B3050 Module Revision: x00000000
B3050 Module Type: Left Hand
PCI-EISA Bus Bridge Present on PCI Segment
Device Class: Host Bus to PCI Bridge
MC-PCI Command Register x46490FF1 Module Self-Test Passed LED On.
Delayed PCI Bus Reads Protocol: Enabled
Bridge to PCI Transactions: Enabled
Bridge REQUESTS 64 Bit Data Transactions
Bridge ACCEPTS 64 Bit Data Transactions
PCI Address Parity Check: Enabled
MC Bus CMD/Addr Parity Check: Enabled
MC Bus NXM Check: Enabled
Check ALL Transactions for Errors
Use MC_BMSK for 16 Byte Align Blk Mem Wrt
Wrt PEND_NUM Threshold: 9.
RD_TYPE Memory Prefetch Algorithm: Short
RL_TYPE Mem Rd Line Prefetch Type: Medium
RM_TYPE Mem Rd Multiple Cmd Type: Long
ARB_MODE PCI Arbitration: Round Robin
Mem Host Address Ext Reg x00000000 HAE Sparse Mem Adr<31:27> x00000000
IO Host Adr Ext Register x00000000 PCI Upper Adr Bits<31:25> x00000000
Interrupt Ctrl Register x00000003 Write Device Interrupt Info Struct:Enabled
Interrupt Request x00800000 Interrupts asserted x00000000
Hard Error
Interrupt Mask0 Register x00E51100
Interrupt Mask1 Register x00000000
MC Error Info Register 0 x00008010
MC Bus Trans Addr<31:4>: 8010
MC Error Info Register 1 x800E80F4 MC bus trans addr <39:32> x000000F4
MC Command is MemIdle
CPU0 Master at Time of Error
Device ID 2 x00000002
MC error info valid
CAP Error Register x83000000 Error Detected but Not Logged
MC bus cmd/addr parity error
MC error info latched
PCI Bus Trans Error Adr x00000000
MDPA Status Register x00000000 MDPA Status Register Data Not Valid
MDPA Error Syndrome Reg x00000000 MDPA Syndrome Register Data Not Valid
MDPB Status Register x00000000 MDPB Status Register Data Not Valid
MDPB Error Syndrome Reg x00000000 MDPB Syndrome Register Data Not Valid
** IOD SUBPACKET -> ** IOD 1 Register Subpacket
WHOAMI x000008BA Module Revision 2.
VCTY ASIC Rev = 0
Bcache Size = 2MB
CPU = 0
This Bus Bridge Phy Addr x000000FBE0000000
IOD# 1
Dev Type & Rev Register x06000032 CAP Chip Revision: x00000002
B3040 Module Revision: x00000003
B3050 Module Revision: x00000000
B3050 Module Type: Left Hand
Internal CAP Chip Arbiter: Enabled
Device Class: Host Bus to PCI Bridge
MC-PCI Command Register x46490FF1 Module Self-Test Passed LED On.
Delayed PCI Bus Reads Protocol: Enabled
Bridge to PCI Transactions: Enabled
Bridge REQUESTS 64 Bit Data Transactions
Bridge ACCEPTS 64 Bit Data Transactions
PCI Address Parity Check: Enabled
MC Bus CMD/Addr Parity Check: Enabled
MC Bus NXM Check: Enabled
Check ALL Transactions for Errors
Use MC_BMSK for 16 Byte Align Blk Mem Wrt
Wrt PEND_NUM Threshold: 9.
RD_TYPE Memory Prefetch Algorithm: Short
RL_TYPE Mem Rd Line Prefetch Type: Medium
RM_TYPE Mem Rd Multiple Cmd Type: Long
ARB_MODE PCI Arbitration: Round Robin
Mem Host Address Ext Reg x00000000 HAE Sparse Mem Adr<31:27> x00000000
IO Host Adr Ext Register x00000000 PCI Upper Adr Bits<31:25> x00000000
Interrupt Ctrl Register x00000003 Write Device Interrupt Info Struct:Enabled
Interrupt Request x00801000 Interrupts asserted x00001000
Hard Error
Interrupt Mask0 Register x00C11011
Interrupt Mask1 Register x00000000
MC Error Info Register 0 x00008010
MC Bus Trans Addr<31:4>: 8010
MC Error Info Register 1 x800E80F4 MC bus trans addr <39:32> x000000F4
MC Command is MemIdle
CPU0 Master at Time of Error
Device ID 2 x00000002
MC error info valid
CAP Error Register x83000014 PCI Target Abort
PCI error address reg locked
Error Detected but Not Logged
MC bus cmd/addr parity error
MC error info latched
PCI Bus Trans Error Adr xC0019CE4
MDPA Status Register x00000000 MDPA Status Register Data Not Valid
MDPA Error Syndrome Reg x00000000 MDPA Syndrome Register Data Not Valid
MDPB Status Register x00000000 MDPB Status Register Data Not Valid
MDPB Error Syndrome Reg x00000000 MDPB Syndrome Register Data Not Valid
PALcode Revision Palcode Rev: 1.19-2
******************************** ENTRY 38 ********************************
Logging OS 1. OpenVMS
System Architecture 2. Alpha
OS version V7.1
Event sequence number 1017.
Timestamp of occurrence 14-MAY-1997 11:42:29
Time since reboot 0 Day(s) 21:57:14
Host name DNAHES
System Model AlphaServer 4100 5/300 2MB
Entry type 37. Crash Re-Start
Bugcheck Minor class 1. Crash Re-start
Bugcheck Msg MACHINECHK, Machine check while in kernel
mode
Process ID x00010000
Process Name
KSP xFFFFFFFF83521B40
ESP xFFFFFFFF83523000
SSP xFFFFFFFF8351D000
USP xFFFFFFFF8351D000
R0 x0000000000000210
R1 x2100000000000000
R2 xFFFFFFFF829B3748
R3 xFFFFFFFF829B3C70
R4 x0000000000000000
R5 xFFFFFFFF80CED280
R6 x0000000000000010
R7 x0000000000000008
R8 x0000000000000001
R9 x0000000000000000
R10 x000000007FFCF800
R11 xFFFFFFFF80E6F240
R12 x0000000000000000
R13 xFFFFFFFF829C0C40
R14 xFFFFFFFF82985000
R15 x00000000009B432C
R16 x0000000000000215
R17 x0000000000000001
R18 x0000000000000001
R19 x0000000000000001
R20 xFFFFFFFF8332A000
R21 xFFFFFFFF80C0E318
R22 x0000000000000100
R23 xFFFFFFFF829B29F0
R24 xFFFFFFFF829A6720
R25 x0000000000000003
R26 x0000000000000210
R27 xFFFFFFFF829BDBF0
R28 xFFFFFFFF8005CD04
FP xFFFFFFFF83521B40
SP xFFFFFFFF83521B40
PC xFFFFFFFF8006AB90
PS x0000000000001F00
PTBR x00000000000000F9
Process Ctl Block Base Re x0000000000C12080
PRBR xFFFFFFFF80C12000
VPTB xFFFFFFFC00000000
System Ctl Block Base Reg x00000000000001AA
Software Interrupt Summar x0000000000000000
ASN x0000000000000000
ASTSR ASTEN x0000000000000000
FEN x0000000000000000
ASN x0000000000000000
IPL x000000000000001F
MCES x0000000000000001
******************************** ENTRY 39 ********************************
System Configuration:
System Information:
System Type AlphaServer 4100 5/300 2MB Primary CPU ID 00
Cycle Time 3.3 nsec (299 MHz) Pagesize 8192 Byte
Memory Configuration:
Cluster PFN Start PFN Count Range (MByte) Usage
#03 0 256 0.0 MB - 2.0 MB Console
#04 256 32511 2.0 MB - 255.9 MB System
#05 32767 1 255.9 MB - 256.0 MB Console
Per-CPU Slot Processor Information:
CPU ID 00 CPU State rc,pa,pp,cv,pv,pmv,pl
CPU Type EV5 Pass 4 (21164) Halt PC 00000000.20000000
PAL Code 1.19-7 Halt PS 00000000.00001F00
CPU Revision .... Halt Code 00000000.00000000
Serial Number .......... "Bootstrap or Powerfail"
Console Vers V4.8-7
Adapter Configuration:
TR Adapter ADP Hose Bus BusArrayEntry Node Device Name / HW-Id
-- ----------- -------- ---- -------------------- ---- -------------------------
1 KA1605 80C6B240 0 GLOBAL_BUS
2 MC_BUS 80C6B600 7 MC_BUS
80C6B818 5 KA1605_PCI
80C6B850 4 KA1605_PCI
80C6B968 1 KA1605_MEMORY
3 PCI 80C6BA00 61 PCI
80C6BC50 PKA: 1 NCR 53C810 SCSI
80C6BC88 2 00000000.000110E8
80C6BCC0 3 PBB
80C6BD30 DRA: 5 Mylex DAC960 RAID
4 PCI 80C6BF40 61 PCI
80C6C118 PKB: 0 Qlogic ISP1020 SCSI-2
5 PCI 80C6C8C0 60 PCI
80C6CAD0 1 MERCURY
80C6CB08 GQA: 2 S3 Trio32/64
80C6CB78 EWA: 4 DC21041 - 10 mbit NI (Tul
ip)
80C6CBB0 EWB: 5 DC21041 - 10 mbit NI (Tul
ip)
6 EISA 80C6CDC0 60 EISA
80C6CF98 0 System Board
7 XBUS 80C6D340 60 XBUS
80C6D518 0 EISA_SYSTEM_BOARD
80C6D550 DVA: 1 Floppy
80C6D588 LRA: 2 Line Printer (parallel po
rt)
80C6D5C0 TTA: 3 NS16450 Serial Port
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 603.1 | Fill error | POBOXB::STEINMAN | Wed May 14 1997 14:13 | 18 | |
The CPU and IOD errors indicate a Fill error from PCI1. The CPU
footprint is the WHOAMI value of 2F7A -- bit 13 indicates fill error,
and bits 12:6 indicate address<38:33> of the transaction that caused
the fill error.....the IOD1 subpacket's CAP ERROR shows a master
abort on the PCI.
The MC_Bus parity error initiated by the CPU is an side-effect of the
fill error. When an unexpected fill error occurs, the CPU may generate
a parity error during a memidle bus transaction -- but this only occurs
after a fill_error, which is the real problem here.
What devices are in PCI1? It's possible that one is sick, or that
there is another problem elsewhere in the I/O subsystem ...
Just my $0.02
mo
| |||||
| 603.2 | correction, WHOAMI<11:6> | POBOXB::STEINMAN | Wed May 14 1997 14:33 | 4 | |
Correction, bits 11:6 of WHOAMI indicate address<38:33> ....
mo
| |||||
| 603.3 | clue config is included | UTRTSC::DRUMMEN | By motorcycle we do it fast | Wed May 14 1997 15:48 | 116 |
mo,
I do have a clue config added to entry .0, also in this entry. Besides
that we do get errorlog entries like nr 35 see added below. I heard from the
customer that this system contains a non-DEC PCI interface JCA0:, which is
interfacing somehow to their factory. The driver for this interface is the
GEDRIVER from DIGITAL, and is modified by a software-specialist from Digital.
regards Ton Drummen
******************************** ENTRY 35 ********************************
Logging OS 1. OpenVMS
System Architecture 2. Alpha
OS version V7.1
Event sequence number 889.
Timestamp of occurrence 13-MAY-1997 14:39:11
Time since reboot 0 Day(s) 0:53:59
Host name DNAHES
System Model AlphaServer 4100 5/300 2MB
Entry type 0. Unknown Entry Type
---- Device Profile ----
Unit DNAHES$JCA0
Product Name UNKNOWN
---- UNKNOWN DEVICE ---- ----- Not Decoded -----
15--<-12 11--<-08 07--<-04 03--<-00 :Byte Order
0000: 04000A01 C00189B8 0002C028 0000000F *....(...........*
0010: FFFFFFFF 18003134 00000000 00000000 *........41......*
0020: 0000000C 00000001 00000000 00000001 *................*
0030: 00000000 00000000 00000000 00000000 *................*
----- Software Info -----
UCB$x_ERTCNT 0. Retries Remaining
UCB$x_ERTMAX 0. Retries Allowable
IRP$Q_IOSB x000000000000022C
UCB$x_STS x00000110 Online
Busy
VMS DC$_CLASS 96.
VMS DT$_TYPE 14.
IRP$L_PID x00010040 Requestor "PID"
IRP$x_BOFF 2488. Byte Page Offset
IRP$x_BCNT 2. Transfer Size In Byte(s)
UCB$x_ERRCNT 1. Errors This Unit
UCB$L_OPCNT 3. QIO's This Unit
ORB$L_OWNER x00010004 Owners UIC
UCB$L_DEVCHAR1 x2C440000 Available
Error Logging
Capable of Input
Capable of Output
Real Time
******************************** ENTRY 36 ********************************
System Configuration:
System Information:
System Type AlphaServer 4100 5/300 2MB Primary CPU ID 00
Cycle Time 3.3 nsec (299 MHz) Pagesize 8192 Byte
Memory Configuration:
Cluster PFN Start PFN Count Range (MByte) Usage
#03 0 256 0.0 MB - 2.0 MB Console
#04 256 32511 2.0 MB - 255.9 MB System
#05 32767 1 255.9 MB - 256.0 MB Console
Per-CPU Slot Processor Information:
CPU ID 00 CPU State rc,pa,pp,cv,pv,pmv,pl
CPU Type EV5 Pass 4 (21164) Halt PC 00000000.20000000
PAL Code 1.19-7 Halt PS 00000000.00001F00
CPU Revision .... Halt Code 00000000.00000000
Serial Number .......... "Bootstrap or Powerfail"
Console Vers V4.8-7
Adapter Configuration:
TR Adapter ADP Hose Bus BusArrayEntry Node Device Name / HW-Id
-- ----------- -------- ---- -------------------- ---- -------------------------
1 KA1605 80C6B240 0 GLOBAL_BUS
2 MC_BUS 80C6B600 7 MC_BUS
80C6B818 5 KA1605_PCI
80C6B850 4 KA1605_PCI
80C6B968 1 KA1605_MEMORY
3 PCI 80C6BA00 61 PCI
80C6BC50 PKA: 1 NCR 53C810 SCSI
80C6BC88 2 00000000.000110E8
80C6BCC0 3 PBB
80C6BD30 DRA: 5 Mylex DAC960 RAID
4 PCI 80C6BF40 61 PCI
80C6C118 PKB: 0 Qlogic ISP1020 SCSI-2
5 PCI 80C6C8C0 60 PCI
80C6CAD0 1 MERCURY
80C6CB08 GQA: 2 S3 Trio32/64
80C6CB78 EWA: 4 DC21041 - 10 mbit NI (Tul
ip)
80C6CBB0 EWB: 5 DC21041 - 10 mbit NI (Tul
ip)
6 EISA 80C6CDC0 60 EISA
80C6CF98 0 System Board
7 XBUS 80C6D340 60 XBUS
80C6D518 0 EISA_SYSTEM_BOARD
80C6D550 DVA: 1 Floppy
80C6D588 LRA: 2 Line Printer (parallel po
rt)
80C6D5C0 TTA: 3 NS16450 Serial Port
| |||||
| 603.4 | Error on DMA hit in Scatter/Gather window... | POBOXB::DUNCAN | Wed May 14 1997 17:55 | 23 | |
As Mo points out, this is a PCI 1 detected target abort. What is
interesting is the address in PCI Bus Trans Error Adr: xC0019CE4.
By convention, addresses with bits 30 & 31 set are for the host
bus bridge scatter/gather map - that indicates this is a DMA which
was terminated by the host bridge. I don't remember the conditions
under which this happens - it should have been documented in
Chapter 5 of the SPM.
/SHD
==================================================================
CAP Error Register x83000014 PCI Target Abort
PCI error address reg locked
Error Detected but Not Logged
MC bus cmd/addr parity error
MC error info latched
PCI Bus Trans Error Adr xC0019CE4
==================================================================
| |||||
| 603.5 | GEDRIVER | POBOXB::STEINMAN | Wed May 14 1997 19:31 | 12 | |
Ton,
Do you know if the modified GEDRIVER was developed/tested on a 4100? We
have seen cases in the past where 'homemade' PCI adapters that run on
other platforms have trouble on the 4100, due to the PCI and I/O
subsystem being much faster on the 4100, latency-wise. In those cases,
driver modifications were necessary.
Don't know if this applies here, but it's something to consider.
/mo
| |||||
| 603.6 | RAID and QLOGIC and SRM console bug? | MAY21::CUMMINS | Wed May 14 1997 19:56 | 55 | |
It's possible this is the same issue as that described by me in note 599.1.
The CLUE CONFIG output points to a QLOGIC behind a bridge on the same bus
as a RAID controller. An experiment to try would be to put the RAID and
QLOGIC cards in different PCI hoses/buses.
A less obtrusive experiment would be to provide the following info:
P00>>> epci -c 1 0 5 0 0 -n 20 # RAID config space CSRs
P00>>> epci -c 1 0 3 0 0 -n 20 # PBB config space CSRs
P00>>> epci -c 1 2 0 0 0 -n 20 # QLOGIC config space CSRs
Given the following adapter configuration..
Adapter Configuration:
TR Adapter ADP Hose Bus BusArrayEntry Node Device Name / HW-Id
-- ----------- -------- ---- -------------------- ---- -------------------------
3 PCI 80C6BA00 61 PCI
80C6BC50 PKA: 1 NCR 53C810 SCSI
80C6BC88 2 00000000.000110E8
80C6BCC0 3 PBB
80C6BD30 DRA: 5 Mylex DAC960 RAID
4 PCI 80C6BF40 61 PCI
80C6C118 PKB: 0 Qlogic ISP1020 SCSI-2
5 PCI 80C6C8C0 60 PCI
80C6CAD0 1 MERCURY
80C6CB08 GQA: 2 S3 Trio32/64
80C6CB78 EWA: 4 DC21041 - 10 mbit NI (Tulip)
80C6CBB0 EWB: 5 DC21041 - 10 mbit NI (Tulip)
The EPCI command has help text should the adapter config (hose, slot, bus)
have changed since the CLUE CONFIG was posted here..
P00>>>help epci
NAME
epci
FUNCTION
examine PCI space.
SYNOPSIS
epci [-] <hose> <bus> <slot> <function> <register> <address>
[-io]
[-mem]
[-dense]
[-config]
[-register]
[-eisa <slot>]
[-n <count>]
[-x]
Please provide feedback if should get a chance to try such an experiment.
Thanks,
BC
| |||||
| 603.7 | the info out of epci | UTRTSC::DRUMMEN | By motorcycle we do it fast | Thu May 15 1997 11:12 | 119 |
BC,
Here is the info you requested.
regards Ton Drummen
P00>>>epci -c 1 0 5 0 0 -n 20
Hose 1 Bus 0 Slot 5 Function 0 Offset 0
e pmem:fbc0050018 -1 -n 20 -s 80
pmem: FBC0050018 00011069
pmem: FBC0050098 02000147
pmem: FBC0050118 01040002
pmem: FBC0050198 0000FF10
pmem: FBC0050218 00100001
pmem: FBC0050298 04008000
pmem: FBC0050318 00000000
pmem: FBC0050398 00000000
pmem: FBC0050418 00000000
pmem: FBC0050498 00000000
pmem: FBC0050518 00000000
pmem: FBC0050598 00000000
pmem: FBC0050618 04000000
pmem: FBC0050698 00000000
pmem: FBC0050718 00000000
pmem: FBC0050798 00040114
pmem: FBC0050818 00000000
pmem: FBC0050898 00000000
pmem: FBC0050918 00000000
pmem: FBC0050998 00000000
pmem: FBC0050A18 00000000
pmem: FBC0050A98 00000000
pmem: FBC0050B18 00000000
pmem: FBC0050B98 00000000
pmem: FBC0050C18 00000000
pmem: FBC0050C98 00000000
pmem: FBC0050D18 00000000
pmem: FBC0050D98 00000000
pmem: FBC0050E18 00000000
pmem: FBC0050E98 00000000
pmem: FBC0050F18 00000000
pmem: FBC0050F98 00000000
pmem: FBC0051018 00000000
P00>>>epci -c 1 0 3 0 0 -n 20
Hose 1 Bus 0 Slot 3 Function 0 Offset 0
e pmem:fbc0030018 -1 -n 20 -s 80
pmem: FBC0030018 00011011
pmem: FBC0030098 02800146
pmem: FBC0030118 06040002
pmem: FBC0030198 0001F810
pmem: FBC0030218 00000000
pmem: FBC0030298 00000000
pmem: FBC0030318 00020200
pmem: FBC0030398 02800000
pmem: FBC0030418 04100410
pmem: FBC0030498 3FF04000
pmem: FBC0030518 00000000
pmem: FBC0030598 00000000
pmem: FBC0030618 00000000
pmem: FBC0030698 00000000
pmem: FBC0030718 00000000
pmem: FBC0030798 00030000
pmem: FBC0030818 0000000C
pmem: FBC0030898 00000000
pmem: FBC0030918 00FFFFFF
pmem: FBC0030998 00FFFFFF
pmem: FBC0030A18 00000000
pmem: FBC0030A98 00000000
pmem: FBC0030B18 00000000
pmem: FBC0030B98 00000000
pmem: FBC0030C18 00000000
pmem: FBC0030C98 00000000
pmem: FBC0030D18 00000000
pmem: FBC0030D98 00000000
pmem: FBC0030E18 00000000
pmem: FBC0030E98 00000000
pmem: FBC0030F18 00000000
pmem: FBC0030F98 00000000
pmem: FBC0031018 00000000
P00>>>
P00>>>epci -c 1 0 2 0 0 -n 20
Hose 1 Bus 2 Slot 0 Function 0 Offset 0
e pmem:fbc0400018 -1 -n 20 -s 80
pmem: FBC0400018 10201077
pmem: FBC0400098 02000147
pmem: FBC0400118 01000002
pmem: FBC0400198 0000F810
pmem: FBC0400218 00101001
pmem: FBC0400298 04110000
pmem: FBC0400318 00000000
pmem: FBC0400398 00000000
pmem: FBC0400418 00000000
pmem: FBC0400498 00000000
pmem: FBC0400518 00000000
pmem: FBC0400598 00000000
pmem: FBC0400618 04100000
pmem: FBC0400698 00000000
pmem: FBC0400718 00000000
pmem: FBC0400798 0000010C
pmem: FBC0400818 00000000
pmem: FBC0400898 00000000
pmem: FBC0400918 00000000
pmem: FBC0400998 00000000
pmem: FBC0400A18 00000000
pmem: FBC0400A98 00000000
pmem: FBC0400B18 00000000
pmem: FBC0400B98 00000000
pmem: FBC0400C18 00000000
pmem: FBC0400C98 00000000
pmem: FBC0400D18 00000000
pmem: FBC0400D98 00000000
pmem: FBC0400E18 00000000
pmem: FBC0400E98 00000000
pmem: FBC0400F18 00000000
pmem: FBC0400F98 00000000
pmem: FBC0401018 10201077
| |||||
| 603.8 | HARMNY::CUMMINS | Thu May 15 1997 16:12 | 7 | ||
The output looks good. Back to ground zero - SRM bug only affects newer
PCI-PCI bridges. This particular PCI-PCI bridge card only supports 16-bit
I/O space.
Have you tried removing cards to see if the device works okay by itself?
BC
| |||||