From: "Michel Dänzer" <michel@daenzer.net>
To: Harald Welte <laforge@gnumonks.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: insmod ipv6 freezes current linuxppc-2.5 and 2.5-benh
Date: Sun, 14 Dec 2003 11:38:51 +0100 [thread overview]
Message-ID: <1071398331.1642.105.camel@thor.asgaard.local> (raw)
In-Reply-To: <20031213090332.GH8950@obroa-skai.de.gnumonks.org>
On Sat, 2003-12-13 at 10:03, Harald Welte wrote:
>
> The actual problem seems not to be an infinite loop, but rather a very
> long loop. IF you wait long enough, it will eventually work. A
> significant delay (i.e. assumed long loop) is also observed while
> loading any module. Something like 10 - 15 seconds for every module
> that I'm loading during startup (ipv6, tulip, dmasound_pmac, ...)
>
> The machine is completely frozen during that loop, not even the cursor
> is blinking anymore.
>
> compiling the kernel with gcc 2.95 or 3.0 removes those symptoms.
As I'm not seeing this, you may want to compare your .config to mine,
which is http://penguinppc.org/~daenzer/config-2.6.0-test11-benh
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Software libre enthusiast | http://svcs.affero.net/rm.php?r=daenzer
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-14 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 20:12 insmod ipv6 freezes current linuxppc-2.5 and 2.5-benh Harald Welte
2003-11-21 3:54 ` Benjamin Herrenschmidt
2003-11-21 15:33 ` Harald Welte
2003-11-30 15:55 ` Harald Welte
2003-12-02 15:59 ` Michel Dänzer
2003-12-13 9:03 ` Harald Welte
2003-12-14 10:38 ` Michel Dänzer [this message]
2003-12-02 16:21 ` Franz Sirl
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=1071398331.1642.105.camel@thor.asgaard.local \
--to=michel@daenzer.net \
--cc=benh@kernel.crashing.org \
--cc=laforge@gnumonks.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).