On Tue, May 13, 2008 at 7:51 PM, Joseph L. Casale
<JCasale at activenetwerx.com> wrote:> I was just following the wiki and installing Zaptel under my CentOS 5.1 Xen
DomU
> and after starting the service, the vm crashed. Now when restarting it, I
get the following.
> Any ideas?
>
> Thanks!
> jlc
>
>
> Kernel BUG at kernel/timer.c:331
> invalid opcode: 0000 [1] SMP
> last sysfs file: /class/zaptel/zapctl/dev
> CPU 0
> Modules linked in: ztdummy(U) xpp_usb(U) xpp(U) wcusb(U) wctdm(U) wcfxo(U)
wctdm24xxp(U) wcte11xp(U) wct1xxp(U) wcte12xp(U) wct4xxp(U) tor2(U) zaptel(U)
crc_ccitt dm_multipath parport_pc lp parport pcspkr dm_snapshot dm_zero
dm_mirror dm_mod xenblk ext3 jbd ehci_hcd ohci_hcd uhci_hcd
> Pid: 853, comm: modprobe Not tainted 2.6.18-53.1.19.el5xen #1
> RIP: e030:[<ffffffff8021c055>] [<ffffffff8021c055>]
__mod_timer+0x19/0xbe
> RSP: e02b:ffff88000dbadd18 EFLAGS: 00010046
> RAX: 0000000000000000 RBX: ffffffff806992a0 RCX: 00000000fffef0d7
> RDX: 00000000000000fa RSI: 00000000fffef0dc RDI: ffffffff806992a0
> RBP: ffff88000de5c000 R08: 00000000ffffffff R09: 0000000000000020
> R10: 0000000000000000 R11: 0000000000000000 R12: ffff88000d3ed000
> R13: 00000000fffef0dc R14: ffffffff882a5580 R15: ffffc20000077940
> FS: 00002aaaaaabe240(0000) GS:ffffffff80599000(0000)
knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000
> Process modprobe (pid: 853, threadinfo ffff88000dbac000, task
ffff88000f8d4100)
> Stack: ffff88000d3ed000 ffff88000d3ed470 0000000000000000
ffff88000de5c000
> ffff88000d3ed000 ffff88000d3ed470 ffffffff882a5580 ffffffff803847a7
> ffff88000dbaddef 0000000000000400
> Call Trace:
> [<ffffffff803847a7>] rtc_do_ioctl+0x1c5/0x701
> [<ffffffff88121aab>] :zaptel:zt_register+0x156/0x25b
> [<ffffffff80282ca0>] __cond_resched+0x1c/0x44
> [<ffffffff8026187d>] _spin_lock_irq+0x9/0x14
> [<ffffffff8025ff21>] wait_for_completion+0xa1/0xaa
> [<ffffffff882a4301>] :ztdummy:init_module+0x1c4/0x24b
> [<ffffffff8028e9a9>] blocking_notifier_call_chain+0x2d/0x36
> [<ffffffff8029b716>] sys_init_module+0x16a6/0x1857
> [<ffffffff8025d102>] system_call+0x86/0x8b
> [<ffffffff8025d07c>] system_call+0x0/0x8b
>
>
> Code: 0f 0b 68 5d 21 47 80 c2 4b 01 48 8d 74 24 08 48 89 df 45 31
> RIP [<ffffffff8021c055>] __mod_timer+0x19/0xbe
> RSP <ffff88000dbadd18>
> <0>Kernel panic - not syncing: Fatal exception
>
This looks like it may be your problem. http://bugs.digium.com/view.php?id=9592
(0070069)
qwell - administrator
09-06-07 17:05
Closing.
The simple solution here is to just comment out the #define USE_RTC in
ztdummy.c. The ztxen module does not appear to be needed.
Thanks,
Steve Totaro