From owner-freebsd-security Sun Feb 3 14:57:59 2002 Delivered-To: freebsd-security@freebsd.org Received: from walter.dfmm.org (walter.dfmm.org [209.151.233.240]) by hub.freebsd.org (Postfix) with ESMTP id 827BC37B416 for ; Sun, 3 Feb 2002 14:57:53 -0800 (PST) Received: (qmail 33839 invoked by uid 1000); 3 Feb 2002 22:57:48 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Feb 2002 22:57:48 -0000 Date: Sun, 3 Feb 2002 14:57:44 -0800 (PST) From: Jason Stone X-X-Sender: To: Subject: Re: crashs on 4.5RC In-Reply-To: Message-ID: <20020203143638.N6370-100000@walter> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > i updated my 4.4 to an 4.5RC the first time that i compiled .. it was > > crashing almost everysingle hour .. i booted up again on the old > > 4.5PRE-RELEASE .. and recompile the kernel with the new updates from > > You need to be more specific. What do you mean by "crash" -- do you > get a system panic, a system hang, a reboot without a message? Is any > output generated along the way? One common pitfall identified in the > release notes was a change in default sizing of socket buffers, which > requires some busy sites to increase nmbclusters (either by > recompiling with different kernel configuration settings, or simply > updating loader.conf to use a larger hard-coded value). Potentially, > you could be running into that. I may have had a similar experience. My server running 4.5RC crashed inexplicably a couple days ago. The kernel panicked, and I think it hung while trying to generate a crashdump (the tech who rebooted it said there was a message about, "unable to open ata device," or somesuch - sorry I can't be more specific - I couldn't get to the console, and there was no crashdump after rebooting). The last messages in my logs before the box went down were: Feb 2 11:47:28 walter /kernel: m_retry failed, consider increase mbuf value Feb 2 11:47:28 walter /kernel: m_retryhdr failed, consider increase mbuf value Feb 2 11:47:29 walter /kernel: fxp0: mbuf allocation failed, packet dropped! Feb 2 11:47:29 walter last message repeated 15 times So my question is, is it possible to panic and crash a FreeBSD box by overflowing its nmbclusters? -Jason ----------------------------------------------------------------------- I worry about my child and the Internet all the time, even though she's too young to have logged on yet. Here's what I worry about. I worry that 10 or 15 years from now, she will come to me and say "Daddy, where were you when they took freedom of the press away from the Internet?" -- Mike Godwin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: See https://private.idealab.com/public/jason/jason.gpg iD8DBQE8XcBsswXMWWtptckRAk3tAJ4zQSxJ+iVjAJtVeFSDYm6QnTB1JwCeOtwD vporCSXlvOmgB4r8Bpl2TI0= =c3FZ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message