[Asterisk-Dev] modprobe wcfxo causes fc3 box to crash

Alex Litvak alexl at netintegrations.net
Fri Dec 10 16:46:39 MST 2004


Hello everybody,

After going through multiple posts on Internet  and trying different
things I can't seems get zaptel wcfxo loaded on the server correctly.
I run dual P3 500 Mhz box.  After reading README.udev

I put a file 60-zaptel.rules /etc/udev/rules.d

# Section for zaptel device
KERNEL="zapctl",     NAME="zap/ctl"
KERNEL="zaptimer",   NAME="zap/timer"
KERNEL="zapchannel", NAME="zap/channel"
KERNEL="zappseudo",  NAME="zap/pseudo"
KERNEL="zap[0-9]*",  NAME="zap/%n"

In /etc/udev/permissions.d/50-udev.permissions I added:

# zaptel devices
zap/ctl:root:root:0664
zap/timer:root:root:0664
zap/channel:root:root:0664
zap/pseudo:root:root:0664
zap/*:root:root:0644

I then ran make linux26, make install, make config.  I replaced insmod
and rmmod in /etc/init.d/zaptel with modprobe and modprobe -r according
to suggestions made in groups. 
 
When I run modprobe wcfxo I get following:
Notice: Configuration file is /etc/zaptel.conf
line 0: Unable to open master device '/dev/zap/ctl'

1 error(s) detected

FATAL: Error running install command for wcfxo

I see zaptel and wcfxo is loaded if I run lsmod though.  In 1 minute my
box crashes
Rebooting the box and running it again, same thing.

/var/log/messages before crash
Dec 10 17:24:30 conference kernel: Zapata Telephony Interface Registered
on major 196
Dec 10 18:36:03 conference kernel: wcfxo: DAA mode is 'FCC'
Dec 10 18:36:03 conference kernel: Uhhuh. NMI received for unknown
reason 15 on CPU 0.
Dec 10 18:36:03 conference kernel: Dazed and confused, but trying to
continue
Dec 10 18:36:03 conference kernel: Do you have a strange power saving
mode enabled?
Dec 10 18:36:03 conference kernel: Found a Wildcard FXO: Generic Clone
Dec 10 17:24:33 conference udev[4636]: configured rule in
'/etc/udev/rules.d/60-zaptel.rules' at line 4 applied, '
zapchannel' becomes 'zap/channel'
Dec 10 17:24:33 conference udev[4635]: configured rule in
'/etc/udev/rules.d/60-zaptel.rules' at line 3 applied, '
zaptimer' becomes 'zap/timer'
Dec 10 17:24:33 conference udev[4636]: creating device node
'/dev/zap/channel'
Dec 10 17:24:33 conference udev[4635]: creating device node
'/dev/zap/timer'
Dec 10 17:24:33 conference udev[4649]: configured rule in
'/etc/udev/rules.d/60-zaptel.rules' at line 5 applied, '
zappseudo' becomes 'zap/pseudo'
Dec 10 17:24:33 conference udev[4649]: creating device node
'/dev/zap/pseudo'
Dec 10 17:24:33 conference udev[4650]: configured rule in
'/etc/udev/rules.d/60-zaptel.rules' at line 2 applied, '
zapctl' becomes 'zap/ctl'
Dec 10 17:24:33 conference udev[4650]: creating device node
'/dev/zap/ctl'
Dec 10 17:24:33 conference udev[4665]: configured rule in
'/etc/udev/rules.d/60-zaptel.rules' at line 6 applied, '
zap1' becomes 'zap/%n'
Dec 10 17:24:33 conference udev[4665]: creating device node '/dev/zap/1'


After each reboot /dev/zap disappears due to udev dynamic nature I
guess.

I tried to build  zaptel commenting out

ifeq ($(DYNFS),)
else
        @echo "**** Dynamic filesystem detected -- not creating device
nodes"
        @echo "**** If you are running udev, read README.udev"
endif

I see the devices created and can load wcfxpro but server crushes within
less than a minute nevertheless

Has anyone have an idea?  I am ready to give up on FC3 although I wonder
of the hardware has anything to do with my problem.

Thanks in Advance,

Alex


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20041210/7fd01998/attachment.htm


More information about the asterisk-dev mailing list