From owner-freebsd-arm@FreeBSD.ORG  Thu Oct 31 15:08:16 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id DD27FB13
 for <arm@freebsd.org>; Thu, 31 Oct 2013 15:08:16 +0000 (UTC)
 (envelope-from iz-rpi03@hs-karlsruhe.de)
Received: from smtp.hs-karlsruhe.de (smtp.HS-Karlsruhe.DE [193.196.64.25])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id A36B22598
 for <arm@freebsd.org>; Thu, 31 Oct 2013 15:08:16 +0000 (UTC)
Received: from iz-wera01.hs-karlsruhe.de ([193.196.65.46])
 by smtp.hs-karlsruhe.de with esmtp (Exim 4.80.1)
 (envelope-from <iz-rpi03@hs-karlsruhe.de>)
 id 1Vbtr5-002zQS-1r; Thu, 31 Oct 2013 16:08:15 +0100
X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.5
From: Ralf Wenk <iz-rpi03@hs-karlsruhe.de>
To: arm@freebsd.org
Subject: Regression between r254984 and r255943 on Raspberry Pi: failed to 
 create new mbuf
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 31 Oct 2013 16:08:13 +0100
Message-Id: <E1Vbtr5-002zQS-1r@smtp.hs-karlsruhe.de>
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2013 15:08:16 -0000

Hello,

while rsync(1)-ing an 1 GB file the rpi gets almost unresponsible
after a while and on the serial console there are lots of

smsc0: warning: failed to create new mbuf

kernel messages. Occasionaly dotted with the

[zone: mbuf_cluster] kern.ipc.nmbclusters limit reached

kernel message. The problem is reproduceable.
Increasing the value of kern.ipc.nmbclusters by the factor of 2 just delayed
the moment the problem happens.

An old r254984 kernel does not show this problem.

r257114 and r255943 do. A test with r255463 is currently ongoing.

Ralf