From owner-freebsd-stable@FreeBSD.ORG Thu Jun 5 17:56:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17C1C1065670 for ; Thu, 5 Jun 2008 17:56:25 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id C0E9B8FC1D for ; Thu, 5 Jun 2008 17:56:24 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by yx-out-2324.google.com with SMTP id 31so106285yxl.13 for ; Thu, 05 Jun 2008 10:56:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=3uxFe9TqZCeh0VjJujJq9XdlRFsIkTdz0gf0npjXPWs=; b=Ef1wC56iwk7uQ9AFLDhCfFFFV0yZ0Vdcr3IWPEIVaPmMB/JZxYBulIxU18JFsMsHZt eFVwV9s+xjc6T+mJvwveb/O3mKMptVqtVSUyBIVnzwnExDwfeU6cAkwo57SjPBiZbb+m xpgwB51ZYGQxEfzwR9U2kD+YF9c6zMKe54uxs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=FSaWt4Z+kjC0Yxxjmd6AQkX/GfONrUcF4GFNpKXwi8GY5TQLXytdL7MQrJhI3r1f9B Si1p1BExvNpMsrrVqn+YBa5HzXYfRB1oSt2dIVifyFh1U/zW/uXc1L72uKDA5w2ISK1h J5w37KmDNTOFQrSFYrXVYEqCon42eq/oukgfI= Received: by 10.151.42.9 with SMTP id u9mr2147230ybj.83.1212687000833; Thu, 05 Jun 2008 10:30:00 -0700 (PDT) Received: by 10.150.53.16 with HTTP; Thu, 5 Jun 2008 10:30:00 -0700 (PDT) Message-ID: Date: Thu, 5 Jun 2008 18:30:00 +0100 From: "Chris Rees" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2008 17:56:25 -0000 On Thursday, June 05, 2008 10:23:55 -0400 John Baldwin > wrote: > I'm glad to hear that. I have a server that uses bce, and it was completely > non-functional until I hunted down some beta code that made it usable. I'd > like to upgrade, but this is a critical server with no redundancy (and it's a > hobby site with no money to pay for expensive support), and I'm not about to > upgrade unless I know for certain the problems won't reoccur, because I have to > upgrade remotely and pay money if the system goes down. > > The problems with that driver were bad enough when the server was being > configured in my study. (The system would lock up, and only a hard reboot > would restore networking.) It would be hell trying to troubleshoot problems if > I had to drive the 45 miles to the hosting site and spend a night there trying > to get the server back up, then go to work the next day. > > # uname -a > FreeBSD www.stovebolt.com 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #2: Mon Oct > 16 15:38:02 CDT 2006 root@www.stovebolt.com:/usr/obj/usr/src/sys/GENERIC > i386 > > # grep bce /var/run/dmesg.boot > bce0: mem > 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci9 > bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz > miibus0: on bce0 > bce0: Ethernet address: 00:13:72:fb:2a:ad > bce1: mem > 0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci5 > bce1: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz > miibus1: on bce1 > bce1: Ethernet address: 00:13:72:fb:2a:ab > > # grep bce0 /var/log/messages > May 2 09:10:31 www kernel: bce0: link state changed to DOWN > May 2 09:10:39 www kernel: bce0: link state changed to UP > May 25 07:49:49 www kernel: bce0: link state changed to DOWN > May 25 07:50:31 www kernel: bce0: link state changed to UP > May 26 21:28:36 www kernel: bce0: link state changed to DOWN > May 26 21:28:40 www kernel: bce0: link state changed to UP > May 27 13:13:21 www kernel: bce0: link state changed to DOWN > May 27 13:13:31 www kernel: bce0: link state changed to UP > > It's been like that since the server was installed. > > So, if I upgrade to 6.3 or 7.0, am I still going to experience these problems? > Is the server going to stop working entirely? How can I know that for sure > before starting an upgrade? Damn, that's fascinating. I get that with nfe, on my xbox; amnesiac# uname -a FreeBSD amnesiac.bayofrum.net 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #9: Wed May 28 23:14:21 BST 2008 root@amnesiac.bayofrum.net:/usr/obj/usr/src/sys/AMNESIAC i386 amnesiac# uptime 6:27PM up 7 days, 18:53, 1 user, load averages: 0.00, 0.05, 0.06 amnesiac# tail /var/log/messages Jun 3 17:39:31 amnesiac kernel: pid 37682 (python), uid 80 inumber 871485 on /usr/spare: filesystem full Jun 4 17:07:24 amnesiac kernel: nfe0: link state changed to DOWN Jun 4 17:07:34 amnesiac kernel: nfe0: link state changed to UP Jun 4 17:07:40 amnesiac kernel: nfe0: link state changed to DOWN Jun 4 17:07:54 amnesiac kernel: nfe0: link state changed to UP Jun 4 18:39:50 amnesiac kernel: nfe0: link state changed to DOWN Jun 4 18:40:01 amnesiac kernel: nfe0: link state changed to UP Jun 4 18:40:07 amnesiac kernel: nfe0: link state changed to DOWN Jun 4 18:40:21 amnesiac kernel: nfe0: link state changed to UP Jun 5 18:26:58 amnesiac sudo: chris : TTY=ttyp0 ; PWD=/usr/home/chris ; USER=root ; COMMAND=/usr/bin/su Hm, I swear that's getting more regular. Anyway, it hasn't lost permanantly yet, but I was just ignoring them (my Linux background :$). Should I be worried?? I'll provide any other details if anyone's interested.