Date: Fri, 20 Aug 2004 12:57:45 +0200 (CEST) From: =?iso-8859-1?q?Laurentiu=20Pancescu?= <plaur_27@yahoo.de> To: "Chad Leigh -- Shire.Net LLC" <chad@shire.net> Cc: freebsd-questions@freebsd.org Subject: Re: dealing with deffective RAM Message-ID: <20040820105745.75718.qmail@web50804.mail.yahoo.com> In-Reply-To: <03DE37B3-F276-11D8-B2C6-003065A70D30@shire.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--- "Chad Leigh -- Shire.Net LLC" <chad@shire.net> schrieb: > What motherboard and chipset? It's a Chaintech 7AJA0, based on VIA KT133. The chipset has some known problems: there was a registry patch for Windows 2000, that avoided hard hangs (the IDE controller and the processor ended up waiting for each other to free the PCI bus, for periods between a few seconds and three hours, according to the documentation). They claimed no other OS was affected by this (they had Linux drivers on the CD, so I assume "other" included Linux). When trying to install Windows 2000, this happened almost every time, either during hardware detection, or during the final DCOM registration. It happened just once or twice to get hardware hanging under Linux, in about 2.5 years of exclusive usage (even under heavy load). Since I use FreeBSD 4, about 6 months ago), I didn't get any hardware hangs, but some programs sigsegv-ed unexpectedly, and unreproducible. Maybe this is related to the memory, not the chipset issue. > We replaced the motherboard with something else. It looks like the best thing to do, imho. I hope high-quality boards from Asus, Epox or MSI don't exhibit such problems. Laurentiu ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040820105745.75718.qmail>