-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Jan 20, 2006 at 08:38:09AM -0000, Plant, Dean wrote:
> Rodrigo Barbosa wrote:
> >>> Have you tried disabling hyperthreading? I had suffered this problem
> >>> when we started buying Intel Xeon's, disabling HT'ing seemed to fix
> >>> the problem for me.
> >>
> >> Some people suggested that too. I'm asking for two of these systems
> >> to be sent back from our remote data center. I'll try it then.
> >>
> >> Did you just ended up running without hyperthreading? Did you ever
> >> find a solution? It seems an awful waste if you can't use it.
> >
> > Disabling HT only solves it on single processor systems.
>
> In my case it fixed our dual processor systems (Dell PE2650) but to be
> honest I was never quite sure if it was an OS patch or HT'ing. I just
> disable HT'ing, build and they just work, I have not seen this problem
> for a while now.
Did't solve for me on a Dual Xeon. The problem was reduced, happens
less frequently, but still happens :(
[]s
- --
Rodrigo Barbosa <rodrigob@xxxxxxxxxxxxxxx>
"Quid quid Latine dictum sit, altum viditur"
"Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFD0Q2DpdyWzQ5b5ckRAri/AJ9DEDPlWNKrT9S7Yha4NImPVw+yaACeMQuO
/KnaeI7ZJbM4uFskZPe7vyA=
=OyJl
-----END PGP SIGNATURE-----
