#322 Page allocation failure with e1000e (v1.0.15)

closed
e1000e (107)
standalone_driver
5
2013-07-09
2009-12-09
arturpiechocki
No

Hello,

I have tested new e1000e driver (v1.0.15) and have got call trace with page allocation failure.It was kernel 2.6.27.10, bonding ALB and copy with use Samba, RSYNC and DRBD to other host.With e1000e 1.0.2.5 problem did not occur, but maybe it was accident. Any suggestion?

Thank you in advance

Discussion

  • arturpiechocki
    arturpiechocki
    2009-12-09

    dmesg

     
    Attachments
  • sorry to hear of your problem. Our driver handles allocation failures just fine, but the kernel developers wanted us to leave in the WARN message from the memory allocator. We can make the warning go away with a small code change to add a GFP_NOWARN to the allocation flags. The driver will still work and count memory allocation failures in the ethtool statistics. Otherwise as long as your system keeps functioning and these messages only print once, and infrequently, these messages are not a fatal error or an indication of a driver bug.

    In your case the memory subsystem was unable to provide a single page (order 0) of memory on demand (from interrupt context) which happens sometimes, often more on one kernel than another.

    I think you were just lucky that the problem didn't occur with 1.0.2.5.

    Please let me know if you would like a nowarn patch for 1.0.15 or newer.

     
  • Todd Fujinaka
    Todd Fujinaka
    2013-07-09

    Closing due to inactivity.

     
  • Todd Fujinaka
    Todd Fujinaka
    2013-07-09

    • status: open --> closed