From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Tue 18 Nov 2003 - 13:20:55 GMT
On Tue, Nov 18, 2003 at 08:46:34AM -0400, James MacLean wrote:
> Hi Dariush,
> Old vserver for me is fine (2.4.22 + c17). Wanted to make up a new kernel,
> saw this new branch of Vserver with 2.4.23-rc1 patches ready to go, so
> went that route :).
> I also patched in/ turned on the realtime kernel. It patched clean, but
> hey, who knows ;(. But the Oops suggests it's network.
I really would appreciate if you could test the following:
take a 2.4.23-rc1 as you patched it, _without_ the RT stuff
(vanilla + vserver patch only)
and a 2.4.22 with vs1.00 with the RT stuff
and try to crash it ... the oops would be nice, but
the fact that it crashes/don't crash is valuable info
> On Tue, 18 Nov 2003, Dariush Pietrzak wrote:
> > > experience need only do a "netstat -nap --inet" from the root server when
> > > a vserver it alive... Or atleast, that is all that I do :).
> > Sorry, I haven't been following, you get this oops on 2.4.23rc1 with new
> > vserver and with old vserver?
> > I'm putting together 2.4.23rc1 this week, so far I found one easily
> > fixable kernel panic, I'm using ctx17e, netstat -nap --inet works as
> > expected.
> > regards,
> James B. MacLean macleajb_at_ednet.ns.ca
> Department of Education
> Nova Scotia, Canada
> B3M 4B2
> Vserver mailing list
Vserver mailing list