From: antoine <an...@na...> - 2005-06-02 23:26:55
|
Thanks, almost all applied cleanly - I skipped the s390 ones for now. Compiling still requires a `touch arch/um/sys-x86_64/.stub_segv.o.d` to make it proceed. Works for me! (tm) But I can't get it to boot into init properly, I can only boot with init=/bin/bash. (then remount root rw, mount proc) Every time I run a command, I get something like: bash: child setpgid (15484 to 15484): No such process (I remember seeing this one before - but I can't remember the solution :-( I can bring the network up manually (ifconfig) and ping (in and out), but running any of the /etc/init.d/ scripts locks up, same goes for starting sshd or even "Hello World" in hello.sh Sometimes when it goes into a spin, it loos on this (to infinity): "[42949450.500000] fix_range_common: failed, killing current process" Not sure where do go from here... Maybe patching with just the minimum? It needs roughly at least up to fix-tt-USR1-handlers to be able to boot (otherwise you get the error I posted yesterday). Antoine On Thu, 2005-06-02 at 17:06 -0400, Jeff Dike wrote: > On Thu, Jun 02, 2005 at 06:51:22AM +0100, antoine wrote: > > I applied the patches on the website to 2.6.12-rc5 (mm1 and mm2: most > > patches apply cleanly to both, some have been merged in mm2 obviously), > > I got an error here: > > I pushed out a fixed set of patches (against -mm2) that work for me. > > There were some include changes in stub_segv.c. > > The .d file thing is still there. That seems to have been caused by my > changing stub_segv.c to a userspace file. > > Jeff |