Date: Tue, 24 Feb 2004 15:15:46 -0500 From: Jesse Guardiani <jesse@wingnet.net> To: freebsd-current@freebsd.org Subject: Re: 5.2.1-RC2 debug kernel PANIC "Memory modified after free" Message-ID: <c1gbdi$5kd$1@sea.gmane.org> References: <c0vsqa$su0$1@sea.gmane.org> <20040218220443.GA76951@troutmask.apl.washington.edu> <200402181818.43959.jesse@wingnet.net> <20040218234109.GA77908@troutmask.apl.washington.edu> <c12kmv$t5s$1@sea.gmane.org> <c19bjf$em7$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jesse Guardiani wrote: [...] > And to recap, the stock 5.2.1rc2 kernel boots just fine. However, it > core dumps on random ocassions, and I was hoping to get a gdb backtrace > from a debug kernel core. But my debug kernel won't boot! > > The major differences I see from GENERIC to my debug kernel are that > I don't include 'options SMP' or 'options apic' in my debug kernel > and my debug kernel has WATCHDOG and all of the other debug options > turned on. I can post a diff if anyone is interested. > > Thanks! Going once.... I'm probably going to attempt an upgrade to -CURRENT at the end of this week, so if anyone is actually interested in debugging this problem with me then they should contact me ASAP. I consider this error pretty darn bad because I can't run a debug kernel anymore. Do we really want to ship 5.2.1-RELEASE with this kind of a bug lurking in the wings? -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c1gbdi$5kd$1>