Messages in this thread |  | | Date | Fri, 1 Sep 2000 22:13:27 +0200 | From | Pavel Machek <> | Subject | Re: 2.2.16 deadlocking in schedule() |
| |
Hi!
> > > I think I have found something. I've currently got 4 processes deadlocked > > > on DAC960_WaitForCommand. > > > > > > This machine is a VA Linux VAR Server 3000. > > > > If they stay deadlocked there then let Leonard Zubkoff know. He's both the > > DAC960 guru and happens to work for VA so will know the box too 8) > > With Leonard's help, I have determined that it is a defective card. After > some amount of time, it ceases to generate interrupts. Now to contact > support...
Hmm, then hook it on timer interrupt ;-). Seriously, if it only misses few interrupts, then generate interrupt for it once a second; that should pick up any interrupts missed. Pavel -- I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |