linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Tvrtko Ursulin <tvrtko@ursulin.net>
Cc: Milan Broz <gmazyland@gmail.com>,
	dm-crypt@saout.de, linux-kernel@vger.kernel.org,
	okozina@redhat.com, linux-rt-users@vger.kernel.org
Subject: Re: [dm-crypt] cryptsetup not working under 3.6 - RT patch set seem to break it
Date: Tue, 30 Oct 2012 10:40:01 +0100	[thread overview]
Message-ID: <20121030094001.GV639@pengutronix.de> (raw)
In-Reply-To: <508EEAF2.4090506@ursulin.net>

On Mon, Oct 29, 2012 at 08:45:38PM +0000, Tvrtko Ursulin wrote:
> On 29/10/12 20:14, Tvrtko Ursulin wrote:
> >On 29/10/12 19:47, Milan Broz wrote:
> >>On 10/29/2012 08:31 PM, Tvrtko Ursulin wrote:
> >>>Just tried 3.6.4 and it is still broken. Is there anything else I could
> >>>try to debug this?
> >>
> >>See response from response from Ondra on dmcrypt list - your kernel
> >>config
> >>is perhaps broken.
> >
> >I don't think that reached me - perhaps I was not copied.
> >
> >Weird yes, I mean no one can spot anything bad with my config...
> >
> >>Please use fresh checkout, run make oldconfig and try again.
> >>(Many people use 3.6 already and there is no other report.)
> >
> >... and I just used it today to configure a fresh 3.6.4 (plus -rt10
> >patches) without a problem.
> >
> >Unless RT patchset is the culprit. Hm.. that would be unexpected, but I
> >guess it is worth a shot. I'll let you know what happens without -rt.
> 
> Ha, this is exciting, vanilla 3.6.4 works, with -rt10 patch it does not.
I experienced that problem, too. This is on a laptop with encrypted
rootfs, so debugging is a bit harder here. I am just setting up another
machine to debug that.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  parent reply	other threads:[~2012-10-30  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50830D33.5050807@ursulin.net>
     [not found] ` <5083C61C.5090807@gmail.com>
     [not found]   ` <5083E4A8.3060501@ursulin.net>
     [not found]     ` <5083E87B.2080908@gmail.com>
     [not found]       ` <5083EC61.8070505@ursulin.net>
     [not found]         ` <50844D01.9090805@gmail.com>
     [not found]           ` <5084551E.5040304@ursulin.net>
     [not found]             ` <508ED985.5060301@ursulin.net>
     [not found]               ` <508EDD6E.7030908@gmail.com>
     [not found]                 ` <508EE395.9010709@ursulin.net>
     [not found]                   ` <508EE395.9010709-9sj9WOxYP5jR7s880joybQ@public.gmane.org>
2012-10-29 20:45                     ` cryptsetup not working under 3.6 - RT patch set seem to break it Tvrtko Ursulin
2012-10-29 23:51                       ` [dm-crypt] " Thomas Gleixner
2012-10-30  9:40                       ` Uwe Kleine-König [this message]
2012-10-30  9:55                         ` Milan Broz
2012-10-30 15:27                           ` [PATCH] Fix crypto api init for 3.6.4-rt10 Milan Broz
2012-10-30 17:57                             ` Thomas Gleixner
2012-10-30 20:35                               ` Uwe Kleine-König
2012-10-30 18:24                             ` Tvrtko Ursulin

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=20121030094001.GV639@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=okozina@redhat.com \
    --cc=tvrtko@ursulin.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;
as well as URLs for NNTP newsgroup(s).