From: Paul W. <pd...@ro...> - 2003-10-02 17:18:53
|
Patrick, thank-you for the reply, and the translation. My current host kernel is '2.4.21-0.13mdk' with the skas3 patch applied. Mandrake has 2.4.21-0.18 and 2.4.21-0.25 versions available. I think that I have to remember why I used the -0.13mdk version, it may have had to do with the version of the skas patch it matched to, alternatively it may have been laziness since the source was already on my download CD. In any case it looks like I'm going to have to download a new kernel (maybe from kernel.org), and wait a few hours for everything to compile (ancient PII laptop -- very slow turnaround on kernel compiles). Patrick "Petschge" Kilian wrote: >Hi, > >Paul Wujek wrote: > > >>Google gave me one reference to this error message, but unfortunately it >>is in the German UML-HowTo: >> >> http://www.mathematik.uni-marburg.de/~odb/usermodelinux-howto.html >> >>Because I don't know German I can't tell whether it applies to my >>situation, or offers a resolution. >> >> > >I didn't investigate your problem, the following is from my lecture of the >above mentioned url. > >The document talks about 2.2.25 and 2.4.21 _host_ kernels with distribution >dependand patches for the ptrace bug. These "fixes" seem to be able to >trigger the error you are encountering. There seem to be 4 possible ways to >get rid of the error. > >1.) Upgrade to a newer host kernel and hope that your vendor got it right >this time. >2.) Use a kernel from kernel.org and (dependand of the version) life with >the ptrace bug. >3.) Modify the file mm/proc_mm.c of the _host_ kernel and recompile it. > > --- linux-2.4.21-pre7/mm/proc_mm.c.orig 2003-04-16 16:11:52.000000000 +0200 >+++ linux-2.4.21-pre7/mm/proc_mm.c 2003-04-16 16:17:03.000000000 +0200 >@@ -116,6 +116,7 @@ >if(ret) >goto out_free; > >+ mm->dumpable = 1; >spin_lock(&mmlist_lock); >list_add(&mm->mmlist, ¤t->mm->mmlist); >mmlist_nr++; > >4.) Use skas4 patch as soon as it is availible and patch your host kernel >using this new skas patch. > >IMHO upgrading to a knew host kernel using sources from kernel.org seems to >be the cleanest solution. > > > >>Does anyone have a suggestion as to what could cause this, or how to >>track it down? >> >> >How about stating the source and verion of your host kernel? > >HTH, >Patrick "Petschge" Kilian > > > -- Paul Wujek home: (905) 279-5885 cell: (416) 892-5885 email: pd...@ro... IM msn: pdwxp2 yahoo: paulwujek jabber: paul_wujek/nureality.ca |