On Mon, 2006-08-14 at 06:11 +0200, Herbert Poetzl wrote:
> > I tried to run 220.127.116.11 with the 2.0.2-rc28 patch from
> > vserver.13thfloor.at/Experimental but it oopsed when starting init
> > (and it didn't go on anymore after that), 18.104.22.168 with the 2.0.2-rc26
> > patch worked fine (which was for 22.214.171.124 but only makefile had to be
> > adjusted).
> hmm? would be nice to get a view on the oops
> (i.e. either capture it with a serial console, or
> if that is not possible, take a picture or transcribe
> the text)
> > Perhaps it's something obvious... I'm doing this inside vmware.
> could be, we won't know without the oops :)
I figured, but at that moment I was on holidays - couldn't resist to set
something up on a virtual machine I was offered though ;)
I'm back now, here's the oops:
I don't know if there was something above it, it happens quite fast - if
you can tell me how to get a larger console (80x50 or so) I could try
It's an oops, not a panic, but as you can see Init "starts" but doesn't
do anything anymore after that. It's plain 126.96.36.199 patched with the
available 188.8.131.52 patch.
> > Kernel config available on request, perhaps even the kernel log (if
> > needed, but then I'll need to reboot into the new/old kernel) - more
> > info from sid3windr @ #vserver as well...
> okay, will look into it then ...
Vserver mailing list
Received on Thu Aug 17 12:44:18 2006