I wonder; there's a weird problem with softintr's on sparc64, if it's this easy to convert to kcont, doing so might either expose or eliminate the problem? i doubt it; the problem isn't with softintr's in general. it is with the softclock interrupt *only*. .mrg.