From: Arjan van de Ven <arjanv@redhat.com>
To: stepka@tris.sk
Cc: linux-kernel@vger.kernel.org, marian.stepka@onsemi.com
Subject: Re: PROBLEM: Kernel pging problem
Date: Sun, 14 Dec 2003 14:25:25 +0100 [thread overview]
Message-ID: <1071408325.5233.3.camel@laptop.fenrus.com> (raw)
In-Reply-To: <200312141328.22811.mstepka@orangemail.sk>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
> I reinstall my system from RedHat 9 to Fedora Core 1 with latest available
> kernel update from RedHat. I'm using VPN client software which taint the
> kernel but I hope this information could be usefull for kernel development
> and that is reason why I'm posting it. I will include copy of this message to
> proprietary VPN software developers.
the oops points to a problem in the networking side of things, which
thus is most likely caused by your binary only VPN module...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-12-14 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 12:28 PROBLEM: Kernel pging problem Marian Stepka
2003-12-14 13:25 ` Arjan van de Ven [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=1071408325.5233.3.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marian.stepka@onsemi.com \
--cc=stepka@tris.sk \
/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).