From owner-freebsd-stable@FreeBSD.ORG  Sat Nov 26 21:06:04 2011
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 ABD1E106566B
	for <freebsd-stable@freebsd.org>; Sat, 26 Nov 2011 21:06:03 +0000 (UTC)
	(envelope-from mandrews@bit0.com)
Received: from magnum.bit0.com (magnum.bit0.com [IPv6:2604:e700:b0:1::200])
	by mx1.freebsd.org (Postfix) with ESMTP id 63EA28FC08
	for <freebsd-stable@freebsd.org>; Sat, 26 Nov 2011 21:06:03 +0000 (UTC)
Received: from magnum.bit0.com (localhost [127.0.0.1])
	by magnum.bit0.com (Postfix) with ESMTP id B7F6D16985
	for <freebsd-stable@freebsd.org>; Sat, 26 Nov 2011 16:06:02 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=bit0.com; h=message-id
	:date:from:mime-version:to:subject:content-type; s=boogity; bh=8
	Edrs3Ko8VXh+ZqdumdGpK51cccpHUM2g6CYQ9UuRKc=; b=M6UA6GGYorGhTzXG4
	PeS9nQOWxtKAaSvzT6N5jLKUgnNrqJyRmS3K5bsYOfsF7xMd+sx4hGE+Ckaqpwvr
	GV849n6D1red1r6KvDlpyOQI0lokmds6XxCwG3WYqNiwaZ7ftsNBvA0j21ngPjwz
	KIZ37Xzk2kR2+MYhTaYPyqDuXw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=bit0.com; h=message-id:date
	:from:mime-version:to:subject:content-type; q=dns; s=boogity; b=
	VvofLF4+dmtfSbH5omzqZ2QNsXeTWeWVKqXounh+pnymcZYJsl3rPqLFj3NdHhD2
	COxhwCUIVa57S1vJvbz1LKb+lTHZbbm9lf+VlTu9Dhsznjvonxiq/QOBcKOxNDnf
	S4Hi3f6Dlhx7BeTnPzgaHEBEZZ6zAPA5ff0Q8fnHQHI=
Received: from millenniumforce.int.bit0.com
	(207-246-87-56.dsl.static.blueone.net [207.246.87.56])
	(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
	(No client certificate requested)
	by magnum.bit0.com (Postfix) with ESMTPSA id 9138D16984
	for <freebsd-stable@freebsd.org>; Sat, 26 Nov 2011 16:06:02 -0500 (EST)
Message-ID: <4ED154B6.2030304@bit0.com>
Date: Sat, 26 Nov 2011 16:05:58 -0500
From: Mike Andrews <mandrews@bit0.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: 9.0-RC2 re(4) "no memory for jumbo buffers" issue
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Nov 2011 21:06:04 -0000

I have a Supermicro 5015A-H (Intel Atom 330) server with two Realtek 
RTL8111C-GR gigabit NICs on it.  As far as I can tell, these support 
jumbo frames up to 7422 bytes.  When running them at an MTU of 5000 on 
FreeBSD 9.0-RC2, after a week or so of update, with fairly light network 
activity, the interfaces die with "no memory for jumbo buffers" errors 
on the console.  Unloading and reloading the driver (via serial console) 
doesn't help; only rebooting seems to clear it up.

I don't have this issue with any of my em(4) based systems that are also 
using a 5000 byte MTU -- and they push considerably more traffic.

I don't really consider this a regression from FreeBSD 8.2 because 8.2 
didn't support jumbos at all on this hardware... :)

What's the best way to go about debugging this...  which sysctl's should 
I be looking at first?  I have already tried raising kern.ipc.nmbjumbo9 
to 16384 and it doesn't seem to help things... maybe prolonging it 
slightly, but not by much.  The problem is it takes a week or so to 
reproduce the problem each time...