From: Marc Lehmann <pcg@goof.com>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux swap freeze STILL in 2.4.x
Date: Mon, 26 Feb 2001 09:40:00 +0100 [thread overview]
Message-ID: <20010226094000.A4228@fuji.laendle> (raw)
In-Reply-To: <20010225202526.B8890@cerebro.laendle> <Pine.LNX.4.33.0102260801240.1408-100000@mikeg.weiden.de>
In-Reply-To: <Pine.LNX.4.33.0102260801240.1408-100000@mikeg.weiden.de>; from mikeg@wen-online.de on Mon, Feb 26, 2001 at 08:11:55AM +0100
On Mon, Feb 26, 2001 at 08:11:55AM +0100, Mike Galbraith <mikeg@wen-online.de> wrote:
> Hmm.. I remember having this problem and it was a problem with strace.
Well, I obviously strace'd it to find out why I get a memory fault without
one (I would be happy if it worked without strace ;->)
> Anyway, it works fine here with virgin 2.4.2, so it seems unlikely it's
> a kernel problem.
> 259 execve("/sbin/losetup", ["losetup", "/dev/loop0", "/dev/hda5"], [/* 47 vars */]) = 0
The -e switch is causing the memory fault and subsequent breakage:
743 open("/dev/hdd", O_RDWR) = 4
743 open("/dev/loop0", O_RDWR) = 5
743 mlockall(0x3, 0x804c272) = 0
743 ioctl(5, LOOP_SET_FD, 0x4) = -1 ENOSYS (Function not implemented)
743 ioctl(5, LOOP_SET_FD, 0x4) = 0
743 ioctl(5, LOOP_SET_STATUS, 0xbffff5d8) = -1 ENOSYS (Function not implemented)
743 ioctl(5, LOOP_SET_STATUS, 0xbffff5d8) = -1 ENOSYS (Function not implemented)
743 ioctl(5, LOOP_SET_STATUS, 0xbffff5d8) = -1 ENOSYS (Function not implemented)
743 ioctl(5, LOOP_SET_STATUS, 0xbffff5d8) = -1 ENOSYS (Function not implemented)
743 ioctl(5, LOOP_SET_STATUS <unfinished ...>
743 +++ killed by SIGSEGV +++
(which is a strange strace anyway...)
However, I just need to wait until there is a new crypto patch (and, if
not, I'll eventually have to hack it myself to gte my data. After all it's
source... ...)
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
next prev parent reply other threads:[~2001-02-26 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 14:59 Marc Lehmann
2001-02-25 16:58 ` Mike Galbraith
2001-02-25 19:00 ` Marc Lehmann
2001-02-26 6:28 ` Mike Galbraith
2001-02-25 19:22 ` Marc Lehmann
2001-02-25 19:25 ` Marc Lehmann
2001-02-26 7:11 ` Mike Galbraith
2001-02-26 8:40 ` Marc Lehmann [this message]
2001-02-26 10:26 ` Mike Galbraith
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=20010226094000.A4228@fuji.laendle \
--to=pcg@goof.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
/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
all inboxes | Powered by JetHome®