From owner-freebsd-current Tue Jun 6 20:22:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 9D29B37BBA1; Tue, 6 Jun 2000 20:22:43 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12zWPu-000Hru-00; Wed, 07 Jun 2000 10:22:06 +0700 Date: Wed, 7 Jun 2000 10:22:06 +0700 (ALMST) From: Boris Popov To: Mitsuru IWASAKI Cc: freebsd-current@freebsd.org, freebsd-smp@freebsd.org, msmith@freebsd.org, jlemon@flugsvamp.com, sumitani@bd2.hnes.nec.co.jp Subject: Re: SMP + APM = panic -> fixed! In-Reply-To: <20000607020615U.iwasaki@jp.FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Jun 2000, Mitsuru IWASAKI wrote: > We're having this problem for long time (from the old 4.0-CURRENT > days), but Mr. SUMITANI discovered a bug and fixed it. > The problem was that we got worng gdt pointer for the current cpu, > then panic... > The followings is a patch to fix the problem. Thanks a lot, SUMITANI-san! Yes, this fixes panic and even 'halt -p' works as expected. 'zzz' command works too, but machine never come back from the suspend mode (looks like interrupt controller programmed incorrectly or something like this). -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message