4

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.

James
  • 1,117
  • 3
  • 10
  • 16
  • Have you tried a different processor? It's possible the one you have in there now is faulty. There are other possibilities, but that's what I'd do first. – HopelessN00b Aug 27 '12 at 14:05
  • If it instantly restarted after giving you the CPU1 error message, why are there five other error messages on your screen? – David Schwartz Aug 27 '12 at 14:23
  • @DavidSchwartz I had attempted to put the picture above the "Then it instantly restarts". It was an oversight. I believe it goes to CPU7 then restarts quicker than I could have taken a picture or even seen it. Sorry for the misunderstanding! – James Aug 27 '12 at 14:39
  • @HopelessN00b I only have one processor compatible with this board. However. As I have stated. I can install Windows Server 08/Win 7 on it with no problem reading any of the cores. – James Aug 27 '12 at 14:42
  • possible troubleshooting tactic: find out what linux distros this motherboard is certified to support. install one of those and when it fails, call Asus. – longneck Aug 27 '12 at 14:57
  • Do you have the most recent BIOS on your motherboard? – brain99 Aug 29 '12 at 14:21
  • it might be pretty simple, maybe centos 6 don't know how to deal with bulldozer cpu. For me that's the most logical explaination... – Anarko_Bizounours Aug 29 '12 at 14:26
  • Red Hat 6.2 supports Bulldozer, so it stands to reason that CentOS 6.3 does too. Source: http://news.softpedia.com/news/RHEL-6-2-Will-Support-AMD-s-Bulldozer-Opteron-234754.shtml – brain99 Aug 29 '12 at 15:40
  • What do you get before the first CPU not responding message? – Nils Aug 29 '12 at 20:31
  • Perhaps your motherboard/cpu are too new for your kernel. – Tom O'Connor Sep 04 '12 at 11:00
  • 1
    Try to boot KNOPPIX Live CD http://knoppix.net/ in failsave mode to check, is this common linux problem on this particular kernel problem. – Selivanov Pavel Sep 04 '12 at 22:04

6 Answers6

2

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

GioMac
  • 4,544
  • 4
  • 27
  • 41
1

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.

Michael Hampton
  • 244,070
  • 43
  • 506
  • 972
  • I'm leaning towards it being a faulty motherboard. Luckily I have somewhat access to two other exact motherboard and CPUs. I will be doing some trials with this. As for the motherboard/cpu combo. While I would prefer a SuperMicro system with IPMI. It's out of the question financially right now. I appreciate your suggestions. – James Sep 05 '12 at 02:07
0

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.

Spacedust
  • 568
  • 5
  • 13
  • 28
  • Indeed. I can turn off all but first two cores. No success. Is it possible to disable the cores in the grub command line? – James Aug 30 '12 at 00:53
  • I misread. However, I have tried with all cores enabled and with 6 of 8 disabled. No luck either way. – James Aug 30 '12 at 01:39
0

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.

brain99
  • 1,792
  • 12
  • 19
0

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.

womble
  • 96,255
  • 29
  • 175
  • 230
David Van Der Beken
  • 1
-1

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.

The Unix Janitor
  • 2,458
  • 15
  • 13
  • Doesn't that thread describe a totally different problem, even if it is with the same motherboard? – brain99 Aug 29 '12 at 14:40