I am getting a trace wrote to the sys log right after the IP comes up on my unraid system. I honestly don't know what it means as its from a file called blk-core.c. Is this bad news bears? Should I not start my array?
Sep 8 17:46:08 Tower avahi-daemon[11225]: Server startup complete. Host name is Tower.local. Local service cookie is 3033537634. Sep 8 17:46:08 Tower emhttpd: shcmd (57): udevadm settle Sep 8 17:46:09 Tower emhttpd: Autostart disabled Sep 8 17:46:09 Tower kernel: mdcmd (52): stop Sep 8 17:46:09 Tower kernel: md1: stopping Sep 8 17:46:09 Tower kernel: WARNING: CPU: 44 PID: 11259 at block/blk-core.c:781 blk_cleanup_queue+0xd5/0x16c Sep 8 17:46:09 Tower kernel: Modules linked in: md_mod bonding edac_mce_amd kvm_amd kvm mpt3sas crct10dif_pclmul igb crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd k10temp raid_class scsi_transport_sas i2c_piix4 i2c_algo_bit glue_helper i2c_core ahci nvme libahci wmi_bmof mxm_wmi nvme_core wmi ccp button pcc_cpufreq acpi_cpufreq Sep 8 17:46:09 Tower kernel: CPU: 44 PID: 11259 Comm: emhttpd Not tainted 4.18.6-unRAID #1 Sep 8 17:46:09 Tower kernel: Hardware name: System manufacturer System Product Name/ROG ZENITH EXTREME, BIOS 1402 08/03/2018 Sep 8 17:46:09 Tower kernel: RIP: 0010:blk_cleanup_queue+0xd5/0x16c Sep 8 17:46:09 Tower kernel: Code: 00 e8 75 5c 02 00 48 8b 83 98 01 00 00 48 8d b8 80 03 00 00 e8 5f 2a e0 ff 48 89 df e8 cb fe ff ff f6 83 04 02 00 00 02 74 02 <0f> 0b 48 83 7b 18 00 74 1c 48 89 df e8 12 56 00 00 48 8b 73 18 48 Sep 8 17:46:09 Tower kernel: RSP: 0018:ffffc90007e0bbc8 EFLAGS: 00010202 Sep 8 17:46:09 Tower kernel: RAX: ffffffff81e32c00 RBX: ffff881038988000 RCX: 0000000000000000 Sep 8 17:46:09 Tower kernel: RDX: 0000000fffffff01 RSI: 0000000000000000 RDI: ffff881038988140 Sep 8 17:46:09 Tower kernel: RBP: ffff881057e968c8 R08: 0000000000000000 R09: ffff88105df5a540 Sep 8 17:46:09 Tower kernel: R10: ffffffffff492164 R11: ffff8810595ac400 R12: ffff8810389886c8 Sep 8 17:46:09 Tower kernel: R13: ffff881057e94008 R14: ffffffffa00c626f R15: 0000000000000000 Sep 8 17:46:09 Tower kernel: FS: 000014aaab790780(0000) GS:ffff88105df00000(0000) knlGS:0000000000000000 Sep 8 17:46:09 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 8 17:46:09 Tower kernel: CR2: 000000000060b348 CR3: 00000010453ae000 CR4: 00000000003406e0 Sep 8 17:46:09 Tower kernel: Call Trace: Sep 8 17:46:09 Tower kernel: do_stop+0x45/0xab [md_mod] Sep 8 17:46:09 Tower kernel: stop_array.constprop.17+0x77/0x9c [md_mod] Sep 8 17:46:09 Tower kernel: md_proc_write+0x1223/0x163d [md_mod] Sep 8 17:46:09 Tower kernel: ? walk_component+0xc2/0x249 Sep 8 17:46:09 Tower kernel: ? proc_reg_open+0xdf/0xf9 Sep 8 17:46:09 Tower kernel: ? proc_i_callback+0x13/0x13 Sep 8 17:46:09 Tower kernel: ? _cond_resched+0x1b/0x1e Sep 8 17:46:09 Tower kernel: ? dput.part.5+0x33/0xea Sep 8 17:46:09 Tower kernel: ? path_put+0xd/0x16 Sep 8 17:46:09 Tower kernel: ? path_openat+0xb2d/0xc07 Sep 8 17:46:09 Tower kernel: ? do_filp_open+0x83/0xa9 Sep 8 17:46:09 Tower kernel: ? rcu_is_watching+0x5/0x9 Sep 8 17:46:09 Tower kernel: proc_reg_write+0x41/0x5f Sep 8 17:46:09 Tower kernel: ? proc_reg_poll+0x54/0x54 Sep 8 17:46:09 Tower kernel: __vfs_write+0x2e/0x13b Sep 8 17:46:09 Tower kernel: vfs_write+0xc3/0x166 Sep 8 17:46:09 Tower kernel: ksys_write+0x58/0xa6 Sep 8 17:46:09 Tower kernel: do_syscall_64+0x57/0xe6 Sep 8 17:46:09 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Sep 8 17:46:09 Tower kernel: RIP: 0033:0x14aaab36fe81 Sep 8 17:46:09 Tower kernel: Code: c3 0f 1f 84 00 00 00 00 00 48 8b 05 59 91 20 00 c3 0f 1f 84 00 00 00 00 00 8b 05 6a d5 20 00 85 c0 75 16 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 89 d4 53 Sep 8 17:46:09 Tower kernel: RSP: 002b:00007ffe001c1bb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 Sep 8 17:46:09 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000014aaab36fe81 Sep 8 17:46:09 Tower kernel: RDX: 0000000000000004 RSI: 00007ffe001c1bf0 RDI: 0000000000000005 Sep 8 17:46:09 Tower kernel: RBP: 00007ffe001c1d40 R08: 0000000000000000 R09: 0000000000000001 Sep 8 17:46:09 Tower kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000402c60 Sep 8 17:46:09 Tower kernel: R13: 00007ffe001c1fb0 R14: 0000000000000000 R15: 0000000000000000 Sep 8 17:46:09 Tower kernel: ---[ end trace dadb098376631c44 ]--- Sep 8 17:46:09 Tower kernel: md2: stopping Sep 8 17:46:09 Tower kernel: md3: stopping Sep 8 17:46:09 Tower kernel: md4: stopping Sep 8 17:46:09 Tower kernel: md5: stopping Sep 8 17:46:09 Tower kernel: md6: stopping Sep 8 17:46:09 Tower kernel: md7: stopping Sep 8 17:46:09 Tower kernel: md8: stopping Sep 8 17:46:09 Tower kernel: md9: stopping Sep 8 17:46:09 Tower kernel: md10: stopping Sep 8 17:46:09 Tower kernel: md11: stopping Sep 8 17:46:09 Tower kernel: md12: stopping Sep 8 17:46:09 Tower kernel: md13: stopping Sep 8 17:46:09 Tower kernel: md14: stopping Sep 8 17:46:09 Tower avahi-daemon[11225]: Service "Tower" (/services/ssh.service) successfully established. Sep 8 17:46:09 Tower avahi-daemon[11225]: Service "Tower" (/services/smb.service) successfully established. Sep 8 17:46:09 Tower avahi-daemon[11225]: Service "Tower" (/services/sftp-ssh.service) successfully established. Sep 8 17:46:17 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Sep 8 17:46:38 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Sep 8 17:47:49 Tower ool www[12647]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update Sep 8 17:47:49 Tower emhttpd: req (1): cmdStatus=apply&csrf_token=**************** Sep 8 17:47:49 Tower emhttpd: Starting services... Sep 8 17:48:12 Tower ool www[14046]: /usr/local/emhttp/plugins/dynamix/scripts/bootmode '0'
Recommended Comments
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.