Hi.

I have problems with my Debian testing laptop running a 2.4.20 kernel
when trying to synchronize my T625C with jpilot.

It used to work with the previous 2.4.19 kernel, so I consider this to
be some kind of regression.

Now, I cannot make it work, and I get page errors, which soon end up
in kernel panic.


I give a more detailed explanation of the circumstances :

1) start jpilot
2) launch the sync on the cli�, 
3) after several beeps and execution of the right steps by usbmgr, I
click on Sync in jpilot
no synchro is started (that used to happen on the first time with (and
before) 2.4.19, but was working after timeout and restart of the
process after launching again jpilot)
4) timeout happens and the page fault is logged

On suggestion by Greg KH <[EMAIL PROTECTED]>, I did a ksymoops and
obtained this :

ksymoops 2.4.6 on i686 2.4.20.  Options used
     -V (default)
     -k /var/log/ksymoops/20030118110042.ksyms (specified)
     -l /var/log/ksymoops/20030118110042.modules (specified)
     -o /lib/modules/2.4.20/ (default)
     -m /boot/System.map-2.4.20 (default)

Unable to handle kernel paging request at virtual address d0900f30
c01705c6
*pde = 0ff19067
Oops: 0000
CPU:    0
EIP:    0010:[<c01705c6>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282
eax: 00000005   ebx: 00000001   ecx: c0265e80   edx: d0900f20
esi: 00000005   edi: 00000005   ebp: c02bf984   esp: cd35df08
ds: 0018   es: 0018   ss: 0018
Process usbmgr (pid: 481, stackpage=cd35d000)
Stack: c0265e80 00000028 c012fd8f 00000501 ffffffed c9983460 cfe9c800 cffd9320 
       ffffffeb cfe9c800 cd35df8c c0137b47 cfe9c800 c012fef9 00000005 00000001 
       c9983460 cfe9c800 00000000 c012ef65 cfe9c800 c9983460 0804d562 cfe9e000 
Call Trace:    [<c012fd8f>] [<c0137b47>] [<c012fef9>] [<c012ef65>] [<c012ee7a>]
  [<c012f1aa>] [<c0106bc7>]
Code: 0f bf 42 10 39 f0 75 16 0f bf 4a 12 39 cb 7c 0e 0f bf 42 14 


>>EIP; c01705c6 <get_tty_driver+1a/48>   <=====

>>ecx; c0265e80 <tty_fops+0/60>
>>edx; d0900f20 <[usbserial]serial_tty_driver+0/bb>
>>ebp; c02bf984 <chrdevs+4/7f8>
>>esp; cd35df08 <_end+d079570/105516c8>

Trace; c012fd8f <get_chrfops+67/c8>
Trace; c0137b47 <permission+2b/30>
Trace; c012fef9 <chrdev_open+25/4c>
Trace; c012ef65 <dentry_open+e1/188>
Trace; c012ee7a <filp_open+52/5c>
Trace; c012f1aa <sys_open+36/84>
Trace; c0106bc7 <system_call+33/38>

Code;  c01705c6 <get_tty_driver+1a/48>
00000000 <_EIP>:
Code;  c01705c6 <get_tty_driver+1a/48>   <=====
   0:   0f bf 42 10               movswl 0x10(%edx),%eax   <=====
Code;  c01705ca <get_tty_driver+1e/48>
   4:   39 f0                     cmp    %esi,%eax
Code;  c01705cc <get_tty_driver+20/48>
   6:   75 16                     jne    1e <_EIP+0x1e> c01705e4 <get_tty_driver+38/48>
Code;  c01705ce <get_tty_driver+22/48>
   8:   0f bf 4a 12               movswl 0x12(%edx),%ecx
Code;  c01705d2 <get_tty_driver+26/48>
   c:   39 cb                     cmp    %ecx,%ebx
Code;  c01705d4 <get_tty_driver+28/48>
   e:   7c 0e                     jl     1e <_EIP+0x1e> c01705e4 <get_tty_driver+38/48>
Code;  c01705d6 <get_tty_driver+2a/48>
  10:   0f bf 42 14               movswl 0x14(%edx),%eax

Unfortunately, Greg didn't seem to have any clue of the problem... So
I try here hoping that I would have a better chance.

I Hope this helps identify the faulty code.

Any suggestion on how to solve it would be greatly appreciated.

Best regards,

-- 
Olivier BERGER (OpenPGP: 1024D/B4C5F37F)
APRIL (http://www.april.org) - Vive python (http://www.python.org)
P�tition contre les brevets logiciels : http://petition.eurolinux.org


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to