Date: Thu, 22 Aug 2002 11:39:28 +0200 From: Mark Santcroos <marks@ripe.net> To: Udo Schweigert <udo.schweigert@siemens.com> Cc: Martin Blapp <mb@imp.ch>, Soeren Schmidt <sos@freebsd.dk>, Don Lewis <dl-freebsd@catspoiler.org>, ktsin@acm.org, freebsd-current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Memory corruption in CURRENT Message-ID: <20020822093928.GA17084@ripe.net> In-Reply-To: <20020822093050.GA47654@alaska.cert.siemens.de> References: <200208220909.g7M99NcS077303@freebsd.dk> <20020822111650.I45839-100000@levais.imp.ch> <20020822093050.GA47654@alaska.cert.siemens.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 22, 2002 at 11:30:50AM +0200, Udo Schweigert wrote: > Only a little addition from me: I had the same problems on -stable and they > only disappeared after compiling the kernel without debugging. I had the > impression that it has to do with the size of the kernel (but this of course > maybe wrong). After dropping "-g" from kernel compiling I hadn't a problem > again on -stable. (At the moment I do not have -current on a P-IV, the > motherboard is a Fujitsu-Siemens) I will try that asap. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020822093928.GA17084>