[lkml]   [1998]   [Nov]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.1.129 Scheduling Issue?
On Sun, 22 Nov 1998, Tom Eastep wrote:
> Michael K Vance wrote:
> > however. Eventually I was able to get 'top' running, and saw that two
> > instances of 'bash' were taking up 46% and 44% or so of the CPU. I killed
> > both, but then 'init' simply took over 98% or so of the CPU. Killing my window
> > manager (?) seemed to fix all of this.
> >
> > Info:
> >
> > 2.1.129 clean with SMP commented out
> This is a know problem with recent development kernels. Either
> uncomment 'SMP = 1' in your Makefile or get the patch that Linus
> posted the other day.

Maybe it's nice to know for Michael that the problem isn't
with the scheduling code (as he assumed) but with the fork()
and syscall() code, which resulted in schedule() getting
rubbish as input and following the GIGO principle...

let this be your first official kernel hacking lesson :)


Rik -- slowly getting used to dvorak kbd layout...
| Linux memory management tour guide. |
| Scouting Vries cubscout leader. |

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:45    [W:0.060 / U:0.980 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site