[Home]

Summary:ASTERISK-02756: WCUSB driver doesnt work
Reporter:nix (nix)Labels:
Date Opened:2004-11-07 13:57:26.000-0600Date Closed:2011-06-07 14:04:52
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:# ztcfg -v
Zaptel Configuration
======================
1 channels configured.
Segmentation fault

****** ADDITIONAL INFORMATION ******

# cat /etc/SuSE-release
SuSE Linux 9.1 (i586)
VERSION = 9.1
# uname -a
Linux gulsen 2.6.5-7.111-default #1 Wed Oct 13 15:45:13 UTC 2004 i686 i686 i386 GNU/Linux
# cat /var/log/messages
Nov  7 21:51:00 gulsen kernel: usb 1-2: new full speed USB device using address 5
Nov  7 21:51:04 gulsen /etc/hotplug/usb.agent[11832]: need a device for this command
Nov  7 21:51:04 gulsen /etc/hotplug/usb.agent[11825]: need a device for this command
Nov  7 21:51:04 gulsen kernel: ALSA sound/usb/usbmixer.c:611: 6:1: cannot get min/max values for control 2 (id 6)
Nov  7 21:51:04 gulsen kernel: ALSA sound/usb/usbmixer.c:611: 5:1: cannot get min/max values for control 2 (id 5)
Nov  7 21:51:04 gulsen kernel: usb 1-2: control timeout on ep0in
Nov  7 21:51:04 gulsen kernel: ALSA sound/usb/usbmixer.c:611: 6:1: cannot get min/max values for control 2 (id 6)
Nov  7 21:51:04 gulsen kernel: ALSA sound/usb/usbmixer.c:611: 5:1: cannot get min/max values for control 2 (id 5)
Nov  7 21:51:04 gulsen /etc/hotplug/usb.agent[11949]: need a device for this command
Nov  7 21:51:04 gulsen /etc/hotplug/usb.agent[11957]: need a device for this command
Nov  7 21:51:14 gulsen kernel: zaptel: unsupported module, tainting kernel.
Nov  7 21:51:14 gulsen kernel: Zapata Telephony Interface Registered on major 196
Nov  7 21:51:14 gulsen modprobe: FATAL: Error running install command for wcusb
Nov  7 21:51:14 gulsen /etc/hotplug/usb.agent[11832]: ... can't load module wcusb
Nov  7 21:51:14 gulsen /etc/hotplug/usb.agent[11832]: missing kernel or user mode driver wcusb
Nov  7 21:51:14 gulsen kernel: wcusb: unsupported module, tainting kernel.
Nov  7 21:51:14 gulsen kernel: usbcore: registered new driver wcusb
Nov  7 21:51:14 gulsen kernel: Wildcard USB FXS Interface driver registered

*** HERE ztcfg was run ***

Nov  7 21:51:30 gulsen kernel: Unable to handle kernel paging request at virtual address d4feda80
Nov  7 21:51:30 gulsen kernel:  printing eip:
Nov  7 21:51:30 gulsen kernel: c01609eb
Nov  7 21:51:30 gulsen kernel: *pde = 13e9f067
Nov  7 21:51:30 gulsen kernel: Oops: 0000 [#3]
Nov  7 21:51:30 gulsen kernel: CPU:    0
Nov  7 21:51:30 gulsen kernel: EIP:    0060:[cdev_get+11/80]    Tainted: GF U
Nov  7 21:51:30 gulsen kernel: EIP:    0060:[<c01609eb>]    Tainted: GF U
Nov  7 21:51:30 gulsen kernel: EFLAGS: 00210246   (2.6.5-7.111-default)
Nov  7 21:51:30 gulsen kernel: EIP is at cdev_get+0xb/0x50
Nov  7 21:51:30 gulsen kernel: eax: cab34a00   ebx: d4feda80   ecx: c0160be0   edx: 00000000
Nov  7 21:51:30 gulsen kernel: esi: cf7630cc   edi: 00000000   ebp: 00000000   esp: cc18dee0
Nov  7 21:51:30 gulsen kernel: ds: 007b   es: 007b   ss: 0068
Nov  7 21:51:30 gulsen kernel: Process ztcfg (pid: 12162, threadinfo=cc18c000 task=d30177d0)
Nov  7 21:51:30 gulsen kernel: Stack: cab34a00 cf7630cc c0160c00 c1da0b80 cf7630cc c1da0b80 cf7630cc d3fe4ec0
Nov  7 21:51:30 gulsen kernel:        c1fd8770 c0155ab6 00000000 00000002 cc18df44 cc18df70 08086050 c0155be0
Nov  7 21:51:30 gulsen kernel:        cc18df44 d38db000 c1fd8770 d3fe4ec0 c0202d7e cb2f2bcc 00000018 00000101
Nov  7 21:51:30 gulsen kernel: Call Trace:
Nov  7 21:51:30 gulsen kernel:  [chrdev_open+32/272] chrdev_open+0x20/0x110
Nov  7 21:51:30 gulsen kernel:  [<c0160c00>] chrdev_open+0x20/0x110
Nov  7 21:51:30 gulsen kernel:  [dentry_open_it+342/448] dentry_open_it+0x156/0x1c0
Nov  7 21:51:30 gulsen kernel:  [<c0155ab6>] dentry_open_it+0x156/0x1c0
Nov  7 21:51:30 gulsen kernel:  [filp_open+112/128] filp_open+0x70/0x80
Nov  7 21:51:30 gulsen kernel:  [<c0155be0>] filp_open+0x70/0x80
Nov  7 21:51:30 gulsen kernel:  [tty_write+366/432] tty_write+0x16e/0x1b0
Nov  7 21:51:30 gulsen kernel:  [<c0202d7e>] tty_write+0x16e/0x1b0
Nov  7 21:51:30 gulsen kernel:  [sys_open+131/208] sys_open+0x83/0xd0
Nov  7 21:51:30 gulsen kernel:  [<c0155c73>] sys_open+0x83/0xd0
Nov  7 21:51:30 gulsen kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Nov  7 21:51:30 gulsen kernel:  [<c0107e27>] syscall_call+0x7/0xb
Nov  7 21:51:30 gulsen kernel:
Nov  7 21:51:30 gulsen kernel: Code: 83 3b 02 74 13 ff 83 00 01 00 00 e8 25 5d 07 00 89 c6 85 c0
Comments:By: Mark Spencer (markster) 2004-11-07 13:58:43.000-0600

This is a technical support issue and is not appropriate for the bug tracker.  Please read the bug guidelines which were highlighted in yellow when you were placing your bug report, before placing any further bug reports.
By: Mark Spencer (markster) 2004-11-07 14:00:06.000-0600

Sorry, wrong karma comment was supposed to be about placing a bug about a tech support issue.
By: nix (nix) 2004-11-07 19:05:51.000-0600

Sorry for being a pain, but where AM I supposed to report crashes with zaptel drivers? I assume you are talking about the following:
"3. Do not place bugs about trouble you are having with your hardware (e.g. inability to load drivers, modules or cards that are acting up) unless directed to do so by "
???

Directed by Who??
I am happy to call tech support if you like, however I was trying to do the right thing and report this in electronic form before wasting Tech support and my time on an international phone call with a 5 hour time difference.

Please note that I have been selling systems based on Digium hardware as well as hacking on Asterisk for over 12 months now so I am not a newbie just wasting space in the bugtracker.
By: Mark Spencer (markster) 2004-11-07 19:08:21.000-0600

We *cannot* use the bug tracker for technical support issues, period.  It's hard enough to keep it up to date with just software, protocol and similar issues.

You can e-mail support@digium.com and get an electronic version just like here.  The difference is that support@digium.com is for technical support and is better geared for supporting our products.  If you still have trouble you can try to find me on IRC, but again, this is NOT the forum for this kind of problem.