From owner-freebsd-questions Tue Jul 29 11:02:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA03027 for questions-outgoing; Tue, 29 Jul 1997 11:02:41 -0700 (PDT) Received: from stcgate.statcan.ca (stcgate.statcan.ca [142.206.192.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA03014 for ; Tue, 29 Jul 1997 11:02:37 -0700 (PDT) Received: (from root@localhost) by stcgate.statcan.ca (8.6.11/8.6.9) id NAA17600; Tue, 29 Jul 1997 13:42:00 -0400 Received: from stcinet.statcan.ca(142.206.128.146) by stcgate via smap (V1.3) id sma017478; Tue Jul 29 17:41:34 1997 Received: from statcan.ca by statcan.ca (SMI-8.6/SMI-SVR4) id NAA23238; Tue, 29 Jul 1997 13:41:02 -0400 Received: from smtpsha.statcan.ca by bora2.statcan.ca (SMI-8.6/SMI-SVR4) id NAA11460; Tue, 29 Jul 1997 13:02:35 -0400 Received: from smtp_gate.iusd.statcan.ca by smtpsha.statcan.ca (SMI-8.6/SMI-SVR4) id NAA03909; Tue, 29 Jul 1997 13:10:28 -0400 Message-Id: <199707291710.NAA03909@smtpsha.statcan.ca> Date: Tue, 29 Jul 1997 14:14:00 -0400 From: "Jeays, Mike" Subject: Re: Crashed X-server To: Doug White , Mike Jeays Cc: questions X-Mailer: Worldtalk (NetConnex V4.00a)/MIME Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It definitely happened with the older Trident board, and more than once. It seems closely related to very high demands on swap space. Next time I re-install, I will make more. (I currently have 16 MB of real memory, and I think 42 MB of disk swap space - whatever came out of the default sysinstall.) I have a Gigabyte motherboard; I don't remember the model number, and can see any printing on it to tell me what model it is. I had a home-brewed CPU monitor running at the time of the crash, and noticed it got killed first, presumably by FreeBSD randomly killing processes. Then xclock stopped running. After that, everything froze dead; the mouse and all key combinations, and the contents of the display. I have since proved that only the X-server was dead, as I was able to telnet into it from work this morning, and it seemed fine. (I can't run a remote X-terminal from work). Very few processes were running, and nothing related to X or fvwm. ---------- From: Doug White To: Mike Jeays Cc: Bryan K. Ogawa; questions Subject: Re: Crashed X-server Date: Tuesday July 29, 1997 12:49PM On Tue, 29 Jul 1997, Mike Jeays wrote: > > >From what I understand, 24bpp is more prone to bugginess than 32/8 > > bits. Mike, if you are experiencing hard crashes, I am curious if you > > are using 24bpp or 8/32? > > > > -- > > bryan k ogawa http://www.primenet.com/~bkogawa/ > > > > I am using an ATI Mach64 card with 2MB, at 16bpp. I have had similar > lockups with an old Trident 8900C at 8bpp. The ATI will work at 24bpp in > 800x600, but 1024x768 is beyond it (and/or my monitor), as far as I can > tell. Well, I can discount the video card/server combo since this is what I have. If it happens w/ another board, perhaps we need to dig a bit deeper: do you know what motherboard you have? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo