Re: [ES40-developers] Issue with 2nd CPU
Status: Alpha
Brought to you by:
iamcamiel
From: Hittner, D. T. <dav...@ng...> - 2008-03-19 15:12:09
|
Or.... was this because my dual-core (without HyperThreading) CPU was pegged on both cores simulating 2 CPUs and the 21143 thread (literally) just timed out executing the commands? Dave > -----Original Message----- > From: es4...@li... > [mailto:es4...@li...] On > Behalf Of Hittner, David T. > Sent: Wednesday, March 19, 2008 11:04 AM > To: ES40 Developer Discussions > Subject: [ES40-developers] Issue with 2nd CPU > > I added a second CPU (just to see what it would do), and got > the following console output - it shows an error on the > Network card, which does not occur when only one CPU is configured. > > Is there something in the CPU arbitration that we've missed > that prevents the 2nd CPU from running the system diagnostics > simultaneously with the primary CPU? > > Dave > -------------------------------------------------------------- > ---------- > ---- > This is serial port #0 on AlphaSim > > OpenVMS PALcode V1.98-104, Tru64 UNIX PALcode V1.92-105 > > starting console on CPU 0 > initialized idle PCB > initializing semaphores > initializing heap > initial heap 240c0 > memory low limit = 1b0000 heap = 240c0, 17fc0 initializing > driver structures initializing idle process PID initializing > file system initializing hardware initializing timer data > structures lowering IPL CPU 0 speed is 800 MHz create > dead_eater create poll create timer create powerup access > NVRAM Memory size 128 MB testing memory ... > probe I/O subsystem > probing hose 1, PCI > probing hose 0, PCI > probing PCI-to-ISA bridge, bus 1 > bus 0, slot 3 -- pka -- NCR 53C810 > bus 0, slot 4 -- ewa -- DE500-BA Network Controller starting > drivers entering idle loop Partition 0, Memory base: > 000000000, size: 008000000 initializing GCT/FRU at 1c8000 > Initializing pka ewa Memory Testing and Configuration Status > Array Size Base Address Intlv Mode > --------- ---------- ---------------- ---------- > 0 128Mb 0000000000000000 4-Way > > 128 MB of System Memory > Testing the System > Testing the Disks (read only) > Testing the Network > > *** Error (ewa0), Mop loop message timed out from: 00-00-00-ff-ff-ff > *** List index: 0 received count: 3 expected count 4 > > *** Error (ewa0), Mop loop message timed out from: 00-00-00-ff-ff-ff > *** List index: 1 received count: 3 expected count 4 > > *** Error (ewa0), Mop loop message timed out from: 00-00-00-ff-ff-ff > *** List index: 2 received count: 3 expected count 4 > > *** Error (ewa0), Mop loop message timed out from: 00-00-00-ff-ff-ff > *** List index: 3 received count: 3 expected count 4 > > *** Error (ewa0), Mop loop message timed out from: 00-00-00-ff-ff-ff > *** List index: 4 received count: 3 expected count 4 > > *** Error (ewa0), Mop loop message timed out from: 00-00-00-ff-ff-ff > *** List index: 5 received count: 3 expected count 4 > > Loop Reply from: 00-00-00-ff-ff-ff > Loop Reply from: 00-00-00-ff-ff-ff > AlphaServer ES40 Console V7.2-1, built on Jun 9 2006 at 15:36:48 > P00>>> > -------------------------------------------------------------- > ---------- > ---- > > -------------------------------------------------------------- > ----------- > This SF.net email is sponsored by: Microsoft Defy all > challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |