From owner-freebsd-questions@FreeBSD.ORG Mon Jun 4 17:49:51 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 15F3016A468 for ; Mon, 4 Jun 2007 17:49:51 +0000 (UTC) (envelope-from scott@butlerpress.com) Received: from ljcqs129.cnf.com (mail-cluster.cnf.com [63.230.177.41]) by mx1.freebsd.org (Postfix) with ESMTP id EA21413C4B7 for ; Mon, 4 Jun 2007 17:49:48 +0000 (UTC) (envelope-from scott@butlerpress.com) Received: from ljcqs129.cnf.com (localhost [127.0.0.1]) by ljcqs129.cnf.com (Postfix) with ESMTP id A527CF4115 for ; Mon, 4 Jun 2007 10:49:48 -0700 (PDT) Received: from [10.50.240.149] (cnfdcx-131-slb-02-in.cnf.com [10.0.108.132]) by ljcqs129.cnf.com (Postfix) with ESMTP id 8FC7AF407C for ; Mon, 4 Jun 2007 10:49:48 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <20070529232621.GB1575@rot13.obsecurity.org> References: <20070529232621.GB1575@rot13.obsecurity.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Scott Willson Date: Mon, 4 Jun 2007 10:49:45 -0700 To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: Panic With Large Network Copy X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2007 17:49:51 -0000 On May 29, 2007, at 4:26 PM, Kris Kennaway wrote: > On Tue, May 29, 2007 at 03:36:49PM -0700, Scott Willson wrote: >> I am seeing hard (often no core dump) crashes on a new AMD64 box >> running 6.2 RELEASE. When I try to rsync 10+ GB of backup files to >> the new box, I can reliably crash it after about 20 minutes; often >> quicker if I do something else intensive at the same time, like >> compile MySQL. Here are the box specs: >> ASUS M2NPV-VM motherboard >> AMD A64 3800+ 2.4G CPU >> ... >> Most times, I don't even get a core dump. Here's one I did get: >> panic: double fault >> ... >> #9 0xffffffff804371f0 in m_freem (mb=0x0) at uma.h:303 >> #10 0xffffffff80634125 in nve_ospackettx (ctx=0xffffff00798aac00, >> id=0xffffffffb19ea6d0, success=0) at /usr/src/sys/dev/nve/if_nve.c: >> 1551 > > This looks like a nve driver bug to me. You may wish to try the > nfe driver. > > Kris OK, my box is running nicely now. The nfe driver was indeed a good idea, thanks! Here are the details if anyone else has similar problems. 10baseT hub + nve = kernal panics under high load This is the default FreeBSD 6.2 RELEASE configuration. 10baseT hub + nfe + e100phy patch = errors under high load (tx v2 error 0x6204, watchdog timeout) http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html This is a replacement driver + recommended path for my hardware. No panics, but many errors. 10baseT hub + nfe with no patches = errors under high load (tx v2 error 0x6204, watchdog timeout) 10/100/1000baseT switch + nfe + e100phy patch = errors under high load (tx v2 error 0x6204, watchdog timeout) 10/100/1000baseT switch + nfe = No errors! This is a new switch and the nfe driver with no patch. In dmesg, I see 'ukphy0' when I boot. So, as you may have surmised, my motherboard + an old 10baseT hub doesn't work right with any driver. I replaced my very old hub with a new switch, and I am now running the nfe driver with ukphy0. This combination works great. Scott