From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 19:46:28 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D99A16A4CE; Thu, 20 Jan 2005 19:46:28 +0000 (GMT) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5D3F43D1F; Thu, 20 Jan 2005 19:46:27 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j0KJkPiQ017909; Thu, 20 Jan 2005 14:46:25 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <41F00697.7010000@freebsd.org> References: <20050120140300.F1832@bahre.achedra.org> <41F00697.7010000@freebsd.org> Date: Thu, 20 Jan 2005 14:46:24 -0500 To: Scott Long , "Ketrien I. Saihr-Kenchedra" From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: current@freebsd.org Subject: Re: Memory modified after free - Jan20 -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 19:46:28 -0000 At 12:29 PM -0700 1/20/05, Scott Long wrote: >Ketrien I. Saihr-Kenchedra wrote: > >>Screen transcription attached. In a nutshell; >> >>fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 >>device_attach: fdc0 returned 6 >>sio0: <16550A-compatible COM port> port0x3f8-0x3ff irq 4 flags 0x10 on acpi0 >>sio0: type 16550A >>Memory modified after free 0xc1cde200(252) val=0 @ 0xc1cde228 >>panic: Most recently used by none >> >>System was fine with Jan16 srcs, fdc returning 6 is new. Looks >>like a uma problem to me, but odd enough that I'm honestly not >>sure. Need ips(4) for dumpdev, so no dump again. (Argh.) >> > >I'm seeing this quite often too. I'm hoping that Bosko will make >his memguard changes available soon as I'm sure it could quickly >be tracked down with them. Ugh. I see this too, immediately at bootup. The system can't even make it into single-user mode. Right now I can't get a dump of it, since doadump() complaints that it doesn't know my dump device. How do I set the dump-device from the boot-loader? Will a dump of this be of any help to someone, or does the panic happen too late to have any useful information? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu