On Mon, Dec 16, 2002 at 11:25:05PM +0100, Paolo Pisati wrote: > On Mon, Dec 16, 2002 at 09:55:09PM +0100, Marc Fonvieille wrote: > > > > We talked about a problem between X and -CURRENT, we had no problem > > with -STABLE. > > A problem that MAYBE is still present even in CURRENT, don't > you think? >
Once again, I was not talking about the same problem as yours. > As i said, i don't have my laptop right now, so i couldn't > test CURRENT on it ( but i'll do it ASAP ), and i was looking > for someone else with the same problem... > > > > Btw I don't see how memtest can report memory corruption, I thought it > > was to test "hardware" problem. > > hardware problem? > > VERY strange, cause IF i load the agp module i got errors > from memtest, system freeze&crash, then if i disable the > agp module, memtest reports 0 errors (even after hours&hours of > test), no crash&freeze, etcetc > As you can it doesn't look like an hardware problem, i think it's a > FreeBSD-related problem, probably toggled by the agp && drm stuff > You missed my point, memtest is a test for hardware. >From memtest site: memtest is a utility for testing the memory subsystem in a computer to determine if it is faulty. It's to test if your ram is "bad", not to see a software problem. The "memtest crash" may come from a totally different reason and could occur in other situation. In fact you should fill a PR with all infos about your problem. Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message