From owner-freebsd-stable@FreeBSD.ORG Tue Jan 4 11:18:56 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 B0E6F16A4CE for ; Tue, 4 Jan 2005 11:18:56 +0000 (GMT) Received: from mrelay3.uni-hannover.de (mrelay3.uni-hannover.de [130.75.2.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CC4543D31 for ; Tue, 4 Jan 2005 11:18:55 +0000 (GMT) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2])j04BIk9e009493; Tue, 4 Jan 2005 12:18:46 +0100 (MET) Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id D06672DD; Tue, 4 Jan 2005 12:18:41 +0100 (CET) Date: Tue, 4 Jan 2005 12:18:41 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: "M. Warner Losh" Message-Id: <20050104121841.14479f28.gerrit@pmp.uni-hannover.de> In-Reply-To: <20050104.033653.79872994.imp@bsdimp.com> References: <20050103101654.GA51270@pmp.uni-hannover.de> <20050103155826.0fed63ea@arc.pmp.uni-hannover.de> <20050104.033653.79872994.imp@bsdimp.com> Organization: Plasmaphysik X-Mailer: Sylpheed version 1.0.0rc (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.2.2 (mrelay3.uni-hannover.de [130.75.2.41]); Tue, 04 Jan 2005 12:18:46 +0100 (MET) X-Scanned-By: MIMEDefang 2.42 cc: freebsd-stable@freebsd.org Subject: Re: Strange networking problems after update 5.2.1->5.3 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: Tue, 04 Jan 2005 11:18:56 -0000 On Tue, 04 Jan 2005 03:36:53 -0700 (MST) "M. Warner Losh" wrote about Re: Strange networking problems after update 5.2.1->5.3: MWL> : I will do so if it's the support for the cards that is broken. MWL> However, I : have tried 4 different cards now, and only one of them MWL> worked. So I'm : tending to put the blame on the pcmcia bridge and MWL> it's driver. MWL> Blame doesn't belong there, but elsewhere in the system. The second MWL> ed card is broken in the ed driver (people with other bridges have MWL> reported problems), while the cardbus activation issue almost MWL> certainly is a resource issue (because other people with TI-1225 MWL> bridge work). I'll be happy to help you track down that issue, MWL> however. Thank you very much in advance. Please tell me which information you need. cu Gerrit