Hi again :)
Now we are trying to get some usb device to do anything useful.
Of course I expect to trigger bugs, which are left in the code :)
This is, when trying to start wlan:
prism2usb_init: prism2_usb.o: 0.2.1-pre23 Loaded
prism2usb_init: dev_info is: prism2_usb
usbcore: registered new driver prism2_usb
message=lnxreq_ifstate
ifstate=enable
resultcode=no_value
buf_curlen(old) = 0
buf_curlen(new) = 16, xfer_size 8, xfer_size_real 8
S-
num 92e1, rem f96
num 92e1, rem dcd
R-
buf_curlen(old) = 0
buf_curlen(new) = 8, xfer_size 0, xfer_size_real 0
S-
num 92ec, rem 1dc5
num 92ec, rem 1cab
R-
buf_curlen(old) = 0
buf_curlen(new) = 16, xfer_size 8, xfer_size_real 8
S-
num 92f8, rem 1027
num 92f8, rem e5d
R-
buf_curlen(old) = 0
buf_curlen(new) = 8, xfer_size 0, xfer_size_real 0
S-
num 9303, rem 19df
num 9303, rem 18c4
R-
buf_curlen(old) = 0
buf_curlen(new) = 3008, xfer_size 3000, xfer_size_real 3000
buf_curlen(old) = 3008
buf_curlen(new) = 3080, xfer_size 64, xfer_size_real 64
S-
num 9317, rem 19ee
num 9318, rem 15e5
Badness in isp116x_send_queue at drivers/usb/host/ohci-isp116x-emu.c:417
hfa384x_docmd: ctlx failure=REQ_TIMEOUT
hfa384x_drvr_start: cmd_initialize() failed, result=-5
prism2sta_ifstate: hfa384x_drvr_start() failed,result=-5
message=lnxreq_ifstate
ifstate=enable
resultcode=implementation_failure
If anybody sees something obviously weird, please tell me.
Sometime I often trigger this:
Badness in isp116x_send_queue at drivers/usb/host/ohci-isp116x-emu.c:417
with Line 417 being
WARN_ON((!(__isp1362_read_reg16(dev, HCuPINT) & HCuPINT_ISP116x_AIIEOT)));
How do I avoid the occurence of this? I remember havin read here about AIIEOT
Interrupt but excuse me, I don't find it anymore.
When I plug a pcm2702 in and try to play a sound file (alsamixer works fine :))
I get an endless loop of
process_ed_list: Processing ED @ 08c3b040 #9795
process_ed_list: Processing TD ffc03000
process_ed_list: Processing ISO TD 08d53000
Badness in retire_td at drivers/usb/host/ohci-isp116x-emu.c:781
with line 781 being
if (TD_CC_GET(td_flags) != TD_BUSY) {
ohci_dump_td(ohci, __FUNCTION__, td);
WARN_ON(1);
return;
}
Why is the warning/error generated and how to avoid this?
Kind regards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
