RE: kitl-hangs



From your description it sounds like KITL and the driver are aimed at the
same Ethernet device. You will need to make sure they are both not trying to
access the same device. Set the ARGS structure to use one and configure the
driver to use the other.

"San" wrote:

Hi everyone,
Platform/cpu: X86, geode lx800
Chipset: CS5536
Windows ce 6.0

In my target board there are two 82551QM ethernet controllers, i have
enabled kitl and it is working withouth hanging if the ethernet controller
driver is removed in debug built. If i add the ethernet controller driver
then it hangs, the debug messages are at the end.

I tried setting the following environmental variables:
set KERNELNOSHAREETH=1
set BSP_NOSHAREETH=1
set BSP_NOKITLSHAREDIRQ=1
set IMGNOSHAREETH = 1

eventhough i have set the above environmental variable it is trying to load
2 instances...the same ethernet driver is working fine in wince 5.0 on
setting the environmental variable(set IMGNOSHAREETH = 1 and set
BSP_NOSHAREETH=1) the system boots up fine.. and only one instance is getting
loaded. My goal is to use one ethernet for applications and the other for
kernel debugging. I have also tried with the latest ethernet driver from
Intel. (i tried with altering the portmask value to F000 too).

Is there anything i need to add in the catalog?
Is it possible to load a driver, same vendor and device ids only once?
I dont want to load 2 instances of the driver.

4294819049 PID:400002 TID:fa0002 DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\E1002\BusPrefix) returned 2
4294819050 PID:400002 TID:fa0002 NDIS:ndisAddPCMCIADevice INdisOpenDeviceKey
failed
4294819051 PID:400002 TID:fa0002 NDIS:: CE_AddBusFriendlyName()
[successfully created] [HKLM\Comm\BusFriendlyNames\PCI_0_17_0\E1002]
4294819055 PID:400002 TID:fa0002 OSAXST1: >>> Loading Module 'e100.dll'
(0x8340EC24) at address 0xC0DD0000-0xC0DD8000 in Process 'NK.EXE' (0x823BFC80)
4294819068 PID:400002 TID:fa0002 ==>NdisInitializeWrapper
4294819068 PID:400002 TID:fa0002 <==NdisInitializeWrapper
4294819068 PID:400002 TID:fa0002 ==>NdisMRegisterMiniport: NdisWrapperHandle
D062BAB0
4294819068 PID:400002 TID:fa0002 ==>ndisRegisterMiniportDriver:
NdisWrapperHandle D062BAB0
4294819068 PID:400002 TID:fa0002 <==ndisRegisterMiniportDriver: MiniBlock
D062BB30
4294819068 PID:400002 TID:fa0002 NdisMRegisterMiniport: MiniBlock D062BB30
4294819068 PID:400002 TID:fa0002 <==NdisMRegisterMiniport: MiniBlock
D062BB30, Status 0
4294819069 PID:400002 TID:fa0002
4294819069 PID:400002 TID:fa0002 ndisMInitializeAdapter: Miniport D062BD78,
4294819070 PID:400002 TID:fa0002 ==>ndisQueueMiniportOnDriver: Miniport
D062BD78, MiniBlock D062BB30
4294819071 PID:400002 TID:fa0002 <==ndisQueueMiniportOnDriver: Miniport
D062BD78, MiniBlock D062BB30, rc 1
4294819071 PID:400002 TID:fa0002 ==>NdisMSetAttributesEx: Miniport D062BD78
4294819099 PID:400002 TID:fa0002 ## LOOKASIDE INITIALIZE ## [48] bytes,
depth [0]
4294819139 PID:400002 TID:fa0002 ==>NdisMMapIoSpace
4294819139 PID:400002 TID:fa0002 ***NDIS*** (a, 516)
4294819139 PID:400002 TID:fa0002 ==>NdisMRegisterInterrupt: Miniport
D062BD78 Vector 5
4294819139 PID:400002 TID:fa0002 NDIS:: CeConnectInterrupt() --> IRQ[5]
SYSINTR[32]
4294819140 PID:400002 TID:fa0002 ***NDIS*** (a, 735)
4294819140 PID:400002 TID:fa0002 <==NdisMRegisterInterrupt: Miniport
D062BD78, Status 0
4294819146 PID:400002 TID:fa0002 ==>NdisMRegisterAdapterShutdownHandler:
Miniport D062BD78
4294819146 PID:400002 TID:fa0002 <==NdisMRegisterAdapterShutdownHandler:
Miniport D062BD78
4294819147 PID:400002 TID:fa0002
DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI\Instance\E1002) last 98 Ticks
4294819148 PID:400002 TID:fa0002 DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\E1001\BusPrefix) returned 2
4294819149 PID:400002 TID:fa0002 NDIS:ndisAddPCMCIADevice INdisOpenDeviceKey
failed
4294819149 PID:400002 TID:fa0002 NDIS:: CE_AddBusFriendlyName()
[successfully created] [HKLM\Comm\BusFriendlyNames\PCI_0_16_0\E1001]
4294819151 PID:1760002 TID:1010002 [NOTIFY] HandleSystemEvent 7 /ADD HCD2:
4294819151 PID:1760002 TID:1010002 [NOTIFY] HandleSystemEvent 7 /ADD NDS1:
4294819154 PID:400002 TID:fa0002
4294819154 PID:400002 TID:fa0002 ndisMInitializeAdapter: Miniport D062D4F8,
4294819156 PID:400002 TID:fa0002 ==>ndisQueueMiniportOnDriver: Miniport
D062D4F8, MiniBlock D062BB30
4294819156 PID:400002 TID:fa0002 <==ndisQueueMiniportOnDriver: Miniport
D062D4F8, MiniBlock D062BB30, rc 1
4294819156 PID:400002 TID:fa0002 ==>NdisMSetAttributesEx: Miniport D062D4F8
4294819185 PID:400002 TID:fa0002 ## LOOKASIDE INITIALIZE ## [48] bytes,
depth [0]
4294819225 PID:400002 TID:fa0002 ==>NdisMMapIoSpace
4294819225 PID:400002 TID:fa0002 ***NDIS*** (a, 516)
4294819225 PID:400002 TID:fa0002 ==>NdisMRegisterInterrupt: Miniport
D062D4F8 Vector 7
4294819226 PID:400002 TID:fa0002 NDIS:: CeConnectInterrupt() --> IRQ[7]
SYSINTR[29]
4294819226 PID:400002 TID:fa0002 ***NDIS*** (a, 735)

(hangs)
PB Debugger The Kernel Debugger has been disconnected successfully.

.



Relevant Pages

  • Re: Degradation of TCP connection
    ... Gigabit ethernet. ... D card's data buffer can only hold about 64K samples worth of data ... link you posted is for an older version of VxWorks that used a BSD- ... but a bug in the ethernet driver. ...
    (comp.os.vxworks)
  • Re: [PATCH][5/5] RapidIO support: net driver over messaging
    ... It's nothing like Ethernet, the only relation is that an Ethernet network ... It gives easy access to RIO messaging from userspace ... ARP works by the driver emulating a broadcast over RIO by sending the ...
    (Linux-Kernel)
  • Problem with router usb driver...
    ... This driver supports Linux-2.4 kernel. ... configured for LAN, shutdown the ethernet interface: ... The ethernet interface associated with the VKGEther driver was "eth1" ...
    (Ubuntu)
  • Re: Degradation of TCP connection
    ... Gigabit ethernet. ... D card's data buffer can only hold about 64K samples worth of data ... link you posted is for an older version of VxWorks that used a BSD- ... but a bug in the ethernet driver. ...
    (comp.os.vxworks)
  • Problem in compiling Router driver for ubuntu...
    ... This driver supports Linux-2.4 kernel. ... configured for LAN, shutdown the ethernet interface: ... The ethernet interface associated with the VKGEther driver was "eth1" ...
    (Ubuntu)