crash on utopic ec2 instance

Bug #1355891 reported by Scott Moser
This bug report is a duplicate of:  Bug #1350522: EC2 kernel crash due to vmalloc. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Launched an instance on ec2.
Instance actually seems moderately fine, but then trying to create a bridge directly or indirectly will fail.
by indirectly, I mean:

$ sudo apt-get update -qy
$ sudo apt-get install lxc --assume-yes --quiet

$ sudo initctl status lxc-net
lxc-net stop/waiting
$ sudo cat /var/log/upstart/lxc-net.log
add bridge failed: Package not installed
Missing bridge support in kernel
lxc-net stop/pre-start, process 4453
add bridge failed: Package not installed
Missing bridge support in kernel
lxc-net stop/pre-start, process 4509

dmesg shows:
[8772678.887956] ------------[ cut here ]------------^M
[8772678.887979] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2a9/0x340()^M
[8772678.887987] Modules linked in:^M
[8772678.887995] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-7-generic #12-Ubuntu^M
[8772678.888002] 0000000000000009 ffff88000316bb88 ffffffff81776c3f 0000000000000000^M
[8772678.888011] ffff88000316bbc0 ffffffff8106fced ffffffffc03a6000 0000000000000000^M
[8772678.888019] ffff880003b95d08 ffff8800032db340 ffffffffc03a1000 ffff88000316bbd0^M
[8772678.888028] Call Trace:^M
[8772678.888038] [<ffffffff81776c3f>] dump_stack+0x45/0x56^M
[8772678.888049] [<ffffffff8106fced>] warn_slowpath_common+0x7d/0xa0^M
[8772678.888063] [<ffffffff8106fdca>] warn_slowpath_null+0x1a/0x20^M
[8772678.888069] [<ffffffff811a5d39>] vmap_page_range_noflush+0x2a9/0x340^M
[8772678.888076] [<ffffffff811a5dfe>] map_vm_area+0x2e/0x40^M
[8772678.888081] [<ffffffff811a74d0>] __vmalloc_node_range+0x200/0x290^M
[8772678.888093] [<ffffffff810f1214>] ? module_alloc_update_bounds+0x14/0x70^M
[8772678.888103] [<ffffffff810f1214>] ? module_alloc_update_bounds+0x14/0x70^M
[8772678.888112] [<ffffffff81052344>] module_alloc+0x74/0xd0^M
[8772678.888118] [<ffffffff810f1214>] ? module_alloc_update_bounds+0x14/0x70^M
[8772678.888125] [<ffffffff810f1214>] module_alloc_update_bounds+0x14/0x70^M
[8772678.888132] [<ffffffff810f1a22>] layout_and_allocate+0x7a2/0xcc0^M
[8772678.888139] [<ffffffff810f2013>] load_module+0xd3/0x1b40^M
[8772678.888150] [<ffffffff811df764>] ? vfs_read+0x124/0x180^M
[8772678.888157] [<ffffffff811e52e8>] ? kernel_read+0x48/0x60^M
[8772678.888163] [<ffffffff810ef8c1>] ? copy_module_from_fd.isra.45+0x111/0x170^M
[8772678.888171] [<ffffffff810f3bf6>] SyS_finit_module+0x86/0xb0^M
[8772678.888183] [<ffffffff8177ecad>] system_call_fastpath+0x1a/0x1f^M
[8772678.888189] ---[ end trace ec3e769b378024cb ]---^M

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-7-generic 3.16.0-7.12
ProcVersionSignature: User Name 3.16.0-7.12-generic 3.16.0
Uname: Linux 3.16.0-7-generic x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.5-0ubuntu4
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDmesg:
 [8772762.247790] systemd-logind[1405]: New seat seat0.
 [8772762.254049] systemd-logind[1405]: Failed to start unit user@1000.service: Unknown unit: user@1000.service
 [8772762.254068] systemd-logind[1405]: Failed to start user service: Unknown unit: user@1000.service
 [8772762.258380] systemd-logind[1405]: New session 1 of user ubuntu.
Date: Tue Aug 12 15:05:48 2014
Ec2AMI: ami-1697457e
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1e
Ec2InstanceType: m1.small
Ec2Kernel: aki-919dcaf8
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0
ProcModules:

RelatedPackageVersions:
 linux-restricted-modules-3.16.0-7-generic N/A
 linux-backports-modules-3.16.0-7-generic N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Scott Moser (smoser) wrote :
Revision history for this message
Scott Moser (smoser) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1355891

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue happen on prior releases, or is it new with the 3.16 kernel?

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-bug-exists-upstream kernel-da-key
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

It doesn't currently happen on trusty images, if that helps. I have no idea when it was introduced.

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Brad Figg (brad-figg) wrote :

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1355891

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: regression-release
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Are you able to install regular amd64 kernels with dpkg on the test environment? If so, we can perform a bisect and identify which commit introduced this?

tags: added: performing-bisect
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.