From owner-freebsd-stable@FreeBSD.ORG Wed Jun 22 00:42:19 2011 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 151891065676 for ; Wed, 22 Jun 2011 00:42:19 +0000 (UTC) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [IPv6:2001:470:a80a:1:21f:d0ff:fe22:b8a8]) by mx1.freebsd.org (Postfix) with ESMTP id 6F9BE8FC08 for ; Wed, 22 Jun 2011 00:42:18 +0000 (UTC) Received: from kanga.honeypot.net (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 2F74B5EF3A for ; Tue, 21 Jun 2011 19:42:16 -0500 (CDT) X-Virus-Scanned: amavisd-new at honeypot.net Received: from kanga.honeypot.net ([127.0.0.1]) by kanga.honeypot.net (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YQ2Yj+Q+VmeB for ; Tue, 21 Jun 2011 19:42:10 -0500 (CDT) Received: from pooh.honeypot.net (pooh.honeypot.net [10.0.5.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTPSA id 5E3CC5EAD1 for ; Tue, 21 Jun 2011 19:34:39 -0500 (CDT) Message-Id: <621C04D8-6867-44D9-80E9-1E854B6154CD@strauser.com> From: Kirk Strauser To: FreeBSD Stable In-Reply-To: <84E92041-C897-4744-B432-CA3537EE156F@strauser.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Tue, 21 Jun 2011 19:34:36 -0500 References: <84E92041-C897-4744-B432-CA3537EE156F@strauser.com> X-Mailer: Apple Mail (2.936) Subject: SOLVED (was: re0 died last night; here's how I half-revived it) 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: Wed, 22 Jun 2011 00:42:19 -0000 I found the problem: sometime between the May 8 kernel I'd been using and the new one (latest build: 15:02:36 CST today), my system decided to devour socket buffers. I set kern.ipc.maxsockbuf=16777216 and have over an hour of stable multi-user uptime, which is a vast improvement! On Jun 9, 2011, at 9:37 AM, Kirk Strauser wrote: > I have a FreeBSD 8-STABLE system that's been running stably since I > last upgraded and rebooted on May 8. Yesterday, I updated /usr/src > to get ZFS v28 and also seem to have gotten rid of my nice, solid > re0 network interface: > > re0: port > 0xb000-0xb0ff mem 0xea210000-0xea210fff,0xea200000-0xea20ffff irq 16 > at device 0.0 on pci5 > re0: Using 1 MSI-X message > re0: Chip rev. 0x3c000000 > re0: MAC rev. 0x00400000 > miibus0: on re0 > > I'm too tired from lack of sleep due to getting the system back up > and running to remember all the details, but the summary is that it > started autodetecting its media as 10baseT/UTP. Almost immediately > after boot - sometimes while still playing in single-user mode - I'd > start seeing "no buffer space available" error messages all over the > place. > > Forcing media to 1000baseTX/full-duplex fixed the problem for a few > minutes, but it wouldn't stay in that state and would shortly start > throwing "no buffer space available" errors again. Until I've gotten > some sleep and have more mental energy to figure out exactly what's > going on, I've found that forcing the media to 100baseTX keeps it > solidly chugging along (if a little slowly). > > Anyway, that's where I'm at now. If your re NIC is giving you fits > this morning, try setting it to 100baseTX and see if that'll get you > running until a better fix comes along. > > - Kirk > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > "