From owner-freebsd-stable@FreeBSD.ORG Fri Feb 11 15:28:59 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DE6D16A4CE for ; Fri, 11 Feb 2005 15:28:59 +0000 (GMT) Received: from u2.hansa.kiev.ua (citynet-gw.hansa.kiev.ua [217.76.196.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8407343D2D for ; Fri, 11 Feb 2005 15:28:57 +0000 (GMT) (envelope-from dliakh@hansa.ua) Received: from [217.76.196.229] (dliakh@nirvana.hansa.kiev.ua [217.76.196.229]) by u2.hansa.kiev.ua (8.12.9p2/8.12.9) with ESMTP id j1BFSWUn042742; Fri, 11 Feb 2005 17:28:33 +0200 (EET) (envelope-from dliakh@hansa.ua) Message-ID: <420CCF20.3070804@hansa.ua> Date: Fri, 11 Feb 2005 17:28:32 +0200 From: Dmitry Liakh User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: ru-ru, ru MIME-Version: 1.0 To: Lefteris Tsintjelis References: <420B8ED9.1C385BEF@ene.asda.gr> <6.2.1.2.0.20050210121207.04af0690@64.7.153.2> <6.2.1.2.0.20050211073542.047ba9d8@64.7.153.2> <420CC1D7.AEF32E05@ene.asda.gr> In-Reply-To: <420CC1D7.AEF32E05@ene.asda.gr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=-1.0 required=5.0 tests=IN_REP_TO,REFERENCES,USER_AGENT version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-stable@freebsd.org Subject: Re: Server reboots when silo overflows - FreeBSD 4.11 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Feb 2005 15:28:59 -0000 Lefteris Tsintjelis пишет: >Mike Tancsa wrote: > > >>Take out the sio2 and sio3 definitions and just have >> >>device sio >>device puc >> >>leave sio0 and sio1 as is. >> >> > >That didn't work either. Kernel kept on core dumping. > >What worked, and got me pretty worried, is: > >Dmitry Liakh wrote: > > >>Try non-SMP kernel or disable HTT. >> >> > >#options SMP >#options APIC_IO > >When I disabled these 2 everything worked well! I worry because >I have a few installations of v4 with SMP/HTT and there are no >immediate plans to upgrade to v5 yet. > > I afraid that there is only 2 ways to solve: either to do not use puc(4) with SMP kernel or to fix some bugs it have that make it not SMP-compatible. I had the same problem and, unfortunately, I choosed the first way. P.S. there was even some PR on this issue, but I don't know the status of it for now P.P.S. excuse me if there are some mistakes in text, I'm not a native English speaker