Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754704AbdLOBr0 (ORCPT ); Thu, 14 Dec 2017 20:47:26 -0500 Received: from wolff.to ([98.103.208.27]:34292 "HELO wolff.to" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754538AbdLOBrX (ORCPT ); Thu, 14 Dec 2017 20:47:23 -0500 Date: Thu, 14 Dec 2017 19:44:17 -0600 From: Bruno Wolff III To: weiping zhang Cc: Laura Abbott , Jan Kara , Jens Axboe , linux-mm@kvack.org, Linux Kernel Mailing List , regressions@leemhuis.info, linux-block@vger.kernel.org Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register") Message-ID: <20171215014417.GA17757@wolff.to> References: <20171214082452.GA16698@wolff.to> <20171214100927.GA26167@localhost.didichuxing.com> <20171214154136.GA12936@wolff.to> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 792 Lines: 17 On Fri, Dec 15, 2017 at 09:22:21 +0800, weiping zhang wrote: > >Thanks your testing, but I cann't find WARN_ON in device_add_disk from >this boot1.log, could you help reproduce that issue? And does this issue can be >triggered at every bootup ? I don't know what you need for the first question. When I am physically at the machine I can do test reboots. If you have something specific you want me to try I should be able to. Every time I boot with the problem commit, the boot never completes. However it does seem to get pretty far. I get multiple register dumps every time. After a while (a few minutes) I reboot to a wrking kernel. The output I included is from: journalctl -k -b -1 If you think it would be better to see more than dmesg output let me know.