My laptop states 441 nselcoll after 13 days of uptime. My server states 0 (though it was rebooted about 22 hours ago). I have a hunch that many of those collisions are the web browsers and apps using webkit/js.
That’s interesting my laptop has: kern.nselcoll=3944 for 11 days uptime and kern.nselcoll=0 for my firewall with 209 days uptime. Time to do some debugging of my laptop.
@edd I’ve had a play with trying to track down the cause of nselcoll, using the diff here, on my laptop. One reliable way to trigger collisions is running siren (firefox also generate collisions but not as consistently as siren) - the collisions seem to occur in response to key presses in siren, but using ktrace on siren hasn’t given me any further clues…yet…
My laptop states 441 nselcoll after 13 days of uptime. My server states 0 (though it was rebooted about 22 hours ago). I have a hunch that many of those collisions are the web browsers and apps using webkit/js.
That’s interesting my laptop has: kern.nselcoll=3944 for 11 days uptime and kern.nselcoll=0 for my firewall with 209 days uptime. Time to do some debugging of my laptop.
I’d be interested to see which processes cause a collision. Should be as easy as adding a printf in the collision code.
@edd I’ve had a play with trying to track down the cause of nselcoll, using the diff here, on my laptop. One reliable way to trigger collisions is running siren (firefox also generate collisions but not as consistently as siren) - the collisions seem to occur in response to key presses in siren, but using ktrace on siren hasn’t given me any further clues…yet…