Hello dan

By loosing context i want to say :

when it's ok :
srvweb:/var/log# vserver-stat
CTX   PROC    VSZ    RSS  userTIME   sysTIME    UPTIME NAME
0       82 986.7M 220.4M   4m15s84   1m41s00   2h49m11 root server
20      18 424.1M 117.1M   0m10s24   0m01s12   2h48m00 vweb1
21      15 729.1M   107M   0m02s70   0m01s10   2h05m32 vweb2
22      10  63.6M  22.4M   0m00s50   0m00s50   2h05m14 vweb3

when it loose context :
srvweb:/var/log# vserver-stat
CTX   PROC    VSZ    RSS  userTIME   sysTIME    UPTIME NAME
0       82 986.7M 220.4M   4m15s84   1m41s00   2h49m11 root server
20      18 424.1M 117.1M   0m10s24   0m01s12   2h48m00
21      15 729.1M   107M   0m02s70   0m01s10   2h05m32
22      10  63.6M  22.4M   0m00s50   0m00s50   2h05m14

And of course(?) i can't enter anymore in the vserver when it doesn't appear
in vserver-stat. But the processes attached to this vserver continue to run.

This morning Bertl told me to launch testme.sh : the result is ok.
srvweb:/usr/local# ./testme.sh
Linux-VServer Test [V0.16] Copyright (C) 2003-2006 H.Poetzl
chcontext is working.
chbind is working.
Linux 2.6.19-vs2.1.1.4 #2 SMP Sat Dec 9 11:42:13 CET 2006 i686
Ea 0.30.212 273/glibc (DSa) <compat,v11,fscompat,v13,net,v21,oldproc,olduts>
VCI: 0002:0102 273 03000416 (TbLgnP)
---
[000]# succeeded.
[001]# succeeded.
[011]# succeeded.
[031]# succeeded.
[101]# succeeded.
[102]# succeeded.
[201]# succeeded.
[202]# succeeded.

I've REcompiled  util-vservers-0.30.212-rc5 with enable-apis=NOLEGACY. It
works for the moment.... In the previous compil i had left the default
available apis :
v13,net,v21.

srvweb:/usr/local# vserver-info
Versions:
                   Kernel: 2.6.19-vs2.1.1.4
                   VS-API: 0x00020102
             util-vserver: 0.30.212-rc5; Dec  9 2006, 12:38:30

Features:
                       CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
                      CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-13)
                 CPPFLAGS: ''
                   CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W'
                 CXXFLAGS:
'-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0'
               build/host: i686-pc-linux-gnu/i686-pc-linux-gnu
             Use dietlibc: yes
       Build C++ programs: yes
       Build C99 programs: yes
           Available APIs: compat,v11,fscompat,v13,net,v21,oldproc,olduts
            ext2fs Source: e2fsprogs
    syscall(2) invocation: alternative
      vserver(2) syscall#: 273/glibc

Paths:
                   prefix: /usr/local
        sysconf-Directory: ${prefix}/etc
            cfg-Directory: ${prefix}/etc/vservers
         initrd-Directory: $(sysconfdir)/init.d
       pkgstate-Directory: ${prefix}/var/run/vservers
          vserver-Rootdir: /vservers

Patrick


----- Original Message ----- 
From: "Daniel Hokka Zakrisson" <[EMAIL PROTECTED]>
To: <vserver@list.linux-vserver.org>
Sent: Saturday, December 09, 2006 1:52 PM
Subject: Re: [Vserver] Bug again on 2.6.19


> [EMAIL PROTECTED] wrote:
> > Hello all
> >
> > I try util-vservers-0.30.212-rc5 with patch-vs-2.1.1.4.diff on kernel
2.6.19
> > :
> >
> > And a few minutes later after starting vservers, i loose their context
and
> > got this message in syslog :
>
> "Lose their context"? What does that mean exactly?
>
> > Dec  9 11:15:34 srvweb kernel: BUG: warning at
> > kernel/vserver/proc.c:398/proc_vx_info_read()
> > Dec  9 11:15:34 srvweb kernel:  [dump_trace+107/417]
dump_trace+0x6b/0x1a1
> > Dec  9 11:15:34 srvweb kernel:  [show_trace_log_lvl+23/43]
> > show_trace_log_lvl+0x17/0x2b
> > Dec  9 11:15:34 srvweb kernel:  [__func__.0+3843/287512] 0xc0326c7b
> > Dec  9 11:15:34 srvweb kernel: DWARF2 unwinder stuck at 0xc0326c7b
> > Dec  9 11:15:34 srvweb kernel:
> > Dec  9 11:15:34 srvweb kernel: Leftover inexact backtrace:
> > Dec  9 11:15:34 srvweb kernel:
> > Dec  9 11:15:34 srvweb kernel:  [show_trace+15/17] show_trace+0xf/0x11
> > Dec  9 11:15:34 srvweb kernel:  [dump_stack+19/21] dump_stack+0x13/0x15
> > Dec  9 11:15:34 srvweb kernel:  [proc_vx_info_read+90/222]
> > proc_vx_info_read+0x5a/0xde
> > Dec  9 11:15:34 srvweb kernel:  [vfs_read+138/308] vfs_read+0x8a/0x134
> > Dec  9 11:15:34 srvweb kernel:  [sys_read+65/103] sys_read+0x41/0x67
> > Dec  9 11:15:34 srvweb kernel:  [sysenter_past_esp+86/121]
> > sysenter_past_esp+0x56/0x79
> > Dec  9 11:15:34 srvweb kernel:  [__xfrm_state_bump_genids+83/339]
> > __xfrm_state_bump_genids+0x53/0x153
> > Dec  9 11:15:34 srvweb kernel:  =======================
>
> This is probably a race in the proc-code that we haven't been able to
> track down yet, but if you have a sure-fire way to reproduce it, that
> would help a lot.
>
> -- 
> Daniel Hokka Zakrisson
> GPG id: 06723412
> GPG fingerprint: A455 4DF3 990A 431F FECA  7947 6136 DDA2 0672 3412
> _______________________________________________
> 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

Reply via email to