public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <kernel@nn7.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: crypto-loop + highmen -> random crashes in -test11
Date: Thu, 18 Dec 2003 09:30:28 +0100	[thread overview]
Message-ID: <1071736227.18903.7.camel@localhost> (raw)
In-Reply-To: <20031216034059.28db8e91.akpm@osdl.org>

On Tue, 2003-12-16 at 12:40, Andrew Morton wrote:
> Soeren Sonnenburg <kernel@nn7.de> wrote:
> >
> > Hi.
> > 
> > I get random crashes/corruption/ init kills when I use cryptoloop on
> > this highmem enabled ppc machine.
> 
> People have reported cryptoloop+highmem crashes on ia32 as well.  I'm not
> sure if that was with -mm though.
> 
> > Applying the loop-* patches at
> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test10/2.6.0-test10-mm1/broken-out
> > 
> > seem to fix this problem (at least I did not get any crash due to
> > cryptoloop in the last 2 days)
[...]
> Nice, but I don't know why those patches fixed it. hrm.
> 

no idea. all I can say is that it cryptoloop pretends to work reliably since 3 days...

Soeren


  reply	other threads:[~2003-12-18  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-15 20:06 2.6 kgdb without serial port Pavel Machek
2003-12-16  6:34 ` Andrew Morton
2003-12-16 10:30   ` crypto-loop + highmen -> random crashes in -test11 Soeren Sonnenburg
2003-12-16 11:40     ` Andrew Morton
2003-12-18  8:30       ` Soeren Sonnenburg [this message]
2003-12-16 22:45     ` bill davidsen
2003-12-26 18:27   ` 2.6 kgdb without serial port Pavel Machek
2003-12-26 19:08     ` Andrew Morton
2003-12-26 21:18       ` Martin J. Bligh
2003-12-27 10:30       ` Pavel Machek

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=1071736227.18903.7.camel@localhost \
    --to=kernel@nn7.de \
    --cc=akpm@osdl.org \
    --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