Date: Sun, 29 May 2005 20:23:07 +0200 From: Jan-Espen Pettersen <sigsegv@radiotube.org> To: Ian Dowse <iedowse@iedowse.com> Cc: freebsd-usb@freebsd.org Subject: Re: ulpt_tick after close Message-ID: <429A088B.1090405@radiotube.org> In-Reply-To: <200505291310.aa19689@nowhere.iedowse.com> References: <200505291310.aa19689@nowhere.iedowse.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ian Dowse wrote: >In message <42998B18.8020806@radiotube.org>, Jan-Espen Pettersen writes: > > >>I think I'll replace that printf with a panic in ulpt_read_cb to get a >>backtrace next time. (And at the same time update my sources) As it >>would reveal what is actually calling ulpt_read_cb after the callout has >>been stopped. The problem is that this is very unlikely to happen during >>a single print job, but it does over time, so it might take me some time >>to get that backtrace. >> >> > >Thanks for the details. By the way, is it lpd or something else >that is actually accessing the ulpt device? Below is a patch you >could try that will hopefully find out a bit more about what is >going on. You could also change the new return statement in >ulpt_read_cb() to a panic, as the stack trace might reveal more >information like you say. > > It is cups from ports. Thank you very much. Jan-Espen Pettersen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?429A088B.1090405>