On Thursday 23 November 2006 18:49, Herbert Poetzl wrote:
> On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote:
> > On Wed, Nov 22, 2006 at 01:28:42PM +0100, Andreas Baetz wrote:
> > > Because of the CPU scheduling problems I have with 2.6.18.2 and vserver 
> > > vs2.0.2.2-rc6 I tried
> > > 2.6.18.3 and vs2.0.2.2-rc7.
> > > The patch applied cleanly to a vanilla kernel.
> > > The kernel compiled ok.
> > > After booting I tried "vserver deb4 start", that failed and I got
> > > 
> > > kernel BUG at kernel/vserver/network.c:147!
> > >  host kernel: invalid opcode: 0000 [#2]
> > >  host kernel: PREEMPT 
> > >  host kernel: CPU:    0
> > >  host kernel: EIP is at unhash_nx_info+0x6e/0x90
> > >  host kernel: eax: 00000100   ebx: f6c7eee0   ecx: 00000001   edx: 
> > > e8326000
> > >  host kernel: esi: e824ba90   edi: 00000010   ebp: c17efa90   esp: 
> > > e8327f64
> > >  host kernel: ds: 007b   es: 007b   ss: 0068
> > >  host kernel: Process chbind (pid: 4168[#0], ti=e8326000 task=e824ba90 
> > > task.ti=e8326000)
> > >  host kernel: Stack: f6c7eee0 00000004 e8327f9c c012296e f6c7eee0 
> > > 0000ff00 00000000 e8f1da40 
> > >  host kernel: e8327f9c e824bb48 e824bb80 0000ff00 e8f1da40 e824bb48 
> > > e8327f9c e8327f9c 
> > >  host kernel: 000000ff 00000000 0401a8c0 e8326000 c0122a4d c01031e1 
> > > 000000ff 0804c81b 
> > >  host kernel: Call Trace:
> > >  host kernel: Code: 04 c7 03 00 01 10 00 c7 43 04 00 02 20 00 b8 01 00 00 
> > > 00 e8 e5 ed fd ff 89 e0 25 00 e0 ff ff 8b 40 08 a8 08 75 0f 83 c4 08 5b 
> > > c3 <0f> 0b 93 00 1f 5a 43 c0 eb b8 83 c4 08 5b e9 5f 54 2c 00 eb 0d 
> > >  host kernel: EIP: [<c013aebe>] unhash_nx_info+0x6e/0x90 SS:ESP 
> > > 0068:e8327f64
> > > 
> > > I'm back to 2.6.18.2 now.
> > 
> > thanks, should be fixed in the next release 
> 
> vs2.0.2.2-rc8 is out ...

I tried vs2.0.2.2-rc8 with 2.6.18.3, the vserver starts ok, no errors, but when 
I stopped it, the whole system freezed.
Right after "Deconfiguring network interfaces...done."
Nothing worked besides magic sysreq-boot.
Nothing in the syslog. Didn't try a second time due to lack of time.

Andreas


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************

_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to