All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Geggus <lists@fuchsschwanzdomain.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel crash on 2.6.31.x (kcryptd: page allocation failure..)
Date: Sat, 17 Oct 2009 20:38:00 +0000 (UTC)	[thread overview]
Message-ID: <hbd9v8$7rf$1@ultimate100.geggus.net> (raw)
In-Reply-To: 200910172230.13162.elendil@planet.nl

Frans Pop <elendil@planet.nl> wrote:

> What is the _exact_ command sequence you use to reproduce it? I already 
> have a testcase, but a second test case, or a simpler one, may be useful.

Not a particular easy testcase.

This is what I did:

On the crashing machine with the dm-encrypted xfs volume:
ionice -c 3 socat TCP4-LISTEN:5555 - >backup.tar

On the source machine:
tar cv dir |socat - TCP4:targetmachine:5555

You will certainly not need to use tar.

socat /dev/zero TCP4:targetmachine:5555 should work as well.

I don't know if TCP traffic is really needed probably it is.

Regards

Sven

-- 
"We don't know the OS that God uses, but the Vatican uses Linux"
                               (Sister Judith Zoebelein, Vatican Webmaster)

/me is giggls@ircnet, http://sven.gegg.us/ on the Web

  reply	other threads:[~2009-10-17 20:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-17 19:03 Kernel crash on 2.6.31.x (kcryptd: page allocation failure..) Sven Geggus
2009-10-17 20:30 ` Frans Pop
2009-10-17 20:30   ` Frans Pop
2009-10-17 20:30   ` Frans Pop
2009-10-17 20:38   ` Sven Geggus [this message]
2009-10-18 23:41     ` Frans Pop
2009-10-18 23:41       ` Frans Pop
2009-10-18 23:41       ` Frans Pop
2009-10-20 19:16       ` Sven Geggus
2009-10-20 19:16         ` Sven Geggus
2009-10-20 20:02         ` Mel Gorman
2009-10-20 20:02           ` Mel Gorman

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='hbd9v8$7rf$1@ultimate100.geggus.net' \
    --to=lists@fuchsschwanzdomain.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.