Date: Sat, 21 Apr 2018 09:12:24 +0200 From: Milan Obuch <freebsd-arm@dino.sk> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: freebsd-arm@freebsd.org Subject: Re: Problem with regulator_shutdown() introduced in r331989 Message-ID: <20180421091224.5f96da0c@zeta.dino.sk> In-Reply-To: <20180420233847.15b91854dc85bb8113e40d5a@bidouilliste.com> References: <20180407213413.0103754b@zeta.dino.sk> <20180420233847.15b91854dc85bb8113e40d5a@bidouilliste.com>
index | next in thread | previous in thread | raw e-mail
On Fri, 20 Apr 2018 23:38:47 +0200 Emmanuel Vadot <manu@bidouilliste.com> wrote: > On Sat, 7 Apr 2018 21:34:13 +0200 > Milan Obuch <freebsd-arm@dino.sk> wrote: > > > Hi, > > > > after some time with running slightly older sources based kernel I > > decided to upgrade, but current sources based kernel does not boot > > on Orange Pi Zero, maybe on other Allwinner based boards too, I did > > not test them. Problem manifests itself on console with following: > > > > Release APs > > CPU(3) applied BP hardening: not necessary > > CPU(1) applied BP hardening: not necessary > > CPU(2) applied BP hardening: not necessary > > WARNING: WITNESS option enabled, expect reduced performance. > > regulator: shuting down vcc3v0 > > Trying to mount root from ufs:/dev/mmcsd0s2a [rw]... > > GEOM: new disk mmcsd0 > > regulator: shuting down vcc5v0 > > regulator: shuting down vcc-wifi > > mmc0: panic: Invalid enable count > > cpuid = 0 > > time = 1 [ snip ] > > I can override it with either manually entering > > > > set hw.regulator.disable_unused=0 > > > > on loader prompt, or putting line > > > > hw.regulator.disable_unused=0 > > > > into /boot/loader.conf file. > > > > Either way, system boots then normally and works as expected. Has > > anybody any explanation what's going on? What purpose does this > > function actually serve? Reading source, disabling unused regulatos > > looks like a way to conserve power, but I am not sure if I think > > about it the right way. Anyway, something is wrong - why has mmc0 > > invalid enable count? Looks strange to me... > > > > Regards, > > Milan > > Hi, > > r332843 should fix this problem. > > Cheers, > Hi, confirmed - new kernel built works with no workaround, some regulator disabled, boots full to userland: regulator: shuting down vcc3v0 regulator: shuting down vcc3v3 regulator: shuting down vcc5v0 regulator: shuting down vcc-wifi Thanks for fix. Regards, Milanhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180421091224.5f96da0c>