Date: Sat, 4 Apr 1998 08:24:29 -0500 (est) From: Vince Vielhaber <vev@michvhf.com> To: Steve Grandi <grandi@noao.edu> Cc: bugs@FreeBSD.ORG Subject: Re: Running out of places to turn... Message-ID: <Pine.OS2.3.96.980404081250.40A-100000@paprika.michvhf.com> In-Reply-To: <Pine.LNX.3.96.980403222456.4282B-100000@mirfak.tuc.noao.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 3 Apr 1998, Steve Grandi wrote:
> On Fri, 3 Apr 1998, Vince Vielhaber wrote:
>
> >
> > For a quick rundown, I installed 2.2.5 from CD on a P150 (Tyan MB) with
> > 256MB Ram, a 4GB and 6.4GB IDE and a pair of 9GB SCSI drives connected
> > to a 2940UW (that I have set to a max transfer rate of 10Mbps). This is
> > a news machine and I have the the ccd driver configured into the kernel
> > and I'm running the 2-9GB drives as one 18GB drive. The other kernel
> > changes are maxusers set to 256 and the mem size items set at 262100.
> >
>
> I was having similar problems....
>
> How long does the expire take? My system would work fine as long as the
> expire would take a few minutes; but then something would happen and the
> expires would start taking 8 hours! And the system would soon crash;
> somtimes a hard lock up and sometimes with the same "page fault in Kernel
> mode" that you see.
I'm fairly certain it's past that point. I ran a news.daily manually and
it passed that point within an hour or so (right now there are no feeds
going in and no readers connecting). News.daily starts about midnight and
the last hourly report I got (I have a cron job doing ctlinnd mode every
hour at 19 after) was a 5:19am. That's well into the fastrm stage. In
case you didn't catch on, yes it crashed again last nite. This time it
was a priveleged instruction fault while in kernel mode. And it goes on
to say it was a fatal double fault then panic:double fault. Double fault
seems fitting, I feel like I'm in a tennis match with this thing :)
> I finally figured it out...at least my system hasn't crashed for over a
> month. When expire is rebuilding the history file, it tries to fit the
> history.pag file in core. If it can't, expire resorts to using a disk
> file which is horribly inefficient and stresses the system something
> fierce...apparently enough to tickle a latent bug in FreeBSD that causes
> a subsequent crash.
>
> The solution, a common one for 2.2.5+ problems, is to edit /etc/login.conf;
> in particular the news entry. Here is what my entry now looks like:
>
> #
> # Settings used by news subsystem
> #
> news:\
> :path=/usr/local/news/bin /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin:\
> :cputime=infinity:\
> :datasize=infinity:\
> :datasize-cur=infinity:\
> :stacksize=64M:\
> :stacksize-cur=64M:\
> :memorylocked=64M:\
> :memoryuse=128M:\
> :memoryuse-cur=128M:\
> :filesize=infinity:\
> :coredumpsize=infinity:\
> :openfiles=512:\
> :maxproc=128:\
> :priority=0:\
> :requirehome@:\
> :umask=022:\
> :tc=auth-root-defaults:
Mine's not far from this, I may have datasize and memoryuse limited to
200MB and the rest are infinity.
The last crash occurred while expire wasn't running, this time it did,
so I'm going to (at least temporarily) suspect hardware since it's all
new. Sadly I'm beginning to suspect the motherboard as I'm remembering
that a friend of mine got the same one from the same source and it too
failed in a very short time - but first I'm going to try the RAM and
controller since I have spares.
Thanks,
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Searchable Campground Listings http://www.camping-usa.com
"I'm just not a fan of promoting stupidity!
We have elected officials for that job!" -- Rock
==========================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OS2.3.96.980404081250.40A-100000>