>upgrade to the latest linuxtv sources and try to reproduce that
>problem, since you haven't submitted complete logs it's difficult to
>trace the error.
>That issue might already be solved in the latest sources.
>Markus
>On 7/26/07, lwtbenben <lwtbenben@xxxxxxx> wrote:
>>>在2007-07-25，"Markus Rechberger" <mrechberger@xxxxxxxxx> 写道： can you submit
>>>a _full_ syslog file of your system (not only a cut out part of it)?
>>>There was a problem in earlier kernels with USB hotplugging, if a
>>>device disappeared or rebooted the DVB framework deallocated the
>>>structures immediatelly, so if something tried to access the data
>>>structures when the device was already deallocated it caused a kernel
>>>oops.
>>>Markus
>>>On 7/25/07, lwtbenben <lwtbenben@xxxxxxx> wrote:
>>>> Could somebody please give me some explanation about the structure
>>>> usb_data_stream_properties, I have no idea how should I initialize my
>>>> usb_data_stream_properties.
>>>> Thank you in advance.
>>
>> Dear Markus:
>> Thank you for your reply.
>> And last night, I traced this kernel oops, it turned out to be a failure
>> when the DVB core release my stream objects.
>> dvb_usb_exit(struct
>> dvb_usb_device)->dvb_usb_adapter_exit(struct
>> dvb_usb_device)->dvb_usb_adapter_stream_exit(&struct
>> dvb_usb_device *d->adapter)->usb_urb_exit(adap->stream)
>> So I modified my struct dvb_usb_device_properties structure, mainly the
>> usb_data_stream_properties.buffersize, and the kernel oops
>> disappear.
>> But I do not understand, can you give me some help on this issue.
>> And I just can not get the meaning of the usb_data_stream_properties. :(:(
Thank you for ur advice but do we have any material which describes these dvb_usb about data structures?????
财 富 一 骰 间：好 玩 刺 激 的 网 络 大 富 翁 来 啦！快 去 看 看
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
