Date: Sun, 22 Jan 1995 23:59:44 -0600 (CST) From: Joe Greco <jgreco@brasil.moneng.mei.com> To: hackers@FreeBSD.org Cc: ods-admin@ns.sol.net Subject: No pages? revisited (2.0R) Message-ID: <9501230559.AA13170@brasil.moneng.mei.com>
next in thread | raw e-mail | index | archive | help
Odd 2.0R problems revisited...? I have been working with a large local BBS to get them Daemonized. I convinced them to provide FreeBSD shell accounts by offering to supply a router for their Internet connection (freeing up the machine they'd been using - a 4MB 386DX/40). I provided them with a Northgate 386DX/25 motherboard with 5MB last nite, and all seemed well. The hard disk, controller, serial card, display controller were all taken from the DX/40. The motherboard, memory, and WD8003E were taken from sol.net spare inventory and have worked in the past. It crashed early this morning with the dreaded "No pages" (it had been working just dandy on the 386DX/40). They rebooted. It crashed again tonite. The machine is not doing anything at the time of crash, at least that I am aware of - other than acting as internetwork router. There is a chance that it had started /etc/daily this morning, but reports were that it crashed prior to that. Nobody logged in. Just running pppd, named, and trivial other standard stuff. Notes: I did notice at one point that the machine seemed to be mildly funky - it got in a state last night where it was working, but systat would report "Alternate system clock has died, reverting to pigs" on some screens, and vmstat's output was rather funky. We let it go, since it seemed otherwise happy. Systat/etc works now, after a power cycle. Also: the kernel was generated from a 2.0R source tree with a single patch previously supplied to me by David Greenman(I think) that tweaked some magic number in vm/vm_pageout.c from 4 to 16 (vm_pageout_free_min = 16 + something) because I had had a similar problem on my news server (I am not sure if the extra memory I added or the patch fixed it on my news server, but I haven't seen it happen again). So this really makes No Friggin' Sense. As an interim fix, I am going to put 8MB more in the machine tomorrow morning. I suspect some sort of hardware problem - because it WAS working great on their DX/40 - so I may end up swapping in a new motherboard. I'd hate to do that, because this is a great "New Life for Old Hardware." Comments/advice/etc welcome. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9501230559.AA13170>