Sponsored Content
Top Forums UNIX for Advanced & Expert Users Problem with dual processor system Post 41998 by meeps on Monday 20th of October 2003 11:50:31 PM
Old 10-21-2003
Problem with dual processor system

Firstly, here are the main system specs:
2x Pentium III 800MHz
MSI 694D Pro
4x 256MB PC133 SDRAM
420WATT Vantec PSU

In a nut shell, the systems reboots for no apparent reason while starting/installing up any OS when both processors are installed.

I've ran memtest86 for several hours, no errors. I've tested with one stick of ram at a time. I have tried an agp video card and pci. I have tested with no pci cards. I even bought a new powersupply (I was so certain that was the problem).

I've done this with several different operating systems:

Windows 2000 - Gets into the first stage of setup (the blue screen)... The system has to reboot (normal) and then right before the graphical loading screen comes up (black screen with white progress bar) it reboots. At this point I noticed the two processors have different VCore values written on the CPU label, one is 1.75 the other 1.7. I adjusted this in the Bios and it booted into the graphical installer. I turned it off and came back about an hour later to start installing Gentoo (at this point I was thrilled, thought I solved the problem). Back to the same problem :/

Windows 2003 - Finishes the first stage of setup and actually gets into the graphical setup part. The systems freezes and stops responding to input in about 30 seconds.

Gentoo - Boots into the setup *sometimes* Sometimes it will crash as the system is running through the rc.d scripts, other times it's fine (for now). I'll be able to partition and format, browse through directories and such but once I decompress one of the tar.gz stage files (fairly large) the system reboots.

Slackware 9.1 - Reboots itself as the installer loads up.

I read my motherboard manual and it turns out his has an onboard terminator... I popped out the second processor and all is well. No reboots and everything works. Put the processor back and the problem resumes. I even switched the processors, both work - when alone.

Right now I have Slackware running. I compiled a kernel with SMP enabled and tried booting with both processors. It loads up a bit (I see text flying down the screen) and then it reboots.

I read about similar problems where the capacitors around the CPU2 socket had blown and replacing them fixed the problem. Unfortunately, mine are not blown (and yes, I mean unfortunately).

I bought this on eBay. The seller has 100% positive feedback so I doubt he sent me a lemon. He had a picture of the system running XP with both processors. It *could* be a chop or old screenshot but I'll include it anyhow.

http://meeps.no-ip.org:3000/multimedia/winmsd.jpg

Here's the /proc/cpuinfo from one of the times Gentoo partially worked. I'm not sure if this is helpful.

http://meeps.no-ip.org:3000/cpuinfo.txt

Yep, different steppings. Intel's documents say there is no problem and this guy I bought it from apparently had no problems.

That's pretty much it. Anyone have an ideas? First one to solve it gets my first born, any takers? Smilie
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Dual Boot problem,help!!!!

I had Win98 and Win Xp on a dual boot on my system, I formatted my C: drive to get rid of Win98 and installed Linux Madrake in its Place, it all installed ok but when I boot up I can no longer dual boot and it goes straight into Mandrake Linux. How can I get either a dual boot so I can get to XP... (10 Replies)
Discussion started by: Merv
10 Replies

2. AIX

Problem with knlist in AIX 5.3 for Power5 processor

Hi all, I have a AIX 5.3 Installation on the Power5 processor. I am using the knlist API for getting the details of the CPU details like user cpu, kernel cpu, idle cpu and wait cpu. My code is working fine on other Installations of AIX like PowerPC_POWER4 but it is giving wrong values on Power5... (0 Replies)
Discussion started by: rajesht
0 Replies

3. Linux

linux for dual core processor

hi all I bought a new MSI motherboard and intel dual core processor . i have currently installed fedora core 3 for which audio is not detected . can u tell me which version of fedora core will support as i have tried with fedora core 6 which gets installed but gives a error while... (0 Replies)
Discussion started by: nageshrk
0 Replies

4. AIX

HMC & Processor Pool problem

Hi, I am having problem allocating all my processors -- 6 processors -- to sharedpool1 I have 6 processors and I want my lpars to share all these 6 processors. DefaultPool can't be edited. I edit my Sharedpool1 as follows Reserved:0 Max Processors: 6 In my lpar profile: Min: 1... (1 Reply)
Discussion started by: filosophizer
1 Replies

5. HP-UX

how can i know this processor quad or dual core ?

hi every body i want to know if i have server with hp-ux os if i did "machinfo" i will see no of cpu = for example 16 how can i know this is dual or quad core . thanks (2 Replies)
Discussion started by: maxim42
2 Replies

6. Solaris

Manufacturer name of computer system(hardware) , processor

Hi All, Can someone let me know the method or set of commands by which i can retrive manufacturer name of computer system (hardware of machine ) and manufacturer of processor. i get below information when fired psrinfo command : psrinfo -vp The physical processor has 1 virtual processor... (6 Replies)
Discussion started by: omkar.jadhav
6 Replies
REBOOT(8)						      System Manager's Manual							 REBOOT(8)

NAME
reboot - stopping and restarting the system SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ] /sbin/halt [ -lqndars ] /sbin/fastboot [ -lqndarsRD ] DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is necessary to read it in from disk or tape each time it is to be boot strapped. Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first. Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation. Options to reboot are: -l Don't try to tell syslogd(8) what's about to happen. -q Reboot quickly and ungracefully, without shutting down running processes first. -n Don't sync before rebooting. This can be used if a disk or the processor is on fire. -h Don't reboot, simply halt the processor. -d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic. -a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix). -r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD. -s Don't enter multi-user mode after system has rebooted - stay in single user mode. -f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt) flag. -D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program. -R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the root/swap/pipe/dump device. Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this case. Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively. Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user operations. SEE ALSO
autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8) 3rd Berkeley Distribution May 24, 1996 REBOOT(8)
All times are GMT -4. The time now is 12:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy