[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
Server Team, which is subscribed to lxc in Ubuntu.
Well, this is a bug that was introduced in 3.8.0-28-generic. As
3.8.0-27-generic does not seems to be affected.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
kernel
** Tags removed: regression-potential
** Tags added: regression-updated
** Tags removed: regression-updated
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
That works too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
kernel panic when restarting containers
To manage notifications about this bug go to:
Not a lxc bug.
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
kernel panic when restarting containers
To
Christer Solskogen, would you need a backport to a release prior to
Saucy, or may we close this as Status Invalid?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
kernel
apport information
** Description changed:
With 3.8.0-28-generic stopping a container (at least if there under a
minute or so it was started) will crash the kernel.
To repeat
Make sure you have that kernel (release kernel works fine) - its in the
raring-proposed.
Create a container
Christer Solskogen, could you please capture the crash following
https://help.ubuntu.com/community/DebuggingSystemCrash ?
** Tags added: needs-crash-log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
from kmsg:
6[ 75.398771] device vethldju4L entered promiscuous mode
6[ 75.398896] IPv6: ADDRCONF(NETDEV_UP): vethldju4L: link is not ready
4[ 75.402908] cgroup: lxc-start (2032) created nested cgroup for controller
memory which has incomplete hierarchy support. Nested cgroups may change
Christer Solskogen, thank you for providing the crash log. Could you please
test the latest upstream kernel available following
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
upstream developers to examine the issue. Please do not test the daily folder,
but the one all
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.13.6-raring/linux-
image-3.8.13-03081306-generic_3.8.13-03081306.201308021435_amd64.deb
worked!
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream-v3.8.13
--
You received this bug notification because you are a member
Christer Solskogen, could you please confirm this issue exists with the
latest development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please run the following command in the development release
from a Terminal
3.8.0-27-generic also works fine.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
kernel panic when restarting containers
To manage notifications about this bug go to:
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1210859
Title:
kernel panic when restarting containers
To
It's a bit hard, since this bug crashed the host system completly. But
can run that command after the machine boots. It will probably have
something in syslog.
** Tags added: apport-collected
** Description changed:
With 3.8.0-28-generic stopping a container (at least if there under a
Christer Solskogen, could you please execute the following in a terminal:
apport-collect -p linux 1210859
** Tags added: needs-upstream-testing regression-potential
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a
16 matches
Mail list logo
