This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Kernel Bug asterisk

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Kernel Bug asterisk
From: Jason <xen@xxxxxxxxxxxxxxxxx>
Date: Mon, 8 May 2006 01:37:55 -0500 (CDT)
Delivery-date: Mon, 08 May 2006 01:54:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: Jason <xen@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hey guys. I just compiled zaptel ver 1.2.5 into a DomU on xen 3.0.1 unstable and got a kernel bug message after I modprobe ztdummy.
The zaptel module inserts just fine, but ztdummy causes this message. I have
RTC enabled in this kernel and my timing source set to 1000.

------------[ cut here ]------------
kernel BUG at kernel/timer.c:212!
invalid opcode: 0000 [#1]
Modules linked in: ztdummy zaptel
CPU:    0
EIP:    0061:[<c01224c3>]    Not tainted VLI
EFLAGS: 00010046   (2.6.16-xenU #16)
EIP is at __mod_timer+0x83/0xa0
eax: 00000000   ebx: c04ec250   ecx: fbfef000   edx: 00000000
esi: 00000000   edi: 00000001   ebp: ccf33e70   esp: ccf33e5c
ds: 007b   es: 007b   ss: 0069
Process modprobe (pid: 1422, threadinfo=ccf32000 task=c13b7570)
Stack: <0>ccf33e60 00000000 cf6888c0 00000000 00000000 ccf33f4c c0232d15
       00054f56 00000000 00000000 c01896c2 c04e3890 00000000 ccf33e98 00000412
       ccf33eac c0189990 00008000 cf6888c0 ccf33ecc c0189d9f cf6883c0 cf6888c0
Call Trace:
 [<c010512a>] show_stack_log_lvl+0xaa/0xe0
 [<c010533e>] show_registers+0x18e/0x210
 [<c0105539>] die+0xd9/0x180
 [<c0105669>] do_trap+0x89/0xd0
 [<c01059e8>] do_invalid_op+0xb8/0xd0
 [<c0104d4f>] error_code+0x2b/0x30
 [<c0232d15>] rtc_do_ioctl+0x7c5/0xa40
 [<c0233347>] rtc_control+0x67/0xb0
 [<d103519d>] init_module+0x19d/0x210 [ztdummy]
 [<c0134eb5>] sys_init_module+0x135/0x1c0
 [<c0104bd9>] syscall_call+0x7/0xb
Code: 08 89 5c 24 04 89 14 24 e8 2b fe ff ff 8b 45 f4 8b 0d 3c 40 42 c0 84 c0
88 41 01 75 05 80 39 00 75 17 83 c4 0c 89 f0 5b 5e 5d c3 <0f> 0b d4 00 f3 99 3d
c0 eb 87 89 ca eb c2 e8 ba c7 16 00 eb e2

The place where you made your stand never mattered,
only that you were there... and still on your feet

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>