From owner-freebsd-current@FreeBSD.ORG Tue Nov 4 10:38:33 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 07B0F16A4CE for ; Tue, 4 Nov 2003 10:38:33 -0800 (PST) Received: from mail.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD95443FDD for ; Tue, 4 Nov 2003 10:38:31 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 12303 invoked from network); 4 Nov 2003 18:38:30 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 4 Nov 2003 18:38:30 -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 hA4Ic1ce070405; Tue, 4 Nov 2003 13:38:01 -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: <200311041833.27722@harrymail> Date: Tue, 04 Nov 2003 13:38:01 -0500 (EST) From: John Baldwin To: Harald Schmalzbauer X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: current@freebsd.org cc: Lukas Ertl 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 18:38:33 -0000 On 04-Nov-2003 Harald Schmalzbauer wrote: > On Tuesday 04 November 2003 18:19, John Baldwin wrote: >> 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. > > Hmm, I think this answer should be for "New and aPic question"? > > Well I tired to build one (with -curr some weeks ago) with device apic only > which didn't work, I had to add options smp arrrgghhh. Had a look in my file > and saw I did the following: >#options SMP >#options APIC_IO > > Seems I didn't use "device apic" (perhaps I didn't recognize) > > But regardless, when I built a SMP kernel it didn't run on my UP machine. > > Thanks a lot, I just committed a bunch of changes to the interrupt and SMP code. When you update to those changes, you should be able to build a UP kernel with 'device apic' and have it work, and you should be able to build an SMP kernel and have it run on your machine. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/