I'm using an ISDN usb modem as part of the isdn presentation from British Telecom. This requires the hisax st5481 modules that make use of the linux-usb modules. I've been running successfully for about 10 month. Until I upgraded my hardware.
I've been in touch with a developer of hisax/st5481 and he thinks my problem is a generic usb one, so I'm trying this list. The changes: 1. New machine, 2.0G, 512MB memory. uname -a gives: Linux purser 2.4.22 #3 SMP Tue Dec 30 05:41:27 GMT 2003 i686 athlon i386 GNU/Linux 2. The machine now has a Silicon Integrated Systems usb hub but I can't get it working at 2.0 - none of the hub modules will recognise it. There is a cmos option to disable version 2, disabling this at least allows me to get somewhere. The relevant modules are: usb-storage 48824 0 printer 8672 0 hisax_st5481 22260 2 hisax 132608 0 [hisax_st5481] isdn 105216 2 [hisax] isdnhdlc 5372 0 [hisax_st5481] usb-ohci 21192 0 (unused) usbcore 82496 1 [usb-storage printer hisax_st5481 usb-ohci] I also use some usb-storage devices and a usb printer, hence the other modules. I'm not experiencing any problems with these. 4. I've upgraded to kernel 2.4.22, although I did this some weeks ago before the rest of the changes and didn't experience any problems. I'm still using this kernel even though I've now upgraded to redhat 9. The messages: I'm getting kernel messages such as: Jan 12 11:38:51 purser kernel: usb-ohci.c: bug in call from de81b45a; use async! Jan 12 11:38:51 purser kernel: st5481_usb.c: st5481_start_rcv: usb_submit_urb failed,status=-22 Jan 12 11:38:51 purser kernel: st5481_usb.c: st5481_start_rcv: usb_submit_urb failed,status=-22 Jan 12 11:59:30 purser kernel: st5481_b.c: usb_b_out_complete: urb status -75 Jan 12 11:59:30 purser kernel: st5481_usb.c: usb_in_complete: urb status -75 The effects: Everything seems fine apart from the large numbers of the messages, but about 5-6 times a day, there is a kernel panic and crash. Less often, maybe 2-3 times a week, the isdn functions seem to lock up, but stopping and restarting fixes this. I can't spot any pattern that would point to what causes the crashes. I would be extremely grateful for any help you could give me. I've searched for anything relevant, but although I could find reports of similar errors using BT ISDN, there were no fixes. Regards Nick ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
