From owner-freebsd-current@FreeBSD.ORG Tue Nov 4 09:19:37 2003 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 17F0716A4CE for ; Tue, 4 Nov 2003 09:19:37 -0800 (PST) Received: from mail.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A06B43FAF for ; Tue, 4 Nov 2003 09:19:36 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 6693 invoked from network); 4 Nov 2003 17:19:35 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 4 Nov 2003 17:19:35 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id hA4HJBce069926; Tue, 4 Nov 2003 12:19:12 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20031104164627.Y22613@pcle2.cc.univie.ac.at> Date: Tue, 04 Nov 2003 12:19:11 -0500 (EST) From: John Baldwin To: Lukas Ertl X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: current@FreeBSD.org Subject: Re: new interrupt code: panic when going multiuser 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, 04 Nov 2003 17:19:37 -0000 On 04-Nov-2003 Lukas Ertl wrote: > On Tue, 4 Nov 2003, John Baldwin wrote: > >> >> On 04-Nov-2003 Lukas Ertl wrote: >> > On Tue, 4 Nov 2003, Lukas Ertl wrote: >> > >> >> I somehow can't get at a good vmcore :-(. But I found out that the >> >> machine boots fine in "Safe Mode", where DMA and hw.ata.wc is turned off. >> > >> > Ok, if I set hw.ata.ata_dma=0 in loader.conf, it boots fine. Could there >> > be some issue with ATAng + new interrupt code? >> >> Can you provide a dmesg please? There may be a weird issue with >> some PPro's for example that I haven't been able to test. > > Sorry for the noise, I think I found the problem: I had to put "options > SMP" and "device apic" into the kernel, now everythings seems to run fine. > I thought they were only needed for SMP kernels, that's at least what > the comment in GENERIC says... If you still want the dmesg, I can send it > to you. Well, a kernel without SMP and just 'device apic' should work fine, and a kernel with both SMP and 'device apic' should also work fine. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/