From owner-freebsd-current@FreeBSD.ORG Tue Sep 16 14:09:19 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 512D416A4B3 for ; Tue, 16 Sep 2003 14:09:19 -0700 (PDT) Received: from falcon.midgard.homeip.net (h76n3fls24o1048.bredband.comhem.se [213.67.148.76]) by mx1.FreeBSD.org (Postfix) with SMTP id ECD8843FE0 for ; Tue, 16 Sep 2003 14:09:15 -0700 (PDT) (envelope-from ertr1013@student.uu.se) Received: (qmail 46521 invoked by uid 1001); 16 Sep 2003 21:09:14 -0000 Date: Tue, 16 Sep 2003 23:09:14 +0200 From: Erik Trulsson To: Scott Long Message-ID: <20030916210914.GA43230@falcon.midgard.homeip.net> Mail-Followup-To: Scott Long , Mike Silbersack , stable@freebsd.org, current@freebsd.org References: <3F66A446.7090408@freebsd.org> <20030916131622.N54869@news1.macomnet.ru> <20030916200513.R4917@gamplex.bde.org> <3F672308.1080909@freebsd.org> <3F673285.8080903@potentialtech.com> <3F6735B7.9050109@freebsd.org> <20030916111410.F12166@odysseus.silby.com> <3F673ABA.4000100@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F673ABA.4000100@freebsd.org> User-Agent: Mutt/1.5.4i cc: Mike Silbersack cc: stable@freebsd.org cc: current@freebsd.org Subject: Re: Release Engineering Status Report X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2003 21:09:19 -0000 On Tue, Sep 16, 2003 at 10:30:50AM -0600, Scott Long wrote: > Mike Silbersack wrote: > >On Tue, 16 Sep 2003, Scott Long wrote: > > > > > >>Patches have been floated on the mailing list that revert PAE in its > >>various stages. Maybe those need to be brought back up. Silby? Tor? > >> > >>Scott > > > > > >I believe that Tor's commit on August 30th resolved the PAE-related > >problems, so there is no need for a reversion. Since that time, I've seen > >three panics posted: > > > >1. Some netinet/ related panic which I couldn't make heads or tails of, > >and I haven't any followup reports from the poster. > > > >2. Maxim's buildworld -j64 memory kmap entry exhaustion panic, which can > >be fixed by increasing the number of kmap entries. (Tor has a patch for > >this, I will probably commit it soon.) > > > >3. A panic caused by sending 64K-1 ping packets, which I can't reproduce. > > > >(There's also a small problem with if_xl on pentium-1 machines, but since > >it's my fault and I'm waiting on test results from a guy, we won't talk > >about it.) > > > >(Hey, anyone have a pentium-200 and a 3com 905B card? Contact me, further > >testing can't hurt.) > > > >So, as far as I can tell, there are no remaining problems related to PAE; > >I believe that most people are venting frustration that built up between > >August 9th and 30th. > > > >Mike "Silby" Silbersack > > > > Ok, thanks for the update. Since it is 17 days after Aug 30 and people > are still upset, the status was very unclear to the Release Engineering > Team. So I guess we ened to solicit updates from the people who were > directly experiencing problems, and ask for everyone else to test it as > much as possible. I was one the people who were experiencing stability problems after the PAE commit. I had several unexpected panics and could provoke panics nearly at will on systems that had previously been rock-stable. After the Aug 30 commit I have not had any panics at all and I have not experienced any other stability problems either since then. In my personal experience RELENG_4 is currently quite stable (not counting any commits made during the last 48 hours or so since I have not yet tested any of those), but it is of course possible that other people have run into bugs in components of the kernel that I don't use. (Note: I do not have PAE enabled in the kernel. I have no idea what the situation is for those who actually have enabled PAE, but any problems that may exist there is non-critical IMO since they would not affect any pre-existing configurations.) -- Erik Trulsson ertr1013@student.uu.se