Home / server / Questions / 421614
Accepted
James
Asked: 2012-08-28 05:54:37 +0800 CST

CPU?: Not responding

  • 772

I'm attempting to build a system for co-location. I've been running into issues while trying to install CentOS 6.3

System Specs:

Motherboard: ASUS m5a99x Process: AMD FX-8120 (8-core Bulldozer) Memory: 2x 4gb G-Skill 2133 running at 1600

I keeps giving me an error message:

CPU1: Not Responding.
CPU2: Not Responding.
CPU3: Not Responding.
CPU4: Not Responding.
CPU5: Not Responding.
CPU6: Not Responding.

Then it instantly restarts.

I keeps giving me an error message "CPU<1/2/3/4/5/6>: Not Responding."

I have tried installing it from USB, Multiple DVDs, Multiple Distros. I have also in the bios attempted to disable cores. I was able to disable 2/3 4/5 6/7.

I have also ensured that there is zero overclocking. The system works fine in a windows environment. I'm out of ideas.

linux

6 Answers

  1. Best Answer

    Looks like a installer kernel problem. I bet RHEL 6.3/Fedora 17 will work fine. If you want CentOS - you can try to install same system with newer/different kernel via other medium (PXE boot, USB etc), or use custom spin built with anaconda including newer/other kernel.

    Google link for custom CD creation

    p.s. there is no problem with Bulldozer CPU, it's supported by the kernel, I am running it.

    p.p.s. you can easily specify fresh kernel initrd and image for PXE - it's easier to do

    • 2

  2. Assuming you've actually updated the BIOS as several people have recommended, this leaves you with two possibilities:

    • A faulty CPU
    • A faulty motherboard

    Go pick up a Sempron 140 or something else cheap from a shop and drop it in. If it's the motherboard, you should continue to get these errors; while if it's the CPU the errors should stop.

    In no circumstances should you try to co-locate this thing as is. You'll just have an unresolved problem that you'll have to actually go retrieve your hardware to fix.

    And while we're at it, strongly consider not using a cheap desktop-class motherboard for a server that you aren't going to have physical access to. Consider at the very least a SuperMicro server motherboard with IPMI so you have some sort of remote management capability.

    • 1

  3. Some BIOSes allow you to turn off selected cores on multicore CPUs and you've got probably only one core turned on. Also make sure you've got the latest BIOS version.

    • 0

  4. Aside from checking if you've got the latest BIOS for your motherboard, this forum post on arch linux suggests trying to disable C1E in your BIOS.

    If that does not work, they suggest booting with less cpus to see if that works. Once you get the system booted, you may be able to find additional information.

    • 0

  5. I recently encountered that problem (smpboot core1 not responding) on a Debian 8 (3.16.0-5-amd64) on a Gigabyte MA790X-UD3P (bios version F4) motherboard.

    In my case, I could get back a fully functional system (all cores) after I updated the bios to version F6.

    • 0

  6. Found this post

    http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/472198-opensuse-12-1-uefi-install-64-bit-2.html

    seems cover the problems. I think your only hope is a bios update from asus.

    • -1