> Il giorno 13 feb 2017, alle ore 23:38, Bart Van Assche > <[email protected]> ha scritto: > > On Mon, 2017-02-13 at 22:07 +0000, Bart Van Assche wrote: >> On Mon, 2017-02-13 at 22:07 +0100, Paolo Valente wrote: >>> but what do you think about trying this fix? >> >> Sorry but with ... the same server I used for the previous test still >> didn't boot up properly. A screenshot is available at >> https://goo.gl/photos/Za9QVGCNe2BJBwxVA. >> >>> Otherwise, if you have no news or suggestions, would you be willing to >>> try my micro-logging proposal https://github.com/Algodev-github/bfq-mq? >> >> Sorry but it's not clear to me what logging mechanism you are referring >> to and how to enable it? Are you perhaps referring to >> CONFIG_BFQ_REDIRECT_TO_CONSOLE? > > Anyway, a second screenshot has been added to the same album after I had > applied the following patch: >
Hi Bart, thanks for this second attempt of yours. Although, unfortunately, not providing some clear indication of the exact cause of your hang (apart from a possible deadlock), your log helped me notice another bug. At any rate, as I have just written to Jens, I have pushed a new version of the branch [1] (not just added new commits, but also integrated some old commit with new changes, to make it more quickly). The branch now contains both a fix for the above bug, and, more importantly, a fix for the circular dependencies that were still lurking around. Could you please test it? Crossing my fingers, Paolo [1] https://github.com/Algodev-github/bfq-mq > diff --git a/block/Makefile b/block/Makefile > index 1c04fe19e825..bf472ac82c08 100644 > --- a/block/Makefile > +++ b/block/Makefile > @@ -2,6 +2,8 @@ > # Makefile for the kernel block layer > # > > +KBUILD_CFLAGS += -DCONFIG_BFQ_REDIRECT_TO_CONSOLE > + > > obj-$(CONFIG_BLOCK) := bio.o elevator.o blk-core.o blk-tag.o blk-sysfs.o \ > blk-flush.o blk-settings.o blk-ioc.o blk-map.o \ > blk-exec.o blk-merge.o blk-softirq.o blk-timeout.o \ > > Bart. > Western Digital Corporation (and its subsidiaries) E-mail Confidentiality > Notice & Disclaimer: > > This e-mail and any files transmitted with it may contain confidential or > legally privileged information of WDC and/or its affiliates, and are intended > solely for the use of the individual or entity to which they are addressed. > If you are not the intended recipient, any disclosure, copying, distribution > or any action taken or omitted to be taken in reliance on it, is prohibited. > If you have received this e-mail in error, please notify the sender > immediately and delete the e-mail in its entirety from your system. >
