No subject

old as Aug 20, 2010 -- so this is likely to have been resolved as you stated
already.

On Thu, Oct 14, 2010 at 08:38:31AM -0400, JE Geiger wrote:
>Are you running the most current code snapshot from isely.net?
>
>What is your Kernel version?
>
>I was generating Kernel panics with the in tree Kernel source on rmmod
>with a similar output.  The string is mangled on the "unregistered
>device".  There were problems with 2.6.34.x changes in the
>driver/Kernel objects and order in which object destructors were being
>called within the pvrusb2 driver.  I would defer to Mike for the true
>story of the repair, I observed it from afar a layman.
>
>The name of the object was being printed after it had been destroyed
>thus the mangled/garbage string.  Mike fixed up all the issues.  If
>you are running the most current module code from isely.net and still
>seeing this issue, the problem has come back.
>
>http://www.isely.net/downloads/pvrusb2-mci-20100708.tar.bz2 is the
>most current source.
>
>I was having problems with Kernel 2.6.34.x.  I am now running 2.6.34.7
>with the above current 7/8/10 snapshot and have not had a recurrence
>of the  modprobe/rmmod problem.
>
>
>
>
>
>On Thu, Oct 14, 2010 at 5:11 AM,  <rogerx at sdf.org> wrote:
>> I encountered a CPU run with rmmod pvrusb2 and then several seconds later
>> modprobing pvrusb2.
>>
>> From what top shows, pvrusb2-context either hung on modprobe or rmmod.
>>
>>
>> # tail /var/log/everything/current  -n 20
>> Oct 14 00:53:36 [kernel] tda18271 0-0060: creating new instance
>> Oct 14 00:53:36 [kernel] TDA18271HD/C1 detected @ 0-0060
>> Oct 14 00:53:37 [kernel] tda829x 0-0042: type set to tda8295+18271
>> Oct 14 00:53:40 [kernel] usb 3-4: firmware: requesting v4l-cx2341x-enc.fw
>> Oct 14 00:53:41 [kernel] pvrusb2: firmware2 upload transfer failure
>> Oct 14 00:53:41 [kernel] pvrusb2: Clearing driver error statuss
>> Oct 14 00:53:43 [kernel] cx25840 0-0044: 0x0000 is not a valid video input!
>> Oct 14 00:53:43 [kernel] DVB: registering adapter 0 frontend 0 (Samsung S5H1411
>> QAM/8VSB Frontend)...
>> Oct 14 00:53:43 [kernel] tda829x 0-0042: type set to tda8295
>> Oct 14 00:53:43 [kernel] tda18271 0-0060: attaching existing instance
>> Oct 14 00:53:47 [kernel] usbcore: deregistering interface driver pvrusb2
>> Oct 14 00:53:47 [kernel] pvrusb2: Device being rendered inoperable
>> Oct 14 00:53:47 [kernel] pvrusb2: unregistered device â– â– â– o0 [mpeg]
>> Oct 14 00:53:47 [kernel] pvrusb2: unregistering DVB devices
>> Oct 14 00:54:02 [kernel] SysRq : Emergency Sync
>> Â  Â  Â  Â  Â  Â  Â  Â - Last output repeated 2 times -
>>
>>
>> Top shows:
>> PID Â  USER Â  Â  Â PR Â NI Â VIRT Â RES Â SHR S %CPU %MEM Â  Â TIME+ Â  COMMAND
>> 26142 root      20   0     0    0    0 R  100  0.0    5:31.30 pvrusb2-context
>> 4085  roger     39  19  2636 1188  904 S    1  0.1    4:12.39 top
>> 26299 root      20   0  2656 1176  896 R    1  0.1    0:00.04 top
>>
>> (I've have to re-enable pvrusb2 mailing list to start sending mailing list emails.)
>>
>> --
>> Roger
>> http://rogerx.freeshell.org/
>> _______________________________________________
>> pvrusb2 mailing list
>> pvrusb2 at isely.net
>> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
>>
>_______________________________________________
>pvrusb2 mailing list
>pvrusb2 at isely.net
>http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
>

-- 
Roger
http://rogerx.freeshell.org/