Date: Fri, 2 Dec 2005 19:43:56 -0600 From: Craig Boston <craig@tobuj.gank.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org, imp@freebsd.org Subject: Re: Weird PCI interrupt delivery problem Message-ID: <20051203014356.GC22567@nowhere> In-Reply-To: <200512020817.55769.jhb@freebsd.org> References: <20051130020734.GA6577@nowhere> <200512011342.19417.jhb@freebsd.org> <20051202013146.GA15424@nowhere> <200512020817.55769.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 02, 2005 at 08:17:53AM -0500, John Baldwin wrote: > > Argh, this is driving me up the wall. I had a hunch that it was somehow > > connected to level-triggered interrupts. That seems to not be the case, > > as upon closer inspection the SCI interrupt (9) gets reprogrammed to > > level/low. I can read the ACPI status all day long and the count for > > IRQ 9 goes up and up without freezing... > > Interesting. How about IRQ 11 in non-APIC mode, is it programmed to > level/low? I've seen BIOSes that do very stupid things like have the link > devices set to level/hi or edge/lo or even edge/hi. A verbose boot should > tell you if any settings are changed though, and in the APIC case you should > see the initial defaults as well. Added some printfs to i386/isa/atpic.c. At bootup, everything is programmed by the BIOS to edge/high, except IRQ 11 which is set to level/low. FreeBSD doesn't seem to be changing that as far as I can tell. (this is -APIC -ACPI) Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051203014356.GC22567>