Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 Dec 1996 18:58:22 -0400 (AST)
From:      "J.M. Chuang"  <smp@bluenose.na.tuns.ca>
To:        erich@lodgenet.com (Eric L. Hernes)
Cc:        smp@freebsd.org
Subject:   Re: Status report...
Message-ID:  <199612022258.SAA10867@bluenose.na.tuns.ca>
In-Reply-To: <199612021949.NAA04298@jake.lodgenet.com> from "Eric L. Hernes" at "Dec 2, 96 01:49:28 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
> I just tested a kernel from this morning (12/1).  It is *much* better
> than the one I tried last week.  Last week I got lots of sig11's, but
> I haven't seen one yet!  But I am getting a few silo overflows
> from the mouse, dmesg shows:
> 
I got the same thing. No sig11's. But when I run multiple processes, 
it seems that all the processes are taken care of by the same cpu
and switched back and forth. On the screen of `top':

RUN/#1     cpp
CPU/#1     top

....

RUN/#0     cpp
RUN/#0     top

Is the schedule supposed like that?


I remember before the merge with the current, the multiple processes
were

RUN/#1     cpp
CPU/#0     top

....


Besides, if the system is rebooted, I always got the message like:

I'm on cpu #1, I need to be on cpu #0!


Jim



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612022258.SAA10867>