From owner-freebsd-stable@FreeBSD.ORG Sun Jun 26 13:02:29 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF4B2106564A for ; Sun, 26 Jun 2011 13:02:29 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by mx1.freebsd.org (Postfix) with ESMTP id 5B0568FC13 for ; Sun, 26 Jun 2011 13:02:28 +0000 (UTC) Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta13.westchester.pa.mail.comcast.net with comcast id 0crp1h0021vXlb85Dd2V1K; Sun, 26 Jun 2011 13:02:29 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta17.westchester.pa.mail.comcast.net with comcast id 0d2T1h0131t3BNj3dd2UD7; Sun, 26 Jun 2011 13:02:29 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E3969102C19; Sun, 26 Jun 2011 06:02:25 -0700 (PDT) Date: Sun, 26 Jun 2011 06:02:25 -0700 From: Jeremy Chadwick To: Willem Jan Withagen Message-ID: <20110626130225.GA7164@icarus.home.lan> References: <4E0674ED.5090502@digiware.nl> <4BF3C5A181754319A7A83BE40F321E29@multiplay.co.uk> <4E0719EF.4060403@digiware.nl> <6049DAF547274E10A11C66936374E878@multiplay.co.uk> <4E0723D2.8050706@digiware.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E0723D2.8050706@digiware.nl> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: stable@freebsd.org, Steven Hartland Subject: Re: arcmsr panic runnig 8.2 of 2011 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2011 13:02:29 -0000 On Sun, Jun 26, 2011 at 02:19:30PM +0200, Willem Jan Withagen wrote: > On 26-6-2011 13:50, Steven Hartland wrote: > > ----- Original Message ----- From: "Willem Jan Withagen" > > > >> Well the main key to the problem is that on 2011/06/06 the new version > >> from Areca got imported. So if you have all your boxes with kernels > >> predating 06-06, you're not running the new code. > >> > >> It the above is true and if you have a spare/development box, it would > >> be interesting to see if a very recent 8.2-STABLE would work. > >> > >> But thanx for giving me a reference point. > > > > Ahh when you said 8.2 that infers release not stable which is 8-stable > > in my mind. > > > > So to clarify all our machines are running 8.2-release with a few minor > > imports from stable to fix local issues such as the updated ixgbe driver. > > > > I don't have a box I can use to test stable I'm afraid sorry. > > Hi Steven, > > My sense is more or less the other way around. 8.2 would feel like > 8.2-stable, and only release when specifcally marked so. > But then that's probably where one is coming from. I always run > non-RELEASE version. > > Too bad, I only have one controller and it is in active use.... > I'd otherwise build a clean system. > > But then use this as a point of attention, once you want to proceed from > release into stable.... I would strongly recommend (to both of you) of referring to things by either full version string (e.g. 8.2-RELEASE or 8.2-STABLE), or alternatively by release tag (e.g. RELENG_8_2 or RELENG_8). The "x.y" nomenclature hasn't ever sufficed. Regardless of what convention you go with, always remember to include your kernel/world build date (the date shown in "uname -a" is usually sufficient as long as you haven't done something nonsensical like rebuilding kernel and not world). This is *especially* important when reporting issues with RELENG_8 (8.2-STABLE), because MFC's happen all the time, case in point. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |