[asterisk-users] MeetMe Conference on Asterisk-1.4.13

[GNUbie]

Hello Tzafrir,

On Dec 3, 2007 11:01 PM, Tzafrir Cohen <tzafrir.cohen at xorcom.com> wrote:

>
> Interesting. That explains why depmod was not run at package install
> time. So the next question is: why is that file missing? Do you have
> any guess?


It is because this is on the Xen domU where it only uses the kernel of the
Xen dom0 to boot and everything.  Xen domU is an unprivileged domain or a
guest OS and Xen dom0 stands for domain 0 or the host OS for the Xen domU.

Anyway, I just tried depmod'ing and modprobe'ing once again and I got the
following errors:

# depmod -a
# modprobe ztdummy
Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.4.5.1
Zaptel Echo Canceller: MG2
ztdummy: RTC rate is 1024
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at kernel/timer.c:200
invalid opcode: 0000 [1] SMP
CPU 0
Modules linked in: ztdummy zaptel crc_ccitt ipv6 ipt_TOS xt_multiport
xt_tcpudp iptable_nat xt_limit xt_state ipt_LOG ipt_recent iptable_mangle
ipt_ULOG iptable_filter ip_tables x_tables ip_conntrack_ftp ip_nat_irc
ip_nat ip_conntrack_irc ip_conntrack nfnetlink evdev pcspkr 8250 serial_core
ext3 jbd mbcache dm_mirror dm_snapshot dm_mod
Pid: 18746, comm: modprobe Not tainted 2.6.18-5-xen-amd64 #1
RIP: e030:[<ffffffff8021c71f>]  [<ffffffff8021c71f>] __mod_timer+0x19/0xbf
RSP: e02b:ffff880011393d18  EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffffffff80555280 RCX: 0000000101d011a4
RDX: 00000000000000fa RSI: 0000000101d011a9 RDI: ffffffff80555280
RBP: ffff88001dc1f800 R08: ffffffff80450088 R09: 000000000000001b
R10: 00000000000016ba R11: 0000000000000000 R12: ffff88001131d010
R13: 0000000101d011a9 R14: ffff88001dc1fc20 R15: ffffc200000ac020
FS:  00002b19b92fe6d0(0000) GS:ffffffff804c4000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process modprobe (pid: 18746, threadinfo ffff880011392000, task
ffff88001f67b830)
Stack:  ffff88001131d000  ffff88001dc1f800  0000000000000000
ffff88001dc1f800
 ffff88001131d010  ffffffff88150380  ffff88001dc1fc20  ffffffff8035501a
 ffff880011393d68  ffff880011393de8
Call Trace:
 [<ffffffff8035501a>] rtc_do_ioctl+0x1c5/0x72f
 [<ffffffff88126350>] :zaptel:zt_register+0x156/0x259
 [<ffffffff802946f7>] __link_module+0x0/0x25
 [<ffffffff8025febe>] _spin_lock_irq+0x9/0x14
 [<ffffffff8025e4e9>] wait_for_completion+0xc0/0xc9
 [<ffffffff8814f2bd>] :ztdummy:init_module+0x180/0x208
 [<ffffffff8028a231>] blocking_notifier_call_chain+0x2d/0x36
 [<ffffffff80296deb>] sys_init_module+0x16cc/0x1882
 [<ffffffff8025bdba>] system_call+0x86/0x8b
 [<ffffffff8025bd34>] system_call+0x0/0x8b


Code: 0f 0b 68 62 a2 40 80 c2 c8 00 48 8d 74 24 08 48 89 df 45 31
RIP  [<ffffffff8021c71f>] __mod_timer+0x19/0xbf
 RSP <ffff880011393d18>
 Segmentation fault

#
Message from syslogd at pbx at Tue Dec  4 02:12:41 2007 ...
pbx kernel: invalid opcode: 0000 [1] SMP


Any idea about the above output?

Regards,

GNUbie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20071204/026114fa/attachment.htm