Date: Fri, 1 Apr 2005 21:44:10 +0200 From: Sebastien B <sebastien.b@swissinfo.org> To: freebsd-usb@freebsd.org Subject: Re: panic: uhci_abort_xfer: not in process context (was Re: uplcom / ucom problems on RELENG_5) Message-ID: <200504012144.11468.sebastien.b@swissinfo.org> In-Reply-To: <200503311946.23151.hselasky@c2i.net> References: <6.2.1.2.0.20050329222822.04f7c500@64.7.153.2> <6.2.1.2.0.20050331074641.04f72eb8@64.7.153.2> <200503311946.23151.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> When one is designing a driver, it is very convenient if USB-transfers can > be stopped/started from the callback of another USB-transfer. I have run exactly into the same trouble by calling usbd_bulk_transfer() from a software interrupt handler (scheduled to run from the context of the start procedure of a network interface in order to send packets). The kernel panics with "ehci_abort_xfer: not in process context" a few while after the transfer. Is it the same problem ? Is a software interrupt handler unsuitable for the abort xfer function ? How can I fix it, by using a task queue instead of a software interrupt handler ? Regards, Sebastien
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504012144.11468.sebastien.b>