> On 15.01.2013 23:05, "Bernd Krumböck" wrote: > >>> [ 960.047130] usb_8dev 2-1.4:1.0 can2: Unknown status/error message >>> (0) >>> [ 976.544343] usb_8dev 2-1.4:1.0 can2: Unknown status/error message >>> (0) >>> >>> Did you check these kind of 'unfriendly user' tests? >> >> Not really. At least I don't know what the driver should do. Let me know >> if you have some suggestions. >> > > > Pulling/reconnecting CAN and/or USB under heavy CAN load ;-) Sorry, I meant: How the driver should behave? A test with loopback (canbusload 40%): Jan 16 07:58:36 debian kernel: [40503.434639] CAN device driver interface Jan 16 07:58:38 debian kernel: [40504.900138] usb_8dev 5-2:1.0: can0: firmware: 1.4, hardware: 1.0 Jan 16 07:58:38 debian kernel: [40504.900161] usbcore: registered new interface driver usb_8dev (Starting my script and disconnect usb adapter) Jan 16 08:09:29 debian kernel: [41155.696483] usb_8dev 5-2:1.0: can0: Rx URB aborted (-84) Jan 16 08:09:29 debian kernel: [41155.696490] usb_8dev 5-2:1.0: can0: Tx URB aborted (-71) Jan 16 08:09:29 debian kernel: [41155.697479] usb_8dev 5-2:1.0: can0: Rx URB aborted (-84) Jan 16 08:09:29 debian kernel: [41155.697484] usb_8dev 5-2:1.0: can0: Tx URB aborted (-71) Jan 16 08:09:29 debian kernel: [41155.698479] usb_8dev 5-2:1.0: can0: Rx URB aborted (-84) No surprises: * We received (84) "Illegal byte sequence" * Sending was aborted by (71) "Protocol error" Jan 16 08:09:29 debian kernel: [41155.752054] usb 5-2: USB disconnect, device number 2 Jan 16 08:09:29 debian kernel: [41155.752484] usb_8dev 5-2:1.0: can0: Tx URB aborted (-71) Jan 16 08:09:29 debian kernel: [41155.752489] usb_8dev 5-2:1.0: can0: Tx URB aborted (-108) Jan 16 08:09:29 debian kernel: [41155.752492] usb_8dev 5-2:1.0: can0: Tx URB aborted (-108) Jan 16 08:09:29 debian kernel: [41155.752495] usb_8dev 5-2:1.0: can0: Tx URB aborted (-108) Jan 16 08:09:29 debian kernel: [41155.752499] usb_8dev 5-2:1.0: can0: Tx URB aborted (-108) Jan 16 08:09:29 debian kernel: [41155.752502] usb_8dev 5-2:1.0: can0: Tx URB aborted (-108) Jan 16 08:09:29 debian kernel: [41155.752505] usb_8dev 5-2:1.0: can0: Tx URB aborted (-108) Jan 16 08:09:29 debian kernel: [41155.752508] usb_8dev 5-2:1.0: can0: Tx URB aborted (-108) Jan 16 08:09:29 debian kernel: [41155.752511] usb_8dev 5-2:1.0: can0: Tx URB aborted (-108) Jan 16 08:09:29 debian kernel: [41155.752514] usb_8dev 5-2:1.0: can0: Tx URB aborted (-108) Jan 16 08:09:29 debian kernel: [41155.752522] usb_8dev 5-2:1.0: can0: device disconnected Looks also ok: * Sending was aborted by (108) "transport endpoint shutdown" But after 1 minute my computer freezed!! :-( Did you see this problem during your tests? System: Kernel 3.2.0-4-amd64 SMP on Debian 3.2.35-2 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02) >>> E.g. pulling the USB under receive load brings this output: >>> >>> [ 1343.786427] usb_8dev 2-1.4:1.0 can2: Rx URB aborted (-32) >>> [ 1343.786640] usb_8dev 2-1.4:1.0 can2: Rx URB aborted (-32) Receiving aborted because of "Broken pipe"... >>> >>> (..) another 344 of these URB aborted messages >> >> a bit much... >> >> Maybe we should suppress this messages? >> > > > I did not had the time for tests yesterday. > But i will attach my full-load CAN generator today. > > Regarding the USB abort messages, i'll try the same with my other USB > adapters > and how they behave under these conditions. Okidoki. ;-) > I remember some tests for the PEAK USB mainlining ... let's see. > > Regards, > Oliver > > regards, Bernd -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
