Hi > Hello all > > > Further to my well publicised events with a BT isdn USB NTE, i've > managed to get it going, but every now and again I get one of these > which then causes a kernel page fault (not sure whether related or not). > > Nov 25 07:00:22 home kernel: usb-ohci.c: bug in call from c02029de; use > async! > Nov 25 07:00:22 home kernel: usb-ohci.c: bug in call from c02029de; use > async! > Nov 25 07:00:22 home kernel: st5481_usb.c: usb_in_complete: framing > error > > question is, what does it mean by, "use async" ? > > this is what i get on bootup: > root@home:/etc/rc.d# dmesg |grep usb > usb-ohci.c: USB OHCI at membase 0xc38d5000, IRQ 12 > usb-ohci.c: usb-00:13.0, OPTi Inc. 82C861 > usb.c: new USB bus registered, assigned bus number 1 > usb.c: kmalloc IF c11cae60, numif 1 > usb.c: new device strings: Mfr=0, Product=2, SerialNumber=1 > usb.c: USB device number 1 default language ID 0x0 > usb.c: hub driver claimed interface c11cae60 > usb.c: kusbd: /sbin/hotplug add 1 > usb.c: kusbd policy returned 0xfffffffe > usb.c: kmalloc IF c11caf40, numif 1 > usb.c: skipping descriptor 0x3 > usb.c: skipping descriptor 0x3 > usb.c: skipped 2 class/vendor specific endpoint descriptors > usb.c: new device strings: Mfr=0, Product=1, SerialNumber=0 > usb.c: USB device number 2 default language ID 0x800 > usb.c: unhandled interfaces on device > usb.c: USB device 2 (vend/prod 0x483/0x481d) is not claimed by any active driver. > usb.c: kusbd: /sbin/hotplug add 2 > usb.c: kusbd policy returned 0xfffffffe > > and this is what I get when I load in the device module: > > usb.c: registered new driver st5481_usb > HiSax: Card 1 Protocol EDSS1 Id=st5481_usb0 (0) > usb.c: st5481_usb driver claimed interface c11caf40 > st5481_usb.c: usb_in_complete: framing error > > any ideas appreciated > regards > charles > >
signature.asc
Description: This is a digitally signed message part
