Date: Wed, 5 Nov 2003 06:13:42 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: John Baldwin <jhb@FreeBSD.org> Cc: Lukas Ertl <l.ertl@univie.ac.at> Subject: Re: new interrupt code: panic when going multiuser Message-ID: <20031105055205.L1266@gamplex.bde.org> In-Reply-To: <XFMail.20031104134605.jhb@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
> > 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. Brucehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031105055205.L1266>