Discussion:
Something between r333623 - r333670 locks up at start of boot
(too old to reply)
David Wolfskill
2018-05-16 12:42:55 UTC
Permalink
...on my laptop. Build machine was "fine."

Links -- including to copies of most recent verbose dmesg.boot files --
may be found at <http://www.catwhisker.org/~david/FreeBSD/history/>.

Last successful build & smoke-test of head on my laptop was:

FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #190 r333623M/333625:1200063: Tue May 15 04:24:00 PDT 2018 ***@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64

After updating sources to r333670, build was OK; smoke-test came to a
screeching halt at:

Booting...
/

(The "propeller" spins brefly -- maybe a second or two, then stops.
At that point, the only thing I've found to break out of that is a
power-cycle.)

One possibly-salient item: while the build machine uses the default
vt(4), I had switched the laptop to 'kern.vty="sc"' via /boot/loader.conf
no later than 23 August 2017 (mtime of the file), which seemed to
have had a positive effect with respect to suspend/resume. (The
laptop uses an Nvidia graphics card, in case that's useful to note,
and I prefer to suspend it while I'm commuting by bike with it on
my back.)

I confirmed that booting kernel.old works OK, as does booting/running
stable/11 (which I'm running as I type).

CPU on the laptop is "Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz
(2793.60-MHz K8-class CPU)" Sorry; I don't know how that translates
to Intel code names.

There's more information about the laptop at <https://wiki.freebsd.org/Laptops/Dell_Precision_M4800?highlight=(\bCategoryLaptop\b)>.

Peace,
david
--
David H. Wolfskill ***@catwhisker.org
Mr. Trump: Just how does reneging on the Iran nuclear deal make the US "safer?"

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
unknown
2018-05-17 07:34:03 UTC
Permalink
Post by David Wolfskill
After updating sources to r333670, build was OK; smoke-test came to a
Booting...
/
(...)
One possibly-salient item: while the build machine uses the default
vt(4), I had switched the laptop to 'kern.vty="sc"' via /boot/loader.conf
no later than 23 August 2017 (mtime of the file)
I broke syscons(4) yesterday and bde@ provided a patch which cem@
committed in r333683 [1].

It should work again for you now. Sorry for the breakage.

[1] https://svnweb.freebsd.org/changeset/base/333683
--
Jean-Sébastien Pédron
David Wolfskill
2018-05-17 12:31:04 UTC
Permalink
Post by unknown
...
committed in r333683 [1].
It should work again for you now. Sorry for the breakage.
....
Aye, all better now:

FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #192 r333710M/333710:1200063: Thu May 17 05:23:56 PDT 2018 ***@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64

Thanks! :-)

Peace,
david
--
David H. Wolfskill ***@catwhisker.org
Mr. Trump: Just how does reneging on the Iran nuclear deal make the US "safer?"

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
Continue reading on narkive:
Loading...