• [6.9-beta1] Page Fault


    dorgan
    • Solved

    Not sure of this is unraid 6.9-beta1 issue or not, but just in case it is.

     

    Screenshot_20200427-221815.thumb.jpg.d2ef26ae4d7179a157f69e6ff48b6bd9.jpg




    User Feedback

    Recommended Comments



    I am not noticing anything wrong with the systems I just happen to turn on the monitor today and see this, so figured I would report it.  Please let me know what additional information is needed.

    Link to comment

    Had 2 hard lockups last week, but this time I saw an error without the lockup:

     

    [104171.459847] mdcmd (79): set md_write_method 1

    [104771.511063] mdcmd (80): set md_write_method 0

    [108155.198765] mdcmd (81): spindown 6
    [108156.829365] mdcmd (82): spindown 5
    [111744.657559] mdcmd (83): spindown 2
    [113280.017493] mdcmd (84): spindown 4
    [115274.774346] mdcmd (85): spindown 3
    [120367.842034] mdcmd (86): set md_write_method 1

    [129625.634158] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
    [129625.634385] BUG: unable to handle page fault for address: ffffc90008097f10
    [129625.634606] #PF: supervisor instruction fetch in kernel mode
    [129625.634824] #PF: error_code(0x0011) - permissions violation
    [129625.635042] PGD 7fb424067 P4D 7fb424067 PUD 7fb425067 PMD 7f5037067 PTE 800000019ebe4163
    [129625.635268] Oops: 0011 [#4] SMP NOPTI
    [129625.635481] CPU: 11 PID: 16040 Comm: shfs Tainted: G      D           5.5.8-Unraid #1
    [129625.635705] Hardware name: System manufacturer System Product Name/PRIME X370-PRO, BIOS 5220 09/12/2019
    [129625.636138] RIP: 0010:0xffffc90008097f10
    [129625.636352] Code: ff ff 00 ca cd 4e 81 88 ff ff 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 72 b5 14 81 ff ff ff ff 38 5d 48 00 40 15 00 00 <00> 48 d3 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    [129625.637010] RSP: 0018:ffffc9000330bc08 EFLAGS: 00010282
    [129625.637227] RAX: ffffc90008097f10 RBX: ffffc90008097f10 RCX: 0000000000000000
    [129625.637450] RDX: 0000000000000000 RSI: ffffc90008097d28 RDI: ffff88879c5bb200
    [129625.637671] RBP: ffff88879c5bb200 R08: 0000000000000000 R09: ffffc9000330bba8
    [129625.637890] R10: 0000000000000068 R11: ffffc9000330bbe0 R12: ffff88877e7a3220
    [129625.638107] R13: ffff8887f57bf9c0 R14: ffff88877e7a3250 R15: ffff88877e7a3230
    [129625.638327] FS:  000014db1d91c700(0000) GS:ffff8887feac0000(0000) knlGS:0000000000000000
    [129625.638548] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [129625.638763] CR2: ffffc90008097f10 CR3: 000000079be62000 CR4: 00000000003406e0
    [129625.638981] Call Trace:
    [129625.639198]  ? fuse_request_end+0x185/0x19a
    [129625.639410]  ? fuse_dev_do_write+0xa2e/0xa75
    [129625.639621]  ? fuse_dev_write+0x5b/0x75
    [129625.639832]  ? do_iter_readv_writev+0xb3/0xf3
    [129625.640042]  ? do_iter_write+0x7c/0xb8
    [129625.640253]  ? vfs_writev+0x74/0xb4
    [129625.640462]  ? __do_sys_newfstat+0x3c/0x5f
    [129625.640675]  ? __fget_light+0x3d/0x47
    [129625.640888]  ? do_writev+0x79/0xe7
    [129625.641102]  ? do_syscall_64+0x7a/0x87
    [129625.641317]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
    [129625.641530] Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap veth xt_nat iptable_filter xfs nfsd lockd grace sunrpc md_mod iptable_nat xt_MASQUERADE nf_nat ip_tables wireguard ip6_udp_tunnel udp_tunnel bonding edac_mce_amd kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel igb wmi_bmof mxm_wmi mpt3sas aesni_intel k10temp crypto_simd i2c_piix4 i2c_algo_bit cryptd nvme i2c_core raid_class ahci scsi_transport_sas ccp glue_helper nvme_core libahci wmi button acpi_cpufreq
    [129625.643307] CR2: ffffc90008097f10
    [129625.643960] ---[ end trace 2647bc31763b741b ]---
    [129625.644222] RIP: 0010:0xffffc90003b23f08
    [129625.644488] Code: Bad RIP value.
    [129625.644741] RSP: 0018:ffffc90003b53c08 EFLAGS: 00010282
    [129625.645000] RAX: ffffc90003b23f08 RBX: ffffc90003b23f08 RCX: 0000000000000000
    [129625.645266] RDX: 0000000000000000 RSI: ffffc90003b23d20 RDI: ffff88879c5bb200
    [129625.645529] RBP: ffff88879c5bb200 R08: 0000000000000000 R09: ffffc90003b53ba8
    [129625.645793] R10: 0000000000000068 R11: ffffc90003b53be0 R12: ffff88841b60fd48
    [129625.646060] R13: ffff8887f57bf9c0 R14: ffff88841b60fd78 R15: ffff88841b60fd58
    [129625.646325] FS:  000014db1d91c700(0000) GS:ffff8887feac0000(0000) knlGS:0000000000000000
    [129625.646594] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [129625.646855] CR2: ffffc90003b23ede CR3: 000000079be62000 CR4: 00000000003406e0
    [170768.074968] mdcmd (87): set md_write_method 0

     

     

    researching the error message indicates a possible fuse issue.

     

    Chip

    kong-diagnostics-20200428-2105.zip

    Link to comment
    On 4/28/2020 at 7:08 PM, dorgan said:

    Please let me know what additional information is needed.

    I already did let you know with the link I posted in my initial reply.

    Link to comment
    On 4/28/2020 at 9:18 PM, DeatheTongue said:

    Had 2 hard lockups last week

    Have you taken care of these Ryzen tweaks?

     

    Link to comment

    I have the same problem it seems. Been really stable for 2 months now but started crashing this weekend, and right now it crashes multiple times a day. The UI still works but is really slow, cpu util is at 100%, can't really get diagnostics because nothing happens. I have attached one of the syslogs with the crash and diagnostics after reboot.

     

    Next I'll try the ryzen tweaks mentioned above.

    syslog-1588600124 homeserver-diagnostics-20200502-2106.zip

    Link to comment

    Just had a crash again even after the ryzen tweaks, I would appreciate any help I can get as it right now crashes every day. I guess roll back to the stable version could work (if this is an 6.9 problem).

    Edited by darkdev
    Link to comment
    58 minutes ago, darkdev said:

    I guess roll back to the stable version could work (if this is an 6.9 problem).

    Downgrade to v6.8.3 and see if it helps, unlikely your problem is v6.9

    Link to comment
    4 hours ago, johnnie.black said:

    Downgrade to v6.8.3 and see if it helps, unlikely your problem is v6.9

    I'll try that, if I have the same problem then I'll make a thread in general support instead.

    Link to comment

    When checking the current server log i found this:

    Apr  5 16:19:37 TOWER kernel: BUG: unable to handle page fault for address: 000000005cefea34
    Apr  5 16:19:37 TOWER kernel: #PF: supervisor instruction fetch in kernel mode
    Apr  5 16:19:37 TOWER kernel: #PF: error_code(0x0010) - not-present page
    Apr  5 16:19:37 TOWER kernel: PGD 274bb3067 P4D 274bb3067 PUD 0 
    Apr  5 16:19:37 TOWER kernel: Oops: 0010 [#1] SMP NOPTI
    Apr  5 16:19:37 TOWER kernel: CPU: 2 PID: 22765 Comm: shfs Not tainted 5.5.8-Unraid #1
    Apr  5 16:19:37 TOWER kernel: Hardware name: Insyde AS Series/Type2 - Board Product Name, BIOS V1.37 01/27/2015
    Apr  5 16:19:37 TOWER kernel: RIP: 0010:0x5cefea34
    Apr  5 16:19:37 TOWER kernel: Code: Bad RIP value.
    Apr  5 16:19:37 TOWER kernel: RSP: 0018:ffffc9000a6a7c08 EFLAGS: 00010202
    Apr  5 16:19:37 TOWER kernel: RAX: 000000005cefea34 RBX: 000000005cefea34 RCX: 0000000000000000
    Apr  5 16:19:37 TOWER kernel: RDX: 0000000000000000 RSI: ffffc9000b857de0 RDI: ffff888238700c00
    Apr  5 16:19:37 TOWER kernel: RBP: ffff888238700c00 R08: 0000000000000000 R09: ffffc9000a6a7ba8
    Apr  5 16:19:37 TOWER kernel: R10: 0000000000000068 R11: ffffc9000a6a7be0 R12: ffff8882387a1b28
    Apr  5 16:19:37 TOWER kernel: R13: ffff8882381713c0 R14: ffff8882387a1b58 R15: ffff8882387a1b38
    Apr  5 16:19:37 TOWER kernel: FS:  000014f6c2721700(0000) GS:ffff888277d00000(0000) knlGS:0000000000000000
    Apr  5 16:19:37 TOWER kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Apr  5 16:19:37 TOWER kernel: CR2: 000000005cefea0a CR3: 000000023d0ec000 CR4: 00000000001006e0
    Apr  5 16:19:37 TOWER kernel: Call Trace:
    Apr  5 16:19:37 TOWER kernel: ? fuse_request_end+0x185/0x19a
    Apr  5 16:19:37 TOWER kernel: ? fuse_dev_do_write+0xa2e/0xa75
    Apr  5 16:19:37 TOWER kernel: ? step_into+0x5d/0x1b2
    Apr  5 16:19:37 TOWER kernel: ? link_path_walk.part.0+0x225/0x41c
    Apr  5 16:19:37 TOWER kernel: ? fuse_dev_write+0x5b/0x75
    Apr  5 16:19:37 TOWER kernel: ? do_iter_readv_writev+0xb3/0xf3
    Apr  5 16:19:37 TOWER kernel: ? do_iter_write+0x7c/0xb8
    Apr  5 16:19:37 TOWER kernel: ? vfs_writev+0x74/0xb4
    Apr  5 16:19:37 TOWER kernel: ? __do_sys_newlstat+0x48/0x6b
    Apr  5 16:19:37 TOWER kernel: ? __fget_light+0x3d/0x47
    Apr  5 16:19:37 TOWER kernel: ? do_writev+0x79/0xe7
    Apr  5 16:19:37 TOWER kernel: ? do_syscall_64+0x7a/0x87
    Apr  5 16:19:37 TOWER kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
    Apr  5 16:19:37 TOWER kernel: Modules linked in: md_mod xt_MASQUERADE iptable_filter iptable_nat nf_nat ip_tables it87 hwmon_vid xfs nfsd lockd grace sunrpc tg3 intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel cryptd intel_cstate i2c_i801 i2c_core ahci libahci video iosf_mbi fan thermal backlight button [last unloaded: md_mod]
    Apr  5 16:19:37 TOWER kernel: CR2: 000000005cefea34
    Apr  5 16:19:37 TOWER kernel: ---[ end trace 10a0e1bdc55a4e53 ]---
    Apr  5 16:19:37 TOWER kernel: RIP: 0010:0x5cefea34
    Apr  5 16:19:37 TOWER kernel: Code: Bad RIP value.
    Apr  5 16:19:37 TOWER kernel: RSP: 0018:ffffc9000a6a7c08 EFLAGS: 00010202
    Apr  5 16:19:37 TOWER kernel: RAX: 000000005cefea34 RBX: 000000005cefea34 RCX: 0000000000000000
    Apr  5 16:19:37 TOWER kernel: RDX: 0000000000000000 RSI: ffffc9000b857de0 RDI: ffff888238700c00
    Apr  5 16:19:37 TOWER kernel: RBP: ffff888238700c00 R08: 0000000000000000 R09: ffffc9000a6a7ba8
    Apr  5 16:19:37 TOWER kernel: R10: 0000000000000068 R11: ffffc9000a6a7be0 R12: ffff8882387a1b28
    Apr  5 16:19:37 TOWER kernel: R13: ffff8882381713c0 R14: ffff8882387a1b58 R15: ffff8882387a1b38
    Apr  5 16:19:37 TOWER kernel: FS:  000014f6c2721700(0000) GS:ffff888277d00000(0000) knlGS:0000000000000000
    Apr  5 16:19:37 TOWER kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Apr  5 16:19:37 TOWER kernel: CR2: 000000005cefea0a CR3: 000000023d0ec000 CR4: 00000000001006e0

     

    But the server did not crash, nor did i experience any issues. The server has been running up to now (8 May) without problems. This seems to be a singular event. Should i reboot?

     

    Edit: It does look exactly like the other reports here, so it might be a real bug. Also it seems to be not Ryzen related as my system is intel based.

    Edited by Videodr0me
    Link to comment
    28 minutes ago, Videodr0me said:

    Edit: It does look exactly like the other reports here, so it might be a real bug. Also it seems to be not Ryzen related as my system is intel based.

    Yes it does, please post the full diags if you haven't rebooted yet.

    Link to comment

    Just a follow up from me, it has been running now for 2 days without problems after downgrading to v6.8.3 (had around 2 crashes a day on 6.9). I'll let you know my status after a week as well.

    Link to comment

    I did not reboot the machine, just to see if more of these page faults show up. And yes it happened again. Will this be fixed in the next beta:

    May  5 08:46:39 TOWER kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
    May  5 08:46:39 TOWER kernel: BUG: unable to handle page fault for address: ffffc900016b3e98
    May  5 08:46:39 TOWER kernel: #PF: supervisor instruction fetch in kernel mode
    May  5 08:46:39 TOWER kernel: #PF: error_code(0x0011) - permissions violation
    May  5 08:46:39 TOWER kernel: PGD 276c19067 P4D 276c19067 PUD 276c1a067 PMD 276489067 PTE 800000019db60163
    May  5 08:46:39 TOWER kernel: Oops: 0011 [#2] SMP NOPTI
    May  5 08:46:39 TOWER kernel: CPU: 2 PID: 26255 Comm: shfs Tainted: G      D           5.5.8-Unraid #1
    May  5 08:46:39 TOWER kernel: Hardware name: Insyde AS Series/Type2 - Board Product Name, BIOS V1.37 01/27/2015
    May  5 08:46:39 TOWER kernel: RIP: 0010:0xffffc900016b3e98
    May  5 08:46:39 TOWER kernel: Code: 00 00 00 30 ca 77 82 88 ff ff d9 b8 07 81 ff ff ff ff 01 96 07 81 ff ff ff ff 98 2a 6a 39 82 88 ff ff 80 0c d6 76 82 88 ff ff <80> 2f ca 77 82 88 ff ff 80 25 6a 39 82 88 ff ff 00 00 00 00 00 00
    May  5 08:46:39 TOWER kernel: RSP: 0018:ffffc900098efc08 EFLAGS: 00010282
    May  5 08:46:39 TOWER kernel: RAX: ffffc900016b3e98 RBX: ffffc900016b3e98 RCX: 0000000000000000
    May  5 08:46:39 TOWER kernel: RDX: 0000000000000000 RSI: ffffc900016b3db0 RDI: ffff888238700c00
    May  5 08:46:39 TOWER kernel: RBP: ffff888238700c00 R08: 0000000000000000 R09: ffffc900098efba8
    May  5 08:46:39 TOWER kernel: R10: 0000000000000068 R11: ffffc900098efbe0 R12: ffff888236450110
    May  5 08:46:39 TOWER kernel: R13: ffff888238700c4c R14: ffff888236450140 R15: ffff888236450120
    May  5 08:46:39 TOWER kernel: FS:  000014f6c2c29700(0000) GS:ffff888277d00000(0000) knlGS:0000000000000000
    May  5 08:46:39 TOWER kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    May  5 08:46:39 TOWER kernel: CR2: ffffc900016b3e98 CR3: 000000023d0ec000 CR4: 00000000001006e0
    May  5 08:46:39 TOWER kernel: Call Trace:
    May  5 08:46:39 TOWER kernel: ? fuse_request_end+0x185/0x19a
    May  5 08:46:39 TOWER kernel: ? fuse_dev_do_write+0xa2e/0xa75
    May  5 08:46:39 TOWER kernel: ? step_into+0x5d/0x1b2
    May  5 08:46:39 TOWER kernel: ? link_path_walk.part.0+0x225/0x41c
    May  5 08:46:39 TOWER kernel: ? fuse_dev_write+0x5b/0x75
    May  5 08:46:39 TOWER kernel: ? do_iter_readv_writev+0xb3/0xf3
    May  5 08:46:39 TOWER kernel: ? do_iter_write+0x7c/0xb8
    May  5 08:46:39 TOWER kernel: ? vfs_writev+0x74/0xb4
    May  5 08:46:39 TOWER kernel: ? __do_sys_newlstat+0x48/0x6b
    May  5 08:46:39 TOWER kernel: ? __fget_light+0x3d/0x47
    May  5 08:46:39 TOWER kernel: ? do_writev+0x79/0xe7
    May  5 08:46:39 TOWER kernel: ? do_syscall_64+0x7a/0x87
    May  5 08:46:39 TOWER kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
    May  5 08:46:39 TOWER kernel: Modules linked in: md_mod xt_MASQUERADE iptable_filter iptable_nat nf_nat ip_tables it87 hwmon_vid xfs nfsd lockd grace sunrpc tg3 intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel cryptd intel_cstate i2c_i801 i2c_core ahci libahci video iosf_mbi fan thermal backlight button [last unloaded: md_mod]
    May  5 08:46:39 TOWER kernel: CR2: ffffc900016b3e98
    May  5 08:46:39 TOWER kernel: ---[ end trace 10a0e1bdc55a4e54 ]---
    May  5 08:46:39 TOWER kernel: RIP: 0010:0x5cefea34
    May  5 08:46:39 TOWER kernel: Code: Bad RIP value.
    May  5 08:46:39 TOWER kernel: RSP: 0018:ffffc9000a6a7c08 EFLAGS: 00010202
    May  5 08:46:39 TOWER kernel: RAX: 000000005cefea34 RBX: 000000005cefea34 RCX: 0000000000000000
    May  5 08:46:39 TOWER kernel: RDX: 0000000000000000 RSI: ffffc9000b857de0 RDI: ffff888238700c00
    May  5 08:46:39 TOWER kernel: RBP: ffff888238700c00 R08: 0000000000000000 R09: ffffc9000a6a7ba8
    May  5 08:46:39 TOWER kernel: R10: 0000000000000068 R11: ffffc9000a6a7be0 R12: ffff8882387a1b28
    May  5 08:46:39 TOWER kernel: R13: ffff8882381713c0 R14: ffff8882387a1b58 R15: ffff8882387a1b38
    May  5 08:46:39 TOWER kernel: FS:  000014f6c2c29700(0000) GS:ffff888277d00000(0000) knlGS:0000000000000000
    May  5 08:46:39 TOWER kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    May  5 08:46:39 TOWER kernel: CR2: 000000005cefea0a CR3: 000000023d0ec000 CR4: 00000000001006e0

     

    Edited by Videodr0me
    Link to comment
    8 hours ago, Videodr0me said:

    I did not reboot the machine, just to see if more of these page faults show up. And yes it happened again. Will this be fixed in the next beta:

    Have you tried booting in SAFE mode? Technically you should test in SAFE mode before reporting a bug, and I see you have some very old plugins installed, plugins that have been deprecated for years and should have been replaced long ago by dockers.

    Nzbget.plg - 2016.09.17.1
    Sonarr.plg - 2017.02.15.1
    Transmission.plg - 2016.09.17.1
    

     

    Link to comment
    2 hours ago, trurl said:

    Have you tried booting in SAFE mode? Technically you should test in SAFE mode before reporting a bug, and I see you have some very old plugins installed, plugins that have been deprecated for years and should have been replaced long ago by dockers.

    
    Nzbget.plg - 2016.09.17.1
    Sonarr.plg - 2017.02.15.1
    Transmission.plg - 2016.09.17.1
    

     

    As I stated, I did not reboot at all. System is up for 44 days, in this time the page fault occured twice. I find it highly unlikely that the pagefaults have anything to do with these plugins, as others without these plugins report exactly the same page faults. The next time i reboot i might try safe mode for a brief period, but as these pagefaults occur rarely I would not pin to much hope reproducing these faults. Never had any of these with previous versions - not even with the other rc that used a 5.x kernel.

    Link to comment
    On 5/19/2020 at 7:19 PM, johnnie.black said:

    This looks more like a kernel issue, likely gone on the next beta/rc.

    I wonder if i should go back to 6.8.3 or wait for a new beta. Is there any rough timeframe for when the next beta will be dropped upon us?

    Link to comment
    On 4/28/2020 at 5:08 PM, dorgan said:

    I'm on the 6.9.0 beta 1. and my server also has been randomly freezing with this in the tail -f in ssh:

    Jun 26 23:32:43 MediaXen kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
    Jun 26 23:32:43 MediaXen kernel: BUG: unable to handle page fault for address: ffffc9000a96bf08
    Jun 26 23:32:43 MediaXen kernel: #PF: supervisor instruction fetch in kernel mode
    Jun 26 23:32:43 MediaXen kernel: #PF: error_code(0x0011) - permissions violation
    Jun 26 23:32:43 MediaXen kernel: PGD 66742d067 P4D 66742d067 PUD 66742e067 PMD 66066f067 PTE 8000000195bb9063
    Jun 26 23:32:43 MediaXen kernel: Oops: 0011 [#1] SMP PTI
    Jun 26 23:32:43 MediaXen kernel: CPU: 16 PID: 17756 Comm: shfs Not tainted 5.5.8-Unraid #1
    Jun 26 23:32:43 MediaXen kernel: Hardware name: Supermicro X9DRi-LN4+/X9DR3-LN4+/X9DRi-LN4+/X9DR3-LN4+, BIOS 3.2 03/04/2015
    Jun 26 23:32:43 MediaXen kernel: RIP: 0010:0xffffc9000a96bf08
    Jun 26 23:32:43 MediaXen kernel: Code: ff ff 00 04 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0 b3 14 81 ff ff ff ff 18 86 1b 00 9e 7f 00 00 <00> 70 71 1a 00 00 00 00 00 d5 bd 26 19 13 b4 3b 00 00 00 00 00 00
    Jun 26 23:32:43 MediaXen kernel: RSP: 0018:ffffc9000b2d3c08 EFLAGS: 00010282
    Jun 26 23:32:43 MediaXen kernel: RAX: ffffc9000a96bf08 RBX: ffffc9000a96bf08 RCX: 0000000000000000
    Jun 26 23:32:43 MediaXen kernel: RDX: 0000000000000000 RSI: ffffc9000a96bd20 RDI: ffff8886430b2200
    Jun 26 23:32:43 MediaXen kernel: RBP: ffff8886430b2200 R08: 0000000000000000 R09: ffffc9000b2d3ba8
    Jun 26 23:32:43 MediaXen kernel: R10: 0000000000000068 R11: ffffc9000b2d3be0 R12: ffff8881561d7088
    Jun 26 23:32:43 MediaXen kernel: R13: ffff888663456840 R14: ffff8881561d70b8 R15: ffff8881561d7098
    Jun 26 23:32:43 MediaXen kernel: FS:  0000152fb07d9700(0000) GS:ffff888667c80000(0000) knlGS:0000000000000000
    Jun 26 23:32:43 MediaXen kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Jun 26 23:32:43 MediaXen kernel: CR2: ffffc9000a96bf08 CR3: 00000006088c4004 CR4: 00000000000606e0
    Jun 26 23:32:43 MediaXen kernel: Call Trace:
    Jun 26 23:32:43 MediaXen kernel: ? fuse_request_end+0x185/0x19a
    Jun 26 23:32:43 MediaXen kernel: ? fuse_dev_do_write+0xa2e/0xa75
    Jun 26 23:32:43 MediaXen kernel: ? fuse_dev_write+0x5b/0x75
    Jun 26 23:32:43 MediaXen kernel: ? do_iter_readv_writev+0xb3/0xf3
    Jun 26 23:32:43 MediaXen kernel: ? do_iter_write+0x7c/0xb8
    Jun 26 23:32:43 MediaXen kernel: ? vfs_writev+0x74/0xb4
    Jun 26 23:32:43 MediaXen kernel: ? __do_sys_newfstat+0x3c/0x5f
    Jun 26 23:32:43 MediaXen kernel: ? __fget_light+0x3d/0x47
    Jun 26 23:32:43 MediaXen kernel: ? do_writev+0x79/0xe7
    Jun 26 23:32:43 MediaXen kernel: ? do_syscall_64+0x7a/0x87
    Jun 26 23:32:43 MediaXen kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
    Jun 26 23:32:43 MediaXen kernel: Modules linked in: md4 sha512_ssse3 sha512_generic cmac cifs libarc4 xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap veth xt_nat xt_MASQUERADE iptable_filter iptable_nat nf_nat ip_tables xfs md_mod bonding igb i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd ipmi_ssif isci glue_helper intel_cstate libsas aacraid i2c_i801 intel_uncore i2c_core ahci intel_rapl_perf scsi_transport_sas libahci wmi ipmi_si button [last unloaded: i2c_algo_bit]
    Jun 26 23:32:43 MediaXen kernel: CR2: ffffc9000a96bf08
    Jun 26 23:32:43 MediaXen kernel: ---[ end trace 95101aa1ab5de029 ]---
    Jun 26 23:32:43 MediaXen kernel: RIP: 0010:0xffffc9000a96bf08
    Jun 26 23:32:43 MediaXen kernel: Code: ff ff 00 04 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0 b3 14 81 ff ff ff ff 88 ca 09 00 9e 7f 00 00 <00> c4 6c 26 00 00 00 00 00 d5 bd 26 19 13 b4 3b 00 00 00 00 00 00
    Jun 26 23:32:43 MediaXen kernel: RSP: 0018:ffffc9000b2d3c08 EFLAGS: 00010282
    Jun 26 23:32:43 MediaXen kernel: RAX: ffffc9000a96bf08 RBX: ffffc9000a96bf08 RCX: 0000000000000000
    Jun 26 23:32:43 MediaXen kernel: RDX: 0000000000000000 RSI: ffffc9000a96bd20 RDI: ffff8886430b2200
    Jun 26 23:32:43 MediaXen kernel: RBP: ffff8886430b2200 R08: 0000000000000000 R09: ffffc9000b2d3ba8
    Jun 26 23:32:43 MediaXen kernel: R10: 0000000000000068 R11: ffffc9000b2d3be0 R12: ffff8881561d7088
    Jun 26 23:32:43 MediaXen kernel: R13: ffff888663456840 R14: ffff8881561d70b8 R15: ffff8881561d7098
    Jun 26 23:32:43 MediaXen kernel: FS:  0000152fb07d9700(0000) GS:ffff888667c80000(0000) knlGS:0000000000000000
    Jun 26 23:32:43 MediaXen kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Jun 26 23:32:43 MediaXen kernel: CR2: ffffc9000a96bf08 CR3: 00000006088c4004 CR4: 00000000000606e0

     

    Link to comment
    7 hours ago, DevXen said:

    I'm on the 6.9.0 beta 1. and my server also has been randomly freezing with this in the tail

    Upgrade to beta22

    Link to comment
    On 6/28/2020 at 1:31 AM, johnnie.black said:

    Upgrade to beta22

    just saw your reply. beta25, now. but i'll update to it. thank you.

    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.