Date: Thu, 22 Aug 2002 09:43:45 +0200 (CEST) From: Martin Blapp <mb@imp.ch> To: Don Lewis <dl-freebsd@catspoiler.org> Cc: <marks@ripe.net>, <ktsin@acm.org>, <freebsd-current@FreeBSD.ORG>, <hackers@FreeBSD.ORG> Subject: Memory corruption in CURRENT Message-ID: <20020822094025.L34509-100000@levais.imp.ch> In-Reply-To: <200208220704.g7M74Lwr035988@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi all, 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. Martin 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?20020822094025.L34509-100000>