bonding: don't use stale speed and duplex information

Bug #1646068 reported by Nicolas Dichtel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Joseph Salisbury
Trusty
Incomplete
Medium
Joseph Salisbury
Vivid
Won't Fix
Medium
Joseph Salisbury
Xenial
Incomplete
Medium
Joseph Salisbury

Bug Description

This upstream patch is missing (needed for all kernel between 3.9 and 4.4 (both included)):

266b495f11d6 bonding: don't use stale speed and duplex information
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=266b495f11d6

Without this patch, reported speeds can be wrong.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1646068

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
Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
Changed in linux (Ubuntu Trusty):
status: New → Triaged
Changed in linux (Ubuntu Vivid):
status: New → Triaged
Changed in linux (Ubuntu Xenial):
status: New → Triaged
Changed in linux (Ubuntu Trusty):
importance: Undecided → Medium
Changed in linux (Ubuntu Vivid):
importance: Undecided → Medium
Changed in linux (Ubuntu Xenial):
importance: Undecided → Medium
tags: added: kernel-da-key trusty vivid xenial
Changed in linux (Ubuntu):
status: Triaged → In Progress
Changed in linux (Ubuntu Trusty):
status: Triaged → In Progress
Changed in linux (Ubuntu Vivid):
status: Triaged → In Progress
Changed in linux (Ubuntu Xenial):
status: Triaged → In Progress
Changed in linux (Ubuntu):
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)
Changed in linux (Ubuntu Xenial):
assignee: nobody → Joseph Salisbury (jsalisbury)
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I built a vivid and Xenial test kernel with the patch. The test kernels can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1646068/vivid/
http://kernel.ubuntu.com/~jsalisbury/lp1646068/xenial

The patch needed a minor backport to apply to Xenial. Vivid needed the same backport of the patch, but also required commit 69a2338 as a prerequisite.

Trusty on the other hand requires quite a few prerequisite commits for the patch to apply cleanly. I'm still working to identify all the prereqs.

Could you test the Vivid an Xenial test kernels to see if the resolve the bug. I'll post an update when the Trusty test kernel is ready.

Revision history for this message
Nicolas Dichtel (nicolas-dichtel) wrote :

The bug has been seen by one of our client and the patch has fixed the problem for them, but we never succeed to reproduce the problem. The commitlog of the patch also confirms the analysis.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks for the update, Nicholas. Did the client confirm the vivid or xenial test kernel resolves the bug, or maybe both?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

There is now a Trusty test kernel available as well. It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1646068/trusty

Changed in linux (Ubuntu):
status: In Progress → Incomplete
Changed in linux (Ubuntu Trusty):
status: In Progress → Incomplete
Changed in linux (Ubuntu Vivid):
status: In Progress → Incomplete
Changed in linux (Ubuntu Xenial):
status: In Progress → Incomplete
Revision history for this message
Vincent JARDIN (vincent-jardin) wrote :

They build their own kernel, they cannot test your http://kernel.ubuntu.com/~jsalisbury/lp1646068/trusty

From the code review, this fix is needed.

Changed in linux (Ubuntu):
status: Incomplete → In Progress
Changed in linux (Ubuntu Trusty):
status: Incomplete → In Progress
Changed in linux (Ubuntu Vivid):
status: Incomplete → In Progress
Changed in linux (Ubuntu Xenial):
status: Incomplete → In Progress
Changed in linux (Ubuntu):
status: In Progress → Incomplete
Changed in linux (Ubuntu Trusty):
status: In Progress → Incomplete
Changed in linux (Ubuntu Vivid):
status: In Progress → Incomplete
Changed in linux (Ubuntu Xenial):
status: In Progress → Incomplete
Revision history for this message
Andy Whitcroft (apw) wrote : Closing unsupported series nomination.

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: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.