When the timer interrupt fires, io-pkt is not scheduled. From the kernel trace:

Interrupt 0x0, Entry, who procnto-instr - CPU 1 idle interrupt 0x0 ip 0xf00879ae
Interrupt 0x0 Process 1, Handler Entry, pid 1 interrupt 0x0 ip 0xf005a430 area 0x0 process procnto-instr
Interrupt 0x0 Process 1, Handler Exit, interrupt 0x0 sigev_notify 0
Interrupt 0x0, Exit, interrupt 0x0 flags 0x81
<no Sigevent like other interrupts>

Yes, we use "priority=32" when mounting the e1000 driver on the second stack. This is reflected in the priority labels 
in the kernel trace (we ran wide mode to verify thread priorities).

Mark

Where do you get the information that io-usb disable interrupt for long time(how long), as far as I remember there was 
some host controller driver making lots delay, but that only on initalization. 
Sent from BlackBerry

----- Original Message -----
From: Armin Steinhoff [mailto:community-noreply@qnx.com]
Sent: Friday, December 21, 2012 05:03 PM
To: drivers-networking@community.qnx.com <drivers-networking@community.qnx.com>
Cc: Info System - IS Automated Notifications; Info System - IS Automated Notifications
Subject: Re: Two instances of io-pkt interfering with each other

Mark Dowdy wrote:
> Ah, forgot to mention that. We are running 6.5.0 SP1. We can't move back to 6.4.1 because we have a new multicore 
machine that we're about to deploy and the NIC in that machine (Intel 82576, device id 10c9h) isn't supported in 6.4.1.

OK ... be careful if you use APIC/MSI.
An other critical point is the PCI interrupt if it is shared with io-usb 
...  the resource manager of io-usb seems to disable/block that shared 
interrupt for a longer time.

--Armin

>
> We're using the devnp-e1000 driver from SP1 (see below), I'll try the driver Dennis referenced to see if it makes any 
difference.
>
> # use -i /lib/dll/devnp-e1000.so
> NAME=devnp-e1000.so
> DESCRIPTION=Driver for Intel 82544 Gigabit Ethernet controllers
> DATE=2012/06/20-13:37:46-EDT
> STATE=stable
> HOST=gusbuild4
> USER=builder
> VERSION=6.5.0
> TAGID=650SP1-166
>
> Thanks.
>
> Mark
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post98293
> To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com
>





_______________________________________________

Networking Drivers
http://community.qnx.com/sf/go/post98295
To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

There are some shared interrupts but not with io-usb.

# pci

PCI version    = 3.00

Class          = Mass Storage (IDE)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 2680h,  631xESB/632xESB/3100 Chipset SATA IDE Controller
PCI index      = 0h
BAR - 0 [I/O]  = 0h enabled
BAR - 1 [I/O]  = 0h enabled
BAR - 2 [I/O]  = 0h enabled
BAR - 3 [I/O]  = 0h enabled
BAR - 4 [I/O]  = 1870h enabled
PCI Int Pin    = INT B
Interrupt line = no connection

Class          = Network (Ethernet)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 1096h,  80003ES2LAN Gigabit Ethernet Controller (Copper)
PCI index      = 0h
BAR - 0 [Mem]  = d8020000h enabled
BAR - 1 [Mem]  = d8000000h enabled
BAR - 2 [I/O]  = 2000h enabled
PCI Expansion ROM = 0h disabled
PCI Int Pin    = INT A
Interrupt line = 11
CPU Interrupt  = bh

Class          = Network (Ethernet)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 1096h,  80003ES2LAN Gigabit Ethernet Controller (Copper)
PCI index      = 1h
BAR - 0 [Mem]  = d8060000h enabled
BAR - 1 [Mem]  = d8040000h enabled
BAR - 2 [I/O]  = 2020h enabled
PCI Expansion ROM = 0h disabled
PCI Int Pin    = INT B
Interrupt line = 10
CPU Interrupt  = ah

Class          = Display (VGA)
Vendor ID      = 1002h, ATI Technologies Inc
Device ID      = 515eh,  ES1000
PCI index      = 0h
BAR - 0 [Mem]  = d0000000h enabled
BAR - 1 [I/O]  = 3000h enabled
BAR - 2 [Mem]  = d8200000h enabled
PCI Expansion ROM = 0h disabled
PCI Int Pin    = INT A
Interrupt line = 11
CPU Interrupt  = bh