[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171221153631.GA2300@wolff.to>
Date:   Thu, 21 Dec 2017 09:36:31 -0600
From:   Bruno Wolff III <bruno@...ff.to>
To:     weiping zhang <zwp10758@...il.com>
Cc:     Laura Abbott <labbott@...hat.com>, Jan Kara <jack@...e.cz>,
        Jens Axboe <axboe@...nel.dk>, linux-mm@...ck.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        regressions@...mhuis.info,
        weiping zhang <zhangweiping@...ichuxing.com>,
        linux-block@...r.kernel.org
Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for
 bdi_debug_register")
On Thu, Dec 21, 2017 at 23:31:40 +0800,
  weiping zhang <zwp10758@...il.com> 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.
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.
Powered by blists - more mailing lists
 
