• Kernel Panics

    Abbell

    By Abbell

      • Urgent

    I have been getting kernel panics fairly often and it has caused me to lose 5TB of data as it caused my drives to lose stability while performing rebuilds.

    image.thumb.png.61c90b4e8c8cea018d8d41ea7c671117.png

     

    I have set the syslog so I can see what is happening before such failures.

    So I am watching the logs as diligently as I can. Rebuilds take more than a day and fails have already forced me to lose an entire drive. 

    un 19 15:10:14 Tower kernel: CPU: 36 PID: 0 Comm: swapper/36 Tainted: P           O      5.15.46-Unraid #1
Jun 19 15:10:14 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. TRX40 AORUS MASTER/TRX40 AORUS MASTER, BIOS F5q 04/12/2021
Jun 19 15:10:14 Tower kernel: RIP: 0010:refcount_warn_saturate+0xa7/0xe8
Jun 19 15:10:14 Tower kernel: Code: 05 f1 5a fb 00 01 e8 d8 66 42 00 0f 0b c3 80 3d e1 5a fb 00 00 75 53 48 c7 c7 fa a6 0f 82 c6 05 d1 5a fb 00 01 e8 b9 66 42 00 <0f> 0b c3 80 3d c1 5a fb 00 00 75 34 48 c7 c7 22 a7 0f 82 c6 05 b1
Jun 19 15:10:14 Tower kernel: RSP: 0018:ffffc90000d28eb0 EFLAGS: 00010282
Jun 19 15:10:14 Tower kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027
Jun 19 15:10:14 Tower kernel: RDX: 0000000000000003 RSI: ffffc90000d28d38 RDI: ffff889ffd91c510
Jun 19 15:10:14 Tower kernel: RBP: ffff888137cacc40 R08: ffff88a07f0da6a8 R09: ffffffff8284e288
Jun 19 15:10:14 Tower kernel: R10: 00000fffffffffff R11: 000000002d2d2d2d R12: 0000000000000000
Jun 19 15:10:14 Tower kernel: R13: 0000000000000006 R14: ffff888137cad5e0 R15: ffff888100ab9e80
Jun 19 15:10:14 Tower kernel: FS:  0000000000000000(0000) GS:ffff889ffd900000(0000) knlGS:0000000000000000
Jun 19 15:10:14 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 19 15:10:14 Tower kernel: CR2: 00000000005c3958 CR3: 000000000620a000 CR4: 0000000000350ee0
Jun 19 15:10:14 Tower kernel: Call Trace:
Jun 19 15:10:14 Tower kernel: <IRQ>
Jun 19 15:10:14 Tower kernel: refcount_dec_and_test+0x24/0x2a
Jun 19 15:10:14 Tower kernel: __put_task_struct+0x98/0xaf
Jun 19 15:10:14 Tower kernel: rcu_do_batch+0x216/0x40a
Jun 19 15:10:14 Tower kernel: rcu_core+0x1c2/0x1f3
Jun 19 15:10:14 Tower kernel: ? timekeeping_get_ns+0x1c/0x32
Jun 19 15:10:14 Tower kernel: __do_softirq+0xef/0x218
Jun 19 15:10:14 Tower kernel: __irq_exit_rcu+0x4d/0x88
Jun 19 15:10:14 Tower kernel: sysvec_apic_timer_interrupt+0x66/0x7d
Jun 19 15:10:14 Tower kernel: </IRQ>
Jun 19 15:10:14 Tower kernel: <TASK>
Jun 19 15:10:14 Tower kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20
Jun 19 15:10:14 Tower kernel: RIP: 0010:arch_local_irq_enable+0x7/0x8
Jun 19 15:10:14 Tower kernel: Code: a2 bc 1c 00 85 db 48 89 e8 79 03 48 63 c3 5b 5d 41 5c 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> 0f 1f 44 00 00 55 49 89 d3 48 81 c7 b0 00 00 00 48 83 c6 70 53
Jun 19 15:10:14 Tower kernel: RSP: 0018:ffffc9000041fea0 EFLAGS: 00000246
Jun 19 15:10:14 Tower kernel: RAX: ffff889ffd92bb40 RBX: 0000000000000001 RCX: 000000000000001f
Jun 19 15:10:14 Tower kernel: RDX: 0000000000000024 RSI: 0000000000000024 RDI: 0000000000000000
Jun 19 15:10:14 Tower kernel: RBP: ffff88810b2d0c00 R08: 00000000ffffffff R09: 071c71c71c71c71c
Jun 19 15:10:14 Tower kernel: R10: 0000000000000020 R11: 0000000000000021 R12: ffffffff82314da0
Jun 19 15:10:14 Tower kernel: R13: 0000000000000001 R14: 0000173a0ba852f5 R15: 0000000000000000
Jun 19 15:10:14 Tower kernel: cpuidle_enter_state+0x117/0x1db
Jun 19 15:10:14 Tower kernel: cpuidle_enter+0x2a/0x36
Jun 19 15:10:14 Tower kernel: do_idle+0x1b7/0x225
Jun 19 15:10:14 Tower kernel: cpu_startup_entry+0x1d/0x1f
Jun 19 15:10:14 Tower kernel: secondary_startup_64_no_verify+0xb0/0xbb
Jun 19 15:10:14 Tower kernel: </TASK>

    This has caused me no small amount of anxiety. I have to have a stable system.
     

    tower-diagnostics-20220619-1612.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    Abbell

    un 19 22:41:59 Tower kernel: general protection fault, probably for non-canonical address 0xd23d8b6528eb907e: 0000 [#1] SMP NOPTI
    Jun 19 22:41:59 Tower kernel: CPU: 18 PID: 81212 Comm: shfs Tainted: P           O      5.15.46-Unraid #1
    Jun 19 22:41:59 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. TRX40 AORUS MASTER/TRX40 AORUS MASTER, BIOS F5q 04/12/2021
    Jun 19 22:41:59 Tower kernel: RIP: 0010:udp4_lib_lookup2.isra.0+0x50/0x17c
    Jun 19 22:41:59 Tower kernel: Code: 84 42 01 00 00 89 f3 0f b7 74 24 0c 48 89 fd 41 89 cc 4c 8d 70 e8 45 89 c5 31 d2 31 c0 89 74 24 08 4d 85 f6 0f 84 1d 01 00 00 <49> 3b 6e 30 0f 85 01 01 00 00 66 45 3b 6e 08 0f 85 f6 00 00 00 41
    Jun 19 22:41:59 Tower kernel: RSP: 0018:ffffc90000a10e90 EFLAGS: 00010286
    Jun 19 22:41:59 Tower kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
    Jun 19 22:41:59 Tower kernel: RDX: 0000000000000000 RSI: 000000000000c740 RDI: ffff88834c008458
    Jun 19 22:41:59 Tower kernel: RBP: ffff88834c008458 R08: 0000000000000000 R09: 00000000810d2007
    Jun 19 22:41:59 Tower kernel: R10: 0000000000000013 R11: ffffc90000a10ff8 R12: 0000000000000000
    Jun 19 22:41:59 Tower kernel: R13: 0000000000000000 R14: d23d8b6528eb904e R15: ffffffff8173c89d
    Jun 19 22:41:59 Tower kernel: FS:  00001463dcd09640(0000) GS:ffff889ffd480000(0000) knlGS:0000000000000000
    Jun 19 22:41:59 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Jun 19 22:41:59 Tower kernel: CR2: 000014f93ac08690 CR3: 0000000188080000 CR4: 0000000000350ee0
    Jun 19 22:41:59 Tower kernel: Call Trace:
    Jun 19 22:41:59 Tower kernel: <IRQ>
    Jun 19 22:41:59 Tower kernel: ? __udp4_lib_lookup+0x94/0x316
    Jun 19 22:41:59 Tower kernel: ? __udp4_lib_lookup+0x94/0x316
    Jun 19 22:41:59 Tower kernel: __udp4_lib_lookup+0xa7/0x316
    Jun 19 22:41:59 Tower kernel: ? call_timer_fn+0x59/0xde
    Jun 19 22:41:59 Tower kernel: ? __run_timers+0x146/0x184
    Jun 19 22:41:59 Tower kernel: ? enqueue_hrtimer+0x62/0x69
    Jun 19 22:41:59 Tower kernel: ? recalibrate_cpu_khz+0x1/0x1
    Jun 19 22:41:59 Tower kernel: ? run_timer_softirq+0x19/0x2d
    Jun 19 22:41:59 Tower kernel: __do_softirq+0xef/0x218
    Jun 19 22:41:59 Tower kernel: __irq_exit_rcu+0x4d/0x88
    Jun 19 22:41:59 Tower kernel: sysvec_apic_timer_interrupt+0x66/0x7d
    Jun 19 22:41:59 Tower kernel: </IRQ>
    Jun 19 22:41:59 Tower kernel: <TASK>
    Jun 19 22:41:59 Tower kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20
    Jun 19 22:41:59 Tower kernel: RIP: 0010:xfs_dir2_sf_get_parent_ino+0x9/0x1d [xfs]
    Jun 19 22:41:59 Tower kernel: Code: 00 81 e2 00 00 01 00 48 83 fa 01 48 83 d8 ff 80 7e 01 00 74 07 48 0f c9 48 89 08 c3 0f c9 89 08 c3 0f 1f 44 00 00 80 7f 01 00 <75> 08 8b 47 02 0f c8 89 c0 c3 48 8b 47 02 30 c0 48 0f c8 c3 0f 1f
    Jun 19 22:41:59 Tower kernel: RSP: 0018:ffffc90007c57d90 EFLAGS: 00000206
    Jun 19 22:41:59 Tower kernel: RAX: 000000000000000a RBX: ffffc90007c57ee0 RCX: 00001463cc2c1ac8
    Jun 19 22:41:59 Tower kernel: RDX: ffffffffa0b8addc RSI: 0000000000000001 RDI: ffff888173512a00
    Jun 19 22:41:59 Tower kernel: RBP: ffffc90007c57de8 R08: 0000000000e8e024 R09: 00001463cc2c1ac4
    Jun 19 22:41:59 Tower kernel: R10: 0000000000e8e024 R11: 0000000000000000 R12: ffff8881097b9000
    Jun 19 22:41:59 Tower kernel: R13: 0000000000000000 R14: ffff888217b89680 R15: 0000000000000008
    Jun 19 22:41:59 Tower kernel: xfs_dir2_sf_getdents+0xf2/0x25d [xfs]
    Jun 19 22:41:59 Tower kernel: xfs_readdir+0xe8/0x149 [xfs]
    Jun 19 22:41:59 Tower kernel: iterate_dir+0x98/0x146
    Jun 19 22:41:59 Tower kernel: __do_sys_getdents64+0x6b/0xd4
    Jun 19 22:41:59 Tower kernel: ? filldir+0x1a3/0x1a3
    Jun 19 22:41:59 Tower kernel: do_syscall_64+0x83/0xa5
    Jun 19 22:41:59 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae
    Jun 19 22:41:59 Tower kernel: RIP: 0033:0x1463dda385c3
    Jun 19 22:41:59 Tower kernel: Code: ef b8 ca 00 00 00 0f 05 eb b3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 b8 ff ff ff 7f 48 39 c2 48 0f 47 d0 b8 d9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 71 48 10 00 f7 d8
    Jun 19 22:41:59 Tower kernel: RSP: 002b:00001463dcd089e8 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9
    Jun 19 22:41:59 Tower kernel: RAX: ffffffffffffffda RBX: 00001463cc2c1ab0 RCX: 00001463dda385c3
    Jun 19 22:41:59 Tower kernel: RDX: 0000000000008000 RSI: 00001463cc2c1ab0 RDI: 0000000000000018
    Jun 19 22:41:59 Tower kernel: RBP: ffffffffffffff88 R08: 0000000000000030 R09: 00001463cc2c1a80
    Jun 19 22:41:59 Tower kernel: R10: 00001463cc2907c0 R11: 0000000000000293 R12: 00001463cc2c1a84
    Jun 19 22:41:59 Tower kernel: R13: 0000000000000002 R14: 00001463cc2c1a80 R15: 00001463b81170b0
    Jun 19 22:41:59 Tower kernel: </TASK>
    Jun 19 22:41:59 Tower kernel: Modules linked in: xt_mark veth xt_nat macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp nvidia_modeset(PO) nvidia_uvm(PO) ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod nvidia(PO) it87 hwmon_vid efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding atlantic igb r8169 realtek radeon drm_ttm_helper ttm drm_kms_helper btusb btrtl gigabyte_wmi wmi_bmof mxm_wmi edac_mce_amd kvm_amd btbcm btintel kvm drm bluetooth mpt3sas crct10dif_pclmul backlight crc32_pclmul crc32c_intel raid_class ahci ecdh_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl agpgart scsi_transport_sas libahci ecc syscopyarea nvme i2c_algo_bit i2c_piix4 sysfillrect ccp sysimgblt i2c_core nvme_core k10temp fb_sys_fops thermal wmi button acpi_cpufreq [last unloaded: atlantic]
    Jun 19 22:41:59 Tower kernel: ---[ end trace 8f5b0ea12e0fe1e9 ]---
    Jun 19 22:41:59 Tower kernel: RIP: 0010:udp4_lib_lookup2.isra.0+0x50/0x17c
    Jun 19 22:41:59 Tower kernel: Code: 84 42 01 00 00 89 f3 0f b7 74 24 0c 48 89 fd 41 89 cc 4c 8d 70 e8 45 89 c5 31 d2 31 c0 89 74 24 08 4d 85 f6 0f 84 1d 01 00 00 <49> 3b 6e 30 0f 85 01 01 00 00 66 45 3b 6e 08 0f 85 f6 00 00 00 41
    Jun 19 22:41:59 Tower kernel: RSP: 0018:ffffc90000a10e90 EFLAGS: 00010286
    Jun 19 22:41:59 Tower kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
    Jun 19 22:41:59 Tower kernel: RDX: 0000000000000000 RSI: 000000000000c740 RDI: ffff88834c008458
    Jun 19 22:41:59 Tower kernel: RBP: ffff88834c008458 R08: 0000000000000000 R09: 00000000810d2007
    Jun 19 22:41:59 Tower kernel: R10: 0000000000000013 R11: ffffc90000a10ff8 R12: 0000000000000000
    Jun 19 22:41:59 Tower kernel: R13: 0000000000000000 R14: d23d8b6528eb904e R15: ffffffff8173c89d
    Jun 19 22:41:59 Tower kernel: FS:  00001463dcd09640(0000) GS:ffff889ffd480000(0000) knlGS:0000000000000000
    Jun 19 22:41:59 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Jun 19 22:41:59 Tower kernel: CR2: 000014f93ac08690 CR3: 0000000188080000 CR4: 0000000000350ee0
    Crashed again

    Edited by Abbell
    Link to comment
    JorgeB

    RAM is running @ 3600MT/s, with your config it should be set @ 2667MT/s, overclocked RAM is known to cause salability issues and even data corruption with some AMD servers, more info here.

    Link to comment
    Abbell

    As much as it will pain me, I will adjust the memory speed.

    Are you able to supply the original website for the compatibility settings?

    Edited by Abbell
    Link to comment
    Abbell

    I ordered replacement memory just to be on the safe side. I also confirmed motherboard compatibility with it.
    CORSAIR Vengeance LPX 256GB (8 x 32GB) 288-Pin PC RAM DDR4 2666 (PC4 21300) Desktop Memory Model CMK256GX4M8A2666C16

    Link to comment
    Abbell

    OK.. I lied. But it did not cause a fail at least

    Jun 25 23:52:39 Tower kernel: CPU: 47 PID: 113786 Comm: kworker/47:2 Tainted: P        W  O      5.15.46-Unraid #1
    Jun 25 23:52:39 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. TRX40 AORUS MASTER/TRX40 AORUS MASTER, BIOS F5q 04/12/2021
    Jun 25 23:52:39 Tower kernel: Workqueue: events macvlan_process_broadcast [macvlan]
    Jun 25 23:52:39 Tower kernel: RIP: 0010:nf_nat_setup_info+0x6f/0x773 [nf_nat]
    Jun 25 23:52:39 Tower kernel: Code: 89 fb 49 89 f5 41 89 d4 76 02 0f 0b 48 8b 93 80 00 00 00 89 d0 25 00 01 00 00 45 85 e4 75 07 89 d0 25 80 00 00 00 85 c0 74 07 <0f> 0b e9 32 06 00 00 48 8b 83 90 00 00 00 4c 8d 7c 24 28 48 8d 73
    Jun 25 23:52:39 Tower kernel: RSP: 0018:ffffc90000f0cbe0 EFLAGS: 00010202
    Jun 25 23:52:39 Tower kernel: RAX: 0000000000000080 RBX: ffff88812674d2c0 RCX: ffff8881e8149380
    Jun 25 23:52:39 Tower kernel: RDX: 0000000000000180 RSI: ffffc90000f0cccc RDI: ffff88812674d2c0
    Jun 25 23:52:39 Tower kernel: RBP: ffffc90000f0ccb0 R08: 00000000ef01a8c0 R09: 0000000000000000
    Jun 25 23:52:39 Tower kernel: R10: 0000000000000158 R11: 0000000000000000 R12: 0000000000000000
    Jun 25 23:52:39 Tower kernel: R13: ffffc90000f0cccc R14: 0000000000000000 R15: 0000000000000001
    Jun 25 23:52:39 Tower kernel: FS:  0000000000000000(0000) GS:ffff88bf7dbc0000(0000) knlGS:0000000000000000
    Jun 25 23:52:39 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Jun 25 23:52:39 Tower kernel: CR2: 0000153a03afe690 CR3: 00000001d66d4000 CR4: 0000000000350ee0
    Jun 25 23:52:39 Tower kernel: Call Trace:
    Jun 25 23:52:39 Tower kernel: <IRQ>
    Jun 25 23:52:39 Tower kernel: ? pollwake+0x5b/0x75
    Jun 25 23:52:39 Tower kernel: ? wake_up_q+0x3e/0x3e
    Jun 25 23:52:39 Tower kernel: ? ipt_do_table+0x563/0x5b0 [ip_tables]
    Jun 25 23:52:39 Tower kernel: ? __wake_up_common_lock+0x8a/0xb4
    Jun 25 23:52:39 Tower kernel: __nf_nat_alloc_null_binding+0x68/0x7f [nf_nat]
    Jun 25 23:52:39 Tower kernel: nf_nat_inet_fn+0xa6/0x187 [nf_nat]
    Jun 25 23:52:39 Tower kernel: nf_nat_ipv4_local_in+0x2a/0xae [nf_nat]
    Jun 25 23:52:39 Tower kernel: nf_hook_slow+0x3e/0x93
    Jun 25 23:52:39 Tower kernel: ? ip_protocol_deliver_rcu+0x135/0x135
    Jun 25 23:52:39 Tower kernel: NF_HOOK.constprop.0+0x73/0xce
    Jun 25 23:52:39 Tower kernel: ? ip_protocol_deliver_rcu+0x135/0x135
    Jun 25 23:52:39 Tower kernel: ip_sabotage_in+0x4c/0x59 [br_netfilter]
    Jun 25 23:52:39 Tower kernel: nf_hook_slow+0x3e/0x93
    Jun 25 23:52:39 Tower kernel: ? ip_rcv_finish_core.constprop.0+0x358/0x358
    Jun 25 23:52:39 Tower kernel: NF_HOOK.constprop.0+0x73/0xce
    Jun 25 23:52:39 Tower kernel: ? default_do_nmi+0x3b/0xe0
    Jun 25 23:52:39 Tower kernel: ? ip_rcv_finish_core.constprop.0+0x358/0x358
    Jun 25 23:52:39 Tower kernel: __netif_receive_skb_one_core+0x79/0x9a
    Jun 25 23:52:39 Tower kernel: process_backlog+0xab/0x143
    Jun 25 23:52:39 Tower kernel: __napi_poll.constprop.0+0x2a/0x114
    Jun 25 23:52:39 Tower kernel: net_rx_action+0xe8/0x1f2
    Jun 25 23:52:39 Tower kernel: __do_softirq+0xef/0x218
    Jun 25 23:52:39 Tower kernel: do_softirq+0x50/0x68
    Jun 25 23:52:39 Tower kernel: </IRQ>
    Jun 25 23:52:39 Tower kernel: <TASK>
    Jun 25 23:52:39 Tower kernel: netif_rx_ni+0x53/0x85
    Jun 25 23:52:39 Tower kernel: macvlan_broadcast+0x116/0x144 [macvlan]
    Jun 25 23:52:39 Tower kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]
    Jun 25 23:52:39 Tower kernel: process_one_work+0x198/0x27a
    Jun 25 23:52:39 Tower kernel: worker_thread+0x19c/0x240
    Jun 25 23:52:39 Tower kernel: ? rescuer_thread+0x28b/0x28b
    Jun 25 23:52:39 Tower kernel: kthread+0xde/0xe3
    Jun 25 23:52:39 Tower kernel: ? set_kthread_struct+0x32/0x32
    Jun 25 23:52:39 Tower kernel: ret_from_fork+0x22/0x30
    Jun 25 23:52:39 Tower kernel: </TASK>
    Jun 25 23:52:39 Tower kernel: ---[ end trace 87b9c87a0e7ba204 ]---

    Link to comment
    JorgeB
    2 hours ago, Abbell said:

    Jun 25 23:52:39 Tower kernel: macvlan_broadcast+0x116/0x144 [macvlan]
    Jun 25 23:52:39 Tower kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]

    Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.

    https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/

    See also here:

    https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

    Link to comment
    Abbell

    That will be a challenge. I will read into it and see if I can come up with a proper way to work it out.

    Currently I have 2 NICs running LADP LAG for the main server. One NIC for a Quarantine network and one NIC not really doing much other than being in my camera network.

    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.