limetech Posted June 8, 2018 Share Posted June 8, 2018 Installation and Bug Reporting Instructions Getting back in the saddle after a move which took far longer than it should have... This is a small update to bring us up-to-date with the latest LTS kernel and fix a handful of bugs. Let's test this over the weekend and release 6.5.3 stable on Monday along with 6.6.0 next soon thereafter. Version 6.5.3-rc2 2018-06-08 Linux kernel: version 4.14.48 Management: Small update to create_network_ini to suppress progress information when using cURL. update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} webgui: Remove unused tags from docker templates webgui: apcups: ensure numeric fields are 0 if the values are empty webgui: bug fix: prevent deleting user template when (letter case) renaming a docker container webgui: Strip HTML from back-end webgui: make entire menu items clickable for gray and azure themes Version 6.5.3-rc1 2018-05-18 Summary: In order to fix VM startup issue we need to change the linux kernel preemption model: CONFIG_PREEMPT=no (previous setting) This option reduces the latency of the kernel by making all kernel code (that is not executing in a critical section) preemptible. This allows reaction to interactive events by permitting a low priority process to be preempted involuntarily even if it is in kernel mode executing a system call and would otherwise not be about to reach a natural preemption point. This allows applications to run more 'smoothly' even when the system is under load, at the cost of slightly lower throughpu and a slight runtime overhead to kernel code. Select this if you are building a kernel for a desktop or embedded system with latency requirements in the milliseconds range. CONFIG_PREEMPT_VOLUNTARY=yes (new in this release) This option reduces the latency of the kernel by adding more "explicit preemption points" to the kernel code. These new preemption points have been selected to reduce the maximum latency of rescheduling, providing faster application reactions, at the cost of slightly lower throughput. This allows reaction to interactive events by allowing a low priority process to voluntarily preempt itself even if it is in kernel mode executing a system call. This allows applications to run more 'smoothly' even when the system is under load. Select this if you are building a kernel for a desktop system. Linux kernel: version 4.14.41 set CONFIG_PREEMPT=no and CONFIG_PREEMPT_VOLUNTARY=yes 2 1 Quote Link to comment
Jcloud Posted June 8, 2018 Share Posted June 8, 2018 (edited) 23 hours ago, limetech said: saddle after a move which took far longer than it should have... I know that feeling - ah, the joys of moving. Will update system tonight, will edit post if there are any issues, but my bet is $5 on, "boring, just works." I hope all who are involved likes the new location. Edit: No issues to report, from 6.5.3 rc1 to rc2. Edited June 9, 2018 by Jcloud Quote Link to comment
Dazog Posted June 8, 2018 Share Posted June 8, 2018 No issues upgrading from 6.5.3 rc1 to rc2 Can't wait for 6.6 with kernel 4.17 1 Quote Link to comment
jetskijoe Posted June 8, 2018 Share Posted June 8, 2018 I cannot wait for the latest docker. That will really help out everything. I have about 25 dockers running right now and probably will have a few more once the new version comes out and can use some of the new features. Quote Link to comment
nickp85 Posted June 9, 2018 Share Posted June 9, 2018 Just updated rc1 to rc2, nothing bad to report Quote Link to comment
Mat1926 Posted June 9, 2018 Share Posted June 9, 2018 Just waiting for the stable release...Thnx for the update guys... Quote Link to comment
luisv Posted June 9, 2018 Share Posted June 9, 2018 Just updated one of my servers, so far so good. Quote Link to comment
GHunter Posted June 9, 2018 Share Posted June 9, 2018 Updated from 6.5.3-rc1 last night. No issues to report. Thanks guys! Quote Link to comment
itimpi Posted June 9, 2018 Share Posted June 9, 2018 I have had no problems with the upgrade. Quote Link to comment
PSYCHOPATHiO Posted June 9, 2018 Share Posted June 9, 2018 updated last night, all is good and things just seem to be running even smoother. Thank you guys Quote Link to comment
cybrnook Posted June 9, 2018 Share Posted June 9, 2018 Upgrade from RC1 went fine, so far no issues. Quote Link to comment
1812 Posted June 9, 2018 Share Posted June 9, 2018 no observed issues after upgrade Quote Link to comment
jpowell8672 Posted June 10, 2018 Share Posted June 10, 2018 6.5.2 to 6.5.3-rc2 No Problems on Upgrade and Running for the past 22 Hours. Thanks for all your hard work! Quote Link to comment
JM2005 Posted June 10, 2018 Share Posted June 10, 2018 Looking good here as well. I just updated. Quote Link to comment
moose Posted June 10, 2018 Share Posted June 10, 2018 Upgraded from 6.5.2 to 6.5.3-rc2. No issues! Quote Link to comment
nexusmaniac Posted June 11, 2018 Share Posted June 11, 2018 Runs perfectly for me, no fuss with the upgrade a couple of days ago Quote Link to comment
S80_UK Posted June 12, 2018 Share Posted June 12, 2018 Update for me also painless. Congrats on the move(s), too. Quote Link to comment
nexusmaniac Posted June 13, 2018 Share Posted June 13, 2018 Jun 12 22:49:11 Raptor kernel: ------------[ cut here ]------------ Jun 12 22:49:11 Raptor kernel: WARNING: CPU: 4 PID: 0 at net/netfilter/nf_conntrack_core.c:769 __nf_conntrack_confirm+0x97/0x4d6 Jun 12 22:49:11 Raptor kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables vhost_net tun vhost tap macvlan xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod nct6775 hwmon_vid igb ptp pps_core i2c_algo_bit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ipmi_ssif crct10dif_pclmul crc32_pclmul ttm crc32c_intel ghash_clmulni_intel pcbc drm_kms_helper aesni_intel aes_x86_64 crypto_simd glue_helper drm cryptd ahci intel_cstate agpgart i2c_i801 libahci i2c_core intel_uncore video syscopyarea sysfillrect intel_rapl_perf ie31200_edac sysimgblt backlight fb_sys_fops thermal button fan ipmi_si acpi_cpufreq [last unloaded: pps_core] Jun 12 22:49:11 Raptor kernel: CPU: 4 PID: 0 Comm: swapper/4 Not tainted 4.14.48-unRAID #1 Jun 12 22:49:11 Raptor kernel: Hardware name: ASUSTeK COMPUTER INC. P9D-M Series/P9D-M Series, BIOS 1801 01/19/2016 Jun 12 22:49:11 Raptor kernel: task: ffff88041d79b600 task.stack: ffffc90001928000 Jun 12 22:49:11 Raptor kernel: RIP: 0010:__nf_conntrack_confirm+0x97/0x4d6 Jun 12 22:49:11 Raptor kernel: RSP: 0018:ffff88042fd03958 EFLAGS: 00010202 Jun 12 22:49:11 Raptor kernel: RAX: 0000000000000188 RBX: 0000000000001898 RCX: 0000000051da362f Jun 12 22:49:11 Raptor kernel: RDX: 0000000000000001 RSI: 000000000000011f RDI: ffffffff81c08a7c Jun 12 22:49:11 Raptor kernel: RBP: ffff8803aee7dd00 R08: ffff88007d825e00 R09: ffff8803ec518100 Jun 12 22:49:11 Raptor kernel: R10: 00000000000002b8 R11: 0000000000000006 R12: ffffffff81c88480 Jun 12 22:49:11 Raptor kernel: R13: 000000000000151f R14: ffff88007d825e00 R15: ffff88007d825e58 Jun 12 22:49:11 Raptor kernel: FS: 0000000000000000(0000) GS:ffff88042fd00000(0000) knlGS:0000000000000000 Jun 12 22:49:11 Raptor kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 12 22:49:11 Raptor kernel: CR2: 00001481abc16000 CR3: 0000000001c0a003 CR4: 00000000001606e0 Jun 12 22:49:11 Raptor kernel: Call Trace: Jun 12 22:49:11 Raptor kernel: <IRQ> Jun 12 22:49:11 Raptor kernel: ipv4_confirm+0xac/0xb4 [nf_conntrack_ipv4] Jun 12 22:49:11 Raptor kernel: nf_hook_slow+0x37/0x96 Jun 12 22:49:11 Raptor kernel: ip_local_deliver+0x97/0xb0 Jun 12 22:49:11 Raptor kernel: ? inet_del_offload+0x3e/0x3e Jun 12 22:49:11 Raptor kernel: ip_sabotage_in+0x2b/0x31 Jun 12 22:49:11 Raptor kernel: nf_hook_slow+0x37/0x96 Jun 12 22:49:11 Raptor kernel: ip_rcv+0x2e3/0x32a Jun 12 22:49:11 Raptor kernel: ? ip_local_deliver_finish+0x1aa/0x1aa Jun 12 22:49:11 Raptor kernel: __netif_receive_skb_core+0x69f/0x718 Jun 12 22:49:11 Raptor kernel: netif_receive_skb_internal+0x8f/0x95 Jun 12 22:49:11 Raptor kernel: br_pass_frame_up+0x111/0x11e Jun 12 22:49:11 Raptor kernel: ? br_port_flags_change+0xf/0xf Jun 12 22:49:11 Raptor kernel: br_handle_frame_finish+0x41a/0x44a Jun 12 22:49:11 Raptor kernel: ? br_pass_frame_up+0x11e/0x11e Jun 12 22:49:11 Raptor kernel: br_nf_hook_thresh+0x93/0x9e Jun 12 22:49:11 Raptor kernel: ? br_pass_frame_up+0x11e/0x11e Jun 12 22:49:11 Raptor kernel: br_nf_pre_routing_finish+0x225/0x237 Jun 12 22:49:11 Raptor kernel: ? br_pass_frame_up+0x11e/0x11e Jun 12 22:49:11 Raptor kernel: ? nf_nat_ipv4_in+0x21/0x68 [nf_nat_ipv4] Jun 12 22:49:11 Raptor kernel: br_nf_pre_routing+0x2be/0x2ce Jun 12 22:49:11 Raptor kernel: ? br_nf_forward_ip+0x313/0x313 Jun 12 22:49:11 Raptor kernel: nf_hook_slow+0x37/0x96 Jun 12 22:49:11 Raptor kernel: br_handle_frame+0x279/0x2a3 Jun 12 22:49:11 Raptor kernel: ? br_pass_frame_up+0x11e/0x11e Jun 12 22:49:11 Raptor kernel: ? br_handle_local_finish+0x31/0x31 Jun 12 22:49:11 Raptor kernel: __netif_receive_skb_core+0x448/0x718 Jun 12 22:49:11 Raptor kernel: ? inet_gro_receive+0x241/0x24f Jun 12 22:49:11 Raptor kernel: ? recalibrate_cpu_khz+0x6/0x6 Jun 12 22:49:11 Raptor kernel: netif_receive_skb_internal+0x8f/0x95 Jun 12 22:49:11 Raptor kernel: napi_gro_receive+0x42/0x76 Jun 12 22:49:11 Raptor kernel: igb_poll+0xb6b/0xb91 [igb] Jun 12 22:49:11 Raptor kernel: net_rx_action+0xfb/0x24f Jun 12 22:49:11 Raptor kernel: __do_softirq+0xcd/0x1c2 Jun 12 22:49:11 Raptor kernel: irq_exit+0x4f/0x8e Jun 12 22:49:11 Raptor kernel: do_IRQ+0xa5/0xbb Jun 12 22:49:11 Raptor kernel: common_interrupt+0x7d/0x7d Jun 12 22:49:11 Raptor kernel: </IRQ> Jun 12 22:49:11 Raptor kernel: RIP: 0010:cpuidle_enter_state+0xe3/0x135 Jun 12 22:49:11 Raptor kernel: RSP: 0018:ffffc9000192bef8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffd9 Jun 12 22:49:11 Raptor kernel: RAX: ffff88042fd20840 RBX: 0000000000000000 RCX: 000000000000001f Jun 12 22:49:11 Raptor kernel: RDX: 000117a9e3245377 RSI: 0000000000020040 RDI: 0000000000000000 Jun 12 22:49:11 Raptor kernel: RBP: ffff88042fd28420 R08: 0003b4dc7bdaf84a R09: 0000000000000078 Jun 12 22:49:11 Raptor kernel: R10: ffffc9000192bed8 R11: 0000000000000024 R12: 0000000000000005 Jun 12 22:49:11 Raptor kernel: R13: 000117a9e3245377 R14: ffffffff81c56678 R15: 000117a9e2bfd1a7 Jun 12 22:49:11 Raptor kernel: ? cpuidle_enter_state+0xbb/0x135 Jun 12 22:49:11 Raptor kernel: do_idle+0x11a/0x179 Jun 12 22:49:11 Raptor kernel: cpu_startup_entry+0x18/0x1a Jun 12 22:49:11 Raptor kernel: secondary_startup_64+0xa5/0xb0 Jun 12 22:49:11 Raptor kernel: Code: 48 c1 eb 20 89 1c 24 e8 31 f9 ff ff 8b 54 24 04 89 df 89 c6 41 89 c5 e8 a9 fa ff ff 84 c0 75 b9 49 8b 86 80 00 00 00 a8 08 74 02 <0f> 0b 4c 89 f7 e8 03 ff ff ff 49 8b 86 80 00 00 00 0f ba e0 09 Jun 12 22:49:11 Raptor kernel: ---[ end trace 8d93d45211c347fa ]--- Nice little calltrace last night, just got to my unRAID machine this morning to upgrade it to 6.5.3 I'm going to continue with the upgrade to Stable from rc2 ... But thought it would be best to post my calltrace in here! Quote Link to comment
reey Posted July 1, 2018 Share Posted July 1, 2018 On 6/8/2018 at 9:36 PM, limetech said: Let's test this over the weekend and release 6.5.3 stable on Monday along with 6.6.0 next soon thereafter. @limetech I don't want to be impatient, but what was meant by soon thereafter? Do you have any schedule for releasing a test build? Regards reey Quote Link to comment
smdion Posted July 1, 2018 Share Posted July 1, 2018 3 hours ago, reey said: @limetech I don't want to be impatient, but what was meant by soon thereafter? Do you have any schedule for releasing a test build? Regards reey Soon is a wonderful LimeTech trademark, which means, whenever its ready. Extra patience is usually recommended 1 Quote Link to comment
CHBMB Posted July 1, 2018 Share Posted July 1, 2018 They're working on it. I can assure you of that 1 Quote Link to comment
Recommended Posts
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.