On Wednesday 06 December 2006 21:50, Herbert Poetzl wrote:
> On Wed, Dec 06, 2006 at 12:11:44PM +0100, Andreas Baetz wrote:
> > > On Tuesday 28 November 2006 15:54, Herbert Poetzl wrote:
> > > > On Tue, Nov 28, 2006 at 08:11:35AM +0100, Andreas Baetz wrote:
> > > > > On Sunday 26 November 2006 23:22, Herbert Poetzl wrote:
> > > > > > On Fri, Nov 24, 2006 at 08:11:39AM +0100, Andreas Baetz wrote:
> > > > > > > On Thursday 23 November 2006 18:49, Herbert Poetzl wrote:
> > > > > > > > On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote:
> > > > > > > > >
> > > > > > > > > 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."
> > > > > >
> > > > > > okay, maybe you get around, the stack trace of
> > > > > > all processes would probably tell us more ...
> > > > > I wrote down some of the trace output by hand:
> > > >
> > > > hmm, the numbers of those dumps would be interesting,
> > > > especially if you have an unstripped kernel (vmlinux)
> > > > available, so we can figure _where_ this happens
> > > >
> > > > so a serial console or some other means of recording
> > > > them would be very helpful, if not available, try
> > > > with a photo camera ...
> > > >
> >
> > some more info:
> > I copied the / of a working vserver and used it as / of deb4.
> > "vserver deb4 stop" now works.
> > It seems that something inside the / of the old deb4 is causing
> > the system to crash when no more processes are running with that xid.
>
> > So if a user of a certain vserver manages to create that condition in
> > a vserver, then ending all processes in that vserver, the user could
> > manage to crash the host.
>
> yes, please try if you can reproduce that with
>
> http://vserver.13thfloor.at/Experimental/patch-2.6.18.5-vs2.1.1.3.diff
>
> if yes, we should have the necessary debugging
> harnish to track that down, if it can't be
> recreated there, consider it already fixed in
> the next stable release ...
>
> TIA,
> Herbert
>
With 2.6.18.5 and patch-2.6.18.5-vs2.1.1.3.diff the bug is gone.
Also, hard CPU scheduling works again.
Great work, many thanks !!!
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
Received on Thu Dec 7 08:37:26 2006