Date: Tue, 03 Dec 1996 08:49:46 +0800 From: Peter Wemm <peter@spinner.dialix.com> To: "J.M. Chuang" <smp@bluenose.na.tuns.ca> Cc: erich@lodgenet.com (Eric L. Hernes), smp@freebsd.org Subject: Re: Status report... Message-ID: <199612030049.IAA02845@spinner.DIALix.COM> In-Reply-To: Your message of "Mon, 02 Dec 1996 18:58:22 -0400." <199612022258.SAA10867@bluenose.na.tuns.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
"J.M. Chuang" wrote: > > 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': [..] I know about some problems here, I bailed out last night before I fell asleep with a jumbo set of diffs to back out some more stuff again, given my .. umm... "deadly" ... track record of problems with commits while 99% asleep at the keyboard. If you were to time a 'make -j 8' or whatever, you'll currently notice that it is no faster than a 'make'.... Parallel scheduling is rather broken as a result of automatically starting the AP cpu's. I don't know why, but turning it off (again!) fixes it. > Besides, if the system is rebooted, I always got the message like: > > I'm on cpu #1, I need to be on cpu #0! Yes, according to the MPSPEC, the only cpu that is allowed to reboot or halt the system is the primary CPU. The reboot code has to try and shift itself onto cpu#0 if it starts elsewhere. > Jim Cheers, -Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612030049.IAA02845>