atom feed47 messages in org.freebsd.freebsd-hackersMemory corruption in CURRENT
FromSent OnAttachments
Martin BlappAug 22, 2002 12:43 am 
Mark SantcroosAug 22, 2002 2:06 am 
Soeren SchmidtAug 22, 2002 2:09 am 
Martin BlappAug 22, 2002 2:23 am 
Soeren SchmidtAug 22, 2002 2:28 am 
Udo SchweigertAug 22, 2002 2:30 am 
Don LewisAug 22, 2002 2:31 am 
Terry LambertAug 22, 2002 2:33 am 
Terry LambertAug 22, 2002 2:38 am 
Mark SantcroosAug 22, 2002 2:39 am 
Mark SantcroosAug 22, 2002 2:40 am 
Mark SantcroosAug 22, 2002 2:40 am 
Don LewisAug 22, 2002 2:48 am 
Terry LambertAug 22, 2002 2:54 am 
Mark SantcroosAug 22, 2002 2:59 am 
Terry LambertAug 22, 2002 3:16 am 
KT SinAug 22, 2002 3:18 am 
Don LewisAug 22, 2002 3:23 am 
Mark SantcroosAug 22, 2002 3:25 am 
Martin BlappAug 22, 2002 3:45 am 
Terry LambertAug 22, 2002 4:17 am 
Terry LambertAug 22, 2002 4:23 am 
Terry LambertAug 22, 2002 4:30 am 
Mark SantcroosAug 22, 2002 4:33 am 
Mark SantcroosAug 22, 2002 4:35 am 
Soeren SchmidtAug 22, 2002 4:40 am 
Mark SantcroosAug 22, 2002 4:43 am 
Terry LambertAug 22, 2002 4:44 am 
Soeren SchmidtAug 22, 2002 4:55 am 
Mark SantcroosAug 22, 2002 5:01 am 
Terry LambertAug 22, 2002 5:13 am 
Terry LambertAug 22, 2002 5:21 am 
Mark SantcroosAug 22, 2002 5:26 am 
Bosko MilekicAug 22, 2002 6:19 am 
Martin BlappAug 22, 2002 6:45 am 
Martin BlappAug 22, 2002 8:48 am 
Don LewisAug 22, 2002 11:33 am 
David O'BrienAug 22, 2002 12:29 pm 
Kenneth CulverAug 22, 2002 12:57 pm 
Martin BlappAug 22, 2002 1:06 pm 
Mark SantcroosAug 22, 2002 1:29 pm 
Alexander LeidingerAug 22, 2002 2:22 pm 
Julian ElischerAug 22, 2002 2:28 pm 
Alexander LeidingerAug 22, 2002 2:34 pm 
Maxim M. KazachekAug 22, 2002 7:19 pm 
"Vladimir B. " GrebenschikovAug 23, 2002 4:09 am 
"Vladimir B. " GrebenschikovAug 24, 2002 8:36 am 
Subject:Memory corruption in CURRENT
From:Martin Blapp (mb@imp.ch)
Date:Aug 22, 2002 12:43:23 am
List:org.freebsd.freebsd-hackers

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 majo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message