From owner-freebsd-current@FreeBSD.ORG Tue Aug 24 04:22:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C74116A4CE for ; Tue, 24 Aug 2004 04:22:49 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D75B843D41 for ; Tue, 24 Aug 2004 04:22:48 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i7O4KPwj089133; Tue, 24 Aug 2004 00:20:25 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i7O4KOJU089130; Tue, 24 Aug 2004 00:20:24 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 24 Aug 2004 00:20:24 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: andy@bradfieldprichard.com.au In-Reply-To: <53654.203.41.12.153.1093299636.squirrel@bpgate.speednet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: PLEASE TEST: IPI deadlock avoidance patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Aug 2004 04:22:49 -0000 On Tue, 24 Aug 2004 andy@bradfieldprichard.com.au wrote: > > > > Thanks to everybody for confirming the fix :-) > > -- > > With the patch applied, during a make -j4 buildworld my box still hangs > with the following (bright-white) messages on the console: > > > ... > panic: APIC: Previous IPI is stuck > cpuid = 0; > boot() called on cpu#0 > Uptime: 3h57m24s > Cannot dump. No dump device defined. > panic: malloc(M_WAITOK) in interrupt context > cpuid = 0; > KDB: enter: panic > Could you set the following sysctl: debug.kdb.stop_cpus=0 It's also a tunable in HEAD, but not yet RELENG_5, so you'll need to set it at run time. This will prevent KDB from trying to IPI the other CPUs to stop them while the current CPU is in KDB. However, during an IPI deadlock, this won't work. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > > :( > > > Some dmesg info: > > > FreeBSD 5.3-BETA1 #0: Mon Aug 23 23:46:21 EST 2004 > root@hummer:/slim/obj/hummer/src-current/src/sys/GENERIC > WARNING: WITNESS option enabled, expect reduced performance. > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Pentium Pro (198.95-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x619 Stepping = 9 > Features=0xfbff > real memory = 536870912 (512 MB) > avail memory = 515706880 (491 MB) > MPTable: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 4 > ioapic0: Assuming intbase of 0 > ioapic1: Assuming intbase of 16 > ioapic1 irqs 16-31 on motherboard > ioapic0 irqs 0-15 on motherboard > > > > -andyf > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >