From: Milan Broz <mbroz@redhat.com>
To: Nigel Cunningham <nigel@tuxonice.net>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
dm-crypt@saout.de, Pedro Ribeiro <pedrib@gmail.com>,
tuxonice-devel@tuxonice.net,
Kernel development list <linux-kernel@vger.kernel.org>,
kgdb-bugreport@lists.sourceforge.net
Subject: Re: [dm-crypt] kcryptd oops when resuming with TuxOnIce with KDB oops afterwards
Date: Thu, 29 Jul 2010 12:31:19 +0200 [thread overview]
Message-ID: <4C515877.5040101@redhat.com> (raw)
In-Reply-To: <4C50F09C.6050201@tuxonice.net>
On 07/29/2010 05:08 AM, Nigel Cunningham wrote:
> 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.
Is it TuxOnIce only problem?
Or there is similar report with unpatched kernel?
Milan
next prev parent reply other threads:[~2010-07-29 10:31 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 ` Milan Broz [this message]
2010-07-29 11:38 ` [dm-crypt] " Nigel Cunningham
2010-07-29 11:49 ` [TuxOnIce-devel] " Martin Steigerwald
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=4C515877.5040101@redhat.com \
--to=mbroz@redhat.com \
--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=pedrib@gmail.com \
--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