kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #185373
[Bug 1595303] Re: Kernel Panic on AWS EC2 with Ubuntu 14.04 and Strongswan
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 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 this bug, please add the tag:
'kernel-bug-exists-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".
Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc4-yakkety/
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: kernel-da-key
--
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/1595303
Title:
Kernel Panic on AWS EC2 with Ubuntu 14.04 and Strongswan
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hello,
we are running a little VPN-Server to share Data with customers. Since we installed the VPN-Tunnels
the server started to panic every 24 hours with following trace.
732.549376] Workqueue: crypto cryptd_queue_worker [cryptd]
[110732.549376] task: ffff8800bf591800 ti: ffff8800bece6000 task.ti: ffff8800bece6000
[110732.549376] RIP: 0010:[<ffffffff8132bb8d>] [<ffffffff8132bb8d>] scatterwalk_map_and_copy+0x4d/0xc0
[110732.549376] RSP: 0018:ffff8800bece7d50 EFLAGS: 00010202
[110732.549376] RAX: ffff8800e68bd467 RBX: 000000000000087a RCX: 0000000000000010
[110732.549376] RDX: 0000000000000050 RSI: ffff8800e68bd7c0 RDI: ffff8800e68bd460
[110732.549376] RBP: ffff8800bece7d70 R08: 0000000000000001 R09: 0000000000000050
[110732.549376] R10: 0000000000000050 R11: 0000000000000000 R12: 0000000000000000
[110732.549376] R13: ffff8800e68bd690 R14: 0000000000000040 R15: ffffe8ffffc203f0
[110732.549376] FS: 0000000000000000(0000) GS:ffff88010fc20000(0000) knlGS:0000000000000000
[110732.549376] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[110732.549376] CR2: 000000000000000c CR3: 0000000001c0e000 CR4: 00000000001406e0
[110732.549376] Stack:
[110732.549376] ffff8800e68bd598 ffff8800e68bd7c0 ffffffff0000087a ffff8800e68bd408
[110732.549376] ffff8800bece7d90 ffffffffa00dd318 ffff8800e68bd530 0000000000000000
[110732.549376] ffff8800bece7da8 ffffffffa00ddc0b ffff8800e68bd690 ffff8800bece7de0
[110732.549376] Call Trace:
[110732.549376] [<ffffffffa00dd318>] crypto_rfc4543_done+0x48/0x60 [gcm]
[110732.549376] [<ffffffffa00ddc0b>] gcm_decrypt_done+0x3b/0x40 [gcm]
[110732.549376] [<ffffffffa002641b>] cryptd_blkcipher_crypt+0x5b/0x70 [cryptd]
[110732.549376] [<ffffffffa002646c>] cryptd_blkcipher_encrypt+0x1c/0x20 [cryptd]
[110732.549376] [<ffffffffa0026b04>] cryptd_queue_worker+0x54/0x80 [cryptd]
[110732.549376] [<ffffffff81086028>] process_one_work+0x178/0x470
[110732.549376] [<ffffffff81086e41>] worker_thread+0x121/0x410
[110732.549376] [<ffffffff81086d20>] ? rescuer_thread+0x430/0x430
[110732.549376] [<ffffffff8108dc29>] kthread+0xc9/0xe0
[110732.549376] [<ffffffff8108db60>] ? kthread_create_on_node+0x1c0/0x1c0
[110732.549376] [<ffffffff8173a328>] ret_from_fork+0x58/0x90
[110732.549376] [<ffffffff8108db60>] ? kthread_create_on_node+0x1c0/0x1c0
[110732.549376] Code: 4e 2c 45 85 c9 74 37 48 83 c6 20 45 89 d3 45 85 c9 48 89 75 e8 74 73 8b 5e 08 47 8d 14 19 44 39 d2 89 5d f0 72 30 f6 06 02 74 d3 <44> 8b 0c 25 0c 00 00 00 31 f6 eb d4 0f 1f 80 00 00 00 00 48 8b
[110732.549376] RIP [<ffffffff8132bb8d>] scatterwalk_map_and_copy+0x4d/0xc0
[110732.549376] RSP <ffff8800bece7d50>
[110732.549376] CR2: 000000000000000c
[110732.549376] ---[ end trace 56d0731046cb2c7e ]---
[110732.549376] Kernel panic - not syncing: Fatal exception in interrupt
Kind Regards
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Jun 22 20:37 seq
crw-rw---- 1 root audio 116, 33 Jun 22 20:37 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Ec2AMI: ami-87564feb
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-central-1b
Ec2InstanceType: t2.medium
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: Xen HVM domU
Package: linux (not installed)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic root=UUID=e916c124-cf92-4adb-940f-cef6d3f03b71 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
RelatedPackageVersions:
linux-restricted-modules-3.13.0-87-generic N/A
linux-backports-modules-3.13.0-87-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty ec2-images
Uname: Linux 3.13.0-87-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 05/12/2016
dmi.bios.vendor: Xen
dmi.bios.version: 4.2.amazon
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.2.amazon
dmi.sys.vendor: Xen
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Jun 22 20:37 seq
crw-rw---- 1 root audio 116, 33 Jun 22 20:37 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Ec2AMI: ami-87564feb
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-central-1b
Ec2InstanceType: t2.medium
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: Xen HVM domU
Package: linux (not installed)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic root=UUID=e916c124-cf92-4adb-940f-cef6d3f03b71 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
RelatedPackageVersions:
linux-restricted-modules-3.13.0-87-generic N/A
linux-backports-modules-3.13.0-87-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty ec2-images
Uname: Linux 3.13.0-87-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 05/12/2016
dmi.bios.vendor: Xen
dmi.bios.version: 4.2.amazon
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.2.amazon
dmi.sys.vendor: Xen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1595303/+subscriptions
References