[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1987190 Title: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1 Status in zfs-linux package in Ubuntu: Confirmed Bug description: I have a server that has been running its data volume using ZFS in 20.04 without any problem. The volume is using ZFS encryption and a raidz1-0 configuration. I performed a scrub operations before the upgrade and it did not find any problem. After the reboot for the upgrade, I was welcomed with the following message: status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A The volumes still do not have any checksum error but there are 5 zvols that are not accessible. zpool status displays a line similar to the below for each of the five: errors: Permanent errors have been detected in the following files: tank/data/data:<0x0> I run a scrub and it has not identified any problem but the error messages are not there and the data is still not available. There are 10+ other zvols in the zpool that do not have any kind of problem. I have been unable to identify any correlation between the zvols that are failing. I have seen people reporting similar problems in github after the 20.04 to the 22.04 upgrade (see https://github.com/openzfs/zfs/issues/13763). I wonder how widespread the problem will be as more people upgrades to 22.04. I will try to downgrade the version of zfs in the system and report back ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 20 22:24:54 2022 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1
Hi, Attached an up-to-date patch for 2.1.5-1ubuntu6~22.04.1 to be used in Walter his steps in #4 (editing in launchpad is hard :-( ) ** Patch added: "zfs-dkms-2.1.5-1-fix-zero-mac-io-error.patch" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+attachment/5704587/+files/zfs-dkms-2.1.5-1-fix-zero-mac-io-error.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1987190 Title: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1 Status in zfs-linux package in Ubuntu: Confirmed Bug description: I have a server that has been running its data volume using ZFS in 20.04 without any problem. The volume is using ZFS encryption and a raidz1-0 configuration. I performed a scrub operations before the upgrade and it did not find any problem. After the reboot for the upgrade, I was welcomed with the following message: status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A The volumes still do not have any checksum error but there are 5 zvols that are not accessible. zpool status displays a line similar to the below for each of the five: errors: Permanent errors have been detected in the following files: tank/data/data:<0x0> I run a scrub and it has not identified any problem but the error messages are not there and the data is still not available. There are 10+ other zvols in the zpool that do not have any kind of problem. I have been unable to identify any correlation between the zvols that are failing. I have seen people reporting similar problems in github after the 20.04 to the 22.04 upgrade (see https://github.com/openzfs/zfs/issues/13763). I wonder how widespread the problem will be as more people upgrades to 22.04. I will try to downgrade the version of zfs in the system and report back ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 20 22:24:54 2022 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1987190 Title: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1 Status in zfs-linux package in Ubuntu: Confirmed Bug description: I have a server that has been running its data volume using ZFS in 20.04 without any problem. The volume is using ZFS encryption and a raidz1-0 configuration. I performed a scrub operations before the upgrade and it did not find any problem. After the reboot for the upgrade, I was welcomed with the following message: status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A The volumes still do not have any checksum error but there are 5 zvols that are not accessible. zpool status displays a line similar to the below for each of the five: errors: Permanent errors have been detected in the following files: tank/data/data:<0x0> I run a scrub and it has not identified any problem but the error messages are not there and the data is still not available. There are 10+ other zvols in the zpool that do not have any kind of problem. I have been unable to identify any correlation between the zvols that are failing. I have seen people reporting similar problems in github after the 20.04 to the 22.04 upgrade (see https://github.com/openzfs/zfs/issues/13763). I wonder how widespread the problem will be as more people upgrades to 22.04. I will try to downgrade the version of zfs in the system and report back ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 20 22:24:54 2022 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
Still no crashes seen with 4.4.0-79-generic (and newer versions). Would consider this fixed then. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic Status in linux package in Ubuntu: Fix Released Bug description: After upgrading from 4.4.0-77 to 4.4.0-78 I started getting kernel panics. The crashes do not happen immediately, but have happened generally after a couple of minutes, sometimes more. After enabling linux-crashdump stuff, I managed to extract this dmesg. [ 995.103846] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 995.104141] BUG: unable to handle kernel paging request at 88042a284000 [ 995.104407] IP: [] 0x88042a284000 [ 995.104594] PGD 43f20b067 PUD 43f20e067 PMD 42a3da063 PTE 80042a284163 [ 995.104946] Oops: 0011 [#1] SMP [ 995.105143] Modules linked in: zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) ppdev input_leds shpchp serio_raw i2c_piix4 mac_hid parport_pc parport 8250_fintek autofs4 ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse floppy pata_acpi [ 995.107081] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P O 4.4.0-78-generic #99-Ubuntu [ 995.107299] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org 04/01/2014 [ 995.107573] task: 88042a278000 ti: 88042a28 task.ti: 88042a28 [ 995.108070] RIP: 0010:[] [] 0x88042a284000 [ 995.108637] RSP: 0018:88042a283ed0 EFLAGS: 00010082 [ 995.109116] RAX: 0001 RBX: 00e797438af0 RCX: [ 995.109638] RDX: 0001 RSI: 0083 RDI: 0083 [ 995.110143] RBP: 81f38d40 R08: 000a R09: [ 995.110665] R10: 00010002a665 R11: 4c00 R12: 88042a283ed0 [ 995.82] R13: 810ff75e R14: R15: 88042a28 [ 995.111733] FS: () GS:88043fc8() knlGS: [ 995.112486] CS: 0010 DS: ES: CR0: 8005003b [ 995.112978] CR2: 88042a284000 CR3: 00043d246000 CR4: 06e0 [ 995.113497] DR0: DR1: DR2: [ 995.114085] DR3: DR6: fffe0ff0 DR7: 0400 [ 995.114612] Stack: [ 995.114965] 88042a283f28 810c4736 88042a28 88042a284000 [ 995.116204] ee041b0196f77cc4 a1abbcd2b8b123ce [ 995.117389] 88042a283f48 [ 995.118425] Call Trace: [ 995.118811] [] ? cpu_startup_entry+0x176/0x350 [ 995.119293] [] ? start_secondary+0x154/0x190 [ 995.119775] Code: ff ff ff 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 00 02 02 00 00 00 00 00 00 58 3f 28 2a 04 88 ff ff 18 00 00 00 00 00 00 00 8c 27 2a 04 88 ff ff 00 00 00 00 00 00 00 00 02 00 00 00 00 [ 995.125554] RIP [] 0x88042a284000 [ 995.126088] RSP [ 995.126453] CR2: 88042a284000 I've upgraded other machines as well, and only this particular VM shows this behaviour. I have a crash dump, but I haven't looked into the contents yet. Getting the dmesg was already a pain in the behind. The VM this happens on is: - a KVM guest - x86_64, 4 cores - 16gb ram lsb_release: Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial lspci says: 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:02.0 VGA compatible controller: VMware SVGA II Adapter 00:03.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon 00:0a.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:0b.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:12.0 Ethernet controller: Red Hat, Inc Virtio network device 00:1e.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge 00:1f.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge Let me know if there are other helpful details I can provide. If I find out more, I'll update this ticket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
** Tags added: kernel-unable-to-test-upstream -- 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/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 4.4.0-77 to 4.4.0-78 I started getting kernel panics. The crashes do not happen immediately, but have happened generally after a couple of minutes, sometimes more. After enabling linux-crashdump stuff, I managed to extract this dmesg. [ 995.103846] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 995.104141] BUG: unable to handle kernel paging request at 88042a284000 [ 995.104407] IP: [] 0x88042a284000 [ 995.104594] PGD 43f20b067 PUD 43f20e067 PMD 42a3da063 PTE 80042a284163 [ 995.104946] Oops: 0011 [#1] SMP [ 995.105143] Modules linked in: zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) ppdev input_leds shpchp serio_raw i2c_piix4 mac_hid parport_pc parport 8250_fintek autofs4 ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse floppy pata_acpi [ 995.107081] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P O 4.4.0-78-generic #99-Ubuntu [ 995.107299] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org 04/01/2014 [ 995.107573] task: 88042a278000 ti: 88042a28 task.ti: 88042a28 [ 995.108070] RIP: 0010:[] [] 0x88042a284000 [ 995.108637] RSP: 0018:88042a283ed0 EFLAGS: 00010082 [ 995.109116] RAX: 0001 RBX: 00e797438af0 RCX: [ 995.109638] RDX: 0001 RSI: 0083 RDI: 0083 [ 995.110143] RBP: 81f38d40 R08: 000a R09: [ 995.110665] R10: 00010002a665 R11: 4c00 R12: 88042a283ed0 [ 995.82] R13: 810ff75e R14: R15: 88042a28 [ 995.111733] FS: () GS:88043fc8() knlGS: [ 995.112486] CS: 0010 DS: ES: CR0: 8005003b [ 995.112978] CR2: 88042a284000 CR3: 00043d246000 CR4: 06e0 [ 995.113497] DR0: DR1: DR2: [ 995.114085] DR3: DR6: fffe0ff0 DR7: 0400 [ 995.114612] Stack: [ 995.114965] 88042a283f28 810c4736 88042a28 88042a284000 [ 995.116204] ee041b0196f77cc4 a1abbcd2b8b123ce [ 995.117389] 88042a283f48 [ 995.118425] Call Trace: [ 995.118811] [] ? cpu_startup_entry+0x176/0x350 [ 995.119293] [] ? start_secondary+0x154/0x190 [ 995.119775] Code: ff ff ff 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 00 02 02 00 00 00 00 00 00 58 3f 28 2a 04 88 ff ff 18 00 00 00 00 00 00 00 8c 27 2a 04 88 ff ff 00 00 00 00 00 00 00 00 02 00 00 00 00 [ 995.125554] RIP [] 0x88042a284000 [ 995.126088] RSP [ 995.126453] CR2: 88042a284000 I've upgraded other machines as well, and only this particular VM shows this behaviour. I have a crash dump, but I haven't looked into the contents yet. Getting the dmesg was already a pain in the behind. The VM this happens on is: - a KVM guest - x86_64, 4 cores - 16gb ram lsb_release: Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial lspci says: 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:02.0 VGA compatible controller: VMware SVGA II Adapter 00:03.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon 00:0a.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:0b.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:12.0 Ethernet controller: Red Hat, Inc Virtio network device 00:1e.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge 00:1f.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge Let me know if there are other helpful details I can provide. If I find out more, I'll update this ticket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
Due to the nature of the data on the machine and the fact that I don't know what apport will send, I'm unable to execute the apport-collect. # Some data from /usr/bin/crash: KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-78-generic DUMPFILE: dump.201705181342 [PARTIAL DUMP] CPUS: 4 DATE: Thu May 18 13:42:12 2017 UPTIME: 00:16:34 LOAD AVERAGE: 0.21, 0.05, 0.01 TASKS: 547 NODENAME: RELEASE: 4.4.0-78-generic VERSION: #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 MACHINE: x86_64 (2199 Mhz) MEMORY: 16 GB PANIC: "BUG: unable to handle kernel paging request at 88042a284000" PID: 0 COMMAND: "swapper/1" TASK: 88042a278000 (1 of 4) [THREAD_INFO: 88042a28] CPU: 1 STATE: TASK_RUNNING (PANIC) # crash> bt PID: 0 TASK: 88042a278000 CPU: 1 COMMAND: "swapper/1" #0 [88042a283b78] machine_kexec at 8105c0db #1 [88042a283bd8] crash_kexec at 8110e572 #2 [88042a283ca8] oops_end at 81031c49 #3 [88042a283cd0] no_context at 8106ad35 #4 [88042a283d30] __bad_area_nosemaphore at 8106b000 #5 [88042a283d78] bad_area_nosemaphore at 8106b183 #6 [88042a283d88] __do_page_fault at 8106b447 #7 [88042a283de0] trace_do_page_fault at 8106b7f7 #8 [88042a283e10] do_async_page_fault at 81063ef9 #9 [88042a283e20] async_page_fault at 81842be8 #10 [88042a283e38] tick_nohz_idle_exit at 810ff75e #11 [88042a283ed8] cpu_startup_entry at 810c4736 #12 [88042a283f30] start_secondary at 810517c4 # crash> bt -f # #9 [88042a283e20] async_page_fault at 81842be8 88042a283e28: 88042a28 88042a283e38: 810ff75e #10 [88042a283e38] tick_nohz_idle_exit at 810ff75e 88042a283e40: 88042a283ed0 81f38d40 88042a283e50: 00e797438af0 4c00 88042a283e60: 00010002a665 88042a283e70: 000a 0001 88042a283e80: 0001 88042a283e90: 0083 0083 88042a283ea0: 88042a284000 88042a283eb0: 0010 00010082 88042a283ec0: 88042a283ed0 0018 88042a283ed0: 88042a283f28 810c4736 #11 [88042a283ed8] cpu_startup_entry at 810c4736 88042a283ee0: 88042a28 88042a284000 88042a283ef0: ee041b0196f77cc4 a1abbcd2b8b123ce 88042a283f00: 88042a283f10: 88042a283f20: 88042a283f48 88042a283f30: 810517c4 #12 [88042a283f30] start_secondary at 810517c4 # crash> dis tick_nohz_idle_exit 0x810ff74f: mov%r12,0xa8(%rbx) 0x810ff756 : mov%r12,%rsi 0x810ff759 : callq 0x810ff170 0x810ff75e : mov0xd0989b(%rip),%rdi # 0x81e09000 0x810ff765 : sub0x78(%rbx),%rdi # lsmod info's Module Size Used by zfs 2813952 5 zunicode 331776 1 zfs zcommon57344 1 zfs znvpair90112 2 zfs,zcommon spl 102400 3 zfs,zcommon,znvpair zavl 16384 1 zfs ppdev 20480 0 input_leds 16384 0 shpchp 36864 0 serio_raw 16384 0 i2c_piix4 24576 0 8250_fintek16384 0 parport_pc 32768 0 parport49152 2 ppdev,parport_pc mac_hid16384 0 autofs440960 2 ttm94208 0 drm_kms_helper155648 0 syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops16384 1 drm_kms_helper psmouse 131072 0 drm 364544 2 ttm,drm_kms_helper pata_acpi 16384 0 floppy 73728 0 No idea if this is useful though. -- 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/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 4.4.0-77 to 4.4.0-78 I started getting kernel panics. The crashes do not happen immediately, but have happened generally after a couple of minutes, sometimes more. After enabling linux-crashdump stuff, I managed to extract this dmesg. [ 995.103846] kernel
[Kernel-packages] [Bug 1691741] [NEW] Execute NX-protected page - 4.4.0-78-generic - kernel panic
Public bug reported: After upgrading from 4.4.0-77 to 4.4.0-78 I started getting kernel panics. The crashes do not happen immediately, but have happened generally after a couple of minutes, sometimes more. After enabling linux-crashdump stuff, I managed to extract this dmesg. [ 995.103846] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 995.104141] BUG: unable to handle kernel paging request at 88042a284000 [ 995.104407] IP: [] 0x88042a284000 [ 995.104594] PGD 43f20b067 PUD 43f20e067 PMD 42a3da063 PTE 80042a284163 [ 995.104946] Oops: 0011 [#1] SMP [ 995.105143] Modules linked in: zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) ppdev input_leds shpchp serio_raw i2c_piix4 mac_hid parport_pc parport 8250_fintek autofs4 ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse floppy pata_acpi [ 995.107081] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P O 4.4.0-78-generic #99-Ubuntu [ 995.107299] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org 04/01/2014 [ 995.107573] task: 88042a278000 ti: 88042a28 task.ti: 88042a28 [ 995.108070] RIP: 0010:[] [] 0x88042a284000 [ 995.108637] RSP: 0018:88042a283ed0 EFLAGS: 00010082 [ 995.109116] RAX: 0001 RBX: 00e797438af0 RCX: [ 995.109638] RDX: 0001 RSI: 0083 RDI: 0083 [ 995.110143] RBP: 81f38d40 R08: 000a R09: [ 995.110665] R10: 00010002a665 R11: 4c00 R12: 88042a283ed0 [ 995.82] R13: 810ff75e R14: R15: 88042a28 [ 995.111733] FS: () GS:88043fc8() knlGS: [ 995.112486] CS: 0010 DS: ES: CR0: 8005003b [ 995.112978] CR2: 88042a284000 CR3: 00043d246000 CR4: 06e0 [ 995.113497] DR0: DR1: DR2: [ 995.114085] DR3: DR6: fffe0ff0 DR7: 0400 [ 995.114612] Stack: [ 995.114965] 88042a283f28 810c4736 88042a28 88042a284000 [ 995.116204] ee041b0196f77cc4 a1abbcd2b8b123ce [ 995.117389] 88042a283f48 [ 995.118425] Call Trace: [ 995.118811] [] ? cpu_startup_entry+0x176/0x350 [ 995.119293] [] ? start_secondary+0x154/0x190 [ 995.119775] Code: ff ff ff 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 00 02 02 00 00 00 00 00 00 58 3f 28 2a 04 88 ff ff 18 00 00 00 00 00 00 00 8c 27 2a 04 88 ff ff 00 00 00 00 00 00 00 00 02 00 00 00 00 [ 995.125554] RIP [] 0x88042a284000 [ 995.126088] RSP [ 995.126453] CR2: 88042a284000 I've upgraded other machines as well, and only this particular VM shows this behaviour. I have a crash dump, but I haven't looked into the contents yet. Getting the dmesg was already a pain in the behind. The VM this happens on is: - a KVM guest - x86_64, 4 cores - 16gb ram lsb_release: Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial lspci says: 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:02.0 VGA compatible controller: VMware SVGA II Adapter 00:03.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon 00:0a.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:0b.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:12.0 Ethernet controller: Red Hat, Inc Virtio network device 00:1e.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge 00:1f.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge Let me know if there are other helpful details I can provide. If I find out more, I'll update this ticket. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from 4.4.0-77 to 4.4.0-78 I started getting kernel panics. The crashes do not happen immediately, but have happened generally after a couple of minutes, sometimes more. After enabling linux-crashdump stuff, I managed to extract this dmesg. [ 995.103846] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 995.104141] BUG: unable to handle kernel paging request at 88042a284000