On Tue, Oct 04, 2005 at 03:31:54PM -0400, Chuck wrote:
> i just tried doing a reboot on the host letting it stop all vservers itself.
> this is what happened:
I would really like to investigate this, maybe
you could try to catch me on the channel ...
this is a trace which is not supposed to happen
(i.e. an assertion which failed) so it is a good
indication for a kernel bug ...
TIA,
Herbert
> * Remounting remaining filesystems readonly ...------------[ cut
> here ]------------
> kernel BUG at kernel/vserver/context.c:144!
> invalid operand: 0000 [#1]
> SMP
> Modules linked in:
> CPU: 0
> EIP: 0060:[<c0136cb0>] Not tainted VLI
> EFLAGS: 00010246 (2.6.13.1-vs2.1.0-rc2)
> EIP is at free_vx_info+0x70/0x80
> eax: 00000001 ebx: f7d9b080 ecx: f6f5cec0 edx: f666e000
> esi: e316b4fc edi: 00000400 ebp: 00000000 esp: e37d3e50
> ds: 007b es: 007b ss: 0068
> Process mount (pid: 31028, threadinfo=e37d2000 task=e2a5fa80)
> Stack: c011ae58 f666e000 c019a550 e316b4fc c019a5cb f7d9b080 e316b4fc c019a550
> c0182f33 e316b4fc c019a550 c024ada1 e316b4fc e316b4fc c01831b3 e316b4fc
> c0414a94 f4d7c53c c017ff81 e316b4fc e316b4fc 00000000 00000000 f4d7c53c
> Call Trace:
> [<c011ae58>] free_task+0x78/0x80
> [<c019a550>] proc_delete_inode+0x0/0x80
> [<c019a5cb>] proc_delete_inode+0x7b/0x80
> [<c019a550>] proc_delete_inode+0x0/0x80
> [<c0182f33>] generic_delete_inode+0x73/0x100
> [<c019a550>] proc_delete_inode+0x0/0x80
> [<c024ada1>] _atomic_dec_and_lock+0x31/0x50
> [<c01831b3>] iput+0x63/0x90
> [<c017ff81>] dput+0x151/0x1f0
> [<c018063a>] shrink_dcache_sb+0x18a/0x1f0
> [<c016dde5>] do_remount_sb+0x35/0x100
> [<c0185a2d>] do_remount+0xad/0x120
> [<c01864dd>] do_mount+0x21d/0x230
> [<c0186263>] copy_mount_options+0x63/0xc0
> [<c01868ef>] sys_mount+0x9f/0xe0
> [<c0102ff9>] syscall_call+0x7/0xb
> Code: ce b0 3b c0 eb dc f6 42 18 01 74 cf 0f 0b 95 00 ce b0 3b c0 eb c5 0f 0b
> 93 00 ce b0 3b c0 eb b7 0f 0b 92 00 ce b0 3b c0 eb a6 90 <0f> 0b 90 00 ce b0
> 3b c0 eb 94 8d b6 00 00 00 00 57 56 53 83 ec
> /etc/init.d/halt.sh: line 196: 31028 Segmentation fault mount -n -o
> remount,ro "${x}" >&/dev/null
>
>
>
> at this point it will hang forever until i power cycle it.
>
> the last line usually means there was a problem in a guest
>
> --
>
> Chuck
>
>
>
> _______________________________________________
> Vserver mailing list
> [email protected]
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver
