Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 27

Thread: C2750D4I too long pre BIOS startup time




  1. #11
    Join Date
    Jan 2014
    Location
    California
    Posts
    7

    Default Re: C2750D4I too long pre BIOS startup time

    If you think a couple minutes is too long for a server reboot you should try booting a Dell R620.

    I also have this board and did not think much of the long boot up time given my experience with Dell servers. The thing that did bother me is the screen and keyboard/mouse do not become active for a while which made me wonder if I had hooked things up properly the first time. Once they do come up you don't get much time to hit f2/del if you want to adjust the bios params which I wanted to do to set the boot order. Took me a while to get that sorted.

    As far as stability I have not noticed any issues yet. I ran a couple passes with memtest86+ 5.0.1 (nice that it can run multithreaded!) and all seemed fine. I am running Ubuntu 12.04.4 with the 3.5 Kernel. I have ZFS on Linux on it as well (I just moved my drives over from my previous build) and seems to be running well too.

  2. #12
    Join Date
    Jan 2014
    Location
    Netherlands
    Posts
    2

    Default Re: C2750D4I too long pre BIOS startup time

    I hope lockups too with this board. I'm running Debian Jessie with kernel 3.11-2-amd64
    When it locks up I get an message in the event log of the IPMI interface:

    FRB2/Hang in POST Faliure

    When that happens I have to reboot the server manually (or via IPMI), because it just hangs. This is the only error I could trace back to the problem, in the debian logs there was nothing to be found.

    BTW, in Linux I don't have any ACPI support for S3 or S4, so I can't hibernate or sleep the server.
    For now, I just let it poweroff and send a WOL packet to wake it up. But, because of the long boot time I would rather use sleep or hibernate.
    I hope kernel support for that is coming.

  3. #13
    Join Date
    Dec 2013
    Location
    Portugal
    Posts
    9

    Default Re: C2750D4I too long pre BIOS startup time

    Just tried a few days ago BIOS 1.52 and the same happened - some lock-up without report neither on the console or on the log files. I just noticed ASRock just released official BIOS 1.80 with the following change log:

    1. Improve "CSM" policy.
    2. Update Intel SATA initialize code.
    3. Add customize Fan function.
    4. Add "Restore BMC Mac from backup" function.
    5. Support DDR3 16GB.
    6. Improve system boot up time.
    7. Add "ECC support" item to control ECC function.

    Maybe the boot time is now acceptable and hopefully the system lock ups too. I'll give it a try tonight UTC time and report my findings.


  4. #14
    Join Date
    Dec 2013
    Location
    Portugal
    Posts
    9

    Default Re: C2750D4I too long pre BIOS startup time

    I'm still experiencing lockups with BIOS version 1.80. No BIOS events neither kernel traces whatsoever. This time I got 8 wonderful hours uptime! :( In terms of boot time it may have decreased a tiny bit. So, next steps, as I'm suspecting some kind of incompatibility with the Linux kernel dealing with these even newer platforms, I disabled all fancy CPU features in BIOS, only leaving the 8 CPU cores active. If this fails, I'll have to stick with booting the kernel with acpi=off, leaving my system with only one CPU core active, until this is hopefully fixed somehow. I hope this acpi=off + 1 CPU don't cause any lockups though.

  5. #15
    Join Date
    Jan 2014
    Location
    Netherlands
    Posts
    2

    Unhappy Re: C2750D4I too long pre BIOS startup time

    Yup, same here.

    I've upgraded to BIOS 1.80 and within half an hour I had a spontaneous reboot. Didn't experience a lockup (yet).

    Thus far I see no change with the previous BIOS (1.50).

    I also had a problem with the BMC 0.14 upgrade. In the description of the update it says "Add customize Fan function."
    First of all, that option is nowhere to be found in the web interface. What's even worse is that after the upgrade my case fans started running at 100% full time (1500 RPM)!!!

    So I downgraded back to .012 and now they are spinning again at 700/800 RPM. So watch out with BMC 0.14
    I'll wait till the next one...

    And I had my first lockup after the BIOS upgrade too...... :(
    Last edited by pvkleeff; 01-18-2014 at 10:57 PM.

  6. #16
    Join Date
    Jan 2014
    Location
    Sweden
    Posts
    4

    Default Re: C2750D4I too long pre BIOS startup time

    I have installed Ubuntu Server 13.10 instead of Debian 7.3.
    Will install Ubuntu Server 14.04 LTS when it comes.


    Had 3 days of uptime before new bios come
    The computer has not restarted after BIOS update, but I can not get my monitor to work! :D


    [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3]
    16:45:31 up 2 days, 6:44, 1 user, load average: 0.01, 0.08, 0.20

  7. #17
    Join Date
    Dec 2013
    Location
    Portugal
    Posts
    9

    Default Re: C2750D4I too long pre BIOS startup time

    Just to report my last few days with BIOS 1.80 and "CPU fancy stuff" disabled in BIOS -no reboot or lock-up so far, uptime is 09:24:45 up 3 days, 23:12, 2 users, load average: 0.67, 0.72, 0.85. I'm inclined to suspect some interference of one or more of these BIOS CPU settings with the Linux kernel:

    1) Intel SpeedStep Technology
    2) CPU C State Support
    3) No-Execute Memory Protection
    4) Intel Virtualization Technology
    5) Intel Turbo Boost Technology

    Having these settings all disabled have no apparent effect on the system, besides the hopeful stability. I'll leave the system up for a few more days to let this theory consolidate.

    Regarding those BIOS parameters, I have (still a 32 bit) Fedora 20 Linux system running 24/24 with kernel 3.12.7-300.fc20.i686 (not the latest), I'm almost sure I should ignore parameter 4, all the other may impact the stability. Unless some parameter proves useful, for instance to save energy by throttling the CPU clock or voltage down and making sure the kernel makes use of that feature, I will not bother searching which parameters are causing instability. Forum, any suggestions on which parameters should be useful for a 24/24 system with Linux kernel? Many thanks in advance.

  8. #18
    Join Date
    Dec 2013
    Location
    Portugal
    Posts
    9

    Default Re: C2750D4I too long pre BIOS startup time

    Reporting a new lock-up (after a whole week stable) this time with traces, it appears that all is caused by a first kernel Oops and after that, all the system degrades itself causing CPU stalls and such:

    Jan 27 09:03:59 server kernel: [774130.149446] BUG: unable to handle kernel NULL pointer dereference at 00000014
    Jan 27 09:03:59 server kernel: [774130.149680] IP: [<c063b152>] selinux_inode_permission+0x82/0x170
    Jan 27 09:03:59 server kernel: [774130.149872] *pdpt = 000000001d706001 *pde = 0000000000000000
    Jan 27 09:03:59 server kernel: [774130.150068] Oops: 0000 [#1] SMP
    Jan 27 09:03:59 server kernel: [774130.150177] Modules linked in: nfnetlink_queue nfnetlink_log binfmt_misc sch_dsmark xt_nat bridge xt_conntrack nf_conntrack_netlink nfnetlink sch_ingress act_police xt_LOG xt_recent cls_route cls_u32 cls_fw sch_sfq sch_htb iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp nf_nat_sip nf_conntrack_sip nf_nat nf_conntrack tun bsd_comp bluetooth rfkill ppp_synctty ppp_async crc_ccitt ppp_generic slhc 8021q garp stp llc mrp nct6775 hwmon_vid option usb_wwan iTCO_wdt iTCO_vendor_support cdc_acm ftdi_sio gpio_ich coretemp joydev kvm cp210x crc32_pclmul crc32c_intel igb ptp pps_core dca serio_raw microcode ipmi_si ipmi_msghandler lpc_ich i2c_i801 i2c_ismt mfd_core usb_storage raid1 ast i2c_algo_bit drm_kms_helper ttm drm i2c_core
    Jan 27 09:03:59 server kernel: [774130.152786] CPU: 4 PID: 28789 Comm: java Not tainted 3.12.7-300.fc20.i686+PAE #1
    Jan 27 09:03:59 server kernel: [774130.153040] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./C2750D4I, BIOS P1.80 01/14/2014
    Jan 27 09:03:59 server kernel: [774130.153383] task: d70cba80 ti: c780a000 task.ti: c780a000
    Jan 27 09:03:59 server kernel: [774130.153557] EIP: 0060:[<c063b152>] EFLAGS: 00010246 CPU: 4
    Jan 27 09:03:59 server kernel: [774130.153731] EIP is at selinux_inode_permission+0x82/0x170
    Jan 27 09:03:59 server kernel: [774130.165475] EAX: 000009e2 EBX: 00800000 ECX: c0c5cca0 EDX: 00000000
    Jan 27 09:03:59 server kernel: [774130.177327] ESI: 00000081 EDI: d2ba8568 EBP: c780bdb8 ESP: c780bd80
    Jan 27 09:03:59 server kernel: [774130.189184] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
    Jan 27 09:03:59 server kernel: [774130.201022] CR0: 80050033 CR2: 00000014 CR3: 032b8000 CR4: 001007f0
    Jan 27 09:03:59 server kernel: [774130.213016] Stack:
    Jan 27 09:03:59 server kernel: [774130.224982] 00000001 d70cba80 c780bd9c c045d777 000041c0 d2ba8568 ffffbe3f c780bda4
    Jan 27 09:03:59 server kernel: [774130.237292] c045d7e2 c780bdc0 c056bcbe d2ba8568 00000081 b15130d1 c780bdc0 c0636c5a
    Jan 27 09:03:59 server kernel: [774130.249655] c780bdd0 c056c3d0 d9aeb078 c780beb0 c780bddc c056c446 d9aeb078 c780be30
    Jan 27 09:03:59 server kernel: [774130.262078] Call Trace:
    Jan 27 09:03:59 server kernel: [774130.274477] [<c045d777>] ? ns_capable+0x27/0x60
    Jan 27 09:03:59 server kernel: [774130.287007] [<c045d7e2>] ? inode_capable+0x12/0x20
    Jan 27 09:03:59 server kernel: [774130.299558] [<c056bcbe>] ? generic_permission+0xee/0x1e0
    Jan 27 09:03:59 server kernel: [774130.312123] [<c0636c5a>] security_inode_permission+0x1a/0x20
    Jan 27 09:03:59 server kernel: [774130.324689] [<c056c3d0>] __inode_permission+0x40/0xa0
    Jan 27 09:03:59 server kernel: [774130.337336] [<c056c446>] inode_permission+0x16/0x50
    Jan 27 09:03:59 server kernel: [774130.350031] [<c056c84c>] link_path_walk+0x5c/0x730
    Jan 27 09:03:59 server kernel: [774130.362747] [<c056c61f>] ? path_init+0x19f/0x370
    Jan 27 09:03:59 server kernel: [774130.375435] [<c056cf71>] path_lookupat+0x51/0x6a0
    Jan 27 09:03:59 server kernel: [774130.388091] [<c04392aa>] ? native_smp_send_reschedule+0x3a/0x50
    Jan 27 09:03:59 server kernel: [774130.400775] [<c0552ecb>] ? kmem_cache_alloc+0x2b/0x1b0
    Jan 27 09:03:59 server kernel: [774130.413419] [<c047f455>] ? check_preempt_curr+0x65/0x90
    Jan 27 09:03:59 server kernel: [774130.426070] [<c056c22f>] ? getname_flags+0x3f/0x140
    Jan 27 09:03:59 server kernel: [774130.438740] [<c056d5e5>] filename_lookup+0x25/0xb0
    Jan 27 09:03:59 server kernel: [774130.451375] [<c0570960>] user_path_at_empty+0x40/0x70
    Jan 27 09:03:59 server kernel: [774130.464056] [<c04b26ae>] ? do_futex+0x73e/0x9f0
    Jan 27 09:03:59 server kernel: [774130.476736] [<c05709af>] user_path_at+0x1f/0x30
    Jan 27 09:03:59 server kernel: [774130.489497] [<c0566ab9>] vfs_fstatat+0x49/0x90
    Jan 27 09:03:59 server kernel: [774130.502421] [<c0567366>] SyS_stat64+0x26/0x40
    Jan 27 09:03:59 server kernel: [774130.515288] [<c04b29ec>] ? SyS_futex+0x8c/0x140
    Jan 27 09:03:59 server kernel: [774130.528121] [<c09bd18d>] sysenter_do_call+0x12/0x28
    Jan 27 09:03:59 server kernel: [774130.540732] [<c09b007b>] ? dump_stack+0x33/0x52
    Jan 27 09:03:59 server kernel: [774130.552973] Code: c6 04 00 00 00 0f 45 da f7 c6 08 00 00 00 0f 85 b5 00 00 00 89 da 83 ca 04 f7 c6 02 00 00 00 0f 45 da 8b 40 5c 8b 57 24 8b 40 04 <0f> b7 4a 14 8b 52 10 c7 44 24 04 00 00 00 00 89 45 dc 8d 45 e0
    Jan 27 09:03:59 server kernel: [774130.578175] EIP: [<c063b152>] selinux_inode_permission+0x82/0x170 SS:ESP 0068:c780bd80
    Jan 27 09:03:59 server kernel: [774130.590866] CR2: 0000000000000014
    Jan 27 09:03:59 server kernel: [774130.691982] ---[ end trace 14deb918f737bf55 ]---

    Kernel BUG, some bad kernel module I have loaded or BIOS BUG? I'll try to examine more closely, for now I disabled the lm_sensors that seem not to be totally compatible with this motherboard - just a shot in the dark anyway.

  9. #19
    Join Date
    Mar 2014
    Location
    Belgium
    Posts
    1

    Default Re: C2750D4I too long pre BIOS startup time

    Hello,

    Looks like we are on the same boat.

    I'm getting lock-ups by using this mobo as a ESXi 5.5 host for only one VM - pfSense 2.1.1 (4 cores + 8GB RAM + 16GB virtual HDD) with dedicated Intel server dual nics PCIe card.



    update: the MB is no longer able to boot and only the IPMI interface is working... I will try to reset the BIOS :(
    Last edited by aDEO; 03-05-2014 at 03:20 AM. Reason: update

  10. #20
    Join Date
    Mar 2014
    Location
    Colorado
    Posts
    2

    Default Re: C2750D4I too long pre BIOS startup time

    I wish I had read this thread before I bought one of these. Out of the box mine takes 45 seconds or more to post, another 45 seconds or so to boot if I can even see bootup when the display is responding. If it goes to sleep it has to be powered off to wake up. During operation it stalls for minutes doing the simplest of tasks such as installing something with yum or browsing the web. I have a previously purchased board with an atom D525 that outperforms this much more expensive board. I have bios 1.80 with Fedora 19.

Page 2 of 3 FirstFirst 123 LastLast

Thread Information

Users Browsing this Thread

There are currently 3 users browsing this thread. (0 members and 3 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •