From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Snitzer Subject: Re: linux-next: Boot hangs 3 minutes with device mapper on s390 Date: Mon, 4 Mar 2019 23:03:21 -0500 Message-ID: <20190305040321.GA21739@redhat.com> References: <20190301183350.5ff697d4@TP-holzheu> <20190301183050.GA29752@redhat.com> <20190304110334.6f71962a@TP-holzheu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20190304110334.6f71962a@TP-holzheu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Michael Holzheu , Alexander Duyck Cc: Benjamin Block , Heiko Carstens , dm-devel@redhat.com, linux-next@vger.kernel.org, Mikulas Patocka , Steffen Maier List-Id: linux-next.vger.kernel.org Hi, Alexander reported this same boot hang in another thread. I was able to reproduce using an x86_64 .config that Alexander provided. I've pushed this fix out to linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-5.1&id=be2c5301817833f692aadb2e5fa209582db01d3b If you could verify this fix works for you I'd appreciate it. Thanks, Mike