Jump to content
XPEnology Community

Stefanos

Transition Member
  • Posts

    6
  • Joined

  • Last visited

Everything posted by Stefanos

  1. All tests done. Everything works fine, including video transcoding. Great job real3x!
  2. What is the best board for full compatibility?
  3. Thank you. Already tried with 1.03B but with no luck. I don't understand why the first reboot worked fine...
  4. Hi, I'm going really crazy with a new xpenology setup. The mainboard is a GA-J3455-D3H with 8gb ram, nothing special, just 2 sata disks. The first install where the whole boot procedure works fine, and the strange thing is that the first time worked fine for hours, but after the reboot, the nas won't start again. The system gets stuck after "Post Init" where I get a lot of [ 188.105540] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 41s! [insmod:7137] Btw, the CPU number changes randomly at each trial. I've tried everything, but nothing changes. Any suggestion? This is the log: [ 240.088539] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 41s! [insmod:6947] [ 240.095854] Modules linked in: i915(E+) drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) cfbfillrect(E) cfbcopyarea(E) cfbimgblt(E) drm(E) fb(E) fbdev intel_agp(E) intel_gtt(E) agpgart(E) video backlight button synoacl_vfs(PO) hfsplus md4 hmac r8168(OE) ixgbe(E) igb(E) i2c_algo_bit e1000e(E) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd rtc_cmos(E) mdio(E) mpt3sas(E) raid_class(E) scsi_transport_sas(E) megaraid_sas(E) megaraid(E) mptctl(E) mptspi(E) mptscsih(E) mptbase(E) scsi_transport_spi(E) megaraid_mbox(E) megaraid_mm(E) vmw_pvscsi(E) BusLogic(E) usb_storage xhci_pci xhci_hcd usbcore usb_common txuuuuuuuuuj(OE) [last unloaded: apollolake_synobios] [ 240.189002] CPU: 0 PID: 6947 Comm: insmod Tainted: P OEL 4.4.59+ #24922 [ 240.196574] Hardware name: Gigabyte Technology Co., Ltd. Default string/J3455N-D3H, BIOS F3 11/16/2018 [ 240.205879] task: ffff88026d21d200 ti: ffff880274144000 task.ti: ffff880274144000 [ 240.213369] RIP: 0010:[<ffffffffa050abe4>] [<ffffffffa050abe4>] drm_clflush_page+0x54/0xb0 [drm] [ 240.222276] RSP: 0018:ffff880274147910 EFLAGS: 00000293 [ 240.227593] RAX: ffff88026834d000 RBX: 0000160000000000 RCX: 0000000000000000 [ 240.234737] RDX: 0000000000000000 RSI: ffff88026834d000 RDI: ffffea0009a0d340 [ 240.241872] RBP: ffff880274147938 R08: 0000000000000000 R09: 0000000000000000 [ 240.249011] R10: ffff8802728b0c00 R11: 0000160000000000 R12: 0000000000000001 [ 240.256148] R13: 0000000000000000 R14: ffff88026c9e3208 R15: 0000000000000000 [ 240.263290] FS: 00007f1360bf4700(0000) GS:ffff88027fc00000(0000) knlGS:0000000000000000 [ 240.271380] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 240.277135] CR2: 00007f4ddce11148 CR3: 000000026c102000 CR4: 00000000003406f0 [ 240.284272] Stack: [ 240.286293] ffffffffa050acf0 ffff8802741a6200 0000000700000000 ffff880200000001 [ 240.293792] ffff88026c9e3040 ffff880274147950 ffffffffa05f11f4 ffff88026c9e3040 [ 240.301293] ffff880274147978 ffffffffa05f1369 ffff88026c9e3040 0000000000000001 [ 240.308797] Call Trace: [ 240.311260] [<ffffffffa050acf0>] ? drm_clflush_sg+0x50/0x90 [drm] [ 240.317492] [<ffffffffa05f11f4>] __i915_do_clflush+0x14/0x30 [i915] [ 240.323883] [<ffffffffa05f1369>] i915_gem_clflush_object+0x39/0x1e0 [i915] [ 240.330882] [<ffffffffa0600813>] flush_write_domain+0x33/0xe0 [i915] [ 240.337363] [<ffffffffa060306c>] i915_gem_object_set_to_gtt_domain+0x8c/0x120 [i915] [ 240.345233] [<ffffffffa06146dd>] execlists_context_pin+0x14d/0x4e0 [i915] [ 240.352152] [<ffffffffa06104c7>] intel_engine_init_common+0x27/0x380 [i915] [ 240.359235] [<ffffffffa0615ad2>] logical_ring_init+0x12/0xc0 [i915] [ 240.365629] [<ffffffffa0615c62>] logical_render_ring_init+0xe2/0x340 [i915] [ 240.372715] [<ffffffffa0613e50>] ? gen9_init_render_ring+0x30/0x30 [i915] [ 240.379629] [<ffffffffa0610187>] intel_engines_init+0x47/0xb0 [i915] [ 240.386109] [<ffffffffa0605577>] i915_gem_init+0xf7/0x4a0 [i915] [ 240.392236] [<ffffffffa05becde>] i915_driver_load+0xa1e/0xe00 [i915] [ 240.398718] [<ffffffffa05c9797>] i915_pci_probe+0x27/0x40 [i915] [ 240.404818] [<ffffffff812ffb8c>] pci_device_probe+0x8c/0x100 [ 240.410565] [<ffffffff81387641>] driver_probe_device+0x1f1/0x310 [ 240.416666] [<ffffffff813877e2>] __driver_attach+0x82/0x90 [ 240.422243] [<ffffffff81387760>] ? driver_probe_device+0x310/0x310 [ 240.428515] [<ffffffff813856d1>] bus_for_each_dev+0x61/0xa0 [ 240.434179] [<ffffffff813870d9>] driver_attach+0x19/0x20 [ 240.439586] [<ffffffff81386d03>] bus_add_driver+0x1b3/0x230 [ 240.445249] [<ffffffffa06fa000>] ? 0xffffffffa06fa000 [ 240.450395] [<ffffffff81387feb>] driver_register+0x5b/0xe0 [ 240.455971] [<ffffffff812fe667>] __pci_register_driver+0x47/0x50 [ 240.462101] [<ffffffffa06fa03e>] i915_init+0x3e/0x45 [i915] [ 240.467769] [<ffffffff810003b6>] do_one_initcall+0x86/0x1b0 [ 240.473434] [<ffffffff810e1b48>] do_init_module+0x56/0x1be [ 240.479012] [<ffffffff810b7d8d>] load_module+0x1dfd/0x2080 [ 240.484588] [<ffffffff810b51f0>] ? __symbol_put+0x50/0x50 [ 240.490077] [<ffffffff810b8199>] SYSC_finit_module+0x79/0x80 [ 240.495830] [<ffffffff810b81b9>] SyS_finit_module+0x9/0x10 [ 240.501409] [<ffffffff8156a58a>] entry_SYSCALL_64_fastpath+0x1e/0x92 [ 240.507850] Code: 00 16 00 00 48 8d 37 48 01 c6 48 b8 00 00 00 00 00 88 ff ff 48 c1 fe 06 31 d2 48 c1 e6 0c 48 01 c6 8d 02 48 8d 04 30 66 0f ae 38 <8d> 14 0a 81 fa ff 0f 00 00 76 eb 55 48 89 e5 65 48 8b 04 25 c0
  5. @bearcat thank you for the fast response. The motherboard I was referencing to is just an example because it’s cited many times in this category. ‘I’ve started looking at the reported updates but most of the tested configuration are heavy duty server configuration, and i’m Just looking for a fast and reliable MB to use for hoe video streaming. So the cpu could be whatever is better for dms 6.2.1+. Have you any suggestion?
  6. Hi, I need to change my ancient HW, but I’m unsure on which one to choose for a new xpenology setup. I saw few comments reporting issues with transcoding on the J3455-ITX and also not sure if it supports the 6.2. any suggestion? thx S.
×
×
  • Create New...