This bug has been copied from bug #671595 and has been proposed
to be backported to 5.6 z-stream (EUS).
Do you know when this kernel version will be made available ?
Thanks in advance.
(In reply to comment #5)
> Do you know when this kernel version will be made available ?
> Thanks in advance.
Is there any test kernel version we could use to start deploying the servers without waiting until march (our customer is in a hurry!).
(In reply to comment #7)
> Is there any test kernel version we could use to start deploying the servers
> without waiting until march (our customer is in a hurry!).
I can provide you such test kernel. Which arch are you interested in?
I need x86_64 at least, i386 will be nice to have.
(In reply to comment #9)
> I need x86_64 at least, i386 will be nice to have.
Please let me know if you need anything more.
Do you have the kernel-devel packages ?
(In reply to comment #12)
> Do you have the kernel-devel packages ?
They are there now.
(In reply to comment #13)
> (In reply to comment #12)
> > Do you have the kernel-devel packages ?
> They are there now.
One more thing, what are the chances of getting an updated boot image for 5.6 we could use to kickstart servers without having to reconfigure the network later (since with the original 5.6 kernel it will panic as soon as the bonded interface is brought up).
Any news regarding getting the updated boot image ?
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Prior to this update, the be2net driver failed to work with bonding, causing "flapping" errors (the interface switches between states up and down) in the active interface. This was due to the fact that the netdev->trans_start pointer in the be_xmit function was not updated. With this update, the aforementioned pointer has been properly updated and "flapping" errors no longer occur.