From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 22 06:16:31 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 913E437B407 for ; Tue, 22 Jul 2003 06:16:31 -0700 (PDT) Received: from godel.mtl.distributel.net (nat.MTL.distributel.NET [66.38.181.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16C8A43FB1 for ; Tue, 22 Jul 2003 06:16:30 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: from godel.mtl.distributel.net (localhost [127.0.0.1]) h6M9KUEH058233; Tue, 22 Jul 2003 09:20:30 GMT (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by godel.mtl.distributel.net (8.12.9/8.12.9/Submit) id h6M9KURs058232; Tue, 22 Jul 2003 09:20:30 GMT X-Authentication-Warning: godel.mtl.distributel.net: bmilekic set sender to bmilekic@technokratis.com using -f Date: Tue, 22 Jul 2003 09:20:30 +0000 From: Bosko Milekic To: Valentin Nechayev Message-ID: <20030722092030.GB58118@technokratis.com> References: <20030718091248.GO76126@lucky.net> <20030722060106.GE76126@lucky.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030722060106.GE76126@lucky.net> User-Agent: Mutt/1.4.1i cc: Dag-Erling Sm?rgrav cc: hackers@freebsd.org Subject: Re: complicated downgrade X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 13:16:32 -0000 On Tue, Jul 22, 2003 at 09:01:06AM +0300, Valentin Nechayev wrote: > Mon, Jul 21, 2003 at 23:40:05, des wrote about "Re: complicated downgrade": > > >> I need to downgrade a remote FreeBSD system from 5.1-release to 4.8-release > >> remotely without any local help (except possible hitting Reset). > > Maybe if you tell us why you need to do this we can figure out a way > > for you to avoid doing it? > > System periodically hangs up. Average uptime is ~6 hours. No crash info > is available. No serial console is available. Different invariants didn't > help, AFAIK (this testing was done by another admin, so I'm not 100% sure). > 4.8 in any case is considered more stable, so switching can exclude > some software problems or software-caused triggerings of hardware problems. This sounds like the same symptoms as the latest USB problem... when/if you track -current or even run one of the 5.x releases, it's key to realize that this is very active code that you're running; it's not the same thing as running 4.x, for example. The code in 5.x is constantly actively changing, whereas the code in 4.x only receives comparatively well-regulated merges from 5.x, for the most part. Therefore, one of the things to always try is to update to the latest -current, rebuild, and see if you can reproduce. Chances are, your problem may have been fixed and, if not, at least we can be confident that it's reproducable on your hardware with the latest sources. > Just now question isn't so important because it was decided to move to another > box (including more friendly environment), so my question is more theoretical > than practical. But, there is opportunity to play with configs, so I'll try > again to play with invariants, witnesses, etc. > > Thanks to all for help. > > > -netch- Cheers, -- Bosko Milekic * bmilekic@technokratis.com * bmilekic@FreeBSD.org TECHNOkRATIS Consulting Services * http://www.technokratis.com/