From owner-freebsd-isp@FreeBSD.ORG Mon Apr 14 11:01:24 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E78E37B401 for ; Mon, 14 Apr 2003 11:01:24 -0700 (PDT) Received: from ms.securenet.net (ms.securenet.net [205.236.147.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B65143F85 for ; Mon, 14 Apr 2003 11:01:23 -0700 (PDT) (envelope-from vandj@securenet.net) Received: from 127.0.0.1 (localhost.securenet.net [127.0.0.1]) by dummy.domain.name (Postfix) with SMTP id 381C1264DCA for ; Mon, 14 Apr 2003 14:09:41 -0400 (EDT) Received: from office.securenet.net (office.securenet.net [205.236.147.3]) by ms.securenet.net (Postfix) with ESMTP id 0AD49264DDF for ; Mon, 14 Apr 2003 14:09:41 -0400 (EDT) Message-Id: <5.2.0.9.0.20030414135649.02a71398@pop.securenet.net> X-Sender: vandj@pop.securenet.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 14 Apr 2003 14:01:40 -0400 To: freebsd-isp@freebsd.org From: "Jean M. Vandette" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Kernel Bug question X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Apr 2003 18:01:24 -0000 Greetings all, We have had one of our mail servers running 4.8-STABLE reboot every few hours The following messages were found in the /var/log/messages >Apr 13 13:19:20 ms /kernel: panic: malloc: wrong bucket >Apr 13 13:19:20 ms /kernel: >Apr 13 13:19:20 ms /kernel: syncing disks... 75 27 27 27 27 27 27 27 41 3 >3 3 3 3 3 3 8 3 3 3 3 3 3 3 6 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > >Apr 14 06:33:52 ms /kernel: panic: malloc: lost data >Apr 14 06:33:52 ms /kernel: >Apr 14 06:33:52 ms /kernel: syncing disks... 73 16 16 16 16 16 16 16 28 5 >5 5 5 5 5 5 9 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 >Apr 14 06:33:52 ms /kernel: giving up on 1 buffers Looks like a part of the kernel using data that it doesn't own, ie. a kernel bug Anyone else seen this type of message and better still have you found a fix? Jean M. Vandette **John M. Vandette, Consultant vandj@securenet.net** **SecureNet Information Services Inc. Internet Providers** **100 Alexis Nihon Blvd #283 St. Laurent, Quebec, Canada** **"Who does BSD Unix....?" "We do Chucky... We do..."**