RE: e100 doing bad things in 2.5.44.

From: Feldman, Scott (scott.feldman@intel.com)
Date: Sat Oct 26 2002 - 23:30:45 EST


> Well, it holds bdp->isolate_lock for an incredibly long time, so that
> might trigger this. At least interrupts aren't disabled.
>
> Another bug: e100_close doesn't get the lock.

This came up earlier and we're working on getting rid of isolate_lock
altogether. It's a bunch of complication for no real benefit, really.

> > Oct 25 18:38:12 tetrachloride kernel: Mem:0xfeafc000
> > IRQ:20 Speed:0 Mbps Dx:N/A
>
> Cosmetic or real, that's indeed another bug...

We'll I guess no link would give you a speed of zero Mbps. ;)

I'm inclined to strike this message line because it's 1) misleading, 2)
redundant.

-scott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Thu Oct 31 2002 - 22:00:32 EST