[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: kernel panic with pccard insert on recent 7.0 CURRENT
- To: "Paolo Pisati" <piso_(_at_)_freebsd_(_dot_)_org>
- Subject: Re: kernel panic with pccard insert on recent 7.0 CURRENT
- From: "Hidetoshi Shimokawa" <simokawa_(_at_)_FreeBSD_(_dot_)_ORG>
- Date: Wed, 20 Jun 2007 22:51:55 +0900
- Cc: mobile_(_at_)_freebsd_(_dot_)_org, wsk_(_at_)_gddsn_(_dot_)_org_(_dot_)_cn, current_(_at_)_freebsd_(_dot_)_org
On 6/19/07, Paolo Pisati <piso_(_at_)_freebsd_(_dot_)_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_(_at_)_FreeBSD_(_dot_)_ORG
_______________________________________________
freebsd-mobile_(_at_)_freebsd_(_dot_)_org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org