From: koalasoft@gmx.de (Ulrich Mensfeld)
To: linux-kernel@vger.kernel.org
Subject: Kernelpanic in 2.43
Date: 09 Dec 2003 00:00:00 +0000 [thread overview]
Message-ID: <8zZPc72uGbB@koalasoft> (raw)
Hallo,
don't know, whom to adress.
I've following problem: Every Linux-Kernel above 2.4.22 crashes with
capslock and scrolllock blinking, nothing in the message-log, and all i
can do is magic-sysreq and boot.
The problem seems to be reproducable: It seems to occur, when my son wants
to use my pc as a router to the internet. So for detail:
My pc acts as a dsl-router on "half"demand with packtfiltering and masq
(ipchains) for 2 windows-pcs.
"Half"demand means, my son has to make a "ping 10.0.0.2" to open an
outgoing connection, to prevent a bunch of windows tools opening unwanted
connections using "DoD".
But this all works fine under 2.4.18 to 2.4.22. I haven't any idea, what
that could be in 2.4.23.
If i should be more precise, please tell me what i should document.
Regards--
Ulrich
next reply other threads:[~2003-12-09 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 0:00 Ulrich Mensfeld [this message]
2003-12-09 18:35 ` Kernelpanic in 2.43 Martin Josefsson
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=8zZPc72uGbB@koalasoft \
--to=koalasoft@gmx.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