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 Santcroos RIPE Network Coordination Centre
http://www.ripe.net/home/mark/ New Projects Group/TTM
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message