From: Benjamin Herrenschmidt <bh40@calva.net>
To: <costabel@wanadoo.fr>, Paul Mackerras <paulus@linuxcare.com>,
Linux -Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: success 2.4.0-test8 with latest bk
Date: Wed, 13 Sep 2000 14:47:00 +0200 [thread overview]
Message-ID: <20000913124700.2558@mailhost.mipsys.com> (raw)
In-Reply-To: <39BF773E.A5A3D298@univ-rennes1.fr>
>> > 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.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-13 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-12 20:49 success 2.4.0-test8 with latest bk Andreas Tobler
2000-09-12 21:11 ` Martin Costabel
2000-09-12 22:14 ` Geert Uytterhoeven
2000-09-13 12:45 ` Benjamin Herrenschmidt
2000-09-13 12:46 ` Martin Costabel
2000-09-13 12:47 ` Benjamin Herrenschmidt [this message]
2000-09-13 12:58 ` Michel Dänzer
2000-09-13 20:25 ` Michel Lanners
2000-09-13 21:20 ` Martin Costabel
2000-09-14 1:13 ` Takashi Oe
2000-09-14 3:38 ` Paul Mackerras
2000-09-14 6:50 ` Takashi Oe
2000-09-17 5:32 ` Troy Benjegerdes
-- strict thread matches above, loose matches on Subject: below --
2000-09-13 15:56 Iain Sandoe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000913124700.2558@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).