From: Martin Steigerwald <Martin@lichtvoll.de>
To: tuxonice-devel@tuxonice.net
Cc: Nigel Cunningham <nigel@tuxonice.net>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
dm-crypt@saout.de,
Kernel development list <linux-kernel@vger.kernel.org>,
kgdb-bugreport@lists.sourceforge.net
Subject: Re: [TuxOnIce-devel] kcryptd oops when resuming with TuxOnIce with KDB oops afterwards
Date: Thu, 29 Jul 2010 13:49:42 +0200 [thread overview]
Message-ID: <201007291349.53269.Martin@lichtvoll.de> (raw)
In-Reply-To: <4C50F09C.6050201@tuxonice.net>
[-- Attachment #1: Type: Text/Plain, Size: 2125 bytes --]
Am Donnerstag 29 Juli 2010 schrieb Nigel Cunningham:
> Hi Henrique.
Hi Nigel,
> On 29/07/10 12:49, Henrique de Moraes Holschuh wrote:
> > On Thu, 29 Jul 2010, Pedro Ribeiro wrote:
> >> I hit a bug when resuming with TuxOnIce. At the middle of a resume,
> >> it says Compress Read -22 and locks up. I caught the stack trace
> >> with kdb and took photos of that.
> >
> > Maybe this?
> > http://lkml.org/lkml/2010/7/28/398
>
> I don't think so. This issue has been around for a fair while. It's
> just impossible to reliably reproduce, and I haven't yet found the
> time to put some serious effort into tracking down the cause and
> fixing it.
I reported this one as - you said, its an TuxOnIce bug:
https://bugzilla.kernel.org/show_bug.cgi?id=15873
I switched compression on my ThinkPad T23 where it happened all 2-4 days
or so with 2.6.34 from LZO to LZF. And since then I didn't get the error
anymore, but with only 5 attempts so far, so I am not sure whether
switching to LZF "fixed" it:
deepdance:~> cat /sys/power/tuxonice/debug_info
TuxOnIce debugging info:
- TuxOnIce core : 3.1.1.1
- Kernel Version : 2.6.34.1-tp23-toi-3.1.1.1-04990-g3a7d1f4
- Compiler vers. : 4.4
- Attempt number : 5
- Parameters : 0 667656 0 1 0 0
- Overall expected compression percentage: 0.
- Checksum method is 'md4'.
0 pages resaved in atomic copy.
- Compressor is 'lzf'.
Compressed 776593408 bytes into 359897499 (53 percent compression).
- Block I/O active.
- Max outstanding reads 714. Max writes 5.
Memory_needed: 1024 x (4096 + 200 + 76) = 4476928 bytes.
Free mem throttle point reached 983.
- Swap Allocator enabled.
Swap available for image: 229016 pages.
- File Allocator active.
Storage available for image: 0 pages.
- I/O speed: Write 28 MB/s, Read 33 MB/s.
- Extra pages : 26 used/500.
- Result : Succeeded.
Maybe its a good idea to collect information in that bug report, even when
it really is a TuxOnIce one.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-07-29 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 1:30 kcryptd oops when resuming with TuxOnIce with KDB oops afterwards Pedro Ribeiro
2010-07-29 2:49 ` Henrique de Moraes Holschuh
2010-07-29 3:08 ` Nigel Cunningham
2010-07-29 10:31 ` [dm-crypt] " Milan Broz
2010-07-29 11:38 ` Nigel Cunningham
2010-07-29 11:49 ` Martin Steigerwald [this message]
2010-07-30 21:10 ` [Kgdb-bugreport] kcryptd oops when resuming with TuxOnIce with KDBoops afterwards Jason Wessel
2010-07-30 21:33 ` Pedro Ribeiro
2010-07-30 22:53 ` Jason Wessel
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=201007291349.53269.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=dm-crypt@saout.de \
--cc=hmh@hmh.eng.br \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@tuxonice.net \
--cc=tuxonice-devel@tuxonice.net \
/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