From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <39BF79DC.D4861C59@relog.ch> Date: Wed, 13 Sep 2000 14:58:04 +0200 From: Michel Dänzer Reply-To: daenzerm@student.ethz.ch MIME-Version: 1.0 To: Benjamin Herrenschmidt CC: costabel@wanadoo.fr, Paul Mackerras , Linux -Dev Subject: Re: success 2.4.0-test8 with latest bk References: <39BF773E.A5A3D298@univ-rennes1.fr> <20000913124700.2558@mailhost.mipsys.com> Content-Type: text/plain; charset=iso-8859-1 Sender: owner-linuxppc-dev@lists.linuxppc.org List-Id: Benjamin Herrenschmidt wrote: > > >> > You are lucky. For me it stops booting after the "freeing unused kernel > >> > memory" line. The one from 2 days ago had 2 days uptime. > >> > >> Usually this means that some function/data is marked __init while it > >must not. > >> Quick verification: #undef __init / #define __init etc. > >> > >> Just wondering: wouldn't it be possible to write some tool to find such > >bugs? > > > >Update: After a recompilation with today's updates, the latest bk kernel > >boots again for me. > > That's not the first time I notice this strange behaviour. I meant, this > happened to me randomly with various bk kernels for monthes. The problem > usually disappeared by itself after either recompiling the entire kernel, > or changing a few unrelated lines of code and then reompiling. That's > weird, I really don't know what can be causing that. Broken dependencies? Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and the DRI project ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/