Am Mittwoch, 13. Juni 2007 schrieb Patrick McHardy: > Oliver Neukum wrote: > > Am Mittwoch, 13. Juni 2007 schrieb Patrick McHardy: > >>>> > >>>>This can happen if the initial inetdev allocation when the netdevice is > >>>>registered fails. I think it would make sense to try to allocate again > >>>>when adding addresses in that case, otherwise there is no way of > >>>>recovery other than unregistering and registering the device again. > >>> > >>> > >>>With your patch the problem has gone away. Is there a way to especially > >>>stress the system in that regard? > >> > >> > >>Its a failed allocation at NETDEV_REGISTER time. I guess you could > >>keep unloading + reloading the driver module to try to reproduce it. > > > > > > If that is the cause, why doesn't it strike from the very beginning? How > > come it fails after some time? > > > It might also be a failed in_ifaddr allocation. In that case my patch > shouldn't help though.
The problem is that I don't know how to provoke the failure. I might be doing another workload today than yesterday. Perhaps I should do several compilations like yesterday? Regards Oliver - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html