> I've been offering the attached patch to try to debug the source of > the problem before the symptom you described happens. I haven't > gotten any diagnostics back from anyone yet. If you can, please try > it out and let me know.
i've got this running on my laptop but i'm not using it very heavily right now. however, i did see a problem with this patch on a different system i meant to tell you about... ah, good, the console log is still handy: radeondrmkmsfb0 at radeon0 radeon0: info: registered panic notifier wsdisplay0 at radeondrmkmsfb0 kbdmux 1 panic: kernel diagnostic assertion "l->l_exlocks == 0" failed: file "/usr/src5/sys/sys/userret.h", line 87 53 exlocks held cpu0: Begin traceback... vpanic(c0ae3318,dc7f2f1c,dc7f2f9c,c083941d,c0ae3318,c0ab4a0d,c0ae32e0,c0ae32b4,57,35) at netbsd:vpanic+0x121 kern_assert(c0ae3318,c0ab4a0d,c0ae32e0,c0ae32b4,57,35,dc7f2f58,c0688593,0,c4acbd80) at netbsd:kern_assert+0x23 trap() at netbsd:trap+0xbae --- trap (number 6) --- bbbefe30: cpu0: End traceback... fatal breakpoint trap in supervisor mode trap type 1 code 0 eip c022a654 cs 8 eflags 246 cr2 bbbefe30 ilevel 0 esp dc7f2f00 curlwp 0xc4ab2000 pid 1 lid 1 lowest kstack 0xdc7f02c0 Stopped in pid 1.1 (init) at netbsd:breakpoint+0x4: popl %ebp i didn't look any further right then, i just reverted the patch. config options appear to be just DIAGNOSTIC and makeoptions DEBUG. .mrg.