ulpt_tick after close
sigsegv at radiotube.org
Sun May 29 11:22:20 PDT 2005
Ian Dowse wrote:
>In message <42998B18.8020806 at 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.
More information about the freebsd-usb