On Wed, 21 Dec 2005 22:46:00 +0100 (CET), "Siegbert Marschall" <[EMAIL PROTECTED]> wrote:
>Hi, > >> As far as I can tell, the bug smells like a race condition of some sort >> and if my wild guess is correct, it will be difficult to reproduce >> consistently. With some (but not all) race conditions, you can increase >> the chance of triggering them by increasing loads. Since I want the race >> condition to occur, what is the best way stress to the systems while >> also doing make build? >> >well, I have three alphas in the basement where I am trying to figure >this one out, nothing provable yet but everything is pointing into >some hardware problem with the low-end alpha cpus and second-level cache. Due to the old bug reports which may or may not be related, I've been looking into the changes in src/sys/arch/alpha/alpha/locore.s >llsc errors, stuck cachelines and stuff but I didn't dive deep enough >into the code and processor documentations to figure out what's going >on there and will not be in the next weeks/months since I have a few >more pressing issues to take care of first before having the spare >time for this ;) > If I can figure out when the bug entered the tree, it will hopefully make it easy for someone else to figure out the "what" of the problem. Since I lack the skill and experience to deal with figuring out the what, I'm just going to use brute force to figure out the when. ;-) >only thing I can tell is that with netbsd the machines stay up for >weeks/months and with obsd they crash latest after a few days. >no flame, doesn't show that netbsd is better, probably just missing the >tripwire or doesn't care wether it blows. > >good luck, siggi. I've searched the netbsd list archives thoroughly and found no similar bug reports. As far as I know netbsd is not affected. jcr
