From owner-freebsd-stable@FreeBSD.ORG Thu Oct 9 17:36:20 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63D7516A4B3; Thu, 9 Oct 2003 17:36:20 -0700 (PDT) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B7B743F3F; Thu, 9 Oct 2003 17:36:19 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.9p2/8.12.9) with ESMTP id h9A0aGU4036751; Thu, 9 Oct 2003 20:36:17 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.0.0.22.0.20031009202308.0879ec30@209.112.4.2> X-Sender: mdtpop@209.112.4.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Thu, 09 Oct 2003 20:39:09 -0400 To: Murray Stokely , stable@freebsd.org From: Mike Tancsa In-Reply-To: <20031010001355.GA93439@freebsdmall.com> References: <20031010001355.GA93439@freebsdmall.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Subject: Re: [Peter_Losher@isc.org: More freebsd.isc.org issues...] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Oct 2003 00:36:20 -0000 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 ----- > >From: Peter Losher >Subject: More freebsd.isc.org issues... >To: Bosko Milekic >Cc: Peter Losher , > Murray Stokely , 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"