--- Comment From ru...@us.ibm.com 2017-04-06 17:50 EDT---
Sorry about the long delay, but our bridge missed the last two LP status
updates. Validated with 4.4.0-72 and closing on our end. Thanks.
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16042
--
You
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1616107
Title:
Kernel oops + system
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1616107
Title:
Kernel oops + system
https://lists.ubuntu.com/archives/kernel-team/2016-December/081252.html
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu)
Status: Confirmed
Given 4.4 is maintained by gregk-h, I'd suggest you just submit that
patch to stable@k.o...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1616107
Title:
Kernel oops
Based on the investigation so far, it seems to me that this is entirely
a kernel bug, and there is nothing required in the bridge-utils package
in order to fix this issue. So I'm marking this bug as Invalid for
bridge-utils. The kernel tasks remain open. If this is incorrect, please
explain why
I can confirm that I have this issue in a ubuntu based OS (proxmox). I
have the hardware, is there anything I can do to help resolve this
issue?
Setting up /etc/network/interfaces with the "no-auto-down" option
doesn't help, it prevents the interface from coming up all together.
--
You
Default Comment by Bridge
** Tags added: architecture-ppc64le bugnameltc-148746 severity-high
targetmilestone-inin---
** Attachment added: "sosreport from the iaos1 host."
https://bugs.launchpad.net/bugs/1616107/+attachment/4778262/+files/sosreport-iaos1-20161115131621.tar.xz
--
You
Kernel 4.8 just make 16.04 proposed repository. Does it happen on Ubuntu
16.04 with kernel 4.8?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1616107
Title:
Kernel
Unfortunately I have to confirm, that I no longer have the hardware to
test it on.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1616107
Title:
Kernel oops + system
We started a Reverse bisect in comment #17. However, it appears the
hardware is no longer avaiable.
As mentioned in comment #22, this is fixed in Yakkety. You could use
that kernel, but if you can reproduce the bug, we can continue the
reverse bisect? That would allow us to identify the commit
6 weeks later what's the fix for this? I think we can safely assume that
this bug affects everyone using a bridged bnx2x device and 16.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
** Changed in: bridge-utils (Ubuntu Yakkety)
Importance: Undecided => High
** Changed in: bridge-utils (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Importance: High => Critical
** Changed in: bridge-utils (Ubuntu Yakkety)
Importance: High =>
This bug affects me too. I'm working on a Tyan Power8 machine (PPC64el) with
Ubuntu 16.04.1 and 10GB network cards using the bnx2x driver. A configured
network bridge on my machine results in a kernel oops if I trigger a shutdown
or reboot, see attachment.
I installed the 4.8.0-040800-generic
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bridge-utils (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bridge-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
I'll have the servers for another ~2 weeks for testing. After that
they're going off to the customer with Ubuntu 14. Please tell me now if
you need more testing done.
Cheers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The #17 kernel has no oops. Network and bridge are brought up after
boot, however there is no network connectivity on the bridge. "sudo
service networking restart" fixes that and after that everything works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I started a Reverse kernel bisect between v4.4 final and v4.5-rc1. The
kernel bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
1289ace5b4f70f1e68ce785735b82c7e483de863
The test kernel can be downloaded from:
** Also affects: bridge-utils (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Yakkety)
Importance: High
Status: Confirmed
** Also affects: bridge-utils (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux
4.4 final shows the same oops.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1616107
Title:
Kernel oops + system freeze on network-bridge shutdown
Status in
It looks like we can perform a reverse bisect between 4.4 final and
4.5-rc1. Can you give 4.4 final a test, just to confirm it exhibits the
bug and it wasn't introduced in on of the stable updates in 4.4? 4.4
final can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/
More test results:
v4.5 mainline build -> No oops, no problems
v4.5-rc1 mainline build -> No oops, no problems
v4.4.21 mainline build -> Same oops
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
Per comment #10, the bug was fixed somewhere between upstream 4.4 and
4.6. To narrow it down further, so we can perform a reverse bisect can
you test the 4.5 final kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
If 4.5 is good, maybe test 4.5-rc1:
and 4.4.20-040420-generic now includes the xenbus bug...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1616107
Title:
Kernel oops + system freeze on network-bridge
4.4.0-38.57 doesn't fix the issue
4.4.20-040420-generic doesn't fix it either
4.7.* are fine but there's a bug with xenbus that renders 4.7.* unusable with
xen (https://patchwork.kernel.org/patch/9281193/)
4.8rcs are ok
--
You received this bug notification because you are a member of Ubuntu
So I tested a couple of them:
v4.4.19 mainline build -> Same oops
v4.6.4 mainline build -> No oops
Remark: Bridge is up after boot but without network connection. "sudo service
networking restart" fixes that.
v4.6.7 mainline build -> No oops
Remark: Bridge is up after boot but without network
Can you also see if this bug happens with the latest upstream stable 4.4
kernel? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.19/
If it does still happen with 4.4.19, we can perform a reverse bisect to
find the fix that is in 4.8-rc3.
--
You received this bug
Some more information:
On Ubuntu 16.04 LTS:
- The above error occurs in all Ubuntu 16.04 LTS versions since the beta and up
to Ubuntu 16.04.1 LTS with kernel 4.4.0-36-generic #55-Ubuntu
- It does NOT occur in Ubuntu 16.04.1 LTS with manually installed kernel
"v4.8-rc3 mainline build"
-
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-fixed-upstream
** Description changed:
A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
This error does not
apport information
** Tags added: apport-collected
** Description changed:
A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
This error does not appear in Ubuntu 14.04 however.
The error is
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Package changed: ubuntu => linux (Ubuntu)
** Also affects: bridge-utils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
33 matches
Mail list logo
