(no subject)

David Hinds (dhinds@zen.stanford.edu)
Tue, 1 Jun 1999 14:20:03 -0700

>started, never ran those on my laptop), is for the interface to be left in
>a hung state, with the entire networking stack (or at least the bits I can
>get to) completely frozen. I'm forced to reboot to clear the state and
>get back to work.

This was fixed in the 3.0.10 drivers; 3.0.11 is current now.

> The PCMCIA code last time I checked was still calling network device
> driver admin routines from an interrupt. If that hasnt been fixed in
> pcmcia-cs that would explain these kind of behaviours

This used to be safe (or at least, had no visible side effects). It
might be nice to have a goal of documenting kernel interfaces to at
least the extent where it is clear what things can be used in what
contexts.

-- Dave Hinds

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