From owner-freebsd-isp Mon Mar 18 17:30: 3 2002 Delivered-To: freebsd-isp@freebsd.org Received: from nlaredo.globalpc.net (nld2.globalpc.net [207.193.206.189]) by hub.freebsd.org (Postfix) with ESMTP id 6D83B37B402 for ; Mon, 18 Mar 2002 17:29:51 -0800 (PST) Received: from ds9 (ds9.globalpc.net [207.193.204.57]) by nlaredo.globalpc.net (8.9.3/8.9.3) with SMTP id TAA84906 for ; Mon, 18 Mar 2002 19:31:55 -0600 (CST) (envelope-from adrianbsd@globalpc.net) Message-Id: <3.0.6.32.20020318193129.01027cd8@globalpc.net> X-Sender: adrianbsd@globalpc.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 18 Mar 2002 19:31:29 -0600 To: freebsd-isp@freebsd.org From: Adrian Gonzalez Subject: 4.5-STABLE kernel panic - panic: malloc: lost data Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello I'm having a few problems with a server. It's getting kernel panics 3-4 times a week, unfortunately, the server is at a remote POP and I can't get to it right when it happens. I cvsup'ed and recompiled the kernel and system, and made sio0 the console (flags 0x30). After waiting a couple of days for the crash, here's what I got: panic: malloc: lost data mp_lock = 01000001; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 giving up on 31 buffers Uptime: 2d19h56m19s mly0: flushing cache...done Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... This is the only one I've logged so far. Another problem seems to be that sometimes logged messages are chopped to the first one or two characters on the serial console, like: Mar 18 18:32:50 test /kernel: arp: x.x.x.x moved from 00:c0:05:04:28:72 to 00:c0:05:04:16:00 on fxp0 MaMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMaMMMMMaMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMM MMMMMMMMMMMMMMMMMMMMMMMMar 18 18:52:00 radius[19913]: unix_pass: password for failed The serial console is configured at 115200, the serial port works fine for other purposes. No hardware changes have been made to the machine for several months now. The box is a dual PIII (Asus CUR-DLS, serverworks chipset). Basically I have two questions: What can cause this kind of kernel panic? Why are the log messages being chopped? Any help would be greatly appreciated Thanks -Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message