Date: Fri, 1 Apr 2005 21:35:06 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: Mike Tancsa <mike@sentex.net> Cc: freebsd-usb@freebsd.org Subject: Re: panic: uhci_abort_xfer: not in process context (was Re: uplcom / ucom problems on RELENG_5) Message-ID: <200504012135.07798.hselasky@c2i.net> In-Reply-To: <6.2.1.2.0.20050401093603.03253ad0@64.7.153.2> References: <6.2.1.2.0.20050329222822.04f7c500@64.7.153.2> <200504011631.51760.hselasky@c2i.net> <6.2.1.2.0.20050401093603.03253ad0@64.7.153.2>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 01 April 2005 16:50, Mike Tancsa wrote: > At 09:31 AM 01/04/2005, Hans Petter Selasky wrote: > >What dmsg appears when you attach your device? If "ugen", then make sure > > you have got "device ucom" and "device uplcom", in the kernel config > > file. If you are loading "ucom"/"uplcom" from modules, make sure that > > those modules are re-compiled. Else try to enable debugging and see what > > happens: > > Hi, > It was showing up as a ucom device. Also, the patches no longer > apply cleanly after the MFCs that were done yesterday afternoon. I also > have a CURRENT box I can test against if thats easier to try against. Do > you know if the patches apply cleanly on it ? > Some patches will fail, but that is OK until further. I am not sure if the driver will install cleanly with 6-current. Last time I checked was in February. Yours --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504012135.07798.hselasky>