Re: about the shared IRQ with giisr.dll by Stanley
Stanley
Mon May 21 02:56:02 CDT 2007
The problem seems to be solved. It seems to cause by the parameter "PortAddr"
of GIISR_INFO. I give the address which return by MmMapIOSpace(). It will be
data abort when the interrupt is occurred.
Then, I fixed it by giving the kernel space address then it works.
Thanks for your suggestion.
Regards,
"David Liao (MS)" wrote:
> It looks like your GIISR does not identify the Interrupt source correctly.
> I believe the crash is caused by kernel stack overflow due to the intererupt
> storm.
>
> If you do not identify the interrupt correctly (SYSINTR_CHAIN or SYSINTR_NOP
> returned), the static ISR inside OAL will re-enable the interrupt. Because
> the interrupt sources is not removed, interrupt storm happens.
>
> David Liao
>
> "Stanley" <Stanley@discussions.microsoft.com> wrote in message
> news:F610D511-FD6E-4133-9E05-A06097CF41D7@microsoft.com...
> >I use the giisr.dll for sharing the IRQ with 2 port of PS2 device. The
> >module
> > giisr.dll is loaded successfully. But, once the interrupt is occurred, the
> > kernel will crash. Is anyone meet the same problem with me?
> > I use the KITL for debugging but it can't debug in IRQ mode. Please help
> > me
> > to solve it.
> >
> > Regards,
>
>
>