[lkml]   [2000]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.2.16 deadlocking in schedule()

> > > 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.
I'm "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.067 / U:1.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site