Production server with Debian Jessie (system hangs after an invalid opcode)

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I use Debian Jessie on a Xen Server 6.2 since many years without problem. I update Jessie regularly.. since some days, there is a fatal bug.



Aug 31 13:49:46 git kernel: [139139.936636] ------------[ cut here ]------------
Aug 31 13:49:46 git kernel: [139139.936794] kernel BUG at /build/linux-luZh6p/linux-3.16.57/fs/dcache.c:2826!
Aug 31 13:49:46 git kernel: [139139.936949] invalid opcode: 0000 [#1] SMP
Aug 31 13:49:46 git kernel: [139139.937094] Modules linked in: ipt_REJECT xt_multiport iptable_filter ip_tables x_tables xenfs xen_privcmd rpcsec_gss_krb5 nfsd nfs_acl auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd sunrpc fscache intel_rapl ppdev crc32_pclmul joydev evdev serio_raw parport_pc parport aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper ttm drm_kms_helper cryptd drm processor thermal_sys pcspkr button autofs4 hid_generic usbhid hid ext4 crc16 mbcache jbd2 dm_mod sg sr_mod cdrom ata_generic uhci_hcd ehci_hcd crct10dif_pclmul crct10dif_common xen_netfront ata_piix xen_blkfront psmouse crc32c_intel i2c_piix4 i2c_core usbcore libata scsi_mod usb_common floppy
Aug 31 13:49:46 git kernel: [139139.939624] CPU: 3 PID: 2671 Comm: git-upload-pack Not tainted 3.16.0-6-amd64 #1 Debian 3.16.57-2
Aug 31 13:49:46 git kernel: [139139.939974] Hardware name: Xen HVM domU, BIOS 4.1.5 11/28/2013
Aug 31 13:49:46 git kernel: [139139.940414] task: ffff88006b90a010 ti: ffff880004744000 task.ti: ffff880004744000
Aug 31 13:49:46 git kernel: [139139.940529] RIP: 0010:[<ffffffff811d0b50>] [<ffffffff811d0b50>] d_materialise_unique+0x1f0/0x3d0
Aug 31 13:49:46 git kernel: [139139.940529] RSP: 0018:ffff880004747bc0 EFLAGS: 00010286
Aug 31 13:49:46 git kernel: [139139.940529] RAX: ffff880020bdbd98 RBX: ffff8800c62e9718 RCX: 0000000000050005
Aug 31 13:49:46 git kernel: [139139.940529] RDX: 0000000100050005 RSI: ffff8800c62e9718 RDI: ffff880020bdbdf0
Aug 31 13:49:46 git kernel: [139139.940529] RBP: ffff880020bdbd98 R08: 0000000000000004 R09: ffff880020bdbdd8
Aug 31 13:49:46 git kernel: [139139.940529] R10: 0000000000000000 R11: 000000000000000c R12: ffff880056102018
Aug 31 13:49:46 git kernel: [139139.940529] R13: 000000000000003c R14: ffff880056102018 R15: ffff8801013fc3d8
Aug 31 13:49:46 git kernel: [139139.940529] FS: 00007fe25ca6c700(0000) GS:ffff88010f860000(0000) knlGS:0000000000000000
Aug 31 13:49:46 git kernel: [139139.940529] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 31 13:49:46 git kernel: [139139.940529] CR2: 000000000105d028 CR3: 0000000004880000 CR4: 0000000000100670
Aug 31 13:49:46 git kernel: [139139.940529] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 31 13:49:46 git kernel: [139139.940529] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Aug 31 13:49:46 git kernel: [139139.940529] Stack:
Aug 31 13:49:46 git kernel: [139139.940529] ffff8800d19a3700 ffff880004747d58 ffff880004747ce8 ffff880004747e58
Aug 31 13:49:46 git kernel: [139139.940529] 000000000000003c ffff880056102018 ffff8801013fc3d8 ffffffffa0464c3d
Aug 31 13:49:46 git kernel: [139139.940529] ffff8800560488e0 ffffea000387a870 ffff88000000000b ffff880056048aa0
Aug 31 13:49:46 git kernel: [139139.940529] Call Trace:
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa0464c3d>] ? nfs_readdir_page_filler+0x3cd/0x440 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04654e8>] ? nfs_readdir_xdr_to_array+0x1e8/0x2f0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04655f0>] ? nfs_readdir_xdr_to_array+0x2f0/0x2f0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa046560d>] ? nfs_readdir_filler+0x1d/0x80 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811490d0>] ? do_read_cache_page+0x80/0x1b0
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04657bc>] ? nfs_readdir+0x14c/0x5d0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04abfd0>] ? nfs4_xdr_dec_layoutget+0x240/0x240 [nfsv4]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cbbb5>] ? iterate_dir+0xa5/0x120
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cc009>] ? SyS_getdents+0x89/0x100
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cbd00>] ? fillonedir+0xd0/0xd0
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff8153ad9c>] ? system_call_fast_compare_end+0x1c/0x21
Aug 31 13:49:46 git kernel: [139139.940529] Code: 00 f0 ff ff 0f 86 bb fe ff ff 48 83 fd d8 0f 84 9f 01 00 00 4c 89 ef e8 ef e5 ff ff e9 a4 fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 <0f> 0b 66 0f 1f 44 00 00 4c 89 e5 e9 68 fe ff ff 31 c0 45 31 ff
Aug 31 13:49:46 git kernel: [139139.940529] RIP [<ffffffff811d0b50>] d_materialise_unique+0x1f0/0x3d0
Aug 31 13:49:46 git kernel: [139139.940529] RSP <ffff880004747bc0>
Aug 31 13:49:46 git kernel: [139139.956969] ---[ end trace b016cdf86f96eb18 ]---

gitlab@git:~$ uname -a
Linux git 3.16.0-6-amd64 #1 SMP Debian 3.16.57-2 (2018-07-14) x86_64 GNU/Linux


What does invalid opcode: 0000 mean?



Xen is old but it was always working perfectly.. I can't upgrade easily.. it's used in production.



Linux xen-epsitecserver 2.6.32.43-0.4.1.xs1.8.0.855.170800xen #1 SMP Mon Jul 21 05:12:35 EDT 2014 i686 i686 i386 GNU/Linux


Thank you










share|improve this question























  • Have you tried disabling power saving options in the BIOS? See here: askubuntu.com/questions/50833/invalid-opcode-0000
    – Panki
    Aug 31 at 14:00










  • You have problems with your ram memory, sorry. You need to run memtest and replace it. That will corrupt your data soon.
    – Luciano Andress Martini
    Aug 31 at 14:33










  • I've this problem only with one VM on this Xen server. All other VMs are running fine. It's a Proliant server with ECC memory. According to the iLO firmware, everything is working fine. I can tune the VM with Debian Jessie. Do you know if it's possible to run a memtest without rebooting the whole Xen server?
    – Skywalker13
    Sep 1 at 21:30











  • Looks like lists.debian.org/debian-kernel/2016/12/msg00325.html
    – SamLeBarbare
    Sep 4 at 0:31










  • Thanks @SamLeBarbare; yes it looks like this bug. But I've upgraded to Debian Stretch and now, everything is working fine.
    – Skywalker13
    Sep 17 at 10:13














up vote
0
down vote

favorite












I use Debian Jessie on a Xen Server 6.2 since many years without problem. I update Jessie regularly.. since some days, there is a fatal bug.



Aug 31 13:49:46 git kernel: [139139.936636] ------------[ cut here ]------------
Aug 31 13:49:46 git kernel: [139139.936794] kernel BUG at /build/linux-luZh6p/linux-3.16.57/fs/dcache.c:2826!
Aug 31 13:49:46 git kernel: [139139.936949] invalid opcode: 0000 [#1] SMP
Aug 31 13:49:46 git kernel: [139139.937094] Modules linked in: ipt_REJECT xt_multiport iptable_filter ip_tables x_tables xenfs xen_privcmd rpcsec_gss_krb5 nfsd nfs_acl auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd sunrpc fscache intel_rapl ppdev crc32_pclmul joydev evdev serio_raw parport_pc parport aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper ttm drm_kms_helper cryptd drm processor thermal_sys pcspkr button autofs4 hid_generic usbhid hid ext4 crc16 mbcache jbd2 dm_mod sg sr_mod cdrom ata_generic uhci_hcd ehci_hcd crct10dif_pclmul crct10dif_common xen_netfront ata_piix xen_blkfront psmouse crc32c_intel i2c_piix4 i2c_core usbcore libata scsi_mod usb_common floppy
Aug 31 13:49:46 git kernel: [139139.939624] CPU: 3 PID: 2671 Comm: git-upload-pack Not tainted 3.16.0-6-amd64 #1 Debian 3.16.57-2
Aug 31 13:49:46 git kernel: [139139.939974] Hardware name: Xen HVM domU, BIOS 4.1.5 11/28/2013
Aug 31 13:49:46 git kernel: [139139.940414] task: ffff88006b90a010 ti: ffff880004744000 task.ti: ffff880004744000
Aug 31 13:49:46 git kernel: [139139.940529] RIP: 0010:[<ffffffff811d0b50>] [<ffffffff811d0b50>] d_materialise_unique+0x1f0/0x3d0
Aug 31 13:49:46 git kernel: [139139.940529] RSP: 0018:ffff880004747bc0 EFLAGS: 00010286
Aug 31 13:49:46 git kernel: [139139.940529] RAX: ffff880020bdbd98 RBX: ffff8800c62e9718 RCX: 0000000000050005
Aug 31 13:49:46 git kernel: [139139.940529] RDX: 0000000100050005 RSI: ffff8800c62e9718 RDI: ffff880020bdbdf0
Aug 31 13:49:46 git kernel: [139139.940529] RBP: ffff880020bdbd98 R08: 0000000000000004 R09: ffff880020bdbdd8
Aug 31 13:49:46 git kernel: [139139.940529] R10: 0000000000000000 R11: 000000000000000c R12: ffff880056102018
Aug 31 13:49:46 git kernel: [139139.940529] R13: 000000000000003c R14: ffff880056102018 R15: ffff8801013fc3d8
Aug 31 13:49:46 git kernel: [139139.940529] FS: 00007fe25ca6c700(0000) GS:ffff88010f860000(0000) knlGS:0000000000000000
Aug 31 13:49:46 git kernel: [139139.940529] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 31 13:49:46 git kernel: [139139.940529] CR2: 000000000105d028 CR3: 0000000004880000 CR4: 0000000000100670
Aug 31 13:49:46 git kernel: [139139.940529] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 31 13:49:46 git kernel: [139139.940529] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Aug 31 13:49:46 git kernel: [139139.940529] Stack:
Aug 31 13:49:46 git kernel: [139139.940529] ffff8800d19a3700 ffff880004747d58 ffff880004747ce8 ffff880004747e58
Aug 31 13:49:46 git kernel: [139139.940529] 000000000000003c ffff880056102018 ffff8801013fc3d8 ffffffffa0464c3d
Aug 31 13:49:46 git kernel: [139139.940529] ffff8800560488e0 ffffea000387a870 ffff88000000000b ffff880056048aa0
Aug 31 13:49:46 git kernel: [139139.940529] Call Trace:
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa0464c3d>] ? nfs_readdir_page_filler+0x3cd/0x440 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04654e8>] ? nfs_readdir_xdr_to_array+0x1e8/0x2f0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04655f0>] ? nfs_readdir_xdr_to_array+0x2f0/0x2f0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa046560d>] ? nfs_readdir_filler+0x1d/0x80 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811490d0>] ? do_read_cache_page+0x80/0x1b0
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04657bc>] ? nfs_readdir+0x14c/0x5d0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04abfd0>] ? nfs4_xdr_dec_layoutget+0x240/0x240 [nfsv4]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cbbb5>] ? iterate_dir+0xa5/0x120
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cc009>] ? SyS_getdents+0x89/0x100
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cbd00>] ? fillonedir+0xd0/0xd0
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff8153ad9c>] ? system_call_fast_compare_end+0x1c/0x21
Aug 31 13:49:46 git kernel: [139139.940529] Code: 00 f0 ff ff 0f 86 bb fe ff ff 48 83 fd d8 0f 84 9f 01 00 00 4c 89 ef e8 ef e5 ff ff e9 a4 fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 <0f> 0b 66 0f 1f 44 00 00 4c 89 e5 e9 68 fe ff ff 31 c0 45 31 ff
Aug 31 13:49:46 git kernel: [139139.940529] RIP [<ffffffff811d0b50>] d_materialise_unique+0x1f0/0x3d0
Aug 31 13:49:46 git kernel: [139139.940529] RSP <ffff880004747bc0>
Aug 31 13:49:46 git kernel: [139139.956969] ---[ end trace b016cdf86f96eb18 ]---

gitlab@git:~$ uname -a
Linux git 3.16.0-6-amd64 #1 SMP Debian 3.16.57-2 (2018-07-14) x86_64 GNU/Linux


What does invalid opcode: 0000 mean?



Xen is old but it was always working perfectly.. I can't upgrade easily.. it's used in production.



Linux xen-epsitecserver 2.6.32.43-0.4.1.xs1.8.0.855.170800xen #1 SMP Mon Jul 21 05:12:35 EDT 2014 i686 i686 i386 GNU/Linux


Thank you










share|improve this question























  • Have you tried disabling power saving options in the BIOS? See here: askubuntu.com/questions/50833/invalid-opcode-0000
    – Panki
    Aug 31 at 14:00










  • You have problems with your ram memory, sorry. You need to run memtest and replace it. That will corrupt your data soon.
    – Luciano Andress Martini
    Aug 31 at 14:33










  • I've this problem only with one VM on this Xen server. All other VMs are running fine. It's a Proliant server with ECC memory. According to the iLO firmware, everything is working fine. I can tune the VM with Debian Jessie. Do you know if it's possible to run a memtest without rebooting the whole Xen server?
    – Skywalker13
    Sep 1 at 21:30











  • Looks like lists.debian.org/debian-kernel/2016/12/msg00325.html
    – SamLeBarbare
    Sep 4 at 0:31










  • Thanks @SamLeBarbare; yes it looks like this bug. But I've upgraded to Debian Stretch and now, everything is working fine.
    – Skywalker13
    Sep 17 at 10:13












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I use Debian Jessie on a Xen Server 6.2 since many years without problem. I update Jessie regularly.. since some days, there is a fatal bug.



Aug 31 13:49:46 git kernel: [139139.936636] ------------[ cut here ]------------
Aug 31 13:49:46 git kernel: [139139.936794] kernel BUG at /build/linux-luZh6p/linux-3.16.57/fs/dcache.c:2826!
Aug 31 13:49:46 git kernel: [139139.936949] invalid opcode: 0000 [#1] SMP
Aug 31 13:49:46 git kernel: [139139.937094] Modules linked in: ipt_REJECT xt_multiport iptable_filter ip_tables x_tables xenfs xen_privcmd rpcsec_gss_krb5 nfsd nfs_acl auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd sunrpc fscache intel_rapl ppdev crc32_pclmul joydev evdev serio_raw parport_pc parport aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper ttm drm_kms_helper cryptd drm processor thermal_sys pcspkr button autofs4 hid_generic usbhid hid ext4 crc16 mbcache jbd2 dm_mod sg sr_mod cdrom ata_generic uhci_hcd ehci_hcd crct10dif_pclmul crct10dif_common xen_netfront ata_piix xen_blkfront psmouse crc32c_intel i2c_piix4 i2c_core usbcore libata scsi_mod usb_common floppy
Aug 31 13:49:46 git kernel: [139139.939624] CPU: 3 PID: 2671 Comm: git-upload-pack Not tainted 3.16.0-6-amd64 #1 Debian 3.16.57-2
Aug 31 13:49:46 git kernel: [139139.939974] Hardware name: Xen HVM domU, BIOS 4.1.5 11/28/2013
Aug 31 13:49:46 git kernel: [139139.940414] task: ffff88006b90a010 ti: ffff880004744000 task.ti: ffff880004744000
Aug 31 13:49:46 git kernel: [139139.940529] RIP: 0010:[<ffffffff811d0b50>] [<ffffffff811d0b50>] d_materialise_unique+0x1f0/0x3d0
Aug 31 13:49:46 git kernel: [139139.940529] RSP: 0018:ffff880004747bc0 EFLAGS: 00010286
Aug 31 13:49:46 git kernel: [139139.940529] RAX: ffff880020bdbd98 RBX: ffff8800c62e9718 RCX: 0000000000050005
Aug 31 13:49:46 git kernel: [139139.940529] RDX: 0000000100050005 RSI: ffff8800c62e9718 RDI: ffff880020bdbdf0
Aug 31 13:49:46 git kernel: [139139.940529] RBP: ffff880020bdbd98 R08: 0000000000000004 R09: ffff880020bdbdd8
Aug 31 13:49:46 git kernel: [139139.940529] R10: 0000000000000000 R11: 000000000000000c R12: ffff880056102018
Aug 31 13:49:46 git kernel: [139139.940529] R13: 000000000000003c R14: ffff880056102018 R15: ffff8801013fc3d8
Aug 31 13:49:46 git kernel: [139139.940529] FS: 00007fe25ca6c700(0000) GS:ffff88010f860000(0000) knlGS:0000000000000000
Aug 31 13:49:46 git kernel: [139139.940529] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 31 13:49:46 git kernel: [139139.940529] CR2: 000000000105d028 CR3: 0000000004880000 CR4: 0000000000100670
Aug 31 13:49:46 git kernel: [139139.940529] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 31 13:49:46 git kernel: [139139.940529] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Aug 31 13:49:46 git kernel: [139139.940529] Stack:
Aug 31 13:49:46 git kernel: [139139.940529] ffff8800d19a3700 ffff880004747d58 ffff880004747ce8 ffff880004747e58
Aug 31 13:49:46 git kernel: [139139.940529] 000000000000003c ffff880056102018 ffff8801013fc3d8 ffffffffa0464c3d
Aug 31 13:49:46 git kernel: [139139.940529] ffff8800560488e0 ffffea000387a870 ffff88000000000b ffff880056048aa0
Aug 31 13:49:46 git kernel: [139139.940529] Call Trace:
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa0464c3d>] ? nfs_readdir_page_filler+0x3cd/0x440 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04654e8>] ? nfs_readdir_xdr_to_array+0x1e8/0x2f0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04655f0>] ? nfs_readdir_xdr_to_array+0x2f0/0x2f0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa046560d>] ? nfs_readdir_filler+0x1d/0x80 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811490d0>] ? do_read_cache_page+0x80/0x1b0
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04657bc>] ? nfs_readdir+0x14c/0x5d0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04abfd0>] ? nfs4_xdr_dec_layoutget+0x240/0x240 [nfsv4]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cbbb5>] ? iterate_dir+0xa5/0x120
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cc009>] ? SyS_getdents+0x89/0x100
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cbd00>] ? fillonedir+0xd0/0xd0
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff8153ad9c>] ? system_call_fast_compare_end+0x1c/0x21
Aug 31 13:49:46 git kernel: [139139.940529] Code: 00 f0 ff ff 0f 86 bb fe ff ff 48 83 fd d8 0f 84 9f 01 00 00 4c 89 ef e8 ef e5 ff ff e9 a4 fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 <0f> 0b 66 0f 1f 44 00 00 4c 89 e5 e9 68 fe ff ff 31 c0 45 31 ff
Aug 31 13:49:46 git kernel: [139139.940529] RIP [<ffffffff811d0b50>] d_materialise_unique+0x1f0/0x3d0
Aug 31 13:49:46 git kernel: [139139.940529] RSP <ffff880004747bc0>
Aug 31 13:49:46 git kernel: [139139.956969] ---[ end trace b016cdf86f96eb18 ]---

gitlab@git:~$ uname -a
Linux git 3.16.0-6-amd64 #1 SMP Debian 3.16.57-2 (2018-07-14) x86_64 GNU/Linux


What does invalid opcode: 0000 mean?



Xen is old but it was always working perfectly.. I can't upgrade easily.. it's used in production.



Linux xen-epsitecserver 2.6.32.43-0.4.1.xs1.8.0.855.170800xen #1 SMP Mon Jul 21 05:12:35 EDT 2014 i686 i686 i386 GNU/Linux


Thank you










share|improve this question















I use Debian Jessie on a Xen Server 6.2 since many years without problem. I update Jessie regularly.. since some days, there is a fatal bug.



Aug 31 13:49:46 git kernel: [139139.936636] ------------[ cut here ]------------
Aug 31 13:49:46 git kernel: [139139.936794] kernel BUG at /build/linux-luZh6p/linux-3.16.57/fs/dcache.c:2826!
Aug 31 13:49:46 git kernel: [139139.936949] invalid opcode: 0000 [#1] SMP
Aug 31 13:49:46 git kernel: [139139.937094] Modules linked in: ipt_REJECT xt_multiport iptable_filter ip_tables x_tables xenfs xen_privcmd rpcsec_gss_krb5 nfsd nfs_acl auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd sunrpc fscache intel_rapl ppdev crc32_pclmul joydev evdev serio_raw parport_pc parport aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper ttm drm_kms_helper cryptd drm processor thermal_sys pcspkr button autofs4 hid_generic usbhid hid ext4 crc16 mbcache jbd2 dm_mod sg sr_mod cdrom ata_generic uhci_hcd ehci_hcd crct10dif_pclmul crct10dif_common xen_netfront ata_piix xen_blkfront psmouse crc32c_intel i2c_piix4 i2c_core usbcore libata scsi_mod usb_common floppy
Aug 31 13:49:46 git kernel: [139139.939624] CPU: 3 PID: 2671 Comm: git-upload-pack Not tainted 3.16.0-6-amd64 #1 Debian 3.16.57-2
Aug 31 13:49:46 git kernel: [139139.939974] Hardware name: Xen HVM domU, BIOS 4.1.5 11/28/2013
Aug 31 13:49:46 git kernel: [139139.940414] task: ffff88006b90a010 ti: ffff880004744000 task.ti: ffff880004744000
Aug 31 13:49:46 git kernel: [139139.940529] RIP: 0010:[<ffffffff811d0b50>] [<ffffffff811d0b50>] d_materialise_unique+0x1f0/0x3d0
Aug 31 13:49:46 git kernel: [139139.940529] RSP: 0018:ffff880004747bc0 EFLAGS: 00010286
Aug 31 13:49:46 git kernel: [139139.940529] RAX: ffff880020bdbd98 RBX: ffff8800c62e9718 RCX: 0000000000050005
Aug 31 13:49:46 git kernel: [139139.940529] RDX: 0000000100050005 RSI: ffff8800c62e9718 RDI: ffff880020bdbdf0
Aug 31 13:49:46 git kernel: [139139.940529] RBP: ffff880020bdbd98 R08: 0000000000000004 R09: ffff880020bdbdd8
Aug 31 13:49:46 git kernel: [139139.940529] R10: 0000000000000000 R11: 000000000000000c R12: ffff880056102018
Aug 31 13:49:46 git kernel: [139139.940529] R13: 000000000000003c R14: ffff880056102018 R15: ffff8801013fc3d8
Aug 31 13:49:46 git kernel: [139139.940529] FS: 00007fe25ca6c700(0000) GS:ffff88010f860000(0000) knlGS:0000000000000000
Aug 31 13:49:46 git kernel: [139139.940529] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 31 13:49:46 git kernel: [139139.940529] CR2: 000000000105d028 CR3: 0000000004880000 CR4: 0000000000100670
Aug 31 13:49:46 git kernel: [139139.940529] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 31 13:49:46 git kernel: [139139.940529] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Aug 31 13:49:46 git kernel: [139139.940529] Stack:
Aug 31 13:49:46 git kernel: [139139.940529] ffff8800d19a3700 ffff880004747d58 ffff880004747ce8 ffff880004747e58
Aug 31 13:49:46 git kernel: [139139.940529] 000000000000003c ffff880056102018 ffff8801013fc3d8 ffffffffa0464c3d
Aug 31 13:49:46 git kernel: [139139.940529] ffff8800560488e0 ffffea000387a870 ffff88000000000b ffff880056048aa0
Aug 31 13:49:46 git kernel: [139139.940529] Call Trace:
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa0464c3d>] ? nfs_readdir_page_filler+0x3cd/0x440 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04654e8>] ? nfs_readdir_xdr_to_array+0x1e8/0x2f0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04655f0>] ? nfs_readdir_xdr_to_array+0x2f0/0x2f0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa046560d>] ? nfs_readdir_filler+0x1d/0x80 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811490d0>] ? do_read_cache_page+0x80/0x1b0
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04657bc>] ? nfs_readdir+0x14c/0x5d0 [nfs]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffffa04abfd0>] ? nfs4_xdr_dec_layoutget+0x240/0x240 [nfsv4]
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cbbb5>] ? iterate_dir+0xa5/0x120
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cc009>] ? SyS_getdents+0x89/0x100
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff811cbd00>] ? fillonedir+0xd0/0xd0
Aug 31 13:49:46 git kernel: [139139.940529] [<ffffffff8153ad9c>] ? system_call_fast_compare_end+0x1c/0x21
Aug 31 13:49:46 git kernel: [139139.940529] Code: 00 f0 ff ff 0f 86 bb fe ff ff 48 83 fd d8 0f 84 9f 01 00 00 4c 89 ef e8 ef e5 ff ff e9 a4 fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 <0f> 0b 66 0f 1f 44 00 00 4c 89 e5 e9 68 fe ff ff 31 c0 45 31 ff
Aug 31 13:49:46 git kernel: [139139.940529] RIP [<ffffffff811d0b50>] d_materialise_unique+0x1f0/0x3d0
Aug 31 13:49:46 git kernel: [139139.940529] RSP <ffff880004747bc0>
Aug 31 13:49:46 git kernel: [139139.956969] ---[ end trace b016cdf86f96eb18 ]---

gitlab@git:~$ uname -a
Linux git 3.16.0-6-amd64 #1 SMP Debian 3.16.57-2 (2018-07-14) x86_64 GNU/Linux


What does invalid opcode: 0000 mean?



Xen is old but it was always working perfectly.. I can't upgrade easily.. it's used in production.



Linux xen-epsitecserver 2.6.32.43-0.4.1.xs1.8.0.855.170800xen #1 SMP Mon Jul 21 05:12:35 EDT 2014 i686 i686 i386 GNU/Linux


Thank you







debian kernel linux-kernel xen






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 31 at 13:21









ploth

848115




848115










asked Aug 31 at 12:28









Skywalker13

12




12











  • Have you tried disabling power saving options in the BIOS? See here: askubuntu.com/questions/50833/invalid-opcode-0000
    – Panki
    Aug 31 at 14:00










  • You have problems with your ram memory, sorry. You need to run memtest and replace it. That will corrupt your data soon.
    – Luciano Andress Martini
    Aug 31 at 14:33










  • I've this problem only with one VM on this Xen server. All other VMs are running fine. It's a Proliant server with ECC memory. According to the iLO firmware, everything is working fine. I can tune the VM with Debian Jessie. Do you know if it's possible to run a memtest without rebooting the whole Xen server?
    – Skywalker13
    Sep 1 at 21:30











  • Looks like lists.debian.org/debian-kernel/2016/12/msg00325.html
    – SamLeBarbare
    Sep 4 at 0:31










  • Thanks @SamLeBarbare; yes it looks like this bug. But I've upgraded to Debian Stretch and now, everything is working fine.
    – Skywalker13
    Sep 17 at 10:13
















  • Have you tried disabling power saving options in the BIOS? See here: askubuntu.com/questions/50833/invalid-opcode-0000
    – Panki
    Aug 31 at 14:00










  • You have problems with your ram memory, sorry. You need to run memtest and replace it. That will corrupt your data soon.
    – Luciano Andress Martini
    Aug 31 at 14:33










  • I've this problem only with one VM on this Xen server. All other VMs are running fine. It's a Proliant server with ECC memory. According to the iLO firmware, everything is working fine. I can tune the VM with Debian Jessie. Do you know if it's possible to run a memtest without rebooting the whole Xen server?
    – Skywalker13
    Sep 1 at 21:30











  • Looks like lists.debian.org/debian-kernel/2016/12/msg00325.html
    – SamLeBarbare
    Sep 4 at 0:31










  • Thanks @SamLeBarbare; yes it looks like this bug. But I've upgraded to Debian Stretch and now, everything is working fine.
    – Skywalker13
    Sep 17 at 10:13















Have you tried disabling power saving options in the BIOS? See here: askubuntu.com/questions/50833/invalid-opcode-0000
– Panki
Aug 31 at 14:00




Have you tried disabling power saving options in the BIOS? See here: askubuntu.com/questions/50833/invalid-opcode-0000
– Panki
Aug 31 at 14:00












You have problems with your ram memory, sorry. You need to run memtest and replace it. That will corrupt your data soon.
– Luciano Andress Martini
Aug 31 at 14:33




You have problems with your ram memory, sorry. You need to run memtest and replace it. That will corrupt your data soon.
– Luciano Andress Martini
Aug 31 at 14:33












I've this problem only with one VM on this Xen server. All other VMs are running fine. It's a Proliant server with ECC memory. According to the iLO firmware, everything is working fine. I can tune the VM with Debian Jessie. Do you know if it's possible to run a memtest without rebooting the whole Xen server?
– Skywalker13
Sep 1 at 21:30





I've this problem only with one VM on this Xen server. All other VMs are running fine. It's a Proliant server with ECC memory. According to the iLO firmware, everything is working fine. I can tune the VM with Debian Jessie. Do you know if it's possible to run a memtest without rebooting the whole Xen server?
– Skywalker13
Sep 1 at 21:30













Looks like lists.debian.org/debian-kernel/2016/12/msg00325.html
– SamLeBarbare
Sep 4 at 0:31




Looks like lists.debian.org/debian-kernel/2016/12/msg00325.html
– SamLeBarbare
Sep 4 at 0:31












Thanks @SamLeBarbare; yes it looks like this bug. But I've upgraded to Debian Stretch and now, everything is working fine.
– Skywalker13
Sep 17 at 10:13




Thanks @SamLeBarbare; yes it looks like this bug. But I've upgraded to Debian Stretch and now, everything is working fine.
– Skywalker13
Sep 17 at 10:13















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f466026%2fproduction-server-with-debian-jessie-system-hangs-after-an-invalid-opcode%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f466026%2fproduction-server-with-debian-jessie-system-hangs-after-an-invalid-opcode%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay