Problem with Elastix as xen parvirtualized domu

Discussion in 'General' started by vitsoft, May 20, 2009.

  1. vitsoft

    Joined:
    Jun 5, 2007
    Messages:
    13
    Likes Received:
    1
    I installed elastix latest release on a xen paravirtualized domu using ks_xen.cfg.

    During the installation all was fine, but when finished and he machine reboot I was not more able to start it.

    I discover that the kernel panic when try to load dahdi, this is the console log :

    audit(1242825369.755:2): selinux=0 auid=4294967295 ses=4294967295
    rxt1: no version for "dahdi_hdlc_putbuf" found: kernel tainted.
    ----------- [cut here ] --------- [please bite here ] ---------
    Kernel BUG at kernel/timer.c:331
    invalid opcode: 0000 [1] SMP
    last sysfs file: /class/dahdi/dahdi!transcode/dev
    CPU 0
    Modules linked in: dahdi_dummy(U) rcbfx(FU) r1t1(FU) rxt1(FU) xpp_usb(U) xpp(U) wctc4xxp(U) dahdi_transcode(U) wcb4xxp(U) wctdm(U) wcfxo(U) wctdm24xxp(U) wcte11xp(U) wct1xxp(U) wcte12xp(U) wct4xxp(U) dahdi(U) crc_ccitt sunrpc xennet dm_mirror dm_multipath dm_mod parport_pc lp parport pcspkr xenblk ext3 jbd uhci_hcd ohci_hcd ehci_hcd
    Pid: 1559, comm: modprobe Tainted: GF 2.6.18-92.1.22.el5xen #1
    RIP: e030:[<ffffffff8021c9fb>] [<ffffffff8021c9fb>] __mod_timer+0x19/0xbe
    RSP: e02b:ffff88003bd39e18 EFLAGS: 00010046
    RAX: 0000000000000000 RBX: ffffffff806b9320 RCX: 00000000ffff34c5
    RDX: 00000000000000fa RSI: 00000000ffff34ca RDI: ffffffff806b9320
    RBP: ffff88003d6f3000 R08: ffffffff804dd7a8 R09: 0000000000001b08
    R10: 0000000000000000 R11: 0000000000000000 R12: 000000000002e778
    R13: 00000000ffff34ca R14: 00000000159910f8 R15: 00002af1f37e7010
    FS: 00002af1f3d346e0(0000) GS:ffffffff805b0000(0000) knlGS:0000000000000000
    CS: e033 DS: 0000 ES: 0000
    Process modprobe (pid: 1559, threadinfo ffff88003bd38000, task ffff88003e821100)
    Stack: 000000000002e778 00002af1f37e7010 0000000000000000 ffff88003d6f3000
    000000000002e778 00002af1f37e7010 00000000159910f8 ffffffff8038e631
    ffff88003d6b6dc0 0000000000000400
    Call Trace:
    [<ffffffff8038e631>] rtc_do_ioctl+0x1c5/0x701
    [<ffffffff802f222b>] proc_register+0x7d/0x115
    [<ffffffff802f26bd>] create_proc_entry+0x90/0xa5
    [<ffffffff8814c333>] :dahdi:dahdi_register+0x1a3/0x2ca
    [<ffffffff88368318>] :dahdi_dummy:init_module+0x1db/0x257
    [<ffffffff802a19b4>] sys_init_module+0xaf/0x1e8
    [<ffffffff802602f9>] tracesys+0xab/0xb6


    Code: 0f 0b 68 ab 3c 48 80 c2 4b 01 48 8d 74 24 08 48 89 df 45 31
    RIP [<ffffffff8021c9fb>] __mod_timer+0x19/0xbe
    RSP <ffff88003bd39e18>
    <0>Kernel panic - not syncing: Fatal exception


    Any help ??
    I use the x86_64 release.

    Thanks
     
  2. rafael

    Joined:
    May 14, 2007
    Messages:
    1,454
    Likes Received:
    1
    Hi vitsoft,

    It seems to be a bug, so I reported in the Elastix bug track system. The best thing you can do to help us resolv this issue is give feedback to the bug report. So please follow this link, register and help us help you ;)

    http://bugs.elastix.org/view.php?id=98

    Good to see you here and hope to see you around mor often.


    Best Regards,

    Rafael
     
  3. theSecret

    Joined:
    May 21, 2009
    Messages:
    1
    Likes Received:
    0
    hello vitsoft,


    this is a problem with XEN that is not providing RTC Services.

    you have to patch the dadhi sources if you will run Elastix under XEN or KVM.

    Check the following link for detailed instructions.
     
  4. vitsoft

    Joined:
    Jun 5, 2007
    Messages:
    13
    Likes Received:
    1
    The biggest problem is the centos kernel.

    I am the responsable for the network:telephony repository for opensuse and dahdi don't crash the kernel, but the dahdi_dummy module cannot be loaded for some unresolved symbol (rtc).

    I suggest to include in the rpm of dahdi this official patch from digium :


    Patch03

    so we can use elastix on a paravirtuaiized domu.

    P.S.
    This is not needed if you use Full Virtualization I have a machine running elastix with 1 year uptime.
     
  5. damianmora

    Joined:
    Apr 19, 2008
    Messages:
    1
    Likes Received:
    0
    (0000323)
    a_villacis (developer)
    2009-05-20 11:44

    This is a known issue. There is an updated dahdi module that fixes the issue, but it has not yet been included in the Elastix ISO. You can try using GRUB to boot into runlevel 1 (to avoid loading the faulty dahdi), then manually start the network with "service network start", then use yum update to get the updated dahdi modules. After yum updates the kernel modules, you should be able to boot the system normally.
     
  6. vitsoft

    Joined:
    Jun 5, 2007
    Messages:
    13
    Likes Received:
    1
    Thanks to all.
    I solve it using kpartx and then disabling dahdi start.

    The machine come up and then I was able to update the system.

    All work fine now.
     
  7. ramoncio

    Joined:
    May 12, 2010
    Messages:
    1,663
    Likes Received:
    0
    You can also modify the sources. Comment the USE_RTC line in dahdi-dummy.c with //
     

Share This Page