Date: Tue, 16 Nov 2004 18:55:35 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: David Kleiner <david.kleiner@gmail.com> Cc: FreeBSD amd64 mailing list <freebsd-amd64@freebsd.org> Subject: Re: [PATCH] if_sk(4) rx/tx "hangs" Message-ID: <Pine.BSF.4.53.0411161852120.9964@e0-0.zab2.int.zabbadoz.net> In-Reply-To: <f135cf2d041115154615413463@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0411161852120.9964>