Re: Booting anything after r352057 kills console
Pete Wright [p...@nomadlogic.org] wrote: > > I remember having similar issues a while ago when we were first hacking on > drm, one thing to try is updating /boot/loader.conf with the following: > debug.debugger_on_panic=0 > dev.drm.skip_ddb="1" > dev.drm.drm_debug_persist="1" > > these are semi-documented in the wiki here: > https://wiki.freebsd.org/Graphics#Issues_.2F_Bugs > > while they may not solve the issue, they will hopefully give us better info > as to why the system is hanging. Also, are you able to boot the previously > working kernel (iirc you can do this via the boot loader menu) successfully? > and lasty, can you boot single user then manually attempt to load the kernel > module via kldload i915kms.ko? > I am not 100 percent sure that this is a DRM problem. I have de-installed everything related to DRM and commented out the rc.conf statement that loads the DRM modules and still can't get past the last few steps of the startup. I did see that ntpd does read it's configuration file because my /var/log/messages has an entry for reading the leap seconds file. That is the last entry in the /var/log/messages file. I am able to successfully use the beadm choice 7 in the boot chooser to load a previously good boot environment working kernel. I'll try your other suggestions tomorrow morning and post the result to this group. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Booting anything after r352057 kills console
On 9/23/19 2:32 PM, Thomas Laus wrote: Poul-Henning Kamp [p...@phk.freebsd.dk] wrote: In message <11db909b-57ee-b452-6a17-90ec2765c...@acm.org>, Thomas Laus writes: Where do I go from here? The computer is an Intel i5 Skylake with onboard graphics. Based on personal experience: 1. Deinstall drm ports 2. Remove all remaining drm related files under /boot 3. Reinstall drm port That did not work. On a successful boot after using beadm to rollback to r352057, I see the following items startup after setting the ntpd security policy: starting ntpd configuring vt: blanktime sanity check of sshd configuration start sshd start sendmail & sendmail submit as well as cron start background checks login On all svn updates after r352057, the last item logged is the ntpd security policy and then the console goes black. The computer is dead and I can't login through ssh nor change to another console. I hae to hit the reset switch to reboot. Even ctrl-alt-delete is not functioning. I remember having similar issues a while ago when we were first hacking on drm, one thing to try is updating /boot/loader.conf with the following: debug.debugger_on_panic=0 dev.drm.skip_ddb="1" dev.drm.drm_debug_persist="1" these are semi-documented in the wiki here: https://wiki.freebsd.org/Graphics#Issues_.2F_Bugs while they may not solve the issue, they will hopefully give us better info as to why the system is hanging. Also, are you able to boot the previously working kernel (iirc you can do this via the boot loader menu) successfully? and lasty, can you boot single user then manually attempt to load the kernel module via kldload i915kms.ko? cheers, -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Booting anything after r352057 kills console
Poul-Henning Kamp [p...@phk.freebsd.dk] wrote: > > In message <11db909b-57ee-b452-6a17-90ec2765c...@acm.org>, Thomas Laus writes: > > >Where do I go from here? The computer is an Intel i5 Skylake with > >onboard graphics. > > Based on personal experience: > > 1. Deinstall drm ports > > 2. Remove all remaining drm related files under /boot > > 3. Reinstall drm port > That did not work. On a successful boot after using beadm to rollback to r352057, I see the following items startup after setting the ntpd security policy: starting ntpd configuring vt: blanktime sanity check of sshd configuration start sshd start sendmail & sendmail submit as well as cron start background checks login On all svn updates after r352057, the last item logged is the ntpd security policy and then the console goes black. The computer is dead and I can't login through ssh nor change to another console. I hae to hit the reset switch to reboot. Even ctrl-alt-delete is not functioning. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Booting anything after r352057 kills console
On Mon, Sep 23, 2019 at 11:51 PM Poul-Henning Kamp wrote: > > > In message > > , Warner Losh writes: > > >We are working on making drm ports less problematic on upgrade... > > Yes, I know. > > But when you track current, it seems that it takes a port-reinstall > to get on that wagon... > beadm/bectl rules 1) make world/kernel 2) install in new BE 3) make new pkg drm 4) install it in new BE too 5) activate 6) reboot ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Booting anything after r352057 kills console
In message , Warner Losh writes: >We are working on making drm ports less problematic on upgrade... Yes, I know. But when you track current, it seems that it takes a port-reinstall to get on that wagon... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Booting anything after r352057 kills console
On Mon, Sep 23, 2019, 10:02 PM Poul-Henning Kamp wrote: > > In message <11db909b-57ee-b452-6a17-90ec2765c...@acm.org>, Thomas Laus > writes: > > >Where do I go from here? The computer is an Intel i5 Skylake with > >onboard graphics. > > Based on personal experience: > > 1. Deinstall drm ports > > 2. Remove all remaining drm related files under /boot > > 3. Reinstall drm port > We are working on making drm ports less problematic on upgrade... Warner > > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > p...@freebsd.org | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Booting anything after r352057 kills console
In message <11db909b-57ee-b452-6a17-90ec2765c...@acm.org>, Thomas Laus writes: >Where do I go from here? The computer is an Intel i5 Skylake with >onboard graphics. Based on personal experience: 1. Deinstall drm ports 2. Remove all remaining drm related files under /boot 3. Reinstall drm port -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Booting anything after r352057 kills console
I updated my source today and when the computer was booted, the screen turned black at the point that the drm related kernel modules would normally load. Suspecting a drm issue, I commented out the rc.conf line that loads those kernel modules. This did not fix my problem. My last good kernel was r352057. I started to bi-sect the svn updates between today and r352057. Going backward, all the way to r352064 is not working. There were very few changes between r352057 and r352064. None of them seem to be console graphics related. The last entry in my boot log shows a successful entry of the security policy for ntp. No logged messages after this point. Where do I go from here? The computer is an Intel i5 Skylake with onboard graphics. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FreeBSD CI Weekly Report 2019-09-22
(Please send the followup to freebsd-testing@ and note Reply-To is set.) FreeBSD CI Weekly Report 2019-09-22 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-09-16 to 2019-09-22. During this period, we have: * 2048 builds (99% (+3.7) passed, 1% (-3.7) failed) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 359 test runs (77.2% (+18.8) passed, 22.8% (-8.2) unstable) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 42 doc builds (100% passed) Test case status (on 2019-09-22 23:59): | Branch/Architecture | Total | Pass | Fail | Skipped | | --- | -- | -- | -- | --- | | head/amd64 | 7567 (+4) | 7504 (+4) | 0 (0) | 63 (+1) | | head/i386 | 7565 (+4) | 7493 (+3) | 0 (-2) | 72 (+3) | | 12-STABLE/amd64 | 7474 (+41) | 7430 (+41) | 0 (0) | 44 (0) | | 12-STABLE/i386 | 7472 (+41) | 7424 (+44) | 0 (0) | 48 (-3) | | 11-STABLE/amd64 | 6849 (+3) | 6805 (+3) | 0 (0) | 44 (0) | | 11-STABLE/i386 | 6847 (+3) | 6770 (+3) | 34 (0) | 43 (0) | (The statistics from experimental jobs are omitted) If any of the issues found by CI are in your area of interest or expertise please investigate the PRs listed below. The latest web version of this report is available at https://hackmd.io/@FreeBSD-CI/report-20190922 and archive is available at https://hackmd.io/@FreeBSD-CI/, any help is welcome. ## News * [FCP 20190401-ci_policy: CI policy](https://github.com/freebsd/fcp/blob/master/fcp-20190401-ci_policy.md) is in "feedback" state, please check and provide comments on -fcp@ and -hackers@ mailing lists. * [Testing/CI session in DevSummit201909](https://wiki.freebsd.org/DevSummit/201909) ## Failing Tests * https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/ * local.kyua.* (31 cases) * local.lutok.* (3 cases) ## Failing and Flaky Tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * cddl.usr.sbin.dtrace.common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237641 * cddl.usr.sbin.dtrace.amd64.arrays.t_dtrace_contrib.tst_uregsarray_d * https://bugs.freebsd.org/240358 * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ * There are ~60 failing cases, including flakey ones, see https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/ for more details ## Disabled Tests * lib.libc.sys.mmap_test.mmap_truncate_signal https://bugs.freebsd.org/211924 Patch available: https://reviews.freebsd.org/D21566 * sys.fs.tmpfs.mount_test.large https://bugs.freebsd.org/212862 * sys.fs.tmpfs.link_test.kqueue https://bugs.freebsd.org/213662 * sys.kqueue.libkqueue.kqueue_test.main https://bugs.freebsd.org/233586 * sys.kern.ptrace_test.ptrace__PT_KILL_competing_stop https://bugs.freebsd.org/220841 * lib.libc.regex.exhaust_test.regcomp_too_big (i386 only) https://bugs.freebsd.org/237450 * sys.netinet.socket_afinet.socket_afinet_bind_zero (new) https://bugs.freebsd.org/238781 * sys.netpfil.pf.names.names * sys.netpfil.pf.synproxy.synproxy https://bugs.freebsd.org/238870 * sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger https://bugs.freebsd.org/239292 * sys.netpfil.pf.forward.v4 (i386 only) * sys.netpfil.pf.forward.v6 (i386 only) * sys.netpfil.pf.set_tos.v4 (i386 only) https://bugs.freebsd.org/239380 * sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger https://bugs.freebsd.org/239397 * sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger https://bugs.freebsd.org/239399 * sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger https://bugs.freebsd.org/239425 * lib.libc.gen.getmntinfo_test.getmntinfo_test https://bugs.freebsd.org/240049 * sys.sys.qmath_test.qdivq_s64q https://bugs.freebsd.org/240219 * sys.kern.ptrace_test.ptrace__getppid https://bugs.freebsd.org/240510 * lib.libc.sys.stat_test.stat_socket https://bugs.freebsd.org/240621 * (new) sys.netpfil.common.tos.pf_tos (i386 only) https://bugs.freebsd.org/240086 * (new) lib.libarchive.functional_test.test_write_filter_zstd https://bugs.freebsd.org/240683 ## Issues ### Cause build fails * https://bugs.freebsd.org/233735 Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory * https://bugs.freebsd.org/233769 Possible build race: ld: error: unable to find library -lgcc_s ### Cause kernel panics * https://bugs.freebsd.org/238870 sys.netpfil.pf.names.names and sys.netpfil.pf.synproxy.synproxy cause panic Patch exists: * https://reviews.freebsd.org/D20868 * https://reviews.freebsd.org/D20869 ### Open *
