2011/7/26 Konrad Meier <[email protected]>
> I could solve the above problem by a system restart. The mISDN_l1loop
> module was loaded but for some reason could not be used by LCR. The LCR
> error message was:
> 000000 ERROR loop port 1 failed to bind socket. (errno 93)
>
>
> By playing with the mISDN_l1loop module I discovered a strange problem. If
> I load the module with "modprobe mISDN_l1loop pri=1 nchannel=30" all system
> memory is allocated by LCR after some seconds.
>
> If I load it with "nchannel=20" than everithing works fine.
>
> Can someone confirm this problem?
>
> Regards
> Konrad
>
>From my experience, no.
My init.d script does the following in short:
modprobe mISDN_dsp
modprobe mISDN_l1loop nchannel=30 interfaces=2
sleep 1
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -s 192.168.253.0/24 -o eth0 -j
MASQUERADE
screen -S bsc -d -m su gsm -c "osmo-nitb -d
DRLL:DCC:DMM:DRR:DRSL:DNM:DSMS:DMNSMS:DPAG:DMUX -c /etc/openbsc/openbsc.cfg
-m -P"
screen -S lcr -d -m su gsm -c "/usr/sbin/lcr start"
I'm using mISDN_l1loop.ko from current mISDN git because it was not included
in my kernel. Small patch to make it compile:
--- a/drivers/isdn/mISDN/hwchannel.c
+++ b/drivers/isdn/mISDN/hwchannel.c
@@ -19,6 +19,8 @@
#include <linux/module.h>
#include <linux/mISDNhw.h>
+bool flush_work_sync (struct work_struct *);
+
static void
dchannel_bh(struct work_struct *ws)
{
-- Lennart
