From: Johannes Resch <jr@xor.at>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Multiple oopses with 2.4.25
Date: Sun, 07 Mar 2004 16:49:25 +0100 [thread overview]
Message-ID: <404B4485.1050507@xor.at> (raw)
In-Reply-To: <Pine.LNX.4.44.0403050914450.2678-100000@dmt.cyclades>
Hi Marcelo,
On 2004-03-05 13:18, Marcelo Tosatti wrote:
> On Wed, 3 Mar 2004, Johnny Strom wrote:
>>
>>I also get multiple oopse's with 2.4.25 plus the latest
>>ipsec kernel patch form http://www.freeswan.org/.
>>
>>I have to reset the computer to get it working again,
>>below is the oopse's:
>
>
> Dear fellows,
>
> I have seen similar reports.
>
> Can you find out which kernel does not exhibit the behaviour with the same
> freeswan/grsec patches ?
I'm not able to reproduce the oopses.
I've been running 2.4.24 / 2.4.23 with grsec 1.9.13 without any problems
before.
--jr
next prev parent reply other threads:[~2004-03-07 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 20:19 Multiple oopses with 2.4.25 Johnny Strom
2004-03-05 12:18 ` Marcelo Tosatti
2004-03-05 13:09 ` Johnny Strom
2004-03-07 15:49 ` Johannes Resch [this message]
2004-03-08 20:59 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2004-03-03 17:57 Johannes Resch
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=404B4485.1050507@xor.at \
--to=jr@xor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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