• Unraid OS version 6.9.0-rc2 available


    limetech

    As always, prior to updating, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".

     

    Hopefully spin-up/down sorted:

    • External code (docker containers) using 'smartctl -n standby' should work ok with SATA drives.  This will remain problematic for SAS until/unless smartmontools v7.2 is released with support for '-n standby' with SAS.
    • SMART is unconditionally enabled on devices upon boot.  This solves problem where some newly installed devices may not have SMART enabled.
    • Unassigned devices will get spun-down according to 'Settings/Disk Settings/Default spin down delay'.

     

    Updated to 5.10 Linux kernel (5.10.1).

     

    Updated docker.

     

    Fixed bug joining AD domains.

     


     

    Version 6.9.0-rc2 2020-12-18 (vs -rc1)

    Base distro:

    • bind: verison 9.16.8
    • docker: version 19.03.14
    • krb5: version 1.18.2

    Linux kernel:

    • version 5.10.1

    Management:

    • emhttpd: fix external 'smartctl -n standby' causing device spinup
    • emhttpd: enable SMART on devices upon startup
    • emhttpd: unassigned devices spin-down according to global default
    • emhttpd: restore 'poll_attributes' event callout
    • smb: fixed AD join issue
    • webgui: do not try to display SMART info that causes spin-up for devices that are spun-down
    • webgui: avoid php syntax error if autov() source file does not exist

    Edited by limetech

    • Like 8
    • Thanks 4


    User Feedback

    Recommended Comments



    Sounds like UD didnt detect removal, have you tried connecting and then removing again.

     

    If still show maybe worth posting on UD support page if you havent already

    Link to comment
    Share on other sites
    13 hours ago, Ver7o said:

    I unmounted the drive yesterday, however, to my surprise, syslog is still filing with "emhttpd: spinning down /dev/sde" every 15min.

     

    Your diagnostics would reveal what's going on. Perhaps you're mistaking /dev/sde for some other device.

     

    Link to comment
    Share on other sites

    Can anyone please point to an article that explains what spin down/spin up array button does? I only used it to see my HDD temperatures, but I have no ideea how this affects my array. If i press "Spin down" my temp disappears. Is that normal?

    Link to comment
    Share on other sites
    1 hour ago, Johnster said:

    Can anyone please point to an article that explains what spin down/spin up array button does? I only used it to see my HDD temperatures, but I have no ideea how this affects my array. If i press "Spin down" my temp disappears. Is that normal?

    It just puts the drives into a low powered sleep mode, which stops the spindle motor - hence the spin down. Any activity directed towards the drive wakes them up and starts the spindle spinning once again - hence the spin up. It's normal for the temperature to not be displayed, as the drives are effectively turned off.

    Link to comment
    Share on other sites
    On 1/17/2021 at 10:06 AM, Gnomuz said:

    Well, it's been the normal behavior of the Nvidia drivers for a while. A "power limit" is enforced for the card by the vbios and drivers, and when the power drawn approaches this limit, the clocks are throttled.

    If you want to see what the power limits are and to which extent you can adjust them, you just have a look at the output of 'nvidia-smi -q'

    Mine looks like that on a P2000 (which is only powered by the PCIE slot, thus the 75W min & max) :

    
        Power Readings
            Power Management                  : Supported
            Power Draw                        : 65.82 W
            Power Limit                       : 75.00 W
            Default Power Limit               : 75.00 W
            Enforced Power Limit              : 75.00 W
            Min Power Limit                   : 75.00 W
            Max Power Limit                   : 75.00 W

    On this one, no adjustment is possible, as Min and Max Power Limits are the same. And it's almost constantly throttled due to the power cap when folding.

     

    Same output for a RTX 3060 Ti on another rig:

     

    
    [...]
    Clocks Throttle Reasons
            Idle                              : Not Active
            Applications Clocks Setting       : Not Active
            SW Power Cap                      : Active
            HW Slowdown                       : Not Active
                HW Thermal Slowdown           : Not Active
                HW Power Brake Slowdown       : Not Active
            Sync Boost                        : Not Active
            SW Thermal Slowdown               : Not Active
            Display Clock Setting             : Not Active
     [...]
        Power Readings
            Power Management                  : Supported
            Power Draw                        : 194.23 W
            Power Limit                       : 200.00 W
            Default Power Limit               : 200.00 W
            Enforced Power Limit              : 200.00 W
            Min Power Limit                   : 100.00 W
            Max Power Limit                   : 220.00 W
    [...]

    For this one, you can see it is throttled because 194W are drawn out of a 200W limit. But this power limit can be adjusted between 100W and 220W through the command 'nvidia-smi -pl XXX', where XXX is the desired limit in watts.

    That's the way it works, and it makes overclocking/undevolting more complicated. The way to go for efficient folding is to lower the default power limit, while overclocking the GPU (-> same perf with less power) . But it's impossible afaik on an Unraid server, as you need an X-server to launch the required 'nvidia-settings' overclocking utility ...

     

    To summarize, nothing worrying in what you see, and not much to do. The only thing you can try under Unraid is raise the power limit to the max and see if you get better results for your folding. From my personal experience, minimal impact on performance, and a bit more power drawn 😞

    Thank you for your clarification. I have been looking around as well for overclock commands, but haven't been successful and your post confirms my doubts.

    I was wondering if you've been able to find something else?

    The nvidia-smi adjust clock settings only seem to apply to tesla gpus

    I hope settings like these will be added in the future.

    Link to comment
    Share on other sites
    13 hours ago, Rolucious said:

    Thank you for your clarification. I have been looking around as well for overclock commands, but haven't been successful and your post confirms my doubts.

    I was wondering if you've been able to find something else?

    The nvidia-smi adjust clock settings only seem to apply to tesla gpus

    I hope settings like these will be added in the future.

    Nothing new here, under Unraid, I haven't found any way to adjust clock settings with nvidia-settings, as this utility requires at least a "minimal" Xserver, whatever it may mean (my technical skills reach their poor limits).
    I have been able though to overclock an RTX3060ti with nvidia-settings CLI commands under Ubuntu on another rig, but still with a graphic environment like gnome.

    Perhaps a more skilled member of the community could try and identify which minimal setup / add-ons would be required for Unraid to let us use a utility like nvidia-settings, which for the moment is installed by the official nvidia drivers plugin, but is totally nonoperational.

    And I do agree that would be a nice-to-have feature in a near future, which would definitely provide the community with a major step forward compared with former unofficial integrations of the nvidia drivers.

    Link to comment
    Share on other sites
    On 1/16/2021 at 1:10 AM, paulmorabi said:

    I'm having random system freezes always every few days. The first time this occurred I was away from home so was unable to physically access the box for a few days. When I did return home and reboot, I found my VM settings were completely wiped. I thought to restore to RC1 backup but then only discovered that the backup doesn't backup VM settings. In any case, restored and then recreated the VM and upgraded again to RC2. System freezing returns.

     

    I can't get anything useful from the logs but have attached diagnostics. I am going to shut down my VM when not in use as a precautionary measure in case the gpu or usb passthrough is causing the instability.

     

    Prior to RC2, I have been using Unraid 6.90 betas (am a new user since September 2020) and only had the very rare occasional issue so definitely seems like something in the latest release. I'll advise again after a few days if shutting down the VM improves stability.

    fatboy-diagnostics-20210116-1001.zip 76.98 kB · 7 downloads

     

    Is it possible anyone can take a look at the updated diagnostics I've attached? This is causing me real issues as Unraid is crashing every 48-72 hours. In addition to the diagnostics:

     

    * The RX560 card I am passing through is being passed with the BIOS file dumped from it. I'm having no issues at all with the reset bug.

    * I'm also now passing through separate wifi and USB cards. I thought this would reduce the crashes as I suspected it was related to passing the mainboard's usb bus but it's not helped at all. In any case, both of the cards are not affected also by pass through or reset issues. 

    * I can stop and start the VM without any reset or passthrough issues. Since getting separate cards for usb and wifi, I've noticed that rather than freezing, Unraid crashes and reboots.

    * There are no other temperature issues. Everything is running within the default temperature thresholds.

    * When I am not running the VM, Unraid doesn't crash.

    * The crashes don't occur when I am using the VM so it doesn't seem related to any user activity.

    * RC1 and previous releases of 6.9 never exhibited this issue. I had an occasional crash but it was 12 over several months (if that).

    fatboy-diagnostics-20210215-1716.zip

    Link to comment
    Share on other sites
    19 minutes ago, paulmorabi said:

    This is causing me real issues as Unraid is crashing every 48-72 hours. In addition to the diagnostics:

    First thing to check would be a memtest from the boot menu (and then also seeing if there's a difference in behaviour if you turn off XMP / AMP speeds on the memory)

    Link to comment
    Share on other sites
    36 minutes ago, paulmorabi said:

    Is it possible anyone can take a look at the updated diagnostics I've attached?

    The syslog that is contained in your Diagnostics file appears to be after a reboot when the system is not 'acting' up.  Might I suggest that you setup the syslog server and see if that will catch something at the actual time of failure.  The instructions are here:

     

        https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-781601

     

    Link to comment
    Share on other sites
    10 hours ago, Gnomuz said:

    Nothing new here, under Unraid, I haven't found any way to adjust clock settings with nvidia-settings, as this utility requires at least a "minimal" Xserver, whatever it may mean (my technical skills reach their poor limits).
    I have been able though to overclock an RTX3060ti with nvidia-settings CLI commands under Ubuntu on another rig, but still with a graphic environment like gnome.

    Perhaps a more skilled member of the community could try and identify which minimal setup / add-ons would be required for Unraid to let us use a utility like nvidia-settings, which for the moment is installed by the official nvidia drivers plugin, but is totally nonoperational.

    And I do agree that would be a nice-to-have feature in a near future, which would definitely provide the community with a major step forward compared with former unofficial integrations of the nvidia drivers.

    Tried booting in GUI mode ?

    Link to comment
    Share on other sites

    TL;DR Updated to rc2 and can no longer access gui after starting parity check

     

    Thank you, John_M. Moved to:
     

     

     

    Edited by greyday
    Link to comment
    Share on other sites
    1 hour ago, greyday said:

    I was able to do a diagnostics dump, is there anything I should delete before posting the log?

     

    I suggest you start a new thread in the General Help section and include your diagnostics zip file exactly as you retrieved it. It is anonymised by default. You're likely to have problems specific to your setup and you can get help in a separate thread without the noise of all the other conversations going on here.

    • Like 1
    Link to comment
    Share on other sites
    31 minutes ago, John_M said:

     

    I suggest you start a new thread in the General Help section and include your diagnostics zip file exactly as you retrieved it. It is anonymised by default. You're likely to have problems specific to your setup and you can get help in a separate thread without the noise of all the other conversations going on here.

    Cheers, done (link pasted above)

    Link to comment
    Share on other sites

    I hava a Bug in the Network Configuration.
    in eth0 if i set

    IPv4 address assignment: Autonatic

    IPv4 DNS server assignment: Static

    IPv4 DNS server: 1.1.1.1

     

    and Apply

     

    in the network.conf File the changing appears

    in the UI i got:

    IPv4 address assignment: Autonatic

    IPv4 DNS server assignment: Autonatic

    IPv4 DNS server: 

     

    when i now change anything else in eth0 and Apply i now loose the configuration of the static DNS Server 1.1.1.1

    Link to comment
    Share on other sites

    I think there's a bug in the drive temperature monitor thresholds - I am unable to set individual warning or critical temps for drives in my array or the cache. When I click apply, they simply go back to the global setting. This happens with my array both started and stopped, and following a fresh reboot. 

     

    Changing the temps through the global setting does persist. 

    Link to comment
    Share on other sites

    Got the following message in syslog on RC2.  second time I've seen it and I don't notice anything wrong with my server, but thought I would post to see if someone knows something about it.  Looks like something related to the macvlan process maybe?

     

    Feb 19 13:23:57 teraserver kernel: ------------[ cut here ]------------
    Feb 19 13:23:57 teraserver kernel: WARNING: CPU: 13 PID: 23974 at net/netfilter/nf_conntrack_core.c:1120 __nf_conntrack_confirm+0x99/0x1e1
    Feb 19 13:23:57 teraserver kernel: Modules linked in: vhost_net tun vhost vhost_iotlb tap kvm_intel kvm xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables md_mod dm_crypt dm_mod dax veth macvlan xt_nat xt_MASQUERADE iptable_filter iptable_nat nf_nat ip_tables xfs nfsd lockd grace sunrpc nvidia_drm(PO) nvidia_modeset(PO) drm_kms_helper drm backlight agpgart syscopyarea nvidia_uvm(PO) sysfillrect sysimgblt fb_sys_fops nvidia(PO) nct6775 hwmon_vid r8169 realtek tg3 x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd mxm_wmi mpt3sas glue_helper rapl i2c_i801 intel_cstate raid_class i2c_smbus intel_uncore i2c_core input_leds ahci led_class scsi_transport_sas wmi libahci button [last unloaded: kvm]
    Feb 19 13:23:57 teraserver kernel: CPU: 13 PID: 23974 Comm: kworker/13:1 Tainted: P        W  O      5.10.1-Unraid #1
    Feb 19 13:23:57 teraserver kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X79 Extreme4-M, BIOS P3.40 03/10/2018
    Feb 19 13:23:57 teraserver kernel: Workqueue: events macvlan_process_broadcast [macvlan]
    Feb 19 13:23:57 teraserver kernel: RIP: 0010:__nf_conntrack_confirm+0x99/0x1e1
    Feb 19 13:23:57 teraserver kernel: Code: e4 e3 ff ff 8b 54 24 14 89 c6 41 89 c4 48 c1 eb 20 89 df 41 89 de e8 54 e1 ff ff 84 c0 75 b8 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 89 df 44 89 e6 31 db e8 89 de ff ff e8 af e0 ff ff e9 1f 01
    Feb 19 13:23:57 teraserver kernel: RSP: 0018:ffffc9000043cd38 EFLAGS: 00010202
    Feb 19 13:23:57 teraserver kernel: RAX: 0000000000000188 RBX: 0000000000000478 RCX: 000000007f7d0276
    Feb 19 13:23:57 teraserver kernel: RDX: 0000000000000000 RSI: 00000000000000f0 RDI: ffffffff82009c00
    Feb 19 13:23:57 teraserver kernel: RBP: ffff888271c808c0 R08: 00000000fa10a875 R09: ffff8881a92aeaa0
    Feb 19 13:23:57 teraserver kernel: R10: 0000000000000158 R11: ffff888125843200 R12: 00000000000000f0
    Feb 19 13:23:57 teraserver kernel: R13: ffffffff8210da40 R14: 0000000000000478 R15: ffff888271c808cc
    Feb 19 13:23:57 teraserver kernel: FS:  0000000000000000(0000) GS:ffff888627b40000(0000) knlGS:0000000000000000
    Feb 19 13:23:57 teraserver kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Feb 19 13:23:57 teraserver kernel: CR2: 00003c2889e6a008 CR3: 000000000200c001 CR4: 00000000001706e0
    Feb 19 13:23:57 teraserver kernel: Call Trace:
    Feb 19 13:23:57 teraserver kernel: <IRQ>
    Feb 19 13:23:57 teraserver kernel: nf_conntrack_confirm+0x2f/0x36
    Feb 19 13:23:57 teraserver kernel: nf_hook_slow+0x39/0x8e
    Feb 19 13:23:57 teraserver kernel: nf_hook.constprop.0+0xb1/0xd8
    Feb 19 13:23:57 teraserver kernel: ? ip_protocol_deliver_rcu+0xfe/0xfe
    Feb 19 13:23:57 teraserver kernel: ip_local_deliver+0x49/0x75
    Feb 19 13:23:57 teraserver kernel: ip_sabotage_in+0x43/0x4d
    Feb 19 13:23:57 teraserver kernel: nf_hook_slow+0x39/0x8e
    Feb 19 13:23:57 teraserver kernel: nf_hook.constprop.0+0xb1/0xd8
    Feb 19 13:23:57 teraserver kernel: ? l3mdev_l3_rcv.constprop.0+0x50/0x50
    Feb 19 13:23:57 teraserver kernel: ip_rcv+0x41/0x61
    Feb 19 13:23:57 teraserver kernel: __netif_receive_skb_one_core+0x74/0x95
    Feb 19 13:23:57 teraserver kernel: process_backlog+0xa3/0x13b
    Feb 19 13:23:57 teraserver kernel: net_rx_action+0xf4/0x29d
    Feb 19 13:23:57 teraserver kernel: __do_softirq+0xc4/0x1c2
    Feb 19 13:23:57 teraserver kernel: asm_call_irq_on_stack+0x12/0x20
    Feb 19 13:23:57 teraserver kernel: </IRQ>
    Feb 19 13:23:57 teraserver kernel: do_softirq_own_stack+0x2c/0x39
    Feb 19 13:23:57 teraserver kernel: do_softirq+0x3a/0x44
    Feb 19 13:23:57 teraserver kernel: netif_rx_ni+0x1c/0x22
    Feb 19 13:23:57 teraserver kernel: macvlan_broadcast+0x10e/0x13c [macvlan]
    Feb 19 13:23:57 teraserver kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan]
    Feb 19 13:23:57 teraserver kernel: process_one_work+0x13c/0x1d5
    Feb 19 13:23:57 teraserver kernel: worker_thread+0x18b/0x22f
    Feb 19 13:23:57 teraserver kernel: ? process_scheduled_works+0x27/0x27
    Feb 19 13:23:57 teraserver kernel: kthread+0xe5/0xea
    Feb 19 13:23:57 teraserver kernel: ? kthread_unpark+0x52/0x52
    Feb 19 13:23:57 teraserver kernel: ret_from_fork+0x22/0x30
    Feb 19 13:23:57 teraserver kernel: ---[ end trace 388b86a70436712d ]---

     

    Link to comment
    Share on other sites

    Following up.  I ended up having a hard crash of my Unraid server a couple hours later after that message.  This time, I got the following message in syslog when it crashed.  Crashed, as in, dropped network connectivity, refused connections to any container, and no input on the physical console.

     

    Hoping this is right forum to be posting this.  Diagnostics attached.

     

     

    
    
    
    
    HARD CRASH
    
    
    
    Feb 19 15:00:02 teraserver rpcbind[3654]: connect from 192.168.4.7 to getport/addr(555555555)
    Feb 19 15:02:16 teraserver rpcbind[11177]: connect from 192.168.4.7 to getport/addr(555555555)
    Feb 19 15:07:33 teraserver ool www[22782]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/var/lib/docker' '-r'
    Feb 19 15:07:33 teraserver kernel: BTRFS info (device loop2): scrub: started on devid 1
    Feb 19 15:07:57 teraserver kernel: BTRFS info (device loop2): scrub: finished on devid 1 with status: 0
    Feb 19 15:08:05 teraserver kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
    Feb 19 15:08:32 teraserver emhttpd: shcmd (235): /usr/local/sbin/mover &> /dev/null &
    Feb 19 15:13:06 teraserver kernel: general protection fault, probably for non-canonical address 0x315a4c61f4cef4d8: 0000 [#1] SMP PTI
    Feb 19 15:13:06 teraserver kernel: CPU: 15 PID: 0 Comm: swapper/15 Tainted: P        W  O      5.10.1-Unraid #1
    Feb 19 15:13:06 teraserver kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X79 Extreme4-M, BIOS P3.40 03/10/2018
    Feb 19 15:13:06 teraserver kernel: RIP: 0010:nf_conntrack_udp_packet+0x119/0x219
    Feb 19 15:13:06 teraserver kernel: Code: 81 48 8b 73 20 49 c7 c0 9b 6d dc 81 b9 11 00 00 00 e8 f0 9f 11 00 83 c8 ff e9 ea 00 00 00 48 8b 85 b8 00 00 00 48 85 c0 74 1b <0f> b6 50 06 84 d2 74 13 48 01 d0 74 0e 48 8b 00 48 85 c0 74 06 48
    Feb 19 15:13:06 teraserver kernel: RSP: 0018:ffffc90000494b70 EFLAGS: 00010206
    Feb 19 15:13:06 teraserver kernel: RAX: 315a4c61f4cef4d8 RBX: ffffc90000494c68 RCX: 0000000000000011
    Feb 19 15:13:06 teraserver kernel: RDX: 0000000000000014 RSI: 0000000000000000 RDI: ffff888596154200
    Feb 19 15:13:06 teraserver kernel: RBP: ffff888115eae3c0 R08: ffff88819c1a47d0 R09: ffff888115eae3c0
    Feb 19 15:13:06 teraserver kernel: R10: ffffffff8210da40 R11: ffff888115eae3c0 R12: 0000000000000002
    Feb 19 15:13:06 teraserver kernel: R13: 00000000000000b0 R14: 0000000000000014 R15: ffff888115eae3c0
    Feb 19 15:13:06 teraserver kernel: FS:  0000000000000000(0000) GS:ffff888627bc0000(0000) knlGS:0000000000000000
    Feb 19 15:13:06 teraserver kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Feb 19 15:13:06 teraserver kernel: CR2: 000014e0b6b8fbd0 CR3: 000000000200c002 CR4: 00000000001706e0
    Feb 19 15:13:06 teraserver kernel: Call Trace:
    Feb 19 15:13:06 teraserver kernel: <IRQ>
    Feb 19 15:13:06 teraserver kernel: nf_conntrack_in+0x2bc/0x3b7
    Feb 19 15:13:06 teraserver kernel: ? br_handle_frame_finish+0x351/0x351
    Feb 19 15:13:06 teraserver kernel: nf_hook_slow+0x39/0x8e
    Feb 19 15:13:06 teraserver kernel: ? br_nf_forward_finish+0xd0/0xd0
    Feb 19 15:13:06 teraserver kernel: NF_HOOK+0xb7/0xf7
    Feb 19 15:13:06 teraserver kernel: ? br_nf_forward_finish+0xd0/0xd0
    Feb 19 15:13:06 teraserver kernel: br_nf_pre_routing+0x229/0x239
    Feb 19 15:13:06 teraserver kernel: ? br_nf_forward_finish+0xd0/0xd0
    Feb 19 15:13:06 teraserver kernel: br_handle_frame+0x25e/0x2a6
    Feb 19 15:13:06 teraserver kernel: ? br_pass_frame_up+0xda/0xda
    Feb 19 15:13:06 teraserver kernel: __netif_receive_skb_core+0x335/0x4e7
    Feb 19 15:13:06 teraserver kernel: ? inet_gro_receive+0x252/0x264
    Feb 19 15:13:06 teraserver kernel: __netif_receive_skb_list_core+0x78/0x104
    Feb 19 15:13:06 teraserver kernel: netif_receive_skb_list_internal+0x1bf/0x1f2
    Feb 19 15:13:06 teraserver kernel: gro_normal_list+0x1d/0x39
    Feb 19 15:13:06 teraserver kernel: napi_complete_done+0x79/0x104
    Feb 19 15:13:06 teraserver kernel: tg3_poll_msix+0xb3/0x124 [tg3]
    Feb 19 15:13:06 teraserver kernel: net_rx_action+0xf4/0x29d
    Feb 19 15:13:06 teraserver kernel: __do_softirq+0xc4/0x1c2
    Feb 19 15:13:06 teraserver kernel: asm_call_irq_on_stack+0x12/0x20
    Feb 19 15:13:06 teraserver kernel: </IRQ>
    Feb 19 15:13:06 teraserver kernel: do_softirq_own_stack+0x2c/0x39
    Feb 19 15:13:06 teraserver kernel: __irq_exit_rcu+0x45/0x80
    Feb 19 15:13:06 teraserver kernel: common_interrupt+0x119/0x12e
    Feb 19 15:13:06 teraserver kernel: asm_common_interrupt+0x1e/0x40
    Feb 19 15:13:06 teraserver kernel: RIP: 0010:arch_local_irq_enable+0x7/0x8
    Feb 19 15:13:06 teraserver kernel: Code: 00 48 83 c4 28 4c 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 9c 58 0f 1f 44 00 00 c3 fa 66 0f 1f 44 00 00 c3 fb 66 0f 1f 44 00 00 <c3> 55 8b af 28 04 00 00 b8 01 00 00 00 45 31 c9 53 45 31 d2 39 c5
    Feb 19 15:13:06 teraserver kernel: RSP: 0018:ffffc900000e7ea0 EFLAGS: 00000246
    Feb 19 15:13:06 teraserver kernel: RAX: ffff888627be2300 RBX: 0000000000000004 RCX: 000000000000001f
    Feb 19 15:13:06 teraserver kernel: RDX: 0000000000000000 RSI: 000000002f6898f3 RDI: 0000000000000000
    Feb 19 15:13:06 teraserver kernel: RBP: ffffe8fffefc8200 R08: 0000032cd47e275f R09: 0000000000000000
    Feb 19 15:13:06 teraserver kernel: R10: 0000000000002bd2 R11: 071c71c71c71c71c R12: 0000032cd47e275f
    Feb 19 15:13:06 teraserver kernel: R13: ffffffff820c7e80 R14: 0000000000000004 R15: 0000000000000000
    Feb 19 15:13:06 teraserver kernel: cpuidle_enter_state+0x101/0x1c4
    Feb 19 15:13:06 teraserver kernel: cpuidle_enter+0x25/0x31
    Feb 19 15:13:06 teraserver kernel: do_idle+0x1a1/0x20f
    Feb 19 15:13:06 teraserver kernel: cpu_startup_entry+0x18/0x1a
    Feb 19 15:13:06 teraserver kernel: secondary_startup_64_no_verify+0xb0/0xbb
    Feb 19 15:13:06 teraserver kernel: Modules linked in: veth xt_nat xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost vhost_iotlb tap macvlan xt_MASQUERADE iptable_filter iptable_nat nf_nat ip_tables xfs nfsd lockd grace sunrpc md_mod nvidia_drm(PO) nvidia_modeset(PO) drm_kms_helper drm backlight agpgart syscopyarea sysfillrect nvidia_uvm(PO) sysimgblt fb_sys_fops nvidia(PO) nct6775 hwmon_vid r8169 realtek tg3 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd mxm_wmi cryptd glue_helper rapl i2c_i801 mpt3sas intel_cstate i2c_smbus i2c_core raid_class intel_uncore ahci wmi scsi_transport_sas libahci button [last unloaded: realtek]
    Feb 19 15:13:06 teraserver kernel: ---[ end trace 53855679afd353bd ]---
    Feb 19 15:13:06 teraserver kernel: RIP: 0010:nf_conntrack_udp_packet+0x119/0x219
    Feb 19 15:13:06 teraserver kernel: Code: 81 48 8b 73 20 49 c7 c0 9b 6d dc 81 b9 11 00 00 00 e8 f0 9f 11 00 83 c8 ff e9 ea 00 00 00 48 8b 85 b8 00 00 00 48 85 c0 74 1b <0f> b6 50 06 84 d2 74 13 48 01 d0 74 0e 48 8b 00 48 85 c0 74 06 48
    Feb 19 15:13:06 teraserver kernel: RSP: 0018:ffffc90000494b70 EFLAGS: 00010206
    Feb 19 15:13:06 teraserver kernel: RAX: 315a4c61f4cef4d8 RBX: ffffc90000494c68 RCX: 0000000000000011
    Feb 19 15:13:06 teraserver kernel: RDX: 0000000000000014 RSI: 0000000000000000 RDI: ffff888596154200
    Feb 19 15:13:06 teraserver kernel: RBP: ffff888115eae3c0 R08: ffff88819c1a47d0 R09: ffff888115eae3c0
    Feb 19 15:13:06 teraserver kernel: R10: ffffffff8210da40 R11: ffff888115eae3c0 R12: 0000000000000002
    Feb 19 15:13:06 teraserver kernel: R13: 00000000000000b0 R14: 0000000000000014 R15: ffff888115eae3c0
    Feb 19 15:13:06 teraserver kernel: FS:  0000000000000000(0000) GS:ffff888627bc0000(0000) knlGS:0000000000000000
    

     

    teraserver-diagnostics-20210220-0829.zip

    Link to comment
    Share on other sites



    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.