IRQ line problem

NTDEV
1

hi, all
i have written a driver for Video Broadcasting device ( it’s PCI
device) i can load and test this driver in all the s/m’s
The problem is in Compaq s/m’s the IRQ line 7 is used by parallel
device( setup says parallel device is a motherboard device) , my
device loads properly by aquiring IRQ line 7 but when i run my
appication it crashed ( IRQ_NOT_LESS_OR_EQUAL)
and the 2nd parameter of the blue screen gives 7 as the IRQ line.

this happened at very first time ( first run after installing the
driver) after the first crash it is working fine
any suggestions ?

thanks
shiva

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

I am not sure why it would work after the first crash, but what I can offer
is my experience that certain motherboard devices use interrupts that
should not be allocated to the PCI bus. I would check the BIOS settings to
see if you can prevent the BIOS from assigning IRQ 7 to any PCI bus since
it is already used by the parallel port, unless you know that you don’t
want to use the parallel port, in which case you can disable that driver.

Shaun

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Shiva Mallu
Sent: Monday, November 26, 2001 6:30 AM
To: NT Developers Interest List
Subject: [ntdev] IRQ line problem

hi, all
i have written a driver for Video Broadcasting device ( it’s PCI
device) i can load and test this driver in all the s/m’s
The problem is in Compaq s/m’s the IRQ line 7 is used by parallel
device( setup says parallel device is a motherboard device) , my
device loads properly by aquiring IRQ line 7 but when i run my
appication it crashed ( IRQ_NOT_LESS_OR_EQUAL)
and the 2nd parameter of the blue screen gives 7 as the IRQ line.

this happened at very first time ( first run after installing the
driver) after the first crash it is working fine
any suggestions ?

thanks
shiva

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

Shiva, Shaun,

Some times the Bios setup allows disabling the parallel port. If that option
is available, it’s easy to check whether the crash is being caused by a
conflict. Also, before you run the application, looking at the settings of
the device manager will tell whether Windows thinks there’s a conflict.

Also, have you tried to analyze the dump and see what it tells you ?

Alberto.

-----Original Message-----
From: Shaun Ruffell [mailto:xxxxx@tenpennies.com]
Sent: Monday, November 26, 2001 10:34 AM
To: NT Developers Interest List
Subject: [ntdev] RE: IRQ line problem

I am not sure why it would work after the first crash, but what I can offer
is my experience that certain motherboard devices use interrupts that
should not be allocated to the PCI bus. I would check the BIOS settings to
see if you can prevent the BIOS from assigning IRQ 7 to any PCI bus since
it is already used by the parallel port, unless you know that you don’t
want to use the parallel port, in which case you can disable that driver.

Shaun

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Shiva Mallu
Sent: Monday, November 26, 2001 6:30 AM
To: NT Developers Interest List
Subject: [ntdev] IRQ line problem

hi, all
i have written a driver for Video Broadcasting device ( it’s PCI
device) i can load and test this driver in all the s/m’s
The problem is in Compaq s/m’s the IRQ line 7 is used by parallel
device( setup says parallel device is a motherboard device) , my
device loads properly by aquiring IRQ line 7 but when i run my
appication it crashed ( IRQ_NOT_LESS_OR_EQUAL)
and the 2nd parameter of the blue screen gives 7 as the IRQ line.

this happened at very first time ( first run after installing the
driver) after the first crash it is working fine
any suggestions ?

thanks
shiva

You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

4

Wouldn’t in general sharing an ISA interrupt (parallel port) with a PCI
interrupt be bad, wrong, evil, twisted, and unworkable on an nt platform? I
rather doubt that the interrupt configuration is really configured as the
poster thinks.

-----Original Message-----
From: Moreira, Alberto [mailto:xxxxx@compuware.com]
Sent: Monday, November 26, 2001 10:53 AM
To: NT Developers Interest List
Subject: [ntdev] RE: IRQ line problem

Shiva, Shaun,

Some times the Bios setup allows disabling the parallel port. If that option
is available, it’s easy to check whether the crash is being caused by a
conflict. Also, before you run the application, looking at the settings of
the device manager will tell whether Windows thinks there’s a conflict.

Also, have you tried to analyze the dump and see what it tells you ?

Alberto.

-----Original Message-----
From: Shaun Ruffell [mailto:xxxxx@tenpennies.com]
Sent: Monday, November 26, 2001 10:34 AM
To: NT Developers Interest List
Subject: [ntdev] RE: IRQ line problem

I am not sure why it would work after the first crash, but what I can offer
is my experience that certain motherboard devices use interrupts that should
not be allocated to the PCI bus. I would check the BIOS settings to see if
you can prevent the BIOS from assigning IRQ 7 to any PCI bus since it is
already used by the parallel port, unless you know that you don’t want to
use the parallel port, in which case you can disable that driver.

Shaun

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Shiva Mallu
Sent: Monday, November 26, 2001 6:30 AM
To: NT Developers Interest List
Subject: [ntdev] IRQ line problem

hi, all
i have written a driver for Video Broadcasting device ( it’s PCI
device) i can load and test this driver in all the s/m’s
The problem is in Compaq s/m’s the IRQ line 7 is used by parallel device(
setup says parallel device is a motherboard device) , my device loads
properly by aquiring IRQ line 7 but when i run my appication it crashed (
IRQ_NOT_LESS_OR_EQUAL) and the 2nd parameter of the blue screen gives 7 as
the IRQ line.

this happened at very first time ( first run after installing the
driver) after the first crash it is working fine
any suggestions ?

thanks
shiva

You are currently subscribed to ntdev as: xxxxx@compuware.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

5

I don’t know, I thought that this was the sort of thing that the ACPI would
have alleviated ? But at that level you never know how people implement
things, and Mark, you may be right here. That’s why I suggested disabling
the parallel port if possible, it’d quickly tell them whether sharing is the
problem.

Alberto.

-----Original Message-----
From: Roddy, Mark [mailto:xxxxx@stratus.com]
Sent: Monday, November 26, 2001 11:28 AM
To: NT Developers Interest List
Subject: [ntdev] RE: IRQ line problem

Wouldn’t in general sharing an ISA interrupt (parallel port) with a PCI
interrupt be bad, wrong, evil, twisted, and unworkable on an nt platform? I
rather doubt that the interrupt configuration is really configured as the
poster thinks.

-----Original Message-----
From: Moreira, Alberto [mailto:xxxxx@compuware.com]
Sent: Monday, November 26, 2001 10:53 AM
To: NT Developers Interest List
Subject: [ntdev] RE: IRQ line problem

Shiva, Shaun,

Some times the Bios setup allows disabling the parallel port. If that option
is available, it’s easy to check whether the crash is being caused by a
conflict. Also, before you run the application, looking at the settings of
the device manager will tell whether Windows thinks there’s a conflict.

Also, have you tried to analyze the dump and see what it tells you ?

Alberto.

-----Original Message-----
From: Shaun Ruffell [mailto:xxxxx@tenpennies.com]
Sent: Monday, November 26, 2001 10:34 AM
To: NT Developers Interest List
Subject: [ntdev] RE: IRQ line problem

I am not sure why it would work after the first crash, but what I can offer
is my experience that certain motherboard devices use interrupts that should
not be allocated to the PCI bus. I would check the BIOS settings to see if
you can prevent the BIOS from assigning IRQ 7 to any PCI bus since it is
already used by the parallel port, unless you know that you don’t want to
use the parallel port, in which case you can disable that driver.

Shaun

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Shiva Mallu
Sent: Monday, November 26, 2001 6:30 AM
To: NT Developers Interest List
Subject: [ntdev] IRQ line problem

hi, all
i have written a driver for Video Broadcasting device ( it’s PCI
device) i can load and test this driver in all the s/m’s
The problem is in Compaq s/m’s the IRQ line 7 is used by parallel device(
setup says parallel device is a motherboard device) , my device loads
properly by aquiring IRQ line 7 but when i run my appication it crashed (
IRQ_NOT_LESS_OR_EQUAL) and the 2nd parameter of the blue screen gives 7 as
the IRQ line.

this happened at very first time ( first run after installing the
driver) after the first crash it is working fine
any suggestions ?

thanks
shiva

You are currently subscribed to ntdev as: xxxxx@compuware.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

6

I have seen this for serial ports…where the serial driver assigns IRQ 5,
and IRQ 5 is also assigned to devices on the PCI bus. Although, in this
case it didn’t crash, the PCI device that I had written the driver for
reported that it couldn’t allocate IRQ5. Making IRQ5 off limits for PCI
devices fixed the problem in that case.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roddy, Mark
Sent: Monday, November 26, 2001 8:28 AM
To: NT Developers Interest List
Subject: [ntdev] RE: IRQ line problem

Wouldn’t in general sharing an ISA interrupt (parallel port) with a PCI
interrupt be bad, wrong, evil, twisted, and unworkable on an nt platform? I
rather doubt that the interrupt configuration is really configured as the
poster thinks.

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

7

Yeah sure that would be because the PCI interrupt is shared/level and the
ISA interrupt is exclusive/latched, so they wouldn’t mix right and the
attempt to allocate the interrupt object by the (shared/level) PCI device
would fail. But the original poster seemed to think that the interrupt
object allocation succeeded, which means that either he is requesting an
exclusive/latched pci interrupt (bad wrong evil and twisted,) or the
parallel port interrupt is offering itself up as shared/level (bad wrong
evil and twisted.)

I could believe that he couldn’t allocate an interrupt object, and then
crashed later due to a bug in his driver, but I have a real hard time
believing that he actually managed to allocate the parallel port interrupt
object for his pci driver.

-----Original Message-----
From: Shaun Ruffell [mailto:xxxxx@tenpennies.com]
Sent: Monday, November 26, 2001 11:47 AM
To: NT Developers Interest List
Subject: [ntdev] RE: IRQ line problem

I have seen this for serial ports…where the serial driver assigns IRQ 5,
and IRQ 5 is also assigned to devices on the PCI bus. Although, in this
case it didn’t crash, the PCI device that I had written the driver for
reported that it couldn’t allocate IRQ5. Making IRQ5 off limits for PCI
devices fixed the problem in that case.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roddy, Mark
Sent: Monday, November 26, 2001 8:28 AM
To: NT Developers Interest List
Subject: [ntdev] RE: IRQ line problem

Wouldn’t in general sharing an ISA interrupt (parallel port) with a PCI
interrupt be bad, wrong, evil, twisted, and unworkable on an nt platform? I
rather doubt that the interrupt configuration is really configured as the
poster thinks.

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

8

I believe this could happen if his driver was set to start before the
parallel port driver, and there was already a parallel port interrupt
pending. He wouldn’t know it was already allocated, and his driver might
not expect it to be shared. Normally when this type of stuff happens, the
driver simply locks up in the interrupt handler if it is written
properly…and doesn’t cause a blue screen.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roddy, Mark
Sent: Monday, November 26, 2001 8:53 AM
To: NT Developers Interest List
Subject: [ntdev] RE: IRQ line problem

Yeah sure that would be because the PCI interrupt is shared/level and the
ISA interrupt is exclusive/latched, so they wouldn’t mix right and the
attempt to allocate the interrupt object by the (shared/level) PCI device
would fail. But the original poster seemed to think that the interrupt
object allocation succeeded, which means that either he is requesting an
exclusive/latched pci interrupt (bad wrong evil and twisted,) or the
parallel port interrupt is offering itself up as shared/level (bad wrong
evil and twisted.)

I could believe that he couldn’t allocate an interrupt object, and then
crashed later due to a bug in his driver, but I have a real hard time
believing that he actually managed to allocate the parallel port interrupt
object for his pci driver.

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com