From owner-freebsd-stable@FreeBSD.ORG Sun Jun 19 18:40:42 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 7394616A41C for ; Sun, 19 Jun 2005 18:40:42 +0000 (GMT) (envelope-from creep@daedalus.desk.pl) Received: from daedalus.desk.pl (daedalus.desk.pl [62.233.238.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B82643D48 for ; Sun, 19 Jun 2005 18:40:42 +0000 (GMT) (envelope-from creep@daedalus.desk.pl) Received: from localhost (localhost [127.0.0.1]) by daedalus.desk.pl (Postfix) with ESMTP id A4622366652 for ; Sun, 19 Jun 2005 20:33:42 +0200 (CEST) Received: from daedalus.desk.pl ([127.0.0.1]) by localhost (daedalus [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13599-03 for ; Sun, 19 Jun 2005 20:33:41 +0200 (CEST) Received: by daedalus.desk.pl (Postfix, from userid 1023) id 3EFFE36663A; Sun, 19 Jun 2005 20:33:41 +0200 (CEST) Date: Sun, 19 Jun 2005 20:33:41 +0200 From: Marcin Koziej To: freebsd-stable@freebsd.org Message-ID: <20050619183341.GB10873@daedalus.desk.pl> References: <20050618234921.GA1740@daedalus.desk.pl> <20050619110902.GA705@daedalus.desk.pl> <62860.192.168.1.20.1119199973.squirrel@webmail.thilelli.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <62860.192.168.1.20.1119199973.squirrel@webmail.thilelli.net> User-Agent: Mutt/1.4.1i X-Antivirus: Skaner Antywirusowy DESK.pl Subject: Re: re0 "no carrier" problem - Patches found in archives didn't work. 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, 19 Jun 2005 18:40:42 -0000 > Not sure if it is solely "switch related". I encountered the very same > problem for months now using different links ans switches. Moreover, it > seems to be FreeBSD specific since the same machine works better with > others OSes. > > See PR kern/80005 for a more long description on a very similar problem. I've seen this, but it didn't help a lot. I'll try to investigate on this, but I have a question - how? Should i just insert loads o printf's here and there to see what functions are called when the link fails? (Brings back memories... ;>) It would be cool having dtrace ported.... -- m. Brain power of a glass of water.