I’m unsure this is the right way but adding linux package as this was
also caused by kernel upgrade.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Not seeing crashes at 4.4.76-040476-generic for these few days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1702665
Title:
4.4.0-83-generic + Docker + EC2 frequently crashes at
Sure. Upgraded one of an instance running 4.4.76-040476-generic, aside
of existing 4.12 instance.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1702665
Title:
4.4.0-83-generic + Docker
Clarify: Upgraded one of an instance running 4.4.0-83 to
4.4.76-040476-generic, *
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1702665
Title:
4.4.0-83-generic + Docker + EC2
4.12 instance is still running without crash, survived this weekend.
Added kernel-fixed-upstream tag.
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Additional logs from 4.4.0 machine by running `dmesg -w` until crash.
[ 3031.276097] [ cut here ]
[ 3031.276106] WARNING: CPU: 0 PID: 31804 at
/build/linux-0uniEn/linux-4.4.0/net/ipv6/addrconf_core.c:159
in6_dev_finish_destroy+0x6b/0xc0()
[ 3031.276108] Modules linked
Noticed that these log appears before panic occurs for both kind of
panics (GPF and "unable to handle kernel paging request").
[ 210.064089] unregister_netdevice: waiting for lo to become free. Usage count
= 1
[ 1260.052073] unregister_netdevice: waiting for lo to become free. Usage count
= 1
We've switched most of instances in the cluster to c4.large instance
type, but another panic occur. Panic happened at different trace, so
this may not relate to the first GPF, but pasting log below for
information.
Also, t2.small 4.12.x instance is now running 16 hours+, we have not
seen panics
Created new instance and bumped to the 4.12 latest.
$ uname -a
Linux ${HOSTNAME} 4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
We run xenial-based Docker container hosts on EC2 with Amazon ECS.
Recently we refreshed our base image, we started to see frequent panic.
Hosts run Amazon ECS Agent, and the agent automatically creates or
destroys Docker container based on requests onto ECS cluster.
I
10 matches
Mail list logo
