We here are getting the above error. Our group is developing an
application and driver for a Digital transport stream interface card on
NT.
Softice says CLOCK2 - KTEB … ntoskrnl!.text…
KeBugCheckEx
Error=5 (INVALID_PROCESS_ATTACH_ATTEMPT)
My questions are
What are the situations ths error message occurs? (We get this while
using our product!)
Can this error be caused by application or is it only by the driver
code?
What is this CLOCK2?
Stop using KeAttachProcess and use KeStackAttachProcess instead.
KeAttachProcess can only be called once in a call sequence within a given
thread. The second call (without an intervening KeDetachProcess) will cause
this error.
If you aren’t using KeAttachProcess, you need to figure out who is using it
and determine a strategy for dealing with this problem (e.g., posting the
work to a worker thread, where it won’t be in an attached process context.)
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: Anand Madangopal [mailto:xxxxx@tataelxsi.co.in]
Sent: Wednesday, July 31, 2002 2:56 AM
To: File Systems Developers
Subject: [ntfsd] INVALID_PROCESS_ATTACH_ATTEMPT
We here are getting the above error. Our group is developing an
application and driver for a Digital transport stream interface card on
NT.
Softice says CLOCK2 - KTEB … ntoskrnl!.text…
KeBugCheckEx
Error=5 (INVALID_PROCESS_ATTACH_ATTEMPT)
My questions are
What are the situations ths error message occurs? (We get this while
using our product!)
Can this error be caused by application or is it only by the driver
code?
What is this CLOCK2?
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to %%email.unsub%%
We are not using KeProcessAttach!
We are working on this we will get back to you soon. We have another query
in the same product…
we are having
the following issue on the NT 4.0 Platform:
DMA ISSUES:
The Win NT driver needs to do DMA to SDRAM present on a PCI card.
The DMA is done using user mode buffers and MDLs. The DMA controller
present on the PCI card (bus master DMA) is used for this purpose.
The size of each DMA is around 1MB. DMA chaining is used. Each time
IOMaptransfer is called to build the DMA chain list, it always limits
the size of the transfer to 4KB (page size on x86). Hence our loop runs
for 256 times to complete the DMA chaining for 1MB. This limits our DMA
performance on some PC architectures.
Is it possible to configure NT so that IOMapRegister gives a transfer
size that is a multiple of the page size(Eg 64K)? This would cause the
chaining loop to execute fewer times.By doing so can any performance
improvement be acheived? (Eg: Time taken to find consecutive map
registers can offset the # of times the loop is run)
Could you please help us to resolve it. Thank you in advance.
Regards,
Anand Madangopal.
----- Original Message -----
From: “Anand Madangopal”
To: “File Systems Developers”
Sent: Wednesday, July 31, 2002 11:34 AM
Subject: [ntfsd] RE: INVALID_PROCESS_ATTACH_ATTEMPT
> We are not using KeProcessAttach!
>
> We are working on this we will get back to you soon. We have another query
> in the same product…
>
> we are having
> the following issue on the NT 4.0 Platform:
>
> DMA ISSUES:
>
> The Win NT driver needs to do DMA to SDRAM present on a PCI card.
> The DMA is done using user mode buffers and MDLs. The DMA controller
> present on the PCI card (bus master DMA) is used for this purpose.
> The size of each DMA is around 1MB. DMA chaining is used. Each time
> IOMaptransfer is called to build the DMA chain list, it always limits
> the size of the transfer to 4KB (page size on x86). Hence our loop runs
> for 256 times to complete the DMA chaining for 1MB. This limits our DMA
> performance on some PC architectures.
>
> Is it possible to configure NT so that IOMapRegister gives a transfer
> size that is a multiple of the page size(Eg 64K)? This would cause the
> chaining loop to execute fewer times.By doing so can any performance
> improvement be acheived? (Eg: Time taken to find consecutive map
> registers can offset the # of times the loop is run)
>
> Could you please help us to resolve it. Thank you in advance.
>
>
> Regards,
> Anand Madangopal.
>
> —
> You are currently subscribed to ntfsd as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to %%email.unsub%%
>
Please give us a stack dump retreived from the crash dump, or directly from
Windbg, at bugcheck time. Use OS symbols for this, and watch out, NTICE
spits out much more often garbage stack backtraces than Windbg. So
preferably use Windbg.
Dan
----- Original Message -----
From: “Anand Madangopal”
To: “File Systems Developers”
Sent: Wednesday, July 31, 2002 11:34 AM
Subject: [ntfsd] RE: INVALID_PROCESS_ATTACH_ATTEMPT
> We are not using KeProcessAttach!
>
> We are working on this we will get back to you soon. We have another query
> in the same product…
>
> we are having
> the following issue on the NT 4.0 Platform:
>
> DMA ISSUES:
>
> The Win NT driver needs to do DMA to SDRAM present on a PCI card.
> The DMA is done using user mode buffers and MDLs. The DMA controller
> present on the PCI card (bus master DMA) is used for this purpose.
> The size of each DMA is around 1MB. DMA chaining is used. Each time
> IOMaptransfer is called to build the DMA chain list, it always limits
> the size of the transfer to 4KB (page size on x86). Hence our loop runs
> for 256 times to complete the DMA chaining for 1MB. This limits our DMA
> performance on some PC architectures.
>
> Is it possible to configure NT so that IOMapRegister gives a transfer
> size that is a multiple of the page size(Eg 64K)? This would cause the
> chaining loop to execute fewer times.By doing so can any performance
> improvement be acheived? (Eg: Time taken to find consecutive map
> registers can offset the # of times the loop is run)
>
> Could you please help us to resolve it. Thank you in advance.
>
>
> Regards,
> Anand Madangopal.
>
> —
> You are currently subscribed to ntfsd as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to %%email.unsub%%
>