[tulip-bug] Possible deadlock with tulip driver

[A E Lawrence]

Andrew Morton wrote:
> 
> A E Lawrence wrote:
> >
> > I seem to have encountered a possible deadlock using the latest tulip
> > driver which shows up in both 2.2.16 and 2.2.17. Long report attached.
> >
> > ...
> >  Interrupt sources are pending!  CSR5 is 02670055.
> 
> I wonder if this could be the infamous APIC interrupt problem, where
> APICs stop generating interrupts?  I doubt it, because you didn't report
> a Tx timeout, and ifdown/ifup clears the problem.

It seems that there *is* a deadlock in the driver and it has been
reported before. In fact I am told that there are 3 known bugs, although
I haven't had time to investigate myself.

Adrian
-- 
Dr A E Lawrence (from home)