Date: Thu, 20 Jan 2005 14:46:24 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Scott Long <scottl@freebsd.org>, "Ketrien I. Saihr-Kenchedra" <ketrien@error404.nls.net> Cc: current@freebsd.org Subject: Re: Memory modified after free - Jan20 -CURRENT Message-ID: <p0620072bbe15b9825b91@[128.113.24.47]> In-Reply-To: <41F00697.7010000@freebsd.org> References: <20050120140300.F1832@bahre.achedra.org> <41F00697.7010000@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:29 PM -0700 1/20/05, Scott Long wrote: >Ketrien I. Saihr-Kenchedra wrote: > >>Screen transcription attached. In a nutshell; >> >>fdc0: <floppy drive controller> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0620072bbe15b9825b91>