Date: Thu, 09 Oct 2003 20:39:09 -0400 From: Mike Tancsa <mike@sentex.net> To: Murray Stokely <murray@freebsd.org>, stable@freebsd.org Subject: Re: [Peter_Losher@isc.org: More freebsd.isc.org issues...] Message-ID: <6.0.0.22.0.20031009202308.0879ec30@209.112.4.2> In-Reply-To: <20031010001355.GA93439@freebsdmall.com> References: <20031010001355.GA93439@freebsdmall.com>
next in thread | previous in thread | raw e-mail | index | archive | help
We had one system locking up with nothing in the logs. As it was
inproduction, I didnt have too much of a chance to track it down. I
speculated it was some issue with not having IPDIVERT in the kernel while
ipfilter and IPFW2 were in the kernel. Adding IPDIVERT in and turning off
NAT on ppp and letting ipnat do its work over the PPPoE connection did the
trick to stop it from locking up. The box has been small s stable since
then. This is from an Oct 2 snapshot.
The only other issue that comes to mind is tegge made a patch to allow
maxim@macomnet.ru do a make -j64 work on a low RAM situation. But that
corrected panics, not lockups.
---Mike
At 08:13 PM 09/10/2003, Murray Stokely wrote:
>Has anyone seen similar hangs on -STABLE? I'd really like to get to
>the bottom of this before we release 4.9 if possible.
>
> - Murray
>
>----- Forwarded message from Peter Losher <Peter_Losher@isc.org> -----
>
>From: Peter Losher <Peter_Losher@isc.org>
>Subject: More freebsd.isc.org issues...
>To: Bosko Milekic <bmilekic@technokratis.com>
>Cc: Peter Losher <Peter_Losher@isc.org>,
> Murray Stokely <murray@freebsdmall.com>, mwlucas@FreeBSD.org
>Date: Fri, 3 Oct 2003 02:06:44 +0000 (UTC)
>
>It happened again today - Any ideas?
>
>(heading up to power cycle the box now)
>
>On Fri, 26 Sep 2003, Paul Vixie wrote:
>
> > today sf1.isc.org (2/3 of ftp.freebsd.org) was down for a few hours.
> >
> > panic: spin lock sched lock held by 0x86a69be0 for > 5 seconds
> > cpuid = 0; lapic.id = 00000000
> > panic: spin lock sched lock held by 0x86a69be0 for > 5 seconds
> > cpuid = 0; lapic.id = 00000000
> > panic: spin lock sched lock held by 0x86a69be0 for > 5 seconds
> > cpuid = 0; lapic.id = 00000000
> > panic: spin lock sched lock held by 0x86a69be0 for > 5 seconds
> > cpuid = 0; lapic.id = 00000000
> > ...
> >
> > anything that requires us to drive all the way up and hit a reset
> > button is automatically bad for uptime. just so you know.
> >
>
>--
>Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow"
>
>----- End forwarded message -----
>_______________________________________________
>freebsd-stable@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.0.22.0.20031009202308.0879ec30>