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

2019-07-24 Thread Brad Figg
** Tags added: cscc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535055 Title: bnx2x: [bnx2x_alloc_rx_sge:513(ethX)]Can't alloc sge To manage notifications about this bug go to:

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

2019-01-22 Thread Joseph Salisbury via ubuntu-bugs
** Changed in: linux (Ubuntu Trusty) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Trusty) Assignee:

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

2016-01-22 Thread Frode Nordahl
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

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

2016-01-21 Thread Joseph Salisbury
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key ** Tags added: trusty vivid ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New **

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

2016-01-21 Thread Joseph Salisbury
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

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

2016-01-17 Thread Frode Nordahl
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