"Bug: unable to handle kernel paging request"

William G

New Member
Apr 17, 2016
5
0
1
40
I've been noticing that a new box which uses a LSI MegaRaid controller has been falling over every several hours.

The console is showing this 'oops', and on the system console it shows as "Bug: unable to handle kernel paging request"


Code:
Apr 17 08:31:53 vm6 kernel: [   20.479725] PGD 83a02a067 PUD 839ff1067 PMD 83a020067 PTE 8000000847a0a867
Apr 17 08:31:53 vm6 kernel: [   20.479752] Oops: 0001 [#1] SMP
Apr 17 08:31:53 vm6 kernel: [   20.479766] Modules linked in: xt_nat xt_tcpudp softdog iptable_filter nfsd auth_rpcgss nfs_acl nfs lockd grace fscache sunrpc ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables nfnetlink_log nfnetlink intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ast ttm ipmi_ssif crct10dif_pclmul crc32_pclmul drm_kms_helper aesni_intel aes_x86_64 drm lrw gf128mul i2c_algo_bit glue_helper snd_pcm ablk_helper cryptd syscopyarea snd_timer snd sysfillrect mxm_wmi sysimgblt soundcore joydev input_leds ipmi_si 8250_fintek mei_me sb_edac mei edac_core pcspkr ioatdma acpi_pad lpc_ich ipmi_msghandler i2c_i801 shpchp wmi mac_hid vhost_net vhost macvtap macvlan autofs4 zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) hid_generic usbkbd usbmouse usbhid hid ahci ixgbe(O) libahci dca vxlan ip6_udp_tunnel udp_tunnel ptp megaraid_sas pps_core
Apr 17 08:31:53 vm6 kernel: [   20.480189] CPU: 1 PID: 2468 Comm: megasasctl Tainted: P           O    4.2.6-1-pve #1
Apr 17 08:31:53 vm6 kernel: [   20.480213] Hardware name: Supermicro Super Server/X10SDV-4C-TLN2F, BIOS 1.0b 09/09/2015
Apr 17 08:31:53 vm6 kernel: [   20.480236] task: ffff880850548dc0 ti: ffff88083a038000 task.ti: ffff88083a038000
Apr 17 08:31:53 vm6 kernel: [   20.480258] RIP: 0010:[<ffffffffc001dd00>]  [<ffffffffc001dd00>] megasas_mgmt_compat_ioctl+0x100/0x210 [megaraid_sas]
Apr 17 08:31:53 vm6 kernel: [   20.480290] RSP: 0018:ffff88083a03be18  EFLAGS: 00010246
Apr 17 08:31:53 vm6 kernel: [   20.480306] RAX: 0000000000000000 RBX: 00000000ffe8510c RCX: 0000000000000000
Apr 17 08:31:53 vm6 kernel: [   20.480327] RDX: 0000000000000004 RSI: 00000000ffe85118 RDI: 00000000ffe84f3c
Apr 17 08:31:53 vm6 kernel: [   20.480347] RBP: ffff88083a03be58 R08: 00007ffffffff000 R09: 00000000000000c4
Apr 17 08:31:53 vm6 kernel: [   20.480368] R10: 00000000f7702b70 R11: 0000000000000246 R12: 00000000ffe8510c
Apr 17 08:31:53 vm6 kernel: [   20.480388] R13: 00000000ffe84f30 R14: 00000000ffe8510c R15: ffff8808432fc600
Apr 17 08:31:53 vm6 kernel: [   20.480409] FS:  0000000000000000(0000) GS:ffff88087fc40000(0063) knlGS:00000000f7545700
Apr 17 08:31:53 vm6 kernel: [   20.480432] CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
Apr 17 08:31:53 vm6 kernel: [   20.480449] CR2: 00000000ffe84f40 CR3: 000000083b1d2000 CR4: 00000000003406e0
Apr 17 08:31:53 vm6 kernel: [   20.480469] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 17 08:31:53 vm6 kernel: [   20.480489] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Apr 17 08:31:53 vm6 kernel: [   20.480509] Stack:
Apr 17 08:31:53 vm6 kernel: [   20.480516]  ffff880859f7e01c ffff880000000260 ffff880000000204 00000000ffe8510c
Apr 17 08:31:53 vm6 kernel: [   20.480543]  00000000c1144d01 ffff8808432fc600 00000000ffe8510c ffff8808432fc600
Apr 17 08:31:53 vm6 kernel: [   20.480569]  ffff88083a03bf48 ffffffff8125395b 000000000804a000 000000006a382ec0
Apr 17 08:31:53 vm6 kernel: [   20.480595] Call Trace:
Apr 17 08:31:53 vm6 kernel: [   20.480607]  [<ffffffff8125395b>] compat_SyS_ioctl+0xeb/0x1220
Apr 17 08:31:53 vm6 kernel: [   20.480628]  [<ffffffff810675fa>] ? __do_page_fault+0x1ba/0x410
Apr 17 08:31:53 vm6 kernel: [   20.480648]  [<ffffffff8180a762>] sysenter_dispatch+0xf/0x29
Apr 17 08:31:53 vm6 kernel: [   20.480665] Code: 00 e8 55 8e 3b c1 48 85 c0 0f 85 f0 00 00 00 49 8d 74 24 08 49 8d 7d 08 ba 04 00 00 00 e8 39 8e 3b c1 48 85 c0 0f 85 d4 00 00 00 <41> 8b 45 10 85 c0 74 2f 41 8b 45 0c 49 8d 4c 05 14 41 8b 44 24
Apr 17 08:31:53 vm6 kernel: [   20.480825]  RSP <ffff88083a03be18>
Apr 17 08:31:53 vm6 kernel: [   20.480836] CR2: 00000000ffe84f40
Apr 17 08:31:53 vm6 kernel: [   20.481657] ---[ end trace 56f1f58ab4f6d064 ]---

PVE info:
Code:
root@vm6:~# pveversion -v
proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-22 (running version: 4.1-22/aca130cf)
pve-kernel-4.2.6-1-pve: 4.2.6-36
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-29
qemu-server: 4.0-64
pve-firmware: 1.1-7
libpve-common-perl: 4.0-54
libpve-access-control: 4.0-13
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-9
pve-container: 1.0-52
pve-firewall: 2.0-22
pve-ha-manager: 1.0-25
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie
 

Attachments

  • Screenshot 2016-04-17 08.47.32.png
    Screenshot 2016-04-17 08.47.32.png
    578.9 KB · Views: 3

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!