bug maintainers said it was the kernel too. I haven't experienced an application lock up like that before... actually a new stable version of the kernel was already out. I just hadn't implemented it yet. it is now... and I do customize A LOT... I try to break stuff so I can learn how to fix it. ;-)
<br><br><div><span class="gmail_quote">On 6/7/06, <b class="gmail_sendername">Jeremy Bowers</b> <<a href="mailto:jerf@jerf.org">jerf@jerf.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Caleb Cushing wrote:<br>> yeah... I know I've been killing the right process.... because I never<br>> get the "no process killed" error... and I tried killing it's parent<br>> make... then it just became a child of init. I hope init will take care
<br>> of it. fortunately portage runs with gcc niced so it isn't slowing my<br>> computer down with cpu at 100% I'm going to let it run for a while to<br>> see it it goes away... or I can come up with a way to grab an image for
<br>> the bug report I filed...<br><br>Sometimes a process can get stuck in the kernel. Since it never comes<br>out, it never gets around to checking the signals. This is when even -9<br>is ineffective. I used to see it a lot more than I do nowadays.
<br><br>I wouldn't expect there's any point in waiting for it to come out. gcc<br>is a particularly well-constrained program, even if it is complex, and<br>it's not as if it's likely that you found a hidden O(n^4) algorithm in
<br>gcc while compiling what may be the world's most-often compiled code<br>with the compiler most often used to compile it. :)<br><br>One thing to check is that you didn't over-optimize the kernel, since<br>you mentioned you're running Gentoo. I've also rarely encountered
<br>problems with certain combinations of options, although for something as<br>intermittent as this probably is you'll probably never work it all out.<br><br>In my experience, upgrading to the next point release of the kernel
<br>tends to take care of these things, either because the relevant bug is<br>fixed (and you'd never recognize it in the Changelog unless you knew<br>exactly what to look for) or because it simply shakes up the kernel<br>
enough to never again hit that particular corner case. :)<br></blockquote></div><br>