From owner-freebsd-current@FreeBSD.ORG Tue Nov 4 11:13:51 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 C682E16A4CE; Tue, 4 Nov 2003 11:13:51 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1354343F93; Tue, 4 Nov 2003 11:13:50 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id GAA04045; Wed, 5 Nov 2003 06:13:43 +1100 Date: Wed, 5 Nov 2003 06:13:42 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: John Baldwin In-Reply-To: Message-ID: <20031105055205.L1266@gamplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 19:13:51 -0000 > > 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. Clock interrupt handlers have always been a nasty special case. > Please try http://www.FreeBSD.org/~jhb/patches/isa_compat.patch Will try later today. It should work, but adds yet more overhead. > > - 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? No. It looks like the interrupt is really going missing for some reason. This is without any acpica. Bruce