Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752629AbdLUPsY (ORCPT ); Thu, 21 Dec 2017 10:48:24 -0500 Received: from mail-wm0-f47.google.com ([74.125.82.47]:38883 "EHLO mail-wm0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751279AbdLUPsV (ORCPT ); Thu, 21 Dec 2017 10:48:21 -0500 X-Google-Smtp-Source: ACJfBouCMqD33StZkUmtLQLNiZ1HVXw8PUakKy9NXnguvli3ADYPhl/wa1nKotuHkD2dHAgkdpe2vndbeyhtoS3VLP4= MIME-Version: 1.0 In-Reply-To: <20171221153631.GA2300@wolff.to> References: <20171221130057.GA26743@wolff.to> <20171221151843.GA453@wolff.to> <20171221153631.GA2300@wolff.to> From: weiping zhang Date: Thu, 21 Dec 2017 23:48:19 +0800 Message-ID: Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register") To: Bruno Wolff III Cc: Laura Abbott , Jan Kara , Jens Axboe , linux-mm@kvack.org, Linux Kernel Mailing List , regressions@leemhuis.info, weiping zhang , linux-block@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 816 Lines: 18 2017-12-21 23:36 GMT+08:00 Bruno Wolff III : > On Thu, Dec 21, 2017 at 23:31:40 +0800, > weiping zhang wrote: >> >> does every time boot fail can trigger WANRING in device_add_disk ? > > > Not that I see. But the message could scroll off the screen. The boot gets > far enough that systemd copies over dmesg output to permanent storage that I > can see on my next successful boot. That's where I looked for the warning > output you want. I never saw it for any kernels I compiled myself. Only when > I test kernels built by Fedora do I see it. see it every boot ? > I just tried booting to single user and the boot still hangs. > > When I build the kernels, the compiler options are probably a bit different > than when Fedora does. That might affect what happens during boot.