2001-11-05 18:36:51

by Stephan Gutschke

[permalink] [raw]
Subject: Oops when syncing Sony Clie 760 with USB cradle

Hi there,
if anything else is needed, let me know.

Stephan

P.S.:
Tainted, because vfat taints the kernel:
Using /lib/modules/2.4.14-pre8/kernel/fs/vfat/vfat.o
Warning: loading /lib/modules/2.4.14-pre8/kernel/fs/vfat/vfat.o will taint the kernel: no license


ksymoops 2.4.3 on i686 2.4.14-pre8. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.14-pre8/ (default)
-m /boot/System.map-2.4.14-pre8 (default)

Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.

Error (regular_file): read_system_map stat /boot/System.map-2.4.14-pre8 failed
ksymoops: No such file or directory
Nov 5 19:58:36 yvette kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000014
Nov 5 19:58:36 yvette kernel: c01f2193
Nov 5 19:58:36 yvette kernel: *pde = 00000000
Nov 5 19:58:36 yvette kernel: Oops: 0002
Nov 5 19:58:36 yvette kernel: CPU: 0
Nov 5 19:58:36 yvette kernel: EIP: 0010:[visor_open+163/276] Tainted: P
Nov 5 19:58:36 yvette kernel: EFLAGS: 00210202
Nov 5 19:58:36 yvette kernel: eax: c1848800 ebx: df40ec94 ecx: df40ecf0 edx: 00000000
Nov 5 19:58:36 yvette kernel: esi: df40ec00 edi: 00000000 ebp: df40ecf0 esp: dbbd9eb0
Nov 5 19:58:36 yvette kernel: ds: 0018 es: 0018 ss: 0018
Nov 5 19:58:36 yvette kernel: Process jpilot (pid: 430, stackpage=dbbd9000)
Nov 5 19:58:36 yvette kernel: Stack: dc07b000 dbb25ae0 dedfd460 c180e2e0 c01f0864 df40ec94 dbb25ae0 00000000
Nov 5 19:58:36 yvette kernel: 00000000 c018b98b dc07b000 dbb25ae0 00000000 dbb25ae0 dedfd460 c180e2e0
Nov 5 19:58:36 yvette kernel: 4c99880a 08020007 dc07b000 c18094a0 dbbd9f38 dbbd9f38 dee019c0 00000000
Nov 5 19:58:36 yvette kernel: Call Trace: [serial_open+152/168] [tty_open+511/872] [link_path_walk+1553/1752] [permission+43/48] [chrdev_open+62/76]
Nov 5 19:58:36 yvette kernel: Code: 89 42 14 8b 4e 04 0f b6 43 24 c1 e0 0f 8b 11 c1 e2 08 09 c2
Using defaults from ksymoops -t elf32-i386 -a i386

Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: 89 42 14 mov %eax,0x14(%edx)
Code; 00000002 Before first symbol
3: 8b 4e 04 mov 0x4(%esi),%ecx
Code; 00000006 Before first symbol
6: 0f b6 43 24 movzbl 0x24(%ebx),%eax
Code; 0000000a Before first symbol
a: c1 e0 0f shl $0xf,%eax
Code; 0000000c Before first symbol
d: 8b 11 mov (%ecx),%edx
Code; 0000000e Before first symbol
f: c1 e2 08 shl $0x8,%edx
Code; 00000012 Before first symbol
12: 09 c2 or %eax,%edx


1 warning and 1 error issued. Results may not be reliable.


2001-11-05 20:10:50

by Greg KH

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

On Mon, Nov 05, 2001 at 10:36:16AM +0000, Stephan Gutschke wrote:
> Hi there,
> if anything else is needed, let me know.

Could you load the driver with "debug=1" and then try this again? If
the oops happens, can you send me the kernel debug log?

And does this happen at the end of the sync, or the beginning?
Every time? Occasionally?

thanks,

greg k-h

2001-11-06 13:31:44

by Stephan Gutschke

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

Hi Greg,

the output is below, I also added a couple of debug-lines in the
visor_open()
function. Seems to me like port->read_urb is null and maybe that
shouldn't be?
Anyways, if I got that all wrong, don't hit me ;-).
I would have like to look a little more around, but I have not really
any idea of
kernel programming so I have no clue who calls visor_open()
Let me know if I can do anything else.
Oh, and by the way, the crash happens, when I press "Sync" in jpilot,
before that
everything is fine.

see you later
Stephan

P.S. sorry i took so long, but i was a little busy here ;-)


> Nov 6 15:15:59 yvette kernel: hub.c: port 1 connection change
> Nov 6 15:15:59 yvette kernel: hub.c: port 1, portstatus 101, change
> 1, 12 Mb/s
> Nov 6 15:15:59 yvette kernel: hub.c: port 1, portstatus 103, change
> 0, 12 Mb/s
> Nov 6 15:15:59 yvette kernel: hub.c: USB new device connect on
> bus1/1, assigned device number 2
> Nov 6 15:15:59 yvette kernel: usb.c: kmalloc IF dbfdcdc0, numif 1
> Nov 6 15:15:59 yvette kernel: usb.c: new device strings: Mfr=1,
> Product=2, SerialNumber=0
> Nov 6 15:15:59 yvette kernel: usb.c: USB device number 2 default
> language ID 0x409
> Nov 6 15:15:59 yvette kernel: Manufacturer: Sony Corp.
> Nov 6 15:15:59 yvette kernel: Product: Palm Handheld
> Nov 6 15:15:59 yvette kernel: usbserial.c: Sony Clie 4.0 converter
> detected
> Nov 6 15:15:59 yvette kernel: visor.c: visor_startup
> Nov 6 15:15:59 yvette kernel: visor.c: visor_startup - Set config to 1
> Nov 6 15:15:59 yvette kernel: visor.c: Sony Clie 4.0: Number of ports: 2
> Nov 6 15:15:59 yvette kernel: visor.c: Sony Clie 4.0: port 1, is for
> Generic use and is bound to ttyUSB0
> Nov 6 15:15:59 yvette kernel: visor.c: Sony Clie 4.0: port 2, is for
> HotSync use and is bound to ttyUSB1
> Nov 6 15:15:59 yvette kernel: usb-uhci.c: interrupt, status 2, frame# 984
> Nov 6 15:16:02 yvette kernel: usb_control/bulk_msg: timeout
> Nov 6 15:16:02 yvette kernel: visor.c: visor_startup - error getting
> first unknown palm command
> Nov 6 15:16:05 yvette kernel: usb_control/bulk_msg: timeout
> Nov 6 15:16:05 yvette kernel: visor.c: visor_startup - error getting
> second unknown palm command
> Nov 6 15:16:05 yvette kernel: usbserial.c: Sony Clie 4.0 converter
> now attached to ttyUSB0 (or usb/tts/0 for devfs)
> Nov 6 15:16:05 yvette kernel: usbserial.c: Sony Clie 4.0 converter
> now attached to ttyUSB1 (or usb/tts/1 for devfs)
> Nov 6 15:16:05 yvette kernel: usb.c: serial driver claimed interface
> dbfdcdc0
> Nov 6 15:16:05 yvette kernel: usb.c: kusbd: /sbin/hotplug add 2
> Nov 6 15:16:05 yvette kernel: usb.c: kusbd policy returned 0xfffffffe
> Nov 6 15:16:09 yvette kernel: visor.c: visor_open - port 1
> Nov 6 15:16:09 yvette kernel: visor.c: visor_openport->read_urb
> 00000000 <----- should that be that way?
> Nov 6 15:16:09 yvette kernel: visor.c: visor_openport->serial->dev
> dda78e00
> Nov 6 15:16:09 yvette kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000024
> Nov 6 15:16:09 yvette kernel: printing eip:
> Nov 6 15:16:09 yvette kernel: e08a514d
> Nov 6 15:16:09 yvette kernel: *pde = 00000000
> Nov 6 15:16:09 yvette kernel: Oops: 0000
> Nov 6 15:16:09 yvette kernel: CPU: 0
> Nov 6 15:16:09 yvette kernel: EIP: 0010:[<e08a514d>] Tainted: PF
> Nov 6 15:16:09 yvette kernel: EFLAGS: 00210202
> Nov 6 15:16:09 yvette kernel: eax: 00000000 ebx: db4c3094 ecx:
> df61a000 edx: 00000001
> Nov 6 15:16:09 yvette kernel: esi: db4c3000 edi: 00000000 ebp:
> db4c30f0 esp: db4a3eb0
> Nov 6 15:16:09 yvette kernel: ds: 0018 es: 0018 ss: 0018
> Nov 6 15:16:09 yvette kernel: Process jpilot (pid: 533,
> stackpage=db4a3000)
> Nov 6 15:16:09 yvette kernel: Stack: dce3f000 db7279c0 dedb44a0
> c180e2e0 e08a0284 db4c3094 db7279c0 00000000
> Nov 6 15:16:09 yvette kernel: 00000000 c018b98b dce3f000
> db7279c0 00000000 db7279c0 dedb44a0 c180e2e0
> Nov 6 15:16:09 yvette kernel: 4c99880a 08020007 dce3f000
> c18094a0 db4a3f38 db4a3f38 dedb76e0 00000000
> Nov 6 15:16:09 yvette kernel: Call Trace: [<e08a0284>]
> [tty_open+511/872] [link_path_walk+1553/1752] [permission+43/48]
> [chrdev_open+62/76]
> Nov 6 15:16:09 yvette kernel: [dentry_open+225/392]
> [filp_open+82/92] [sys_open+54/148] [system_call+51/56]
> Nov 6 15:16:09 yvette kernel:
> Nov 6 15:16:09 yvette kernel: Code: 8b 40 24 50 68 60 62 8a e0 e8 c5
> 09 87 df 83 c4 08 83 3d 80
> Nov 6 15:16:42 yvette kernel: <7>hub.c: port 1 connection change
> Nov 6 15:16:42 yvette kernel: hub.c: port 1, portstatus 100, change
> 3, 12 Mb/s
> Nov 6 15:16:42 yvette kernel: usb.c: USB disconnect on device 2
> Nov 6 15:16:42 yvette kernel: visor.c: visor_shutdown
> Nov 6 15:16:42 yvette kernel: visor.c: visor_close - port 1







Greg KH wrote:

>On Mon, Nov 05, 2001 at 10:36:16AM +0000, Stephan Gutschke wrote:
>
>>Hi there,
>>if anything else is needed, let me know.
>>
>
>Could you load the driver with "debug=1" and then try this again? If
>the oops happens, can you send me the kernel debug log?
>
>And does this happen at the end of the sync, or the beginning?
>Every time? Occasionally?
>
>thanks,
>
>greg k-h
>


--
Stephan Gutschke



2001-11-06 16:56:11

by Greg KH

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

On Tue, Nov 06, 2001 at 03:27:46PM +0100, Stephan Gutschke wrote:
> Hi Greg,
>
> the output is below, I also added a couple of debug-lines in the
> visor_open() function. Seems to me like port->read_urb is null and
> maybe that shouldn't be?

Hm, yes, port->read_urb should _NOT_ be NULL. Thanks for adding this
check.

Can you send the output of /proc/bus/usb/devices right after you press
the sync button on the Clie? Don't try syncing :)

thanks,

greg k-h

2001-11-06 22:27:38

by Stephan Gutschke

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

there you go, the output from /proc/bus/usb/devices
By the way I have an Clie N710C which is upgraded
to an 760 with OS 4.1S, shouldnt make a difference,
but I just wanted to let you know.


T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=1060
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS=16 #Cfgs= 1
P: Vendor=054c ProdID=0066 Rev= 1.00
S: Manufacturer=Sony Corp.
S: Product=Palm Handheld
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=serial
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms


Greg KH wrote:

>On Tue, Nov 06, 2001 at 03:27:46PM +0100, Stephan Gutschke wrote:
>
>>Hi Greg,
>>
>>the output is below, I also added a couple of debug-lines in the
>>visor_open() function. Seems to me like port->read_urb is null and
>>maybe that shouldn't be?
>>
>
>Hm, yes, port->read_urb should _NOT_ be NULL. Thanks for adding this
>check.
>
>Can you send the output of /proc/bus/usb/devices right after you press
>the sync button on the Clie? Don't try syncing :)
>
>thanks,
>
>greg k-h
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to [email protected]
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>


--
Stephan Gutschke



2001-11-06 23:00:18

by Greg KH

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

On Wed, Nov 07, 2001 at 12:23:27AM +0100, Stephan Gutschke wrote:
> there you go, the output from /proc/bus/usb/devices
> By the way I have an Clie N710C which is upgraded
> to an 760 with OS 4.1S, shouldnt make a difference,
> but I just wanted to let you know.

Ah, that might make the difference. It looks like the number of
endpoints is different on this device, than any other 4.x Clie devices
(they should have 4 bulk endpoints.) The older devices have 2 endpoints
(endpoints are usually done in hardware)

This Clie is reporting to the driver that it _does_ have 2 "ports" (a
port is 2 endpoint pairs in this scheme), but in reality, it doesn't.
The lying device is then causing the driver to oops when it tries to
write to a port that isn't even there.

I'm going to have to rework the driver to fix this problem, give me a
day or so to come up with a solution. Are you willing to try a patch
when I have something?

Thanks for the good error reporting, it really helped.

greg k-h

2001-11-06 23:15:59

by Stephan Gutschke

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

sure i try a patch no problem. Especially because my Clie just did a
hard-reset :-( -- no clue why -- But I am glad when the syncing works
again so i can get my data back on ;-)

See you later
Stephan

Greg KH wrote:

> On Wed, Nov 07, 2001 at 12:23:27AM +0100, Stephan Gutschke wrote:
>
>>there you go, the output from /proc/bus/usb/devices
>>By the way I have an Clie N710C which is upgraded
>>to an 760 with OS 4.1S, shouldnt make a difference,
>>but I just wanted to let you know.
>>
>
> Ah, that might make the difference. It looks like the number of
> endpoints is different on this device, than any other 4.x Clie devices
> (they should have 4 bulk endpoints.) The older devices have 2 endpoints
> (endpoints are usually done in hardware)
>
> This Clie is reporting to the driver that it _does_ have 2 "ports" (a
> port is 2 endpoint pairs in this scheme), but in reality, it doesn't.
> The lying device is then causing the driver to oops when it tries to
> write to a port that isn't even there.
>
> I'm going to have to rework the driver to fix this problem, give me a
> day or so to come up with a solution. Are you willing to try a patch
> when I have something?
>
> Thanks for the good error reporting, it really helped.
>
> greg k-h
>



--
Stephan Gutschke

2001-11-07 17:44:03

by Greg KH

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

On Wed, Nov 07, 2001 at 01:11:50AM +0100, Stephan Gutschke wrote:
> sure i try a patch no problem. Especially because my Clie just did a
> hard-reset :-( -- no clue why -- But I am glad when the syncing works
> again so i can get my data back on ;-)

Hm, in thinking about it, you should be able to sync right now by
talking to /dev/ttyUSB0 instead of /dev/ttyUSB1.

Let me know if this works or not.

thanks,

greg k-h

2001-11-07 22:08:17

by Stephan Gutschke

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

didn't work :-(

This is the output of /var/log/syslog if I connect to ttyUSB0
I am not sure yet though that the problem is in your module.
I know the jpilot worked, before, but I will still try later
to connect to the clie with coldsync as well.
Lets see if that gives anything different.
Let me know what else I can do to help.


Stephan


> Nov 7 21:13:28 yvette kernel: hub.c: port 1 connection change
> Nov 7 21:13:28 yvette kernel: hub.c: port 1, portstatus 101, change 1, 12 Mb/s
> Nov 7 21:13:28 yvette kernel: hub.c: port 1, portstatus 103, change 0, 12 Mb/s
> Nov 7 21:13:28 yvette kernel: hub.c: USB new device connect on bus1/1, assigned device number 6
> Nov 7 21:13:28 yvette kernel: usb.c: kmalloc IF ddcbcf00, numif 1
> Nov 7 21:13:28 yvette kernel: usb.c: new device strings: Mfr=1, Product=2, SerialNumber=0
> Nov 7 21:13:28 yvette kernel: usb.c: USB device number 6 default language ID 0x409
> Nov 7 21:13:28 yvette kernel: Manufacturer: Sony Corp.
> Nov 7 21:13:28 yvette kernel: Product: Palm Handheld
> Nov 7 21:13:28 yvette kernel: usbserial.c: Sony Clie 4.0 converter detected
> Nov 7 21:13:28 yvette kernel: visor.c: visor_startup
> Nov 7 21:13:28 yvette kernel: visor.c: visor_startup - Set config to 1
> Nov 7 21:13:28 yvette kernel: visor.c: Sony Clie 4.0: Number of ports: 2
> Nov 7 21:13:28 yvette kernel: visor.c: Sony Clie 4.0: port 1, is for Generic use and is bound to ttyUSB0
> Nov 7 21:13:28 yvette kernel: visor.c: Sony Clie 4.0: port 2, is for HotSync use and is bound to ttyUSB1
> Nov 7 21:13:28 yvette kernel: usb-uhci.c: interrupt, status 2, frame# 930
> Nov 7 21:13:31 yvette kernel: usb_control/bulk_msg: timeout
> Nov 7 21:13:31 yvette kernel: visor.c: visor_startup - error getting first unknown palm command
> Nov 7 21:13:34 yvette kernel: usb_control/bulk_msg: timeout
> Nov 7 21:13:34 yvette kernel: visor.c: visor_startup - error getting second unknown palm command
> Nov 7 21:13:34 yvette kernel: usbserial.c: Sony Clie 4.0 converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
> Nov 7 21:13:34 yvette kernel: usbserial.c: Sony Clie 4.0 converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
> Nov 7 21:13:34 yvette kernel: usb.c: serial driver claimed interface ddcbcf00
> Nov 7 21:13:34 yvette kernel: usb.c: kusbd: /sbin/hotplug add 6
> Nov 7 21:13:34 yvette kernel: usb.c: kusbd policy returned 0xfffffffe
> Nov 7 21:13:38 yvette kernel: visor.c: visor_open - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_openport->read_urb c65b0cc0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_openport->serial->dev de451a00
> Nov 7 21:13:38 yvette kernel: visor.c: visor_openport->read_urb->transfer_buffer c1b50960
> Nov 7 21:13:38 yvette kernel: visor.c: visor_openport->read_urb->transfer_buffer_length 64
> Nov 7 21:13:38 yvette kernel: visor.c: visor_open just after reading and submitting urb 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5401
> Nov 7 21:13:38 yvette kernel: visor.c: visor_read_bulk_callback - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_read_bulk_callback - length = 6, data = 01 ff 00 00 00 16
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 41
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write_room - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write_room - returns 16896
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = ff
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 08
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write_bulk_callback - port 0
> Nov 7 21:13:38 yvette last message repeated 10 times
> Nov 7 21:13:38 yvette kernel: visor.c: visor_read_bulk_callback - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_read_bulk_callback - length = 22, data = 90 01 00 00 00 00 00 00 00 20 00 00 00 08 00 00 01 00 00 00 00 00
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write_room - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write_room - returns 18432
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 90
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 41
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write_room - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write_room - returns 5376
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 20
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 5e
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - length = 1, data = 40
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write - no more free urbs
> Nov 7 21:13:38 yvette kernel: visor.c: visor_write_bulk_callback - port 0
> Nov 7 21:13:38 yvette last message repeated 23 times
> Nov 7 21:13:38 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5401
> Nov 7 21:13:38 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5402
> Nov 7 21:13:38 yvette kernel: visor.c: visor_set_termios - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_set_termios - data bits = 8
> Nov 7 21:13:38 yvette kernel: visor.c: visor_set_termios - parity = none
> Nov 7 21:13:38 yvette kernel: visor.c: visor_set_termios - stop bits = 1
> Nov 7 21:13:38 yvette kernel: visor.c: visor_set_termios - RTS/CTS is disabled
> Nov 7 21:13:38 yvette kernel: visor.c: visor_set_termios - XON/XOFF is disabled
> Nov 7 21:13:38 yvette kernel: visor.c: visor_set_termios - baud rate = 9600
> Nov 7 21:13:38 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5401
> Nov 7 21:13:38 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5401
> Nov 7 21:13:38 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5403
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_set_termios - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_set_termios - nothing to change...
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - port 0
> Nov 7 21:13:38 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
> Nov 7 21:14:00 yvette kernel: usb-uhci.c: interrupt, status 3, frame# 495
> Nov 7 21:14:00 yvette kernel: visor.c: visor_read_bulk_callback - port 0
> Nov 7 21:14:00 yvette kernel: visor.c: visor_read_bulk_callback - nonzero read bulk status received: -84
> Nov 7 21:14:00 yvette kernel: hub.c: port 1 connection change
> Nov 7 21:14:00 yvette kernel: hub.c: port 1, portstatus 100, change 3, 12 Mb/s
> Nov 7 21:14:00 yvette kernel: usb.c: USB disconnect on device 6
> Nov 7 21:14:00 yvette kernel: visor.c: visor_shutdown
> Nov 7 21:14:00 yvette kernel: visor.c: visor_close - port 0
> Nov 7 21:14:00 yvette kernel: usbserial.c: Sony Clie 4.0 converter now disconnected from ttyUSB0
> Nov 7 21:14:00 yvette kernel: usbserial.c: Sony Clie 4.0 converter now disconnected from ttyUSB1
> Nov 7 21:14:00 yvette kernel: usb.c: kusbd: /sbin/hotplug remove 6
> Nov 7 21:14:00 yvette kernel: usb.c: kusbd policy returned 0xfffffffe
> Nov 7 21:14:00 yvette kernel: hub.c: port 1 enable change, status 100



Greg KH wrote:

> On Tue, Nov 06, 2001 at 03:27:46PM +0100, Stephan Gutschke wrote:
>
>>Hi Greg,
>>
>>the output is below, I also added a couple of debug-lines in the
>>visor_open() function. Seems to me like port->read_urb is null and
>>maybe that shouldn't be?
>>
>
> Hm, yes, port->read_urb should _NOT_ be NULL. Thanks for adding this
> check.
>
> Can you send the output of /proc/bus/usb/devices right after you press
> the sync button on the Clie? Don't try syncing :)
>
> thanks,
>
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>



--
Stephan Gutschke

2001-11-07 22:18:58

by Greg KH

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

On Thu, Nov 08, 2001 at 12:03:44AM +0100, Stephan Gutschke wrote:
> didn't work :-(
>
> This is the output of /var/log/syslog if I connect to ttyUSB0
> I am not sure yet though that the problem is in your module.
> I know the jpilot worked, before, but I will still try later
> to connect to the clie with coldsync as well.
> Lets see if that gives anything different.
> Let me know what else I can do to help.

Yes, you will have to use coldsync to talk to this device right now, as
pilot-link doesn't have support for the 4.x Palm OS USB protocol yet
(jpilot uses pilot-link.)

Let me know if coldsync fails (remember you have to tell coldsync that
you are a m50x, and that you want the "simple" protocol, check the docs
for the proper config file setting.)

thanks,

greg k-h

2001-11-08 03:53:58

by Pete Toscano

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

Just in case it matters any, here's the Clie (760C) part of my
/proc/bus/usb/devices:

T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS=16 #Cfgs= 1
P: Vendor=054c ProdID=0066 Rev= 1.00
S: Manufacturer=Sony Corp.
S: Product=Palm Handheld
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=serial
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms

I'll also be a test monkey for the patch.

pete

On Tue, 06 Nov 2001, Greg KH wrote:

> On Wed, Nov 07, 2001 at 12:23:27AM +0100, Stephan Gutschke wrote:
> > there you go, the output from /proc/bus/usb/devices
> > By the way I have an Clie N710C which is upgraded
> > to an 760 with OS 4.1S, shouldnt make a difference,
> > but I just wanted to let you know.
>
> Ah, that might make the difference. It looks like the number of
> endpoints is different on this device, than any other 4.x Clie devices
> (they should have 4 bulk endpoints.) The older devices have 2 endpoints
> (endpoints are usually done in hardware)
>
> This Clie is reporting to the driver that it _does_ have 2 "ports" (a
> port is 2 endpoint pairs in this scheme), but in reality, it doesn't.
> The lying device is then causing the driver to oops when it tries to
> write to a port that isn't even there.
>
> I'm going to have to rework the driver to fix this problem, give me a
> day or so to come up with a solution. Are you willing to try a patch
> when I have something?
>
> Thanks for the good error reporting, it really helped.
>
> greg k-h

2001-11-08 05:10:18

by Greg KH

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

On Wed, Nov 07, 2001 at 10:53:28PM -0500, Pete Toscano wrote:
> Just in case it matters any, here's the Clie (760C) part of my
> /proc/bus/usb/devices:

Can you try syncing on /dev/ttyUSB0 with coldsync, telling it you have a
m50x and let me know if it works or not?

thanks,

greg k-h

2001-11-08 18:16:35

by Stephan Gutschke

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

hi greg,

I am using coldsync version 2.2.3, which seems to be the
newest snapshot. I read the doc and it says in the changelog
that they removed the "usb_m50x" flag. Seems that using protocol
"simple" should now do the trick.

I do:

coldsync -mb /tmp/ -t serial -p /dev/ttyUSB0

with an .coldsyncrc like this:

listen serial {
protocol: simple;
}

pda "My Palm" {
# snum: XXXX;
username: "Stephan Gutschke";
userid: 256;
default;
}

coldsync just says:
Warning: no device on /dev/ttyUSB0. Sleeping
Please press the HotSync button. <- comes after i press the hotsync
button on my clie



And than i get the things below, which

Nov 8 19:58:53 yvette kernel: hub.c: port 1 connection change
Nov 8 19:58:53 yvette kernel: hub.c: port 1, portstatus 101, change 1,
12 Mb/s
Nov 8 19:58:53 yvette kernel: hub.c: port 1, portstatus 103, change 0,
12 Mb/s
Nov 8 19:58:53 yvette kernel: hub.c: USB new device connect on bus1/1,
assigned device number 4
Nov 8 19:58:53 yvette kernel: usb.c: kmalloc IF cb82a620, numif 1
Nov 8 19:58:53 yvette kernel: usb.c: new device strings: Mfr=1,
Product=2, SerialNumber=0
Nov 8 19:58:53 yvette kernel: usb.c: USB device number 4 default
language ID 0x409
Nov 8 19:58:53 yvette kernel: Manufacturer: Sony Corp.
Nov 8 19:58:53 yvette kernel: Product: Palm Handheld
Nov 8 19:58:53 yvette kernel: usbserial.c: Sony Clie 4.0 converter detected
Nov 8 19:58:53 yvette kernel: visor.c: visor_startup
Nov 8 19:58:53 yvette kernel: visor.c: visor_startup - Set config to 1
Nov 8 19:58:53 yvette kernel: visor.c: Sony Clie 4.0: Number of ports: 2
Nov 8 19:58:53 yvette kernel: visor.c: Sony Clie 4.0: port 1, is for
Generic use and is bound to ttyUSB0
Nov 8 19:58:53 yvette kernel: visor.c: Sony Clie 4.0: port 2, is for
HotSync use and is bound to ttyUSB1
Nov 8 19:58:53 yvette kernel: usb-uhci.c: interrupt, status 2, frame# 1802
Nov 8 19:58:56 yvette kernel: usb_control/bulk_msg: timeout
Nov 8 19:58:56 yvette kernel: visor.c: visor_startup - error getting
first unknown palm command
Nov 8 19:58:59 yvette kernel: usb_control/bulk_msg: timeout
Nov 8 19:58:59 yvette kernel: visor.c: visor_startup - error getting
second unknown palm command
Nov 8 19:58:59 yvette kernel: usbserial.c: Sony Clie 4.0 converter now
attached to ttyUSB0 (or usb/tts/0 for devfs)
Nov 8 19:58:59 yvette kernel: usbserial.c: Sony Clie 4.0 converter now
attached to ttyUSB1 (or usb/tts/1 for devfs)
Nov 8 19:58:59 yvette kernel: usb.c: serial driver claimed interface
cb82a620
Nov 8 19:58:59 yvette kernel: usb.c: kusbd: /sbin/hotplug add 4
Nov 8 19:58:59 yvette kernel: usb.c: kusbd policy returned 0xfffffffe
Nov 8 19:59:01 yvette kernel: visor.c: visor_open - port 0
Nov 8 19:59:01 yvette kernel: visor.c: visor_openport->read_urb db335840
Nov 8 19:59:01 yvette kernel: visor.c: visor_openport->serial->dev de430c00
Nov 8 19:59:01 yvette kernel: visor.c:
visor_openport->read_urb->transfer_buffer ce39af20
Nov 8 19:59:01 yvette kernel: visor.c:
visor_openport->read_urb->transfer_buffer_length 64
Nov 8 19:59:01 yvette kernel: visor.c: visor_open just after reading
and submitting urb 0
Nov 8 19:59:01 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5401
Nov 8 19:59:01 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5402
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - port 0
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - data bits = 8
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - parity = none
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - stop bits = 1
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - RTS/CTS is
disabled
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - XON/XOFF is
disabled
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - baud rate =
230400
Nov 8 19:59:01 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5401
Nov 8 19:59:01 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5401
Nov 8 19:59:01 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5402
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - port 0
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - data bits = 8
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - parity = none
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - stop bits = 1
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - RTS/CTS is
disabled
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - XON/XOFF is
disabled
Nov 8 19:59:01 yvette kernel: visor.c: visor_set_termios - baud rate = 9600
Nov 8 19:59:01 yvette kernel: visor.c: visor_ioctl - port 0, cmd 0x5401
Nov 8 19:59:01 yvette kernel: visor.c: visor_chars_in_buffer - port 0
Nov 8 19:59:01 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
Nov 8 19:59:01 yvette kernel: visor.c: visor_read_bulk_callback - port 0
Nov 8 19:59:01 yvette kernel: visor.c: visor_read_bulk_callback -
length = 6, data = 01 ff 00 00 00 16
Nov 8 19:59:01 yvette kernel: visor.c: visor_chars_in_buffer - port 0
Nov 8 19:59:01 yvette kernel: visor.c: visor_chars_in_buffer - returns 0
Nov 8 19:59:01 yvette kernel: visor.c: visor_read_bulk_callback - port 0
Nov 8 19:59:01 yvette kernel: visor.c: visor_read_bulk_callback -
length = 22, data = 90 01 00 00 00 00 00 00 00 20 00 00 00 08 00 00 01
00 00 00 00 00
Nov 8 20:00:01 yvette kernel: usb-uhci.c: interrupt, status 3, frame# 1889
Nov 8 20:00:01 yvette kernel: visor.c: visor_read_bulk_callback - port 0
Nov 8 20:00:01 yvette kernel: visor.c: visor_read_bulk_callback -
nonzero read bulk status received: -84
Nov 8 20:00:01 yvette kernel: hub.c: port 1 connection change
Nov 8 20:00:01 yvette kernel: hub.c: port 1, portstatus 100, change 3,
12 Mb/s
Nov 8 20:00:01 yvette kernel: usb.c: USB disconnect on device 4
Nov 8 20:00:01 yvette kernel: visor.c: visor_shutdown
Nov 8 20:00:01 yvette kernel: visor.c: visor_close - port 0
Nov 8 20:00:01 yvette kernel: usbserial.c: Sony Clie 4.0 converter now
disconnected from ttyUSB0
Nov 8 20:00:01 yvette kernel: usbserial.c: Sony Clie 4.0 converter now
disconnected from ttyUSB1
Nov 8 20:00:01 yvette kernel: usb.c: kusbd: /sbin/hotplug remove 4
Nov 8 20:00:01 yvette kernel: usb.c: kusbd policy returned 0xfffffffe
Nov 8 20:00:01 yvette kernel: hub.c: port 1 enable change, status 100


Greg KH wrote:

> On Thu, Nov 08, 2001 at 12:03:44AM +0100, Stephan Gutschke wrote:
>
>>didn't work :-(
>>
>>This is the output of /var/log/syslog if I connect to ttyUSB0
>>I am not sure yet though that the problem is in your module.
>>I know the jpilot worked, before, but I will still try later
>>to connect to the clie with coldsync as well.
>>Lets see if that gives anything different.
>>Let me know what else I can do to help.
>>
>
> Yes, you will have to use coldsync to talk to this device right now, as
> pilot-link doesn't have support for the 4.x Palm OS USB protocol yet
> (jpilot uses pilot-link.)
>
> Let me know if coldsync fails (remember you have to tell coldsync that
> you are a m50x, and that you want the "simple" protocol, check the docs
> for the proper config file setting.)
>
> thanks,
>
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>



--
Stephan Gutschke

2001-11-12 18:15:39

by Greg KH

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

On Thu, Nov 08, 2001 at 08:12:04PM +0100, Stephan Gutschke wrote:
>
> listen serial {
> protocol: simple;
> }

I just had a report of someone getting this to work by using
"protocol: net"

Could you try that?

thanks,

greg k-h

2001-11-14 04:04:45

by Werner Almesberger

[permalink] [raw]
Subject: Re: Oops when syncing Sony Clie 760 with USB cradle

Greg KH wrote:
> I just had a report of someone getting this to work by using
> "protocol: net"

Worked for me, thanks a lot ! The kernel complained about some
unrecognized packet on the first try/tries, but now it always seems to
work.

Linux 2.4.15-pre4 on Sony Vaio C1VN, ColdSync 2.2.3, Sony Clie N710C
upgraded to PalmOS 4.1.

"protocol: simple" yields:

##### Bad response ID: expected 0x9a, got 0x93.
Warning: Restore: Can't delete database "BigClock": -1.
Error: Can't restore directory.
##### Bad response ID: expected 0xaf, got 0x9a.
Error: Error during DlpEndOfSync: (7) Invalid request ID.

Trying to use ttyUSB1 always yields:

visor.c: Device lied about number of ports, please use a lower one.

- Werner

--
_________________________________________________________________________
/ Werner Almesberger, Lausanne, CH [email protected] /
/_http://icawww.epfl.ch/almesberger/_____________________________________/