2.6.34 is the version where I started having problems. I had to update the in kernel pvrusb2 driver to the isely.net version to get the problem to go away.
The problem is that there is the driver that Mike keeps up to date, the v4l stuff, then the kernel itself. It appears that there is quite a time lag between the problem being fixed in Mike's tree and it migrating up to the real kernel at kernel.org that everyone pulls from. I am not sure all of the fixes ever made it to even the most current kernel 2.6.36.... Download the current version, make modules, make modules_install, reboot, then modprobe and rmmod several times in a row. It should fix the issues. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, October 14, 2010 11:56 AM To: Communications nexus for pvrusb2 driver Subject: Re: [pvrusb2] CPU Run pvrusb2-context Sorry, forgotten to mention kernel version. $ uname -a Linux localhost2.local 2.6.34-gentoo-r6 #2 SMP PREEMPT Tue Oct 12 18:01:46 AKDT 2010 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux ... using in kernel pvrusb2 modules. As far as the main standard kernel version, Gentoo's Changelog does not denote the kernel patch version it is at on this particular 2.6.34 version -- or I'm completely missing finding it within the Changelog. Is there someplace else I'm missing where the Linux kernel standard (patch) version is located, or is this because Gentoo is entirely masking the version with their kernel version naming scheme? From what I see within the Changelog for gentoo-sources kernel, it's entries are as 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, <[email protected]> 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 >> [email protected] >> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 >> >_______________________________________________ >pvrusb2 mailing list >[email protected] >http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 > -- Roger http://rogerx.freeshell.org/ _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
