From owner-freebsd-current@FreeBSD.ORG Tue Nov 4 10:46:56 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 AE41616A4CE for ; Tue, 4 Nov 2003 10:46:56 -0800 (PST) Received: from mail.speakeasy.net (mail8.speakeasy.net [216.254.0.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6B0543FE1 for ; Tue, 4 Nov 2003 10:46:55 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 3693 invoked from network); 4 Nov 2003 18:46:47 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 4 Nov 2003 18:46:47 -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 hA4Ik5ce070464; Tue, 4 Nov 2003 13:46:11 -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: <20031105043233.G840@gamplex.bde.org> Date: Tue, 04 Nov 2003 13:46:05 -0500 (EST) From: John Baldwin To: Bruce Evans 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:46:56 -0000 On 04-Nov-2003 Bruce Evans 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. > > I have noticed the following problems with the new interrupt code so far: > - it conflicts with a few thousand lines of local changes. > - yesterday's backup kernels which I preserved to run benchmarks with > all hang at boot time while probing atapicam devices. Backing out > rev.1.23 of ata-lowlevel.c fixes the hang, but I didn't back up > yesterday's sources so it will take some work to regenerate working > versions of yesterday's kernels. > > The following is without the local changes: > - cyintr(int unit) panics becauase it is passed a pointer to somewhere. > I think all compat_isa devices are broken for unit 0 because unit 0 > is represented by a null pointer. Ah, ok. Yes, this is a semantic change. To try and support clock interrupts, a fast handler that passes a NULL argument will get a pointer to the intrframe as its argument. I got the idea via sparc64 from jake@. Perhaps something can be faked up in the compat_isa shims to fix this. Please try http://www.FreeBSD.org/~jhb/patches/isa_compat.patch > - on a BP6, UP kernels without apic work except for cyintr(), but SMP > kernels have problems with missing interrupts for ata devices and hang > at boot time. Is this related to the ata-lowlevel commit you mentioned above? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/