BUG: unable to handle kernel paging request at e000dfc0 on i386 saucy server installations

[Para Siva]

The following error occurs in almost all the saucy server installations with 512MB RAM on a kvm/libvirt VMs starting from 3.11.0-3-generic onwards. occurs with 20130821 onwards. They don't appear to impact the tests that are run afterwords though.

Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.962782] BUG: unable to handle kernel paging request at e000cf40
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.962911] IP: [<c104c07b>] kmap_atomic_prot+0x1b/0x100
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.963056] *pdpt = 0000000001a56001 *pde = 0000000000000000
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.963176] Oops: 0000 [#1] SMP
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.963256] Modules linked in: cirrus ttm microcode(F) drm_kms_helper drm psmouse(F) serio_raw(F) virtio_balloon(F) syscopyarea(F) sysfillrect(F) sysimgblt(F) i2c_piix4 mac_hid lp(F) parport(F) floppy(F)
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.963719] CPU: 0 PID: 671 Comm: apparmor_parser Tainted: GF 3.11.0-4-generic #9-Ubuntu
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.963842] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.963932] task: dd714060 ti: dd80c000 task.ti: dd80c000
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] EIP: 0060:[<c104c07b>] EFLAGS: 00010202 CPU: 0
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] EIP is at kmap_atomic_prot+0x1b/0x100
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] EAX: dd80c000 EBX: dd80de28 ECX: 80000000 EDX: 00000163
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] ESI: e000cf40 EDI: 00000010 EBP: dd80dde8 ESP: dd80ddd8
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] CR0: 80050033 CR2: e000cf40 CR3: 1d7bc000 CR4: 000006b0
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] Stack:
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] dd738000 dd80de28 00000ff0 00000010 dd80ddf0 c104c179 dd80de08 c12be7f0
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] 00000000 00000000 db64d180 dfbfc000 dd80de10 c12be862 dd80de1c c12beff3
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] db672d80 dd80de4c c12bf6ee 000087c1 dd80d000 00000010 00000000 e000cf40
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] Call Trace:
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c104c179>] kmap_atomic+0x19/0x20
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c12be7f0>] hash_walk_next+0x30/0x60
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c12be862>] hash_walk_new_entry+0x42/0x50
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c12beff3>] crypto_hash_walk_first_compat+0x33/0x40
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c12bf6ee>] shash_compat_update+0x1e/0x50
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c12b661e>] aa_calc_profile_hash+0x11e/0x160
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c12ae90e>] aa_unpack+0x35e/0xb90
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c12a8100>] ? profile_remove+0x50/0x50
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c12ad4c3>] aa_replace_profiles+0x33/0x9d0
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c1146c88>] ? vmalloc+0x38/0x40
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c12fb92c>] ? _copy_from_user+0x2c/0x40
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c12a8100>] ? profile_remove+0x50/0x50
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c12a8135>] profile_replace+0x35/0x50
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c11694ad>] vfs_write+0x9d/0x1b0
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c1169b59>] SyS_write+0x49/0x90
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] [<c163d00d>] sysenter_do_call+0x12/0x28
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] Code: 0b eb 0d 90 90 90 90 90 90 90 90 90 90 90 90 90 55 89 e5 57 56 53 83 ec 04 3e 8d 74 26 00 89 c6 89 e0 25 00 e0 ff ff 83 40 14 01 <8b> 06 c1 e8 1e 69 c0 40 03 00 00 05 40 92 95 c1 2b 80 0c 03 00
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] EIP: [<c104c07b>] kmap_atomic_prot+0x1b/0x100 SS:ESP 0068:dd80ddd8
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] CR2: 00000000e000cf40
Aug 29 07:52:10 utah-13683-saucy-server-i386 kernel: [ 5.964022] ---[ end trace f6fbef05fc478567 ]---

Steps to reproduce:
1. Install a saucy server VM on qemu-kvm with 512 MB RAM
2. Reboot

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-4-generic 3.11.0-4.9
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-4-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.12.1-0ubuntu2
Architecture: i386
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CurrentDmesg:

Date: Thu Aug 29 17:11:28 2013
HibernationDevice: RESUME=UUID=b7fe413c-9a44-4711-abd8-1a5668f63fbc
InstallationDate: Installed on 2013-08-29 (0 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Alpha i386 (20130829)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Bochs Bochs
MarkForUpload: True
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=10dc23f7-0649-4ca9-a7ee-7b77bfaddead ro
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-4-generic N/A
 linux-backports-modules-3.11.0-4-generic N/A
 linux-firmware 1.113
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

I'd like to perform a bisect to identify the commit that introduced this regression. Can you test the following two kernels and post back if rc5 is good and rc6 has the bug:

v3.11-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc5-saucy/
v3.11-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc6-saucy/

[Tyler Hicks (tyhicks)]

Thanks for the bug report! This is a duplicate of bug #1216294.

There's no need to test mainline, as Joseph asked you to do. This is caused by an AppArmor patch that is specific to Ubuntu and not yet upstream.

The tip on 512MB RAM server VMs will be helpful. I'm setting up such a VM right now. Thanks again!