Both CPU modules are good as I can boot using either in slot 0 - does
this mean that
the main board has a fault?
Are both CPUs the exact same speed?
Better yet if they're the exact same P/N as well.
There are two different kinds of 900 MHz CPUs and they can't be mixed and
matched.
If they're identical, then I'd say swap the slots the CPUs are in.
Should the error stick with slot 1, then it's probably the system board.
If the error moves to slot 0, then the new CPU is bad.
Re: CPU boot problem on 2.6.0-test3-bk8 ... the exact number of cpus you have will get testers able to boot until ...entries are bogus and alias the entries we actually want. ... send the line "unsubscribe linux-kernel" in ... (Linux-Kernel)
Re: PHP von Solaris Sparc slow ... Now why do I suspect that your 280R has 800Mhz cpus,... what *exact* test are you doing? ... -- http://www.blastwave.org/ for solaris pre-packaged binaries with pkg-get Organized by the author of pkg-get [Trim the no-bots from my address to reply to me by email!] ... (comp.unix.solaris)
Re: E450 only finding one processor ... > On boot up the system fails post on both processors but upon boot disk ... If not and your system board P/N is 501-2996, then it only supports 250/300 MHz CPUs.... I'm not sure what you consider slot 3 and what the OS calls slot 3 is likely different from how the system board is numbered. ... their both installed the right way and the dc-dc converters too (there are enough pictures stuck to the chassis to get that point across ... (comp.sys.sun.hardware)
Re: Sun blade 2000 2nd CPU module ... The system boots with a single module (I've tested booting using ... which uses the same family of system boards and CPUs as the Sun Blade ... This apparently burned out something on the system board which was ... (comp.sys.sun.hardware)
kernel trap 12 with interrupts disabled, 5.3-stable ... I have updated a system from FreeBSD 4.10 to 5.3 (I did a fresh new ... At the same time we put a new CPUs in there. ... page fault while in kernel mode ... add 2 new CPUs is more likely to reveal a RAM problem that was not known ... (freebsd-stable)
