Date: Wed, 8 Sep 1999 15:12:30 +0200 (MET DST) From: Mikael Hybsch <micke@securitydynamics.com> To: freebsd-hackers@freebsd.org Subject: Problem with SMP in 3.3-RC Message-ID: <Pine.GSO.4.10.9909081436260.14599-100000@spirit.dynas.se>
next in thread | raw e-mail | index | archive | help
I have been running a 3.2-STABLE from around June 1st on my Asus P2B-D with 2 400MHz PII CPUs (128MB memory) without any problems. Yesterday I cvsup'ed RELENG_3 and now SMP doesn't work anymore. Halfway through /etc/rc some severe memory corruption seems to occur as all new processes core dumps immediately on signal 11. Finally the machine locks up and the reset button it the only way out. Same kernel without SMP works fine. Looking through the commitlogs, I found the two entries below that could be related. So I checked out a RELENG_3 src/sys from 1999/08/29, but that kernel failes in the same way. Tonight I will try to compile and run an older RELENG_3 GENERIC kernel. Does anyone have any idea of what's causing this problem? Is there some driver that doesn't work with SMP? msmith 1999/08/30 18:19:33 PDT MFC: Intel 686 and AMD K6/2 memory range attribute support. This merge brings all of the memory range attribute support from -current back to -stable, as requested by a number of folks. msmith 1999/09/02 16:57:06 PDT Bring back the rest of the changes required to make memory range support work on SMP systems. Tested by various folks on the -stable list, thanks for their patience and support. -- Mikael Hybsch Email: micke@securitydynamics.com Security Dynamics AB Phone: +46-8-7250900 Box 10704 Fax: +46-8-6494970 S-121 29 STOCKHOLM, SWEDEN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.9909081436260.14599-100000>