[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616949
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616949
Title:
guest on bridge becomes inaccessible
Joseph,
I'm sorry, I'd not seen the request for test. This is unfortunately
non-trivial to test.
I agree, the next thing to do is to check and see if the issue is still
present in upstream, the hwe for 16.04 and the current GA for 16.04.
I dont expect that I will haev any time to look at this
Which newer kernel are you referring to? Were you able to test either
of the ones mentioned in comment #3?
The latest 4.4 stable kernel is now at 4.4.30:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.30/
The latest mainline kernel is 4.9-rc4:
Wonder if anything has happened here.
This is still a pain, and basically bridges dont work well with the newer
kernel.
Curtis's re-appearance here is that a node was rebooted, and their stack
failed after it went into the newer kernel.
--
You received this bug notification because you are a
** Tags added: jujuqa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616949
Title:
guest on bridge becomes inaccessible
To manage notifications about this bug go to:
We can perform a kernel bisect to identify the commit that introduced
this bug. Can you first test the latest upstream stable 4.4 kernel to
see if this bug is already fixed? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.19/
It might also be good to test the