On 06-09-23 17:27 Matthieu CASTET wrote:

> Hi,
> On Fri, 22 Sep 2006 17:44:21 -0400, Daniel Drake wrote:
> > 
> > Looks like the housekeeping work functions rescheduled themselves after 
> > the disconnect. There was a possible race where this might have happened 
> > for a short time, but it is believed to be fixed now. So this all 
> > depends on the date of your snapshot.
> > 
> I got the same problem again.
> I am under the impression that network interface is still present.
> So it is ether an usb-core bug not calling disconnect or the disconnect
> that hang somewhere (deadlock, ...).

Ok, if the disconnect() is called unregister_netdev() is called,
which should stop the interface, which will then disable the
callback handler. That doesn't appear to happen. Next step needs
to be to find that.

Uli Kunitz

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

Reply via email to