http://downloadmirror.intel.com/1334...leaseNotes.pdf

There it is, the smoking gun. Release 1676... wow.. .that's an obscure
one.

Thanks you all again!
--
David E. Cross

On Wed, 20 Jun 2007, David Cross wrote:

> Thanks all.. it was the memory. It wasn't "bad".. .memtest (or anythign else
> didn't actually fail, the only way I could tell is with a stopwatch and
> watching loop times)... but pulling 1/2 of the RAM fixed it.. it doesn't
> matter which set was in, as long as both sets its fine.
>
> --
> David E. Cross
>
> On Wed, 20 Jun 2007, Jeremy Chadwick wrote:
>
>> On Wed, Jun 20, 2007 at 10:24:01AM -0400, David Cross wrote:
>>> Ok the subject line is misleading.. but I don't know how else to put it.
>>> I
>>> have a machine on which SOME programs are slow. VERY SLOW. Other
>>> programs
>>> run just fine. I cannot seem to find the source of the problem.

>>
>> Two things I can think of:
>>
>> 1) Memory issues -- memtest86 could help show this kind of problem. Try
>> removing memory, and if the problem continues, swapping the pair you
>> removed with the pair that's installed.
>>
>> 2) Disk issues -- reading /usr/bin/sed off the disk where there's a
>> soon-to-be-bad block. The disk may be trying to work around it and
>> doing a delayed read (inducing EC). This seems less likely to be the
>> case than bad memory, but I've seen it happen.
>>
>> --
>> | Jeremy Chadwick jdc at parodius.com |
>> | Parodius Networking http://www.parodius.com/ |
>> | UNIX Systems Administrator Mountain View, CA, USA |
>> | Making life hard for others since 1977. PGP: 4BD6C0CB |
>>

>

_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis...reebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"