Bug 612861 - bnx2 page allocation failure
Summary: bnx2 page allocation failure
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Stanislaw Gruszka
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-09 09:17 UTC by Albert Strasheim
Modified: 2010-07-13 19:31 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-13 17:39:45 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/var/log/messages (121.41 KB, text/plain)
2010-07-09 09:17 UTC, Albert Strasheim
no flags Details
Proposed fix. (2.87 KB, text/plain)
2010-07-10 13:27 UTC, Stanislaw Gruszka
no flags Details

Description Albert Strasheim 2010-07-09 09:17:34 UTC
Created attachment 430579 [details]

Description of problem:

I was bringing up a bnx2 interface (eth2) on a Dell M610 while receiving data on another bnx2 interface (eth0) at about 20 MB/s.

I had the following error from the kernel in /var/log/messages:

page allocation failure. order:0, mode:0x20

Version-Release number of selected component (if applicable):


How reproducible:

ifup a few bnx2 interfaces while receiving data

Additional info:

/var/log/messages attached

Comment 1 Stanislaw Gruszka 2010-07-10 13:27:59 UTC
Created attachment 430878 [details]
Proposed fix.

Are you able to test this patch?

Comment 2 Albert Strasheim 2010-07-13 08:38:35 UTC
Thanks for the patch. I can test it, but so far I have been unable to reproduce the allocation failure on the unpatched kernel. Do you have any idea what I need to do to see the allocation failure again on the unpatched kernel before I try the patch?

Comment 3 Stanislaw Gruszka 2010-07-13 17:39:45 UTC
(In reply to comment #2)
> Do you have any idea what I
> need to do to see the allocation failure again on the unpatched kernel before I
> try the patch?    

No. I saw a few memory allocation failures in random places and there was no working steps to reproduce to any of them :(

Since this is issue is not reproducible, I will only post patch upstream, without applying it to fedora kernel.

Thanks for reporting.

Note You need to log in before you can comment on or make changes to this bug.