From: Andreas Steinmetz <ast@domdv.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Oops in swsusp
Date: Mon, 11 Apr 2005 01:17:57 +0200 [thread overview]
Message-ID: <4259B425.4090105@domdv.de> (raw)
Pavel,
during testing of the encrypted swsusp_image on x86_64 I did get an Oops
from time to time at memcpy+11 called from swsusp_save+1090 which turns
out to be the memcpy in copy_data_pages() of swsusp.c.
The Oops is caused by a NULL pointer (I don't remember if it was source
or destination).
This Oops seems to be unrelated to the encrypted image addition as I
didn't touch any code in that area.
--
Andreas Steinmetz SPAMmers use robotrap@domdv.de
next reply other threads:[~2005-04-10 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 23:17 Andreas Steinmetz [this message]
2005-04-11 6:59 ` Oops in swsusp Rafael J. Wysocki
2005-04-11 13:09 ` Andreas Steinmetz
2005-04-11 16:01 ` Andreas Steinmetz
2005-04-11 17:02 ` Rafael J. Wysocki
2005-04-11 11:00 ` 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=4259B425.4090105@domdv.de \
--to=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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