From owner-freebsd-smp Fri Nov 29 13:17:36 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07394 for smp-outgoing; Fri, 29 Nov 1996 13:17:36 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA07388 for ; Fri, 29 Nov 1996 13:17:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id OAA29993 for ; Fri, 29 Nov 1996 14:17:26 -0700 Message-Id: <199611292117.OAA29993@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: freebsd-smp@freebsd.org Subject: SMP-current hang problems. In-reply-to: Your message of "Fri, 29 Nov 1996 20:15:50 +0100." <199611291915.UAA00453@donau.informatik.uni-rostock.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 Nov 1996 14:17:26 -0700 Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, we have decided to more or less freeze development till we figure out the "system hang" problem with the latest code. If you have one of the systems that hangs anywhere in the area of: SMP: Idle procs online, starting an AP! SMP: AP CPU #1 LAUNCHED!! Starting Scheduling... SMP: TADA! CPU #1 made it into the scheduler!. SMP: All 2 CPU's are online! we need to here from you ASAP: have you updated any of your -current tree (ie, the non SMP src/sys part) since 96-11-21? (This is the date that SMP was merged with -current) what does "ls -alt /sys" show? try enabling the kernel debugger and see if you can get to it via CONTROL-ALT-ESCAPE when in the hung state. To use the debugger add: options DDB to your kernel config file. "man ddb" for usage. If you can get from the hung state to ddb, do a trace and/or 'ps'. If you have another system or terminal available you could use this idea from Peter: - try using "options FORCE_COMCONSOLE" and use a 9600 baud serial link on com1, if it's an interrupt problem affecting syscons, it might make sense to try getting syscons out of the picture entirely for a test. Also, "options BREAK_TO_DEBUGGER" is useful, you can send a break and get a DDB prompt on the com port (with comconsole enabled). Note: I (smp) think "options FORCE_COMCONSOLE" should be "options COMCONSOLE", add both to be sure. --- I'm about to change the locking on mpboot.s a little, I'll post it as soon as I prove it works here... -- Steve Passe | powered by smp@csn.net | FreeBSD -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzHe7tEAAAEEAM274wAEEdP+grIrV6UtBt54FB5ufifFRA5ujzflrvlF8aoE 04it5BsUPFi3jJLfvOQeydbegexspPXL6kUejYt2OeptHuroIVW5+y2M2naTwqtX WVGeBP6s2q/fPPAS+g+sNZCpVBTbuinKa/C4Q6HJ++M9AyzIq5EuvO0a8Rr9AAUR tBlTdGV2ZSBQYXNzZSA8c21wQGNzbi5uZXQ+ =ds99 -----END PGP PUBLIC KEY BLOCK-----