From: Christian Kujau <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Subject: Re: lockups with 2.4.2x
Date: Tue, 23 Sep 2003 02:23:37 +0200 [thread overview]
Message-ID: <3F6F9289.3050706@g-house.de> (raw)
In-Reply-To: <3F6D134E.2080505@g-house.de>
hi again,
i seem to have the source to my problem here. a little application named
"dnetc" (RC5-72 number cruncher, see http://www.distributed.net) causes
the lockups when running under 2.4.22. no joke, i too don't want to
believe this, but it's quite reproducable.
ok, the thing is: yes, i can live without this st00pid number-cruncher,
so my system won't crash. otoh, i wonder why this little userspace
application crashes a whole system so badly, that it's not even able to
give an Oops. i will try to "strace ./dnetc" or execute it in the gdb,
but i'm pretty sure, it will crash anyway, and the system won't have
time to show errors or even write them to the disk.
btw, the "dnetc" is some kind of "open source but please don't look into
it" thing, and even if we manage to compile it, the produced output is
invalid.
oh, and i still did not try to remove memory and booting with no
"highmem" or a "not preemtible kernel" and such. will do so, if that helps.
Thanks for reading,
Christian.
--
BOFH excuse #104:
backup tape overwritten with copy of system manager's favourite CD
prev parent reply other threads:[~2003-09-22 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-21 2:56 lockups with 2.4.2x evil
2003-09-21 5:37 ` Christian
2003-09-21 5:38 ` Willy Tarreau
2003-09-21 13:26 ` Christian
2003-09-21 21:49 ` Christian
2003-09-23 0:23 ` Christian Kujau [this message]
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=3F6F9289.3050706@g-house.de \
--to=evil@g-house.de \
--cc=linux-kernel@vger.kernel.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