Date: Fri, 21 May 2004 16:01:45 -0600 From: Nathan Kinkade <nkinkade@ub.edu.bz> To: Gary Kline <kline@thought.org> Cc: FreeBSD Mailing List <freebsd-questions@FreeBSD.ORG> Subject: Re: relatively urgent question (about X) Message-ID: <20040521220145.GM21801@gentoo-npk.bmp.ub> In-Reply-To: <20040521205102.GC34378@tao.thought.org> References: <20040521175046.GA557@tao.thought.org> <20040521204058.GK21801@gentoo-npk.bmp.ub> <20040521205102.GC34378@tao.thought.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--qySB1iFW++5nzUxH Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 21, 2004 at 01:51:02PM -0700, Gary Kline wrote: > On Fri, May 21, 2004 at 02:40:58PM -0600, Nathan Kinkade wrote: > > On Fri, May 21, 2004 at 10:50:46AM -0700, Gary Kline wrote: > > > For some months I've had increasing troubles with my=20 > > > 4.9/4.10 abruptly crashing. This morning I found my > > > workhorse server, tao, down and hung up while trying to > > > fsck /usr. I cleaned everything thoroughly and then > > > started xdm. The grey screen showed, the mouse was frozen; > > > after 30 seconds, BOOM. Another crash. After yet=20 > > > another round of fsck's, I tried startx. To see what=20 > > > errs might kill the X11 boot. No: same blank grey screen, > > > same frozen mouse,same OS crash. > > >=20 > > > I tried /stand/sysinstall to reconfigure X. No luck. > > > I'm now doing my next stable sup upgrade and am doing > > > yet another buildworld && buildkernel. > > >=20 > > > I doubt this will resolve the X Window snafu, tho. So::: > > > what x11/*XFree* ports do I have to fetch/build/install?? > > > ((I'm assuming the reason for the crash was X-related, > > > but this is only a first-SWAG.) Also, if anybody has had a=20 > > > similar problem, please let me know. > > >=20 > > > tia, people, > > >=20 > > > gary, ssh'd in from ethic.thought.org > >=20 > > Could this be a hardware issue? All other things being mostly constant > > I wouldn't think that software usually all of a sudden goes bad or gets > > misconfigured. Possibly it got corrupted on the disk for some reason, > > but then I might wonder what caused the disk to get corrupted in the > > first place. How about trying a new video card and/or peripherals? > > This is assuming that your setup was working one day and then the next > > went bad, or if it is flaky and intermittent. > >=20 > > Nathan >=20 >=20 > Yes, it certainly could be a bad disc or even bad DIMM. > I'm running an i815 motherboard that had video/audio > built in. But the drive may have gotten kicked or bumped. > How can I test a 40G drive?? >=20 > gary Well, any program checking every single block on a 40GB drive would definitely take a long time to complete. I was more suggesting that a hardware problem might be causing the lockup, exclusive of the hardrive. I have seen a bad video card cause X to completely crash a system while X is intitializing. If you had an extra video card around it might be worth plugging it in and giving it a try. Nathan --qySB1iFW++5nzUxH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFArnxJO0ZIEthSfkkRApABAJsEyzTfyncnBB9zfaQKu2T6d8yr4QCgsmxq n+ZbbPMeaWb3uvPC/v2Ax5I= =6Sqy -----END PGP SIGNATURE----- --qySB1iFW++5nzUxH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040521220145.GM21801>