On Wed, Jul 21, 2004 at 12:04:22AM -0700, Julian Elischer wrote: > Jake Hamby wrote: > > 3) Random freezes > > > > > After an average of 30-40 minutes of heavy usage, I get random system > > freezes. I am typically running XFree86 and downloading something > > or reading web pages at the time it happens. More disturbingly, I am > > occasionally seeing files get renamed, for example > > /usr/src/UPDATING.64BIT became /usr/src/UPDATING.64BTT. This happens > > with or without WITNESS, with INVARIANTS enabled, with or without > > ACPI, and with or without SMP. I am using SCHED_ULE and no > > PREEMPTION. > > you are not alone.. I think you just chose a bad moment to > jump into -current > :-/ Who else is getting random memory corruption? I've only ever seen it in my life with bad RAM/bad cooling, but this could be bad anything, including something spamming random addresses with DMA. The characters 'I' and 'T' are far enough apart such that I wouldn't expect a simple memory error which usually seems to appear as a single bit flip. I don't think this is normal at all. Try burning memtest86 to a floppy or CD to ascertain a a bit more about your hardware, first. If it's a piece of hardware randomly DMAing around, taht's certainly pretty terrible. It would be awesome if someone had a utility to map all of the memory in a running system out into a format showing who allocated it, and what it's doing (contigmalloc, malloc, zone, user, free, cached memory information). I would think if you knew the memory getting corrupted and what was reasonably close to it, you could make some guesses as to what's doing it. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green_at_FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\Received on Wed Jul 21 2004 - 08:24:25 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:02 UTC