Skip to contentSkip to conversation

Seg fault when syncing Sony Clie 760 with USB cradle

DISCUSSION Peter A. Goodall 2 participants 4 messages Oct 26, 2001 – Nov 2, 2001

lore
Share & tools
lore
#0 lore raw

I am running Redhat 7.1 with the 2.4.12 kernel and using xfs. I have applied an SGI patch (linux-2.4.12-xfs-2001-10-11.patch.bz2) to run xfs. I am using coldsync 2.2.0 to sync and everytime I try to sync it I get a seg fault. This causes a kernel panic and I am no longer able to use the USB port until I reboot. Below is the end of /var/log/messages:

Oct 25 20:23:10 localhost kernel: usb_control/bulk_msg: timeout 
Oct 25 20:23:10 localhost kernel: visor.c: visor_startup - error getting
first unknown palm command 
Oct 25 20:23:13 localhost kernel: usb_control/bulk_msg: timeout 
Oct 25 20:23:13 localhost kernel: visor.c: visor_startup - error getting
second unknown palm command 
Oct 25 20:23:13 localhost kernel: usbserial.c: Sony Clie 4.0 converter
now attached to ttyUSB0 (or usb/tts/0 for devfs) 
Oct 25 20:23:13 localhost kernel: usbserial.c: Sony Clie 4.0 converter
now attached to ttyUSB1 (or usb/tts/1 for devfs) 
Oct 25 20:23:13 localhost kernel: visor.c: USB HandSpring Visor, Palm
m50x, Sony Clie driver v1.4 
Oct 25 20:23:15 localhost kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000014 
Oct 25 20:23:15 localhost kernel:  printing eip: 
Oct 25 20:23:15 localhost kernel: c88c6103 
Oct 25 20:23:15 localhost kernel: *pde = 00000000 
Oct 25 20:23:15 localhost kernel: Oops: 0002 
Oct 25 20:23:15 localhost kernel: CPU:    0 
Oct 25 20:23:15 localhost kernel: EIP:   
0010:[fat:__insmod_fat_S.bss_L2264+389699/11025069]    Not tainted 
Oct 25 20:23:15 localhost kernel: EIP:    0010:[<c88c6103>]    Not
tainted 
Oct 25 20:23:15 localhost kernel: EFLAGS: 00013202 
Oct 25 20:23:15 localhost kernel: eax: c3c69800   ebx: c71ef494   ecx:
c71ef4f0   edx: 00000000 
Oct 25 20:23:15 localhost kernel: esi: c71ef400   edi: 00000000   ebp:
c2f01edc   esp: c2f01ea4 
Oct 25 20:23:15 localhost kernel: ds: 0018   es: 0018   ss: 0018 
Oct 25 20:23:15 localhost kernel: Process coldsync (pid: 1055,
stackpage=c2f01000) 
Oct 25 20:23:15 localhost kernel: Stack: c2f30000 c50333c0 0000bc01
c88c03f4 c71ef494 c50333c0 c2f30000 00000000 
Oct 25 20:23:15 localhost kernel:        c01cf995 c2f30000 c50333c0
c019e29b c502018c 00000002 c2f30000 c01b579f 
Oct 25 20:23:15 localhost kernel:        c5020100 00000008 c5020100
00000180 00000000 c5020100 00000008 c2ec30a0 
Oct 25 20:23:15 localhost kernel: Call Trace:
[fat:__insmod_fat_S.bss_L2264+365876/11048892] [tty_open+565/960]
[xfs_iunlock+75/128] [xfs_access+47/64] [linvfs_permission+33/48] 
Oct 25 20:23:15 localhost kernel: Call Trace: [<c88c03f4>] [<c01cf995>]
[<c019e29b>] [<c01b579f>] [<c01c0051>] 
Oct 25 20:23:15 localhost kernel:    [permission+29/48]
[chrdev_open+54/64] [dentry_open+230/400] [filp_open+77/96]
[getname+94/160] [sys_open+52/144] 
Oct 25 20:23:15 localhost kernel:    [<c013bcbd>] [<c0133e26>]
[<c0132e76>] [<c0132d7d>] [<c013bb3e>] [<c01330a4>] 
Oct 25 20:23:15 localhost kernel:    [tracesys+31/35] 
Oct 25 20:23:15 localhost kernel:    [<c0106f77>] 
Oct 25 20:23:15 localhost kernel: 
Oct 25 20:23:15 localhost kernel: Code: 89 42 14 8b 4e 04 0f b6 53 24 8b
01 c1 e2 0f c1 e0 08 09 d0 
Oct 25 20:24:07 localhost kernel:  <6>usb.c: USB disconnect on device 2 

Please CC [email protected] in the reply.

- Pete

#1 lore raw
Quoted 5 lines · Peter A. Goodall

I am running Redhat 7.1 with the 2.4.12 kernel and using xfs. I have applied an SGI patch (linux-2.4.12-xfs-2001-10-11.patch.bz2) to run xfs. I am using coldsync 2.2.0 to sync and everytime I try to sync it I get a seg fault. This causes a kernel panic and I am no longer able to use the USB port until I reboot. Below is the end of /var/log/messages:

Does the oops happen at the end of the sync, or at the beginning?

Can you run that oops through ksymoops for me?

thanks,

greg k-h

#2 lore raw
Quoted 4 lines

Does the oops happen at the end of the sync, or at the beginning?

Can you run that oops through ksymoops for me?

Hopefully this will help. I'll paste output below:

ksymoops 2.4.0 on i686 2.4.12-xfs. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.12-xfs/ (default)
-m /boot/System.map-2.4.12-xfs (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.

Warning (compare_maps): ksyms_base symbol __start___kallsyms_R__ver___start___kallsyms not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol __stop___kallsyms_R__ver___stop___kallsyms not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol create_bounce_R__ver_create_bounce not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol highmem_start_page_R__ver_highmem_start_page not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol kallsyms_address_to_symbol_R__ver_kallsyms_address_to_symbol not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol kallsyms_symbol_to_address_R__ver_kallsyms_symbol_to_address not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol kmap_high_R__ver_kmap_high not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol kunmap_high_R__ver_kunmap_high not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says c021b700, System.map says c0151640. Ignoring ksyms_base entry Warning (compare_maps): mismatch on symbol usb_devfs_handle , usbcore says c8854080, /lib/modules/2.4.12-xfs/kernel/drivers/usb/usbcore.o says c8853b40. Ignoring /lib/modules/2.4.12-xfs/kernel/drivers/usb/usbcore.o entry

Oct 26 11:42:45 localhost kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000014
Oct 26 11:42:45 localhost kernel: c88c6103
Oct 26 11:42:45 localhost kernel: *pde = 00000000
Oct 26 11:42:45 localhost kernel: Oops: 0002
Oct 26 11:42:45 localhost kernel: CPU:    0
Oct 26 11:42:45 localhost kernel: EIP:   
0010:[fat:__insmod_fat_S.bss_L2264+389699/11025069]    Not tainted
Oct 26 11:42:45 localhost kernel: EIP:    0010:[<c88c6103>]    Not
tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Oct 26 11:42:45 localhost kernel: EFLAGS: 00210202
Oct 26 11:42:45 localhost kernel: eax: c658fc00   ebx: c6fa1094   ecx:
c6fa10f0   edx: 00000000
Oct 26 11:42:45 localhost kernel: esi: c6fa1000   edi: 00000000   ebp:
c2f57edc   esp: c2f57ea4
Oct 26 11:42:45 localhost kernel: ds: 0018   es: 0018   ss: 0018
Oct 26 11:42:45 localhost kernel: Process coldsync (pid: 1092,
stackpage=c2f5700
Oct 26 11:42:45 localhost kernel: Stack: c53b9000 c45953a0 0000bc01
c88c03f4 c6fa1094 c45953a0 c53b9000 00000000 
Oct 26 11:42:45 localhost kernel:        c01cf995 c53b9000 c45953a0
c019e29b c421fa30 00000002 c53b9000 c01b579f 
Oct 26 11:42:45 localhost kernel:        c421f9a4 00000008 c421f9a4
00000180 00000000 c421f9a4 00000008 c2e99240 
Oct 26 11:42:45 localhost kernel: Call Trace:
[fat:__insmod_fat_S.bss_L2264+365876/11048892] [tty_open+565/960]
[xfs_iunlock+75/128] [xfs_access+47/64] [linvfs_permission+33/48] 
Oct 26 11:42:45 localhost kernel: Call Trace: [<c88c03f4>] [<c01cf995>]
[<c019e29b>] [<c01b579f>] [<c01c0051>] 
Oct 26 11:42:45 localhost kernel:    [<c013bcbd>] [<c0133e26>]
[<c0132e76>] [<c0132d7d>] [<c013bb3e>] [<c01330a4>] 
Oct 26 11:42:45 localhost kernel:    [<c0106f0b>] 
Oct 26 11:42:45 localhost kernel: Code: 89 42 14 8b 4e 04 0f b6 53 24 8b

01 c1 e2 0f c1 e0 08 09 d0

Quoted 1 line
Quoted 1 line

EIP; c88c6103 <[xircom_cb]trigger_transmit+3/20> <=====

Trace; c88c03f4 <[ide-cd].data.end+2d35/7941> Trace; c01cf995 <tty_open+235/3c0>
Trace; c019e29b <xfs_iunlock+4b/80>
Trace; c01b579f <xfs_access+2f/40>
Trace; c01c0051 <linvfs_permission+21/30> Trace; c013bcbd <permission+1d/30>
Trace; c0133e26 <chrdev_open+36/40>
Trace; c0132e76 <dentry_open+e6/190>
Trace; c0132d7d <filp_open+4d/60>
Trace; c013bb3e <getname+5e/a0>
Trace; c01330a4 <sys_open+34/90>
Trace; c0106f0b <system_call+33/38>
Code; c88c6103 <[xircom_cb]trigger_transmit+3/20> 00000000 <_EIP>:
Code; c88c6103 <[xircom_cb]trigger_transmit+3/20> <=====
0: 89 42 14 mov %eax,0x14(%edx) <=====
Code; c88c6106 <[xircom_cb]trigger_transmit+6/20>
3: 8b 4e 04 mov 0x4(%esi),%ecx
Code; c88c6109 <[xircom_cb]trigger_transmit+9/20>
6: 0f b6 53 24 movzbl 0x24(%ebx),%edx
Code; c88c610d <[xircom_cb]trigger_transmit+d/20>
a: 8b 01 mov (%ecx),%eax
Code; c88c610f <[xircom_cb]trigger_transmit+f/20>
c: c1 e2 0f shl $0xf,%edx
Code; c88c6112 <[xircom_cb]trigger_transmit+12/20>
f: c1 e0 08 shl $0x8,%eax
Code; c88c6115 <[xircom_cb]trigger_transmit+15/20>
12: 09 d0 or %edx,%eax

11 warnings issued. Results may not be reliable.

Signature · 4 lines
Pete Goodall
  Support Tech
  Ximian, Inc.
  [email protected]
#3 lore raw
In reply to Greg KH
Quoted 7 lines · Greg KH
Quoted 5 lines · Peter A. Goodall

I am running Redhat 7.1 with the 2.4.12 kernel and using xfs. I have applied an SGI patch (linux-2.4.12-xfs-2001-10-11.patch.bz2) to run xfs. I am using coldsync 2.2.0 to sync and everytime I try to sync it I get a seg fault. This causes a kernel panic and I am no longer able to use the USB port until I reboot. Below is the end of /var/log/messages:

Quoted 7 lines

Does the oops happen at the end of the sync, or at the beginning?

Can you run that oops through ksymoops for me?

thanks,

greg k-h

I noticed that my last kernel was not behaving correctly. Specifically that nfs (unrelated) and devfs were not starting correctly. I upgraded to the 2.4.13 kernel and paid special attention to those two items. Now syncing with Coldsync no longer causes a kernel panic. It just doesn't work. It can't communicate with the Clie to get the serial number and other information. Since I'm using devfs I can't say it is the kernel. I will have to test it further.

- PAG

Signature · 4 lines
Pete Goodall
  Support Tech
  Ximian, Inc.
  [email protected]