DAHLIN-00051: wct1xxp module fails to probe the hardware

[Home]

Summary: DAHLIN-00051: wct1xxp module fails to probe the hardware

Reporter: klaus3000 (klaus3000) Labels:

Date Opened: 2008-10-03 04:22:12 Date Closed: 2008-10-22 06:34:12

Priority: Major Regression? No

Status: Closed/Complete Components: wct1xxp

Versions: 2.0.0 Frequency of
Occurrence

Related
Issues:

Environment: Attachments: ( 0) wct1xxp_pci.diff
( 1) zap2dahdi

Description: "modprobe wct1xxp" results in:

Oct 3 11:21:38 samuel kernel: [877999.378572] t1xxp: probe of 0000:03:08.0 failed with error -5

I never had any issues while using zaptel.

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

$ cat /etc/debian_version
lenny/sid

$ uname -a
Linux samuel 2.6.26-1-686 #1 SMP Wed Sep 10 16:46:13 UTC 2008 i686 GNU/Linux

$ dahdi_hardware
pci:0000:03:08.0 wct1xxp- e159:0001 Digium Wildcard T100P T1/PRI or E100P E1/PRA Board

$ lspci -vvv
.....
03:08.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
Subsystem: Device 6159:0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (250ns min, 32000ns max)
Interrupt: pin A routed to IRQ 20
Region 0: I/O ports at cc00 [size=256]
Region 1: Memory at fe800000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA PME(D0+,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel modules: hisax, wct1xxp

Comments: By: Leif Madsen (lmadsen) 2008-10-07 13:06:19

Please file a bug with the Digium tech support department as that method will get you a result much quicker for this type of hardware issue.

Thanks!
By: klaus3000 (klaus3000) 2008-10-15 04:30:55

Hi!

I contacted the support and they could not help - just told me to reinstall it.

In the end they came to the conclusion, that the T100 card is not supported (although mentioned in the README of DHADI as supported):

from support:
> It is supported by the software, but is not supported by our support
> staff, as the card has reached End of Life. You can get community
> support on irc on #asterisk on irc.freenode.net. Many of the digium
> staff and developers stay in this room, and can answer your questions
> there.

So, is it fine to reopen the bug?
By: Leif Madsen (lmadsen) 2008-10-15 07:54:21

Ummm... well I'll leave this bug open for a little bit to see if anyone picks it up. Sorry I directed you to Digium support, I didn't realize you were using an End of Life product.

There isn't much I'm going to be able to do to help you here, so I think your best bet is really to use the #asterisk IRC channel or the asterisk-users mailing lists.

If you get this resolved, please request to have this bug closed. Thanks!
By: Tzafrir Cohen (tzafrir) 2008-10-15 13:23:51

Could you please give a more complete trace from loading the driver? Preferably with debug=1 . That is: modprobe wct1xxp debug=1 What do you see on /var/log/kern.log ?

-5 means -EIO .
By: Jason Parker (jparker) 2008-10-15 13:28:27

Did the hisax module get loaded and "take control" of the card?
By: Tzafrir Cohen (tzafrir) 2008-10-15 13:36:41

Right. Something is different. But what is it?

The Zaptel wct1xxp module can't be loaded, as zaptel and dahdi can't be loaded at the same time.

Please give us a detailed trace from /var/log/kern.log if you still have it. And even better - if you can replicate this issue now.
By: klaus3000 (klaus3000) 2008-10-16 06:58:31

Hi! no problem - easy to reproduce (I only have to shut down a production box ;-)

So: I unloaded wct1xxp and zaptel. Further I unloaded hisax and isdn module (although they were loaded I never had any issues with zaptel).

Then I installed dahdi (I verifyied that the zaptel modules were deleted).

Then I loaded the modules:

modprobe dahdi debug=1

Oct 16 14:04:34 samuel kernel: [2182470.418415] dahdi: Telephony Interface Registered on major 196
Oct 16 14:04:34 samuel kernel: [2182470.418415] dahdi: Version: 2.0.0

modprobe wct1xxp debug=1

Oct 16 14:04:45 samuel kernel: [2182482.560576] t1xxp: probe of 0000:03:08.0 failed with error -5

Even with debug=1 there is not more information in the logs.

lsmod

wct1xxp 11392 0
dahdi 182728 1 wct1xxp
ipt_REJECT 2784 7
ipt_LOG 5028 7
xt_tcpudp 2816 73
authenc 5056 7
xfrm4_mode_tunnel 2304 14
deflate 2624 0
zlib_deflate 17624 1 deflate
zlib_inflate 14144 1 deflate
ctr 3936 0
twofish 8224 0
twofish_common 13888 1 twofish
camellia 19136 0
serpent 18688 0
blowfish 8352 0
des_generic 16672 7
cbc 3264 7
aes_i586 7744 0
aes_generic 29256 1 aes_i586
xcbc 4296 0
sha256_generic 11360 0
sha1_generic 2304 7
crypto_null 2880 0
crypto_blkcipher 15236 11 authenc,ctr,cbc,crypto_null
af_key 25428 2
ipip 7556 0
esp4 5600 7
tunnel4 3016 1 ipip
ah4 4416 0
ipv6 235300 18
dm_snapshot 14340 0
dm_mirror 15104 0
dm_log 8452 1 dm_mirror
dm_mod 46184 3 dm_snapshot,dm_mirror,dm_log
aead 6400 2 authenc,esp4
iptable_filter 2624 1
ip_tables 10160 1 iptable_filter
x_tables 13284 4 ipt_REJECT,ipt_LOG,xt_tcpudp,ip_tables
psmouse 32336 0
serio_raw 4740 0
pcspkr 2432 0
crc_ccitt 2080 1 dahdi
slhc 5408 0
shpchp 25528 0
pci_hotplug 23460 1 shpchp
button 6064 0
i2c_piix4 7216 0
i2c_core 19828 1 i2c_piix4
sworks_agp 6720 0
agpgart 28776 1 sworks_agp
evdev 8000 0
dcdbas 6272 0
ext3 105256 4
jbd 39444 1 ext3
mbcache 7108 1 ext3
sg 26964 0
sd_mod 22200 6
ide_cd_mod 27652 0
cdrom 30176 1 ide_cd_mod
ata_generic 4676 0
libata 140416 1 ata_generic
dock 8272 1 libata
floppy 47716 0
aacraid 57388 5
ohci_hcd 18500 0
scsi_mod 129356 4 sg,sd_mod,libata,aacraid
usbcore 118160 2 ohci_hcd
e1000 102624 0
serverworks 4932 0 [permanent]
ide_pci_generic 3908 0 [permanent]
ide_core 92628 3 ide_cd_mod,serverworks,ide_pci_generic
thermal 15228 0
processor 32576 1 thermal
fan 4164 0
thermal_sys 10856 3 thermal,processor,fan
By: Tzafrir Cohen (tzafrir) 2008-10-16 08:00:50

Incidentally, the driver does not call pci_unregister_driver() in case of an error.
By: klaus3000 (klaus3000) 2008-10-16 08:54:02

I just reviewed the wct1xxp module from zaptel and dahdi and coud not find any real differences :-(
By: Tzafrir Cohen (tzafrir) 2008-10-22 05:18:15

Looking at it shows a small difference at that area:

- if (pci_enable_device(pdev)) {
- res = -EIO;
+ if (!pci_enable_device(pdev)) {
+ return -EIO;

:-(
By: Tzafrir Cohen (tzafrir) 2008-10-22 05:28:45

Added a patch to fix this (and add some extra messages). I don't want to commit this one just yet, as it will probably turn a module that fails to load to an oopsing one.

So brave testers with hardware: this is your time.
By: klaus3000 (klaus3000) 2008-10-22 06:09:30

Hi tzafrir!

Thanks very much - now the wct1xxp module loads fine. It could not test it with asterisk yet, but I can configure the card with dahdi_cfg and I also /proc/dahdi reports the card with the proper configuration.
By: Digium Subversion (svnbot) 2008-10-22 06:34:09

Repository: dahdi
Revision: 5118

U linux/trunk/drivers/dahdi/wct1xxp.c

------------------------------------------------------------------------
r5118 | tzafrir | 2008-10-22 06:34:08 -0500 (Wed, 22 Oct 2008) | 9 lines

wct1xxp: fix error handling at device startup.

And also give more useful error messages if things go bad.

(closes issue DAHLIN-51)

Patches: wct1xxp_pci.diff uploaded by tzafrir (license 46)
Tested by: klaus3000

------------------------------------------------------------------------

http://svn.digium.com/view/dahdi?view=rev&revision=5118