Le 01.10.2005 09:13:20, Simo Kauppi a écrit :
On Thu, Sep 29, 2005 at 01:18:34AM -0400, Alan Manning wrote:
> Hi. I am having stability issues with the A8V as well. Most
[ ... ]
I'm not sure if this is related in anyway to your problem. I use MSI
K8T
(with VIA K8T800Pro chipset) and there see
On Thu, Sep 29, 2005 at 01:18:34AM -0400, Alan Manning wrote:
> Hi. I am having stability issues with the A8V as well. Most especially I
> can't manually set my ram to 400 instead of 333 even though I am running
> corsair twinx perf ram. Did you even find any sort of resolution for this?
> I'm runn
On Thu, Sep 29, 2005 at 04:04:11PM +, Jean-Luc Coulon (f5ibh) wrote:
> If you have a look in the real settings when set to auto, you will see
> that all the timing parameters are very relaxed.
I don't mind relaxed as long as it is very stable.
> A simple run of memtest will tell you the tru
Le 29.09.2005 17:52:30, Lennart Sorensen a écrit :
On Thu, Sep 29, 2005 at 01:43:25PM +, Jean-Luc Coulon (f5ibh)
wrote:
> I've a 3500+ with twin 2x512k Corsair 3200C2.
> I've experienced some problems:
> I had an Antenc Sonata (380W PSU) and the PSU was not stable. It has
> been replaced wit
On Thu, Sep 29, 2005 at 01:43:25PM +, Jean-Luc Coulon (f5ibh) wrote:
> I've a 3500+ with twin 2x512k Corsair 3200C2.
> I've experienced some problems:
> I had an Antenc Sonata (380W PSU) and the PSU was not stable. It has
> been replaced with a SonataII with more power and stable PSU.
>
> I
Le 29.09.2005 15:29:21, Lennart Sorensen a écrit :
On Thu, Sep 29, 2005 at 01:18:34AM -0400, Alan Manning wrote:
> Hi. I am having stability issues with the A8V as well. Most
especially I
> can't manually set my ram to 400 instead of 333 even though I am
running
> corsair twinx perf ram. Did you
On Thu, Sep 29, 2005 at 01:18:34AM -0400, Alan Manning wrote:
> Hi. I am having stability issues with the A8V as well. Most especially I
> can't manually set my ram to 400 instead of 333 even though I am running
> corsair twinx perf ram. Did you even find any sort of resolution for this?
> I'm runn
Hi. I am having stability issues with the A8V as well. Most especially
I can’t manually set my ram to 400 instead of 333 even though I am
running corsair twinx perf ram. Did you even find any sort of resolution for
this? I’m running a gf6800gt and Athlon 3800 as well. I was thinking
maybe m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
le 26.07.2005 10:02:07, Matthias Wenthe a écrit :
Matthias Wenthe schrieb:
Jean-Luc Coulon (f5ibh) wrote:
[ ... ]
to AUTO, ran my test for about 24 hours now and so far the system
runs like a charm without any errors. I would not even go so fa
Matthias Wenthe schrieb:
Jean-Luc Coulon (f5ibh) wrote:
1) kernel compilation test with the following script:
#!/bin/tcsh
# ramtest
#
make ARCH=i386 bzImage
foreach i (0 1 2 3 4 5 6 7 8 9)
foreach j (0 1 2 3 4 5 6 7 8 9)
foreach k (0 1 2 3 4 5 6 7 8 9)
( make c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 25.07.2005 13:30:20, Mattias Wadenstein a écrit :
On Thu, 21 Jul 2005, Erik Mouw wrote:
On Wed, Jul 20, 2005 at 11:32:33PM -0700, Juan Ortega wrote:
Why dont you simply use memtest86?
Because memtest86 doesn't catch all memory errors, while a
On Thu, 21 Jul 2005, Erik Mouw wrote:
On Wed, Jul 20, 2005 at 11:32:33PM -0700, Juan Ortega wrote:
Why dont you simply use memtest86?
Because memtest86 doesn't catch all memory errors, while a kernel
compile stresses the system in ways memtest86 doesn't. Some memory
errors only happen when th
On Thu, 21 Jul 2005, Erik Mouw wrote:
On Wed, Jul 20, 2005 at 11:32:33PM -0700, Juan Ortega wrote:
Why dont you simply use memtest86?
Because memtest86 doesn't catch all memory errors, while a kernel
compile stresses the system in ways memtest86 doesn't. Some memory
errors only happen when t
On Fri, Jul 15, 2005 at 01:25:55PM +0200, Matthias Wenthe wrote:
> I recently set up a new machine as a mail server for our company
> (aprox. 1000 Users with 60 GByte Traffic/month). Hardware as follows
>
> Asus A8V Deluxe Mainboard,
> nVidia graphic card (NV5M64 [RIVA TNT2 Model 64/Model 64 Pro]
Jean-Luc Coulon (f5ibh) wrote:
1) kernel compilation test with the following script:
#!/bin/tcsh
# ramtest
#
make ARCH=i386 bzImage
foreach i (0 1 2 3 4 5 6 7 8 9)
foreach j (0 1 2 3 4 5 6 7 8 9)
foreach k (0 1 2 3 4 5 6 7 8 9)
( make clean;make ARCH=i386 bzImage
On Wed, Jul 20, 2005 at 11:32:33PM -0700, Juan Ortega wrote:
> Why dont you simply use memtest86?
Because memtest86 doesn't catch all memory errors, while a kernel
compile stresses the system in ways memtest86 doesn't. Some memory
errors only happen when there is IO going on at the same time, whic
Hi,
Why dont you simply use memtest86?
I have the same configuration the test worked fine for a whole night.
The only thing I had to change to have my memory recognize properly was the
speed (from auto to
200MHz for DDR 400)
--- "Jean-Luc Coulon (f5ibh)" <[EMAIL PROTECTED]> wrote:
> -BEG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 20.07.2005 21:32:17, Matthias Wenthe a écrit :
Jean-Luc Coulon wrote:
1) kernel compilation test with the following script:
#!/bin/tcsh
# ramtest
#
make ARCH=i386 bzImage
foreach i (0 1 2 3 4 5 6 7 8 9)
foreach j (0 1 2 3 4 5 6
Jean-Luc Coulon wrote:
1) kernel compilation test with the following script:
#!/bin/tcsh
# ramtest
#
make ARCH=i386 bzImage
foreach i (0 1 2 3 4 5 6 7 8 9)
foreach j (0 1 2 3 4 5 6 7 8 9)
foreach k (0 1 2 3 4 5 6 7 8 9)
( make clean;make ARCH=i386 bzImage > log."$i
Alexander Voss wrote:
1) kernel compilation test with the following script:
#!/bin/tcsh
# ramtest
#
make ARCH=i386 bzImage
foreach i (0 1 2 3 4 5 6 7 8 9)
foreach j (0 1 2 3 4 5 6 7 8 9)
foreach k (0 1 2 3 4 5 6 7 8 9)
( make clean;make ARCH=i386 bzImage > log."$i"$
Matthias Wenthe wrote:
> I recently set up a new machine as a mail server for our company
> (aprox. 1000 Users with 60 GByte Traffic/month). Hardware as follows
>
> Asus A8V Deluxe Mainboard,
> nVidia graphic card (NV5M64 [RIVA TNT2 Model 64/Model 64 Pro],
> 2 Infineon 1 GByte DDR-RAM, PC 3200
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 15.07.2005 13:25:55, Matthias Wenthe a écrit :
[ ... ]
Test 1) produces randomly premature compiler stops in all 64 bit
kernels and in kernel 2.4.27.
In the error logs I often find "Speicherzugriffsfehler" (memory
access failure (hopefully
22 matches
Mail list logo
