On Sun, 4 Jul 2004, Raj Mathur wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > [Cross-posted]
Good to hear at least some aspect of the ma620 is working now... I keep the crosspost because it's related to both topics. > - - Speeds above 9600bps cause some problem in the serial driver. If I > DON'T echo 9600 > /proc/sys/net/irda/max_baud_rate before loading the > MA620 drivers, this is the error I get when trying anything more > complex than a straight discovery on the phone link: > > Jul 4 07:39:32 mail kernel: ma600_change_speed(): bad control byte read-back 42 != > 04 > Jul 4 07:39:32 mail kernel: irda_config_fsm - error: -1 > Jul 4 07:39:35 mail kernel: IrLAP, no activity on link! Well, looks like the driver assumed the speed change failed due to the incorrect serial readback. This test was copied from the old ma600 driver. ma600 is the only dongle driver currently trying to do this raw readback test. There are at least 3 possible reasons for it to fail: * some undisclosed bug somewhere in the raw read mode * this test might happened to work (kind of) with old ma600 driver due to echo readback, but not really reading back from the dongle * readback might behave differently for the ma620 usb version That's why there is a comment in the code and the corresponding lines are prepared to be disabled ;-) Simply try editing the file linux/drivers/net/irda/ma600-sir.c. In line 197 (2.6.7-vanilla) change the "#if 1" to read "#if 0" and rebuild your module. By chance this will help you out because the speed chance was likely working, just the verification failed. > - - Unloading the PL2303 module (modprobe -r pl2303) results in a kernel > oops: > > Unable to handle kernel NULL pointer dereference at virtual address 00000084 > printing eip: > e2965f2d > *pde = 00000000 > Oops: 0000 [#1] > PREEMPT > Modules linked in: ehci_hcd ohci_hcd pl2303 usbserial snd_pcm_oss snd_mixer_oss > snd_ens1371 snd_rawmidi snd_seq_device snd_pcm snd_page_alloc snd_timer > snd_ac97_codec snd gameport soundcore ipt_MARK ipt_TOS iptable_mangle parport_pc lp > parport iptable_filter ip_tables md5 ipv6 8139too mii crc32 quota_v1 loop vfat fat > usblp uhci_hcd usbmouse usbkbd usbcore > CPU: 0 > EIP: 0060:[<e2965f2d>] Not tainted > EFLAGS: 00010246 (2.6.7) > EIP is at usb_serial_disconnect+0x1d/0x90 [usbserial] > eax: 00000000 ebx: 00000010 ecx: 00000003 edx: 00000000 > esi: 00000000 edi: 00000000 ebp: 00000000 esp: d7871f20 > ds: 007b es: 007b ss: 0068 > Process modprobe (pid: 3811, threadinfo=d7870000 task=d8772250) > Stack: dff0e890 dff0e868 00000000 d7f4d3cc 00000000 e299fea0 e29662e2 00000000 > dff0e858 e299e0bb c03ab360 e299ff80 00000080 e299dfdb e299fea0 c012c8f3 > e299ff80 00000080 d7871f6c 00000000 33326c70 40003330 c01479af d86f8760 > Call Trace: > [<e29662e2>] usb_serial_deregister+0x92/0xa0 [usbserial] > [<e299dfdb>] pl2303_exit+0x1b/0x1d [pl2303] > [<c012c8f3>] sys_delete_module+0x163/0x1a0 > [<c01479af>] do_munmap+0x14f/0x190 > [<c01051eb>] syscall_call+0x7/0xb > > Code: 8b 73 74 75 4e c7 43 74 00 00 00 00 85 f6 74 0b 8d 46 38 89 What happens if you first unplug the ma620 before rmmod pl2303? Anyway, this looks like an issue with usbserial so Greg might be interested. Martin ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
