From owner-freebsd-stable Fri Jan 19 9: 6:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 18C0C37B6A2 for ; Fri, 19 Jan 2001 09:06:27 -0800 (PST) Received: from [128.9.176.134] (ras34.isi.edu [128.9.176.134]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id JAA13664; Fri, 19 Jan 2001 09:06:15 -0800 (PST) User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Fri, 19 Jan 2001 09:06:14 -0800 Subject: Re: SMP & APM (was Re: SMP & signal 11) From: Lars Eggert To: Volker Stolz , , Jamil Taylor , Message-ID: In-Reply-To: <20010119094456.A13840@agamemnon.informatik.rwth-aachen.de> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In local.freebsd-stable, you wrote: >> options SMP >> options APIC_IO >> device apm0 at nexus? # Advanced Power Management >> >> enabled in a kernel config file causes spurious signal 11's under >> FreeBSD-4.2 when more than one CPU is present in the system. > > Just on a specific machine? My dual Celerons are running fine w/o *any* > sig-11 for about a year tracking -STABLE. I've tried it on two different (but identical) brand-new Dell Precision 620's. At first I believed it to be a hardware problem, but then thesecond machine showed the same problems, and not including APM fixes it reliably on both machines. I'd be willing to invest a little time tracking this down, if one of the SMP people told me what information to gather and/or patches to apply. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message