Prev: [PATCH] Tight check of pfn_valid on sparsemem - v4
Next: dlm: use genl_register_family_with_ops()
From: Nils Radtke on 26 Jul 2010 12:00
Hi Milan,

Thank you for your explanation.

So I'll try to find logs regarding this issue (won't be easy though..).

On the other hand, the usb device survives suspend/resume normally, that is,
when using a plain disk, std partition etc.

Ok, I'm going for the logs and if found be back.

Thank you again for your help.


Nils



On Mon 2010-07-26 @ 03-22-45PM +0200, Milan Broz wrote:
# On 07/26/2010 03:06 PM, Nils Radtke wrote:
# > That's what I tried and failed gloriously. I'm trying to revive my memory about the
# > situation: fs could be unmounted, however, the cryptsetup luksClose failed (IRC) and
# > therefore the dmsetup remove consequently failed also.
#
# So instead of "cryptsetup luksClose" use dmsetup remove for crypt device too
# (There was a bug in some version of cryptsetup which failed close if underlying device
# disappeared, should be fixed in >=1.1.2, anyway "dmsetup remove" is low-level equivalent.)
#
# Also see man page and "dmsetup remove -f" flag.
#
# The usb device reinitialization is separate problem, maybe someone can help if you provide
# more logs.
#
# Milan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH] Tight check of pfn_valid on sparsemem - v4
Next: dlm: use genl_register_family_with_ops()