[snip]

Thank you for suggestion, I'm re-installing Gentoo and definitely run
these tools.

For sure I have some hardware "memory" problem as my latest error
message is:

"Uhhuh. NMI received. Dazed and confused, but trying to continue 
You probably have a hardware problem with your RAM chips
NMI: IOCK error (debug interrupt?)
CPU 0
Modules linked in: evdev via_rhine mii parport_pc parport ahci sata_uli
sata_sis sata_sx4 sata_nv sata_via sata_svw sata_sil sata_promis libata
sbp2 ohci1934 ieee1394 usb_storage ohci_hcd uhci_hcd ehci_hcd usbcore
Pid: 5626, comm: rsync Not tainted 2.6.11-gentoo-r3-k8
RIP: 0010:[<ffff....."

Though I've run memtest86 two day ago and 17-passes went without any
errors.
 
-- 
#Joseph

> 
> There are a few tools that will allow you to do some diagnosing.
> 
> These will isolate your harddrive and drive controllers.
> 
>  app-benchmarks/bonnie (2.0.6):  Performance Test of Filesystem I/O using 
> standard C library calls.
>  app-benchmarks/bonnie++ (1.93c):  Hard drive bottleneck testing benchmark 
> suite.
> 
> If is is the motherboard, it should fall over pretty quick.
> 
> Another tool I like is - 
> 
>   app-benchmarks/stress (0.18.6):  Imposes stressful loads on different 
> aspects of the system.
> 
> You'll have to add - app-benchmarks/stress x86, to your 
> /etc/portage/package.keywords
> as they don't have the amd64 keyword in the ebuild.  It builds and runs fine. 
> 
> Stress allows you to load all or parts of the system up for a defined period 
> of time.  It's
> even possible to run the system out of resources.  It's a real nice test of 
> system stabilty.
> All except the Xserver and that's easy to add by running 3 of the rss-glx 
> screensavers
> from a term while running stress.  And if you make the virtual memory 
> component large
> enough at runtime, the system will start swapping.
> 
> This line will get the load up to about 20 and cause about 500MB of swapping
> to occur on a 1P amd64 system with 1 GB of main memory -
> 
>   stress --cpu 16 --io 4 --vm 2 --vm-bytes 1024M --timeout 60s -d 2
> 
> Change the timeout to be around 5 minutes or 600 seconds.  Get a tail -f 
> /var/log/messages
> or use root-tail.  And get a top running in another term.
> 
> Bob
> -  

-- 
gentoo-user@gentoo.org mailing list

Reply via email to