Date: Thu, 22 Aug 2002 11:06:51 +0200 From: Mark Santcroos <marks@ripe.net> To: Martin Blapp <mb@imp.ch> Cc: Don Lewis <dl-freebsd@catspoiler.org>, ktsin@acm.org, freebsd-current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Memory corruption in CURRENT Message-ID: <20020822090651.GA2024@laptop.6bone.nl> In-Reply-To: <20020822094025.L34509-100000@levais.imp.ch> References: <200208220704.g7M74Lwr035988@gw.catspoiler.org> <20020822094025.L34509-100000@levais.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 22, 2002 at 09:43:45AM +0200, Martin Blapp wrote: > I suspect all the SIG4 and SIG11 problems we see are due > memory corruption in CURRENT. > > > In the latter case, the affected file looks like: > > > > case HASH('^', 'e'): > > case HASH('^', 'i'): > > case HASH('^' 'o'): > > \xc0 case HASH('^', 'u'): > > %case HADH('`', \xc0A'): > > ^@ase HASH('`', 'E'): > > case HASH('`', 'I'): > > case HASH('`', 'O'): > > case HASH('`', 'U'): > > > > The file is correct after a reboot, so the corruption was limited to the > > copy cached in RAM. > > Thats memory corruption. I'm also not able anymore > to make 10 buildworlds (without -j, that triggers > panics in pmap code). > > Bye the way, I'm experiencing this since about 4-5 months. > > All hackers, please help to track this down. Is it P4 specific or not? 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-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020822090651.GA2024>