From owner-freebsd-stable@FreeBSD.ORG Thu Feb 10 14:06:31 2005 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 D894E16A4CE for ; Thu, 10 Feb 2005 14:06:31 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D99B43D2F for ; Thu, 10 Feb 2005 14:06:31 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so122433rng for ; Thu, 10 Feb 2005 06:06:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=nvcLQWGFY8RpmLfjd+cCpOtOAYrfNI2k7K1fNsnX/RCAEKFSVjFKp2l/9kUzq39oLSxaostDbxa0c5YSy0YEsn1s3quI1qs2EaNSPAOxh+E9aoMrgjItASrQq+iF0IbNnBTd5IlX0RGbTmvvoQ6fTLexRmkgFBSGhiwXy5+JOGU= Received: by 10.38.90.72 with SMTP id n72mr192717rnb; Thu, 10 Feb 2005 06:06:30 -0800 (PST) Received: by 10.39.1.22 with HTTP; Thu, 10 Feb 2005 06:06:30 -0800 (PST) Message-ID: <3aaaa3a050210060675cf1d7@mail.gmail.com> Date: Thu, 10 Feb 2005 14:06:30 +0000 From: Chris To: Kris Kennaway In-Reply-To: <20050208002923.GA83862@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050207101634.8716616A569@hub.freebsd.org> <20050207212024.H27037@zero> <20050208002923.GA83862@xor.obsecurity.org> cc: T?rgan Flores de Siqueira cc: freebsd-stable@freebsd.org Subject: Re: 5.x concerns X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chris List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Feb 2005 14:06:32 -0000 If this helps, I noticed this recently on the machine that has had tcp lockups. rl0: discard oversize frame (ether type c49b flags 3 len 47956 > max 1514) rl0: discard oversize frame (ether type 98b4 flags 3 len 17725 > max 1514) rl0: discard oversize frame (ether type 8be6 flags 3 len 38514 > max 1514) rl0: discard oversize frame (ether type 5c60 flags 3 len 2270 > max 1514) rl0: discard oversize frame (ether type a338 flags 3 len 58392 > max 1514) rl0: discard oversize frame (ether type 8680 flags 3 len 22762 > max 1514) rl0: discard oversize frame (ether type 2ffa flags 3 len 61086 > max 1514) rl0: discard oversize frame (ether type fc52 flags 3 len 55028 > max 1514) It is still online tho. Chris On Mon, 7 Feb 2005 16:29:23 -0800, Kris Kennaway wrote: > On Mon, Feb 07, 2005 at 09:40:48PM -0200, T?rgan Flores de Siqueira wrote: > > >On Sun, Feb 06, 2005 at 03:01:49PM +0000, Chris wrote: > > > > > >>4 - compatiblity, I remember using 5.2.1 and pretty much all software > > >>worked well in that and then they did the bind defaulting to base and > > >>libs version jump, why wasnt this done in 5.0 so 3rd party apps could > > >>adjust, now we have a situation where most stuff that worked in 4.x > > >>worked well in 5.1 and 5.2.1 but then broke in 5.3 so effectively 5.3 > > >>was liek a new major version over 5.2.1. > > > > > >5.2.1 was clearly marked as a "developer preview" release and you were > > >warned not to rely on it for production use. As a snapshot of > > >FreeBSD-CURRENT, binary compatibility is not guaranteed and often > > >needs to be broken in the course of development. > > > > > >Kris > > > > Just adding a note: I regularly use FreeBSD on a Toshiba notebook, and > > switched from 4.x to 5.x to benefit from cardbus support. > > Well, I started with 5.2.1 and all things did well. Since then, I'm > > trying to track 5-STABLE with no success. Starting with 5.3-RELEASE, > > the ACPI stopped to work, as well as did the rl driver. > > So, I switched back to 5.2.1. > > Sorry to hear that - I hope you submitted bug reports so that someone > can try to fix this, otherwise you might be stuck with 5.2.1 forever. > > Kris > > >