but tests 14 through 16 fail:
/proc/bus/usb/003/067 test 14 --> 22 (error 22) /proc/bus/usb/003/067 test 15 --> 33 (error 33) /proc/bus/usb/003/067 test 16 --> 33 (error 33)
Tests 15 and 16 (iso-out and iso-in, respectively) run successfully when invocating testusb from the test.sh script (the above output was from a ./testusb -a run).
What's more concerning is that after running the iso-out test my kernel log spews out
bad: scheduling while atomic! [<c027d3fc>] schedule+0x47c/0x490 [<c0106aec>] common_interrupt+0x18/0x20 [<c01040c3>] cpu_idle+0x33/0x40 [<c033079a>] start_kernel+0x19a/0x1e0 [<c0330380>] unknown_bootoption+0x0/0x160
forcing me to reboot the machine. Since my USB speakers (also using iso-out) work just fine, I'm thinking the usbtest driver may be missing an unlock somewhere. Anyone recognize this or knows what the problem is?
(Greg KH's 2.6.10 patch (at http://marc.theaimsgroup.com/?l=linux-usb-devel&m=110516407500085&w=2) mentions the "scheduling while atomic" but in a resume context.)
-- Orjan Friberg Axis Communications
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
