Bluetooth: Mesh: initialisation delay after disabling CONFIG_BT_DEBUG_LOG

[vikrant8052]

It is found that we have to have enable CONFIG_BT_DEBUG_LOG=y
then only Mesh initialization happens within second otherwise it takes around 10+ seconds. This bug has introduced after latest new logging subsystem.

To Reproduce

1. flash samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app in nRF52840_pca10056
   with CONFIG_BT_DEBUG_LOG=n (it is by default disable as per current prj.conf)
2. Provision & configure it using nRFMesh App
3. Reset the Board & see device serial terminal

Here NODE takes 10+ seconds to print "Mesh initialized"

It will be good if we could avoid all type of DEBUG LOGs, so that we could avoid that 1 seconds delay as well as to improve the performance. DEBUG log is important only for development with actual product developers may want to disable it.

[carlescufi]

Note that according to @jhedberg this is now generalized in the Bluetooth samples. Logging seems to delay the startup of Bluetooth by about 10 seconds.

[jhedberg]

Looks like this is caused by commit 4d94257. @Vikrant8051 could you try reverting that (git revert 4d94257162b22f37104e9f85238ed7c3486c5a1c) and see if the issue goes away for you?

[vikrant8052]

OK

[vikrant8052]

@jhedberg
I think

git revert 4d94257

has no effect....still Mesh initialization takes some time.

May be #11838 solve the issue. Let me test that.

[vikrant8052]

After merging #11838 there is no effect. Still facing mentioned delay in initialization.

[jhedberg]

@Vikrant8051 you also need #11842 . Both PRs should hopefully be merged soon.

[jhedberg]

@Vikrant8051 both PRs are in master now, so you can just rebase on top of that to see if the issue is now solved.

[vikrant8052]

@nordic-krch @jhedberg @carlescufi
Issue has resolved !!
Thanks for solving it.