in the future please copy net...@vger.kernel.org on networking issues. On Mon, Mar 1, 2010 at 9:34 AM, Richard Hartmann <richih.mailingl...@gmail.com> wrote: > Hi Jesse, > >> the memory allocation (order:0), while unexpected, are not fatal, and >> the e1000 driver is written to handle the failures during allocation. >> >> Does something else happen to the system after this or does operation >> continue? > > I can not be sure, but I _think_ some bogus data made it into userspace. > I did have some binary in a text string I received & logged, which is a > tad unusual.
hm, if that did occur it would be bad. But it does sound like operation continued, which is good. >> You might be able to try the sysctl tweak to reserve a little more >> memory for driver allocations. >> # sysctl vm.min_free_kbytes >> # sysctl -e vm.min_free_kbytes=<double what you have> > > I will try that, thanks. > > >> have you increased the number of rx/tx descriptors in use by e1000? > > No. Should I? I wouldn't recommend it if you're already having issues getting order:0 allocations, it would just make the problem worse. I wanted to make sure you were not. Jesse ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
