PCI System Error on Bus/Device/Function 0078h

[Petri Asikainen]

Hi!
After installing native file access/ AFPTCP I started get abends. I have
tried all avaible combination of AFPTCP, TCPIP, and WINSOCK. (What I
have found ...)

Nov when server is abeded I got message:
"PCI System Error on Bus/Device/Function 0078h"
on server monitor screen. What does that mean? any ideas?
Or any ideas for AFPTCP?

Thank you,

Petri Asikainen

BTW... abend log looks like:
---------------------------------------
Server XXXXXX halted Wednesday, 9 January 2002 13.14.56
Abend 1 on P00: Server-5.00j: Page Fault Processor Exception (Error code
00000000)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 000100B4 EBX = B99C4B20 ECX = BC799EE1 EDX = BC799EE1
ESI = B87E5A80 EDI = C7B5B980 EBP = C7B6E534 ESP = C7B6E524
EIP = FC01CDDA FLAGS = 00014206
FC01CDDA 8B4904 MOV ECX,[ECX+04]=?
EIP in SERVER.NLM at code start +0001CDDAh
Access Location: 0xBC799EE5

The violation occurred while processing the following instruction:
FC01CDDA 8B4904 MOV ECX,[ECX+04]
FC01CDDD 8B1D48794EFC MOV
EBX,[SERVER.NLM|OSAddressSpace]=SERVER.NLM|OSAS
FC01CDE3 8B81FC000000 MOV EAX,[ECX+000000FC]
FC01CDE9 8B89C4020000 MOV ECX,[ECX+000002C4]
FC01CDEF 8D5004 LEA EDX,[EAX+04]
FC01CDF2 39D9 CMP ECX,EBX
FC01CDF4 0F8574000000 JNZ FC01CE6E
FC01CDFA 8B4D0C MOV ECX,[EBP+0C]
FC01CDFD 817908414C5254 CMP [ECX+08],54524C41
FC01CE04 7535 JNZ FC01CE3B

Running process: AFP Work Thread (345): B99C4B20 Process
Created by: NetWare Application
Thread Owned by NLM: AFPTCP.NLM
Stack pointer: C7B6E50C
OS Stack limit: C7B6A640
Scheduling priority: 67371008
Wait state: 5050100 (Delayed)
Stack: --00000001 ?
--C7B5B980 ?
--B87E5A80 ?
--B99C4B20 ?
--C7B6E544 ?
B995CC7A (AFPTCP.NLM|AllocRequestNode+1A)
--000100B4 ?
--BC799EE1 ?
--C7B6E600 ?
B995E95B (AFPTCP.NLM|AFPThread+25B)
--B9D96820 ?
--000138AE ?
--00000159 ?
--00000000 ?
--00000000 ?
--0E0F98DD ?
--00000016 ?
--20504641 ?
--6B726F57 ?
--72685420 ?
--20646165 ?
--35343328 ?
--42203A29 ?
--34433939 ?
--00303242 ?
--00544545 ?
--D0017880 ?
--092F645C ?
--1DD1FB88 ?
--00000003 ?
--D0017880 ?
FC003014 (SERVER.NLM|AppNextThread+74)
--D0017880 ?
--D00150E0 ?
--E0232FC5 ?
--092F645C ?
--00000000 ?
--3B60937B ?
--D00150E0 ?
FC012DE8 (SERVER.NLM|_SchedGetReadyThread+4C)
--00004246 ?
--C7B59B80 ?
--00004246 ?
--B99A4EC0 ?
--000001CC ?
--B99A4EC4 ?
FC00E6FA (SERVER.NLM|BufferFree+A)
--B99A4EC0 ?
FC00B05C (SERVER.NLM|kSemaphoreFreeLegacy+B8)
--0000001A ?
--B99FF460 ?
--000100DE ?
B995E700 (AFPTCP.NLM|AFPThread+0)
--C7B65E40 ?
--C7A97900 ?
--00000000 ?
C8B18264 (THREADS.NLM|getcmd+1DC)
--C7B5B980 ?
C9DE066E (3C986.LAN|altClearNicStats+2DDE)
--C9DFA010 ?
--C7A97900 ?
--00000000 ?
--00000000 ?
--00000000 ?
--B99BF2C0 ?
C8B182D3 (THREADS.NLM|getcmd+24B)
--00000000 ?
FC0162D6 (SERVER.NLM|TcoNewSystemThreadEntryPoint+26)
--B99BF2C0 ?
--00000000 ?
--00000000 ?
--00000004 ?
--000082F3 ?
--00000001 ?
--C7B6E678 ?
C84A61DF (DS.NLM|EmuMapNameToObjectList+58)
--C7B6E8D2 ?
--C7B6A000 ?
--000082F3 ?
--00000001 ?
--C7B6E698 ?
--C7B6E81C ?
--C7B6E90C ?
--C7B6E8D2 ?
--00000004 ?
--C7B6E6A4 ?
C84A620E (DS.NLM|EmuMapNameToObject+23)
--C7B6E8D2 ?
--00000004 ?
--000082F3 ?
--00000001 ?
--C7B6E698 ?
--C7B6E81C ?
--C9DF715C ?
--00000002 ?
--00000001 ?
--C7B6E6D0 ?
FC0B3DC3 (SERVER.NLM|CMoveFast+13)
--C7B6E6E8 ?
--C7A89560 ?

Additional Information:
The CPU encountered a problem executing code in SERVER.NLM. The
problem may be in that module or in data passed to that module by a
process owned by AFPTCP.NLM.

[Marcel Cox [SysOp]]

The PCI System Error message makes this sound like a hardware issue,
and given it happend in a protocol related NLM, this could be the LAN
adapter. Of course, it could also be a BIOS or driver issue. So to
eliminate that possibility, I would recommend that you make sure BIOS
and LAN driver are up to date. Above all, I would sugest you try to
find out what the device with the PCI location address 0078h is. I
think the mapping information is available somewhere through the
Management portal, but I have no means to verify it right now.

Marcel

Petri Asikainen <pa...@cedunet.com> wrote in message news:<3C3C559A...@cedunet.com>...

[Petri Asikainen]

Petri Asikainen wrote:

I looked at mangemet portal, but under "PCI resources" theres no device
using 078h !(?)

Could this mean that there's bug some where else?

Petri

[Marcel Cox [SysOp]]

Petri,

The PCI address (not device ID) is a 16 bit value that is defined as
follows :

bits 0-2 : function number
bits 3-7 : device number
bits 8-15 : bus number

in your case, the value 0078h means bus=0, device=15, function=0

To address PCI devices, Novell uses a logical slot addressing. The mapping
between logical slot numbers and PCI device addresses can be found in the
server registry unde "My Server\Instance_Info" (in Portal, look under
Application -> Registry). For each logical slot value, you will have a
registry entry with a class value that specifies the bus type, and an
address value that specifies the addressing within that bus type. For PCI
devices, the address is a string which contains the PCI address as 2 hex
bytes separated by a dot. E.g. you should look for a slot entry whose
address is 0.78

Note that you are using an old and potentially problematic version of
CHPTX.LAN. This driver is equivalent to the Intel CE100B.LAN driver and
all versions below 4.x where problematic. You should check if HP has a 4.x
version of CHPTX.LAN, or else you should switch to CE100B.LAN v4.17 or
later available on Intel's web site (download file : 100pdisk.exe)

---
Marcel Cox
Using VA 5.51 build 315

[Petri Asikainen]

Thanks for intresting information. I looked under Registry and found
that 0078h belogs to PCI device 10005.
I also looked under HWDHARDWARE/PCI and there it says that:
VEN 1166&DEV 0200
BUS 00 DEV 0F FUN 0 (... so this same device, is it?)
Detected State 0x04
Class 0x06 0x00
Sub Class 0x01 0x00
HIN 0x15 0x27

But how I know what device is it? When I look under PCI Device
information/10095 theres only Configuration Spaces and Offsets listed,
no additional information like names.

CHPTX card have not TCPIP binded. But I'll update drivers any way.

Petri