Joseph wrote:
I went back to Sata Drive and started from scratch and when I tried to
do "emerge --sync" I got this error:
"Uhhuh. HMI 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....."
Is it problem with my standard memory or CPU memory cache?
I'v run memtest86 two day ago and 17-passes went without any errors.
Does your BIOS have any options for memory timings? If so, maybe you
can try to back those off to more conservative values.
Memtest86 would probably not show a problem with memory timings, because
it works in a very linear fasion. Compiling or heavy IO (like you get
with emerge --sync) accesses memory in a very random order.
-Richard
--
[email protected] mailing list
