Never, I haven't. Actually, I did knew it was possible to set the affinity, but I was never curious about it until I got this. and checked the cpu_smp_affinity and was always set to 'f'
I did, however, installed some time ago 'ulatencyd' and 'schedtool', but I uninstalled them (--purge remove) before creating the bug (and yes, the system was rebooted after remove the packages). Would it be possible that those packages screwed something else? After changing all my processes affinity, I haven't rebooted the system, so I don't know if I'm going to get this again or not. Will check again tomorrow. cheers 2012/4/30 Ben Hutchings <b...@decadent.org.uk> > On Mon, 2012-04-30 at 12:32 -0300, Wido wrote: > > Ok, not a kernel bug! > > > > > > My last question 'default taskset is set to mask 8, is that ok?' is > > the key. I have a 4 cores system and mask 8 means the 4th core (the > > one beeing actually used). > > Right, it selects CPU 3 only (according to Linux numbering). > > > I changed all the proccesses affinity to 'f' and then the processes > > started to spread in all 4 cores, as it should. > > > > > > Funniest part is, default_smp_affinity is set to 'f', so I don't know > > why proccesses start with affinity 8 > > I don't know. Did you explicitly configure the affinity of anything > before this? > > Ben. > > -- > Ben Hutchings > Design a system any fool can use, and only a fool will want to use it. > -- Wido
