bnx2x: [bnx2x_alloc_rx_sge:513(ethX)]Can't alloc sge

Bug #1535055 reported by Frode Nordahl on 2016-01-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned
Trusty
Medium
Unassigned
Vivid
Medium
Unassigned

Bug Description

During high traffic these messages appear in dmesg.

I believe this has been fixed with this patch:
https://patchwork.ozlabs.org/patch/477200/

Backport potential?

Frode Nordahl (fnordahl) wrote :
description: updated

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1535055

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Frode Nordahl (fnordahl) wrote :

The logs you request was attached manually to the original bug report.

I am unable to have the automatic tools do this for me as we are running a IPv6-only DC and the endpoints used have no IPv6 address.

Please let me know what, if anything, is missing from the attached log/report.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
tags: added: trusty vivid
Changed in linux (Ubuntu Trusty):
status: New → Confirmed
Changed in linux (Ubuntu Vivid):
status: New → Confirmed
Changed in linux (Ubuntu Trusty):
importance: Undecided → Medium
Changed in linux (Ubuntu Vivid):
importance: Undecided → Medium
Joseph Salisbury (jsalisbury) wrote :

I built a Vivid test kernel with a cherry pick of commit:4cace67. The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1535055/

Can you test this kernel and see if it resolves this bug?

Thanks in advance!

Changed in linux (Ubuntu Vivid):
status: Confirmed → In Progress
Changed in linux (Ubuntu Trusty):
status: Confirmed → In Progress
Changed in linux (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Trusty):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Vivid):
assignee: nobody → Joseph Salisbury (jsalisbury)
Frode Nordahl (fnordahl) wrote :

Thank you for your prompt response! I will put this kernel on one of the servers displaying the behaviour and run through operations we know triggers the message. I will report back to you after the weekend.

This bug was nominated against a series that is no longer supported, ie vivid. The bug task representing the vivid nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Vivid):
status: In Progress → Won't Fix
Changed in linux (Ubuntu Trusty):
status: In Progress → Confirmed
Changed in linux (Ubuntu):
status: In Progress → Confirmed
assignee: Joseph Salisbury (jsalisbury) → nobody
Changed in linux (Ubuntu Trusty):
assignee: Joseph Salisbury (jsalisbury) → nobody
Changed in linux (Ubuntu Vivid):
assignee: Joseph Salisbury (jsalisbury) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers