> Looking at the trace, I can see the cpu wasn't actually doing
> anything when it crashed. Well, an interrupt occured, and that
> apparently is fatal on my machine. Now I wonder why.
It's easy to explain the crash:
> >>EIP: Trace: c01127ae
Someone called add_timer with either an
Mahadev K Cholachagudda wrote:
>
[...]
> > When an interrupt is delivered, the kernel calls ALL interrupt handlers
> > registered for that interrupt. That means all drivers capable of
> > sharing interrupts should, ideally, have code in their interrupt handler
> > to exit ASAP if no work is nece
- Original Message -
From: "Jeff Garzik" <[EMAIL PROTECTED]>
To: "Mahadev K Cholachagudda" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, September 25, 2000 7:00 PM
Subject: Re: Interrupt sharing
>
>
> On Mon, 25 Sep 2000, Ma
On Mon, 25 Sep 2000, Mahadev K Cholachagudda wrote:
> Hello to all,
>
> I have one doubt and is as below.
>
>
> Suppose say the two drivers driver1 and driver2 will install the ISR for a
> particular interrupt, say UART0.
> After some time the interrupt is generated. At this moment, which driv
On Mon, 25 Sep 2000, Mahadev K Cholachagudda wrote:
> Hello to all,
>
> I have one doubt and is as below.
>
>
> Suppose say the two drivers driver1 and driver2 will install the ISR for a
> particular interrupt, say UART0.
> After some time the interrupt is generated. At this moment, which dr
5 matches
Mail list logo