Re: 2.4.30: pwc pwc_isoc_handler() called with status -84
* Pete Zaitcev <[EMAIL PROTECTED]>: | > > pwc Too many ISOC errors, bailing out. | > > pwc pwc_isoc_handler() called with status -84 [CRC/Timeout (could be anything)]. | | There is no other way but to start splitting patches and diff-ing. | We can narrow this down a little by looking at what _might_ be involved. | Is this device driven by EHCI? yes, i think so. Asus P4C800-E mobo. Details in the tarball. | A snapshot of /proc/bus/usb/devices would be useful (BTW, Gabor, | please do it on both 2.4.28 and 2.4.30-rc). Right now I have .30-rc only: http://gzp.odpn.net/tmp/pwc/pwc.tgz I should compile a new 2.4.28, because I deleted... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.30: pwc pwc_isoc_handler() called with status -84
On Tue, 5 Apr 2005 10:55:52 -0300 Marcelo Tosatti <[EMAIL PROTECTED]> wrote: > CCing Pete. > > On Mon, Apr 04, 2005 at 08:59:57PM +0200, Gabor Z. Papp wrote: > > It was working fine with 2.4.29 and earlier kernels, often with > > 100-150 days uptime. > > > > As I upgraded to 2.4.30-rc kernels, started getting such error in my > > kernel log: > > > > pwc Too many ISOC errors, bailing out. > > pwc pwc_isoc_handler() called with status -84 [CRC/Timeout (could be > > anything)]. There is no other way but to start splitting patches and diff-ing. We can narrow this down a little by looking at what _might_ be involved. Is this device driven by EHCI? A snapshot of /proc/bus/usb/devices would be useful (BTW, Gabor, please do it on both 2.4.28 and 2.4.30-rc). Thanks, -- Pete - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.30: pwc pwc_isoc_handler() called with status -84
Hi Gabor, This seems to be a USB specific problem and my USB knowledge is null. CCing Pete. On Mon, Apr 04, 2005 at 08:59:57PM +0200, Gabor Z. Papp wrote: > I have a Philips 750 webcam camera, equipped with a > Sony CCD sensor + TDA878. > > It was working fine with 2.4.29 and earlier kernels, often with > 100-150 days uptime. > > As I upgraded to 2.4.30-rc kernels, started getting such error in my > kernel log: > > pwc Too many ISOC errors, bailing out. > pwc pwc_isoc_handler() called with status -84 [CRC/Timeout (could be > anything)]. > > [khubd] got 100% cputime, and kernel just printed and printed this > message to the log, generating huge files. :-) > > rc4 is still doing this. 1-2 hour online, the something get mad and > the pwc driver eat the cputime. 2.4.28 was 100% okay from this point > of view. > > http://gzp.odpn.net/tmp/pwc/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.30: pwc pwc_isoc_handler() called with status -84
I have a Philips 750 webcam camera, equipped with a Sony CCD sensor + TDA878. It was working fine with 2.4.29 and earlier kernels, often with 100-150 days uptime. As I upgraded to 2.4.30-rc kernels, started getting such error in my kernel log: pwc Too many ISOC errors, bailing out. pwc pwc_isoc_handler() called with status -84 [CRC/Timeout (could be anything)]. [khubd] got 100% cputime, and kernel just printed and printed this message to the log, generating huge files. :-) rc4 is still doing this. 1-2 hour online, the something get mad and the pwc driver eat the cputime. 2.4.28 was 100% okay from this point of view. http://gzp.odpn.net/tmp/pwc/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
