Date: Tue, 6 Dec 2005 15:20:30 -0500 From: John Baldwin <jhb@freebsd.org> To: Craig Boston <craig@tobuj.gank.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Weird PCI interrupt delivery problem Message-ID: <200512061520.31168.jhb@freebsd.org> In-Reply-To: <20051206035228.GA34979@nowhere> References: <20051130020734.GA6577@nowhere> <20051206015129.GA34415@nowhere> <20051206035228.GA34979@nowhere>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 05 December 2005 10:52 pm, Craig Boston wrote: > On Mon, Dec 05, 2005 at 07:51:29PM -0600, Craig Boston wrote: > > With the ACPI timer disabled (debug.acpi.disabled=timer), the ACPI+APIC > > case now behaves the same as the plain APIC case. Each IRQ gets > > anywhere from 10,000-500,000 interrupts before it simply stops working. > > And to follow up to myself yet again, the i8254 timecounter is also bad > news for APIC. Switching to it, with or without ACPI, causes things to > stop working really fast. > > Just a stab in the dark, but it sounds like there may be something > screwy going on in the interconnect between the I/O APIC and the 8259s. > I'm pretty familiar with old-style (ISA) design, but somewhat fuzzy on > exactly how those two normally coexist, especially when everything is > integrated together on a bridge chip somewhere. > > IIRC there used to be some mixed-mode hacks that have been cleaned up in > 6.0. Might Windows still be doing something similar and that's why it > works? No, Windows doesn't use mixed mode. That stuff only had to do with routing IRQ0 anyways. We use the lapic timer instead of IRQ0 now (as does Windows). -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200512061520.31168.jhb>