Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Quad Core and Two duel core



Ah yes those daft old errors, I've uploaded a new version since I noted that
servers where having trouble for no good reason (gtk isn't required) should
now work. sorry about that.

And thanks again for the sample data.

On 04/06/07, Jarod Wilson <jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org> wrote:
>
> On Jun 04, 2007, at 23:04, Martin Owens wrote:
>
> > wholly mother of random fluctuations in the space time continuum
> > bat man!
> >
> > That's perfect data, does it run HAL/dbus by any chance?
>
> Yup, the system is running RHEL5.
>
> > Thanks for the data, if your able to run
> > http://www.dohickey-project.com/debugger.tar.bz2 it would be fantastic
> > but a lot of these kinds of exotic machines don't have HAL installed
> > since it's mostly a desktop service.
>
> Here come the results of running the various debugger bits on it:
>
> [root at es7000-01 debugger]# ./list-system.py
> Processors:
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
>    Genuine Intel(R) CPU 3.40GHz
> Traceback (most recent call last):
>    File "./list-system.py", line 12, in ?
>      slots = Dohickey.system.Slots()
>    File "/root/debugger/Dohickey/system.py", line 80, in __init__
>      for slot in dmi['slot']:
> KeyError: 'slot'
>
> [root at es7000-01 debugger]# ./list-hardware.py
> Traceback (most recent call last):
>    File "./list-hardware.py", line 5, in ?
>      import gtk
>    File "/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py",
> line 76, in ?
>      _init()
>    File "/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py",
> line 64, in _init
>      _gtk.init_check()
> RuntimeError: could not open display
>
> (I'm ssh'd in w/o X forwarding, can try w/X forwarding tomorrow if
> it'll help)
>
>
> [root at es7000-01 debugger]# ./hardware-debug.sh
> Traceback (most recent call last):
>    File "../list-system.py", line 12, in ?
>      slots = Dohickey.system.Slots()
>    File "/root/debugger/Dohickey/system.py", line 80, in __init__
>      for slot in dmi['slot']:
> KeyError: 'slot'
> Traceback (most recent call last):
>    File "../list-hardware.py", line 5, in ?
>      import gtk
>    File "/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py",
> line 76, in ?
>      _init()
>    File "/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py",
> line 64, in _init
>      _gtk.init_check()
> RuntimeError: could not open display
> es7000-01.lab.boston.redhat.com-debug/
> es7000-01.lab.boston.redhat.com-debug/dmi.txt
> es7000-01.lab.boston.redhat.com-debug/cpuinfo.txt
> es7000-01.lab.boston.redhat.com-debug/bios.txt
> es7000-01.lab.boston.redhat.com-debug/ioports.txt
> es7000-01.lab.boston.redhat.com-debug/hardware.txt
> es7000-01.lab.boston.redhat.com-debug/system.txt
>
> Full results:
>
> http://people.redhat.com/jwilson/misc/cpunotes/
> es7000-01.lab.boston.redhat.com-debug.tar.bz2
>
> Can do the dual dual-core box and a quad-core tomorrow if you like.
>
>
> > P.S Wow
>
> You prefer single-socket quad-core or dual-socket quad-core? :)
>
>
> > On 04/06/07, Jarod Wilson <jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org> wrote:
> >> On Jun 04, 2007, at 21:55, Martin Owens wrote:
> >>
> >> > Hi all,
> >> >
> >> > Does anyone have access to machines that are x86 based and have
> >> either
> >> > 4 cores in 1 cpu or 2 cpus each with 2 cores? or even something
> >> with
> >> > more than 2 cpus (although I've no heard of any x86 machines like
> >> > this)
> >> >
> >> > I need output of /proc/cpuinfo and the dmidecode output so I can
> >> test
> >> > some code against these kinds of variables. I already have
> >> hundreds of
> >> > single cpu, duel cpu and duel core examples but nothing bigger.
> >>
> >> You can find an interesting pair here:
> >>
> >> http://people.redhat.com/jwilson/misc/cpunotes/
> >>
> >> The es7000 is a 16-socket, dual-core, hyperthreading system (64
> >> "cpus"). The precision 490 is a dual dual-core system (ht-capable,
> >> but its shut off). I can get some additional exotic examples if ya
> >> need. :)
> >>
> >> --
> >> Jarod Wilson
> >> jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org
> >>
> >>
> >>
> >> _______________________________________________
> >> Discuss mailing list
> >> Discuss-mNDKBlG2WHs at public.gmane.org
> >> http://lists.blu.org/mailman/listinfo/discuss
> >>
> >>
>
> --
> Jarod Wilson
> jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org
>
>
>
> _______________________________________________
> Discuss mailing list
> Discuss-mNDKBlG2WHs at public.gmane.org
> http://lists.blu.org/mailman/listinfo/discuss
>
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.







BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org