On Mon, Jul 14, 2014 at 10:39:48PM +0000, Haiyang Zhang wrote: > > -----Original Message----- > > From: Sitsofe Wheeler [mailto:sits...@gmail.com] > > Sent: Monday, July 14, 2014 5:31 PM > > To: Haiyang Zhang > > Cc: KY Srinivasan; David S. Miller; de...@linuxdriverproject.org; linux- > > ker...@vger.kernel.org; net...@vger.kernel.org > > Subject: Re: [BISECTED][REGRESSION] Loading Hyper-V network drivers is > > racy in 3.14+ on Hyper-V 2012 R2 > > Thanks for the tests! I will make a patch that can automatically retry > smaller memory allocs when memory is insufficient.
This concerns me a bit - why would there be insufficient memory on a 64 bit VM with 4 GBytes of RAM just after startup (presumably the host's memory isn't the issue)? Additionally, while things might fail just when things are starting up, doing ifup eth0 at some point later succeeds so whatever issue it had seems temporary. Perhaps it would be wise to adding some debugging output to see if the allocation really failed and why... -- Sitsofe | http://sucs.org/~sits/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
