Re: [Vserver] Kernel BUG at kernel/exit.c:676

From: Herbert Poetzl <herbert_at_13thfloor.at>
Date: Mon 01 May 2006 - 04:02:50 BST
Message-ID: <20060501030250.GA14087@MAIL.13thfloor.at>

On Mon, May 01, 2006 at 01:03:47AM +0200, Jan Rekorajski wrote:
> Hi,
> I have serious problem with vserver 2.1.1-rc on SMP systems.
> I don't have UP system to check if it's an SMP-only.
> Kernel is 2.6.16.11, vserver patch 2.1.1-rc17,
>
> I can't run gdb. The following test case will give results as shown
> below:

yep, I can confirm this, it's basically a bad assumption
the following patch makes it a warning until we fix
it in rc19 (by checking for the reaper result)

(only affects init-less guests with debug enabled)

http://vserver.13thfloor.at/Experimental/BAGGINS/delta-reaper-fix01.diff

best,
Herbert

> gdb /bin/ls
> r
>
> and then you will see this:
>
> From the x86-64 machine (4xDC Opteron):
>
> Kernel BUG at kernel/exit.c:676
> invalid opcode: 0000 [1] SMP
> CPU 4
> Modules linked in: vroot nfsd lockd nfs_acl sunrpc ipv6 tg3 ext3 jbd
> mbcache dm_mod 8021q
> Pid: 21617[#100], comm: gdb Not tainted 2.6.16.11 #1
> RIP: 0010:[<ffffffff80132cb5>] <ffffffff80132cb5>{forget_original_parent+437}
> RSP: 0018:ffff8105fa8c5eb8 EFLAGS: 00010002
> RAX: 0000000000000000 RBX: ffff8105cf1a50e8 RCX: 0000000000000078
> RDX: 0000000000000000 RSI: ffff8105fa8c5ef8 RDI: ffff8105cf1a5770
> RBP: ffff81020708d040 R08: 0000000000000000 R09: ffff8105fa8c5ea8
> R10: 0000000000000001 R11: 0000000000000246 R12: ffff8105cf1a5040
> R13: ffff8105cf1a50e8 R14: 0000000000000001 R15: ffff8105cf1a5160
> FS: 00002b03caddebe0(0000) GS:ffff81040709dcc0(0000) knlGS:00000000f7d656c0
> CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
> CR2: 000000000829b574 CR3: 0000000000101000 CR4: 00000000000006e0
> Process gdb (pid: 21617[#100], threadinfo ffff8105fa8c4000, task ffff8105cf1a5040)
> Stack: ffff8105fa8c5ef8 ffff8101ffad2b80 ffff8105cf1a5040 ffff8105fa8c5ef8
> 0000000000000000 0000000000000001 0000000000000000 ffffffff80132e06
> ffff8105fa8c5ef8 ffff8105fa8c5ef8
> Call Trace: <ffffffff80132e06>{exit_notify+246} <ffffffff801333ff>{do_exit+1023}
> <ffffffff8013358c>{do_group_exit+220} <ffffffff8011e084>{cstar_do_call+27}
>
> Code: 0f 0b 68 91 58 36 80 c2 a4 02 90 48 39 ef 74 0a 48 83 bd e0
> RIP <ffffffff80132cb5>{forget_original_parent+437} RSP <ffff8105fa8c5eb8>
> <1>Fixing recursive fault but reboot is needed!
>
> From the 2xPentiumMMX:
>
> kernel BUG at kernel/exit.c:676!
> invalid opcode: 0000 [#1]
> SMP
> CPU: 0
> EIP is at forget_original_parent+0x121/0x200
> eax: 00000000 ebx: ca8a8b20 ecx: 00000000 edx: ca8a8ab0
> esi: ca8a8098 edi: c12b9ab0 ebp: ca8a8098 esp: c5465f48
> ds: 007b es: 007b ss: 0068
> Process gdb (pid: 6053[#100], threadinfo=c5464000 task=ca8a8030)
> Stack: <0>ca8a80dc c5465f6c ca8a8030 ca8a8030 c5465f6c 00000000 c0121c62 ca8a8030
> c5465f6c c5465f6c c5465f6c ca8a8030 c9d1c4c0 c9d1c4c0 00000000 c012215e
> ca8a8030 ca8a8030 00000001 cbb8fe60 c5464000 00000000 c5464000 c012237d
> Call Trace:
> [<c0121c62>] exit_notify+0x32/0x2e0
> [<c012215e>] do_exit+0x24e/0x400
> [<c012237d>] do_group_exit+0x2d/0x90
> [<c0102b99>] syscall_call+0x7/0xb
> Code: 00 89 eb 6a 01 8b 44 24 20 50 52 e8
> 5a fd ff ff 8b 6d 00 83 c4 0c 39 f3 75 c3 59 5b 5b 5e 5f 5d c3 0f 0b 27
> 02 08 3c 2f c0 eb d0 <0f> 0b a4 02 08 3c 2f c0 eb b9 83 be 84 00 00 00
> 10 75 83 83 be
>
> Jan
> --
> Jan R?korajski | ALL SUSPECTS ARE GUILTY. PERIOD!
> baggins<at>mimuw.edu.pl | OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
> BOFH, MANIAC | -- TROOPS by Kevin Rubio
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Mon May 1 04:19:20 2006

[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Mon 01 May 2006 - 04:19:25 BST by hypermail 2.1.8