From owner-freebsd-amd64@FreeBSD.ORG  Tue Nov 16 19:00:10 2004
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 946C416A4CE; Tue, 16 Nov 2004 19:00:10 +0000 (GMT)
Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E6FE743D5C; Tue, 16 Nov 2004 19:00:09 +0000 (GMT)
	(envelope-from bzeeb-lists@lists.zabbadoz.net)
Received: from transport.cksoft.de (localhost [127.0.0.1])
	by transport.cksoft.de (Postfix) with ESMTP
	id C698A1FF9AC; Tue, 16 Nov 2004 20:00:07 +0100 (CET)
Received: by transport.cksoft.de (Postfix, from userid 66)
	id DFF001FF9AB; Tue, 16 Nov 2004 20:00:05 +0100 (CET)
Received: by mail.int.zabbadoz.net (Postfix, from userid 1060)
	id 7FBB7153C4; Tue, 16 Nov 2004 18:55:34 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by mail.int.zabbadoz.net (Postfix) with ESMTP
	id 7CD3B1538C; Tue, 16 Nov 2004 18:55:35 +0000 (UTC)
Date: Tue, 16 Nov 2004 18:55:35 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net
To: David Kleiner <david.kleiner@gmail.com>
In-Reply-To: <f135cf2d041115154615413463@mail.gmail.com>
Message-ID: <Pine.BSF.4.53.0411161852120.9964@e0-0.zab2.int.zabbadoz.net>
References: <Pine.BSF.4.53.0411130037360.85716@e0-0.zab2.int.zabbadoz.net> 
	<20041115070404.GP64152@marvin.riggiland.au> 
	<Pine.BSF.4.53.0411150746530.85716@e0-0.zab2.int.zabbadoz.net> 
	<f135cf2d041115154615413463@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de
cc: FreeBSD current mailing list <current@freebsd.org>
cc: FreeBSD amd64 mailing list <freebsd-amd64@freebsd.org>
Subject: Re: [PATCH] if_sk(4) rx/tx "hangs"
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Nov 2004 19:00:10 -0000

On Mon, 15 Nov 2004, David Kleiner wrote:

Hi,

> Here is what I get when trying to load up the if_sk.ko module:
>
...
> Nov 15 15:31:58 macropus kernel: sk0: no memory for jumbo buffers!
> Nov 15 15:31:58 macropus kernel: sk0: jumbo buffer allocation failed
> Nov 15 15:31:58 macropus kernel: device_attach: sk0 attach returned 12

I had seen this too some weeks ago when loading and unloading the
if_sk.ko repeatedly but I haven't been able to reproduce afterwards.

> This is an Asus "A8V Deluxe (v. 2.0) K8T800 No-WiFi/A" and 6.0-CURRENT
> built on Sat Nov 13 12:08:59 PST 2004.
>
> I also had it crashed while running a 700MB bittorrent transfer (stock
> py-bittorrent) but did not get a crash dump.  The stack trace pointed
> at problem with networking and calling "panic" at the db> prompt
> wedged it solid.

you may perhaps want to update to lastest version which adds some
locking in the jumbo buffer memory functions. This should hopefully
help you.

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT