Trouble with usb modem

	Hi all

I'm trying to use an usb modem from multitech with linux SUSE SLES 9 
SP3, with latest kernel update 2.6.5-7.286.

If the modem is connected during the boot process, the khubd process die 
and I get this dump (cut/paste from dmesg) and all usb devices does not 
respond (also the keyboard!)

Instead, If I make the boot with the modem disconnected and after the 
boot process is completed, I connect the momem, no problem arise.

I'm in the process of opening a support request to novell, but this is 
always a long process and if any of you have a clue or can suggest a way 
to gather more useful information, let me know!

Thank you in advance

Davide Pagnin

usb 2-2: USB disconnect, address -1
Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
<ffffffff80234a10>{strlen+0}
PML4 0
Oops: 0000 [1] SMP
CPU 1
Pid: 2227, comm: khubd Not tainted (2.6.5-7.286-smp 
SLES9_SP3_BRANCH-20070531101258)
RIP: 0010:[<ffffffff80234a10>] <ffffffff80234a10>{strlen+0}
RSP: 0018:000001007ea97d80  EFLAGS: 00010216
RAX: 000001007e79ca80 RBX: 0000000000000000 RCX: ffffffffa01a66a8
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 000001007e0a3080 R08: 0000000000000001 R09: 0062737500000001
R10: 0000000000000246 R11: 0000000000000000 R12: 000001007ff45a00
R13: 000001007e798000 R14: ffffffff804431c0 R15: 0000000000000001
FS:  0000000000000000(0000) GS:ffffffff805dc580(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 000000000365d000 CR4: 00000000000006e0
Process khubd (pid: 2227, threadinfo 000001007ea96000, task 
000001007e1541c0)
Stack: ffffffff801d14d8 0000000000000000 000001007e798000 ffffffff804431c0
        000001007e0a3080 ffffffffa01a67e0 ffffffff801d157a 0000010037ff2030
        0000010037ff20f0 ffffffffa01a67e0
Call Trace:<ffffffff801d14d8>{sysfs_get_dentry+24} 
<ffffffff801d157a>{sysfs_hash_and_remove+58}
        <ffffffff802822da>{device_release_driver+42} 
<ffffffff8028240b>{bus_remove_device+59}
        <ffffffff80281258>{device_del+88} 
<ffffffff80281299>{device_unregister+9}
        <ffffffffa018b461>{:usbcore:hub_port_connect_change+97}
        <ffffffffa018bae2>{:usbcore:hub_thread+706} 
<ffffffff8013d610>{autoremove_wake_function+0}
        <ffffffff8013d610>{autoremove_wake_function+0} 
<ffffffff8011122f>{child_rip+8}
        <ffffffffa018b820>{:usbcore:hub_thread+0} 
<ffffffff80111227>{child_rip+0}


Code: 80 3f 00 48 89 f8 74 08 48 ff c0 80 38 00 75 f8 48 29 f8 c3
RIP <ffffffff80234a10>{strlen+0} RSP <000001007ea97d80>
CR2: 0000000000000000

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel