Date: Wed, 20 Jun 2007 22:51:55 +0900 From: "Hidetoshi Shimokawa" <simokawa@FreeBSD.ORG> To: "Paolo Pisati" <piso@freebsd.org> Cc: mobile@freebsd.org, wsk@gddsn.org.cn, "M. Warner Losh" <imp@bsdimp.com>, current@freebsd.org Subject: Re: kernel panic with pccard insert on recent 7.0 CURRENT Message-ID: <626eb4530706200651s255e2ff2u80d70d2d887c8e4c@mail.gmail.com> In-Reply-To: <20070618183627.GA2183@tin.it> References: <46734A3E.3010903@gddsn.org.cn> <626eb4530706160525o54234621s2de098e64cdeb4fe@mail.gmail.com> <20070616.173002.-457443410.imp@bsdimp.com> <626eb4530706161858l5f60d67ej55874cb9348e649b@mail.gmail.com> <20070618183627.GA2183@tin.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/19/07, Paolo Pisati <piso@freebsd.org> wrote: > On Sun, Jun 17, 2007 at 10:58:12AM +0900, Hidetoshi Shimokawa wrote: > > And INTR_FILTER doesn't seem well-tested at least for > > handling of stray interrupts for filter only IRQs. > > I need the following patch to workaroung the problem. > > > > http://people.freebsd.org/~simokawa/tmp/kern_intr.c-20070617.patch > > on which platform? amd64 > cause, right now, if there's a stray interrupt we disable the > irq line if the interrut disable function is hooked to > ie_disab: My patch may be wrong. But it seems too restrictive to disable the interrupt forever only one stray interrupt. Drivers could return _STRAY even if it is the source. > kern_intr.c::intr_event_handle(): > > ... > if (thread & FILTER_HANDLED) { > if (ie->ie_eoi != NULL) > ie->ie_eoi(ie->ie_source); > } else { > if (ie->ie_disab != NULL) > ie->ie_disab(ie->ie_source); > } > ... > > bye, > P. > > -- /\ Hidetoshi Shimokawa \/ simokawa@FreeBSD.ORG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?626eb4530706200651s255e2ff2u80d70d2d887c8e4c>