Date: Fri, 8 Aug 2008 16:27:55 -0700 (PDT) From: Ping Mai <pingmai@yahoo.com> To: freebsd-acpi@freebsd.org, John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org Subject: Re: missing interrupts? Message-ID: <755343.17576.qm@web52907.mail.re2.yahoo.com> In-Reply-To: <200808081610.03720.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks John. tried it but didn't help. --- On Fri, 8/8/08, John Baldwin <jhb@freebsd.org> wrote: > From: John Baldwin <jhb@freebsd.org> > Subject: Re: missing interrupts? > To: freebsd-acpi@freebsd.org > Cc: "ping" <pingmai@yahoo.com>, freebsd-drivers@freebsd.org, freebsd-hackers@freebsd.org > Date: Friday, August 8, 2008, 1:10 PM > On Friday 08 August 2008 02:16:20 pm ping wrote: > > this is an interrupt handler that's attached to > irq 31 on ioapic1 on a 6.1R > kernel, type INTR_TYPE_NET|INTR_MPSAFE. seems that > it's missing interrupts. > watching the KTR trace, it was running along fine, then it > just stopped. > intr handler stopped getting run. but the interrupt > register on chip was > high. is this a case of lost interrupts? or hardware > problem? > > There is one possible race in the I/O APIC code someone > pointed me at > recently. You can try expanding the scope of the icu_lock > to cover all of > ioapic_program_intpin() to see if it fixes your issue > (sys/<arch>/<arch>/io_apic.c) > > -- > John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?755343.17576.qm>