On Sat, Jan 19, 2008 at 03:52:44PM +0100, dAniel hAhler wrote: > Hello, > > I've now found the reason and a workaround for this. Apparently, it's > related to CONFIG_FAIR_USER_SCHED and can be worked around by > assigning a really small value to the boinc users cpu_share (125 is > the uid of "boinc"): > $ echo 2 | sudo tee /sys/kernel/uids/125/cpu_share >
Correct, that is the way to go about it. > While looking around, I've found the following patch, which seems to > address this: > http://www.ussg.iu.edu/hypermail/linux/kernel/0710.3/3849.html > > It has been posted here, but without any response. > > btw: writing 1 into "cpu_share" totally locks up the computer! > Can you please provide some more details. Can you go into another console (try ctrl-alt-f1) and try to reproduce the issue there. Could you take a photo of the oops/panic and upload it somewhere so that we can see it? Thanks -- regards, Dhaval -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/