Gonzalo Servat wrote:
FWIW, the system is running Gentoo kernel 2.4.19,
<dons asbestos suit> {:-) that is obviously your problem. One of your libaries needs a recompile </asbestos suit>
:-)
Did you say new CPU & mobo? But you didn't list your mobo.
It's a Gigabyte GA-7N400-L1
HW freeze up problem solving 101.
(a)The easy 1 on 1 method.
Replace each and every hardware item one at a time for a period, say 24 hours (a week sounds better in your case since it only happens once a day), until you replace the item that is broke = your system no longer has that fault.
Yeah, but as I said it only started happening after the upgrade to a new mobo/CPU/RAM. What I should do is stick the old motherboard back in for a week and see if happens again. If it doesn't, at least I'll know it's something in the new combo.
Have you done the basic cable/chip wiggle test? (remove+replace),3, * every cable and chip[1].
Sorry Terry, I don't follow this "(remove+replace),3,*" process?
Checked error/message logs?. A faulty CD drive/HD on the way out can do this (timeout messages)
Sure did. Absolutely nothing that would indicate a fault in the logs.
Regards, Gonzalo
-- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
