Re: crash after revision 352091
On Wed, Sep 11, 2019 at 2:12 PM Christos Chatzaras wrote: > > Few hours ago I upgrade FreeBSD-12.0-STABLE (revision 351639) to > FreeBSD-12.0-STABLE (revision 352091). > > After running the new version for few hours 2 of my servers crashed and > auto-reboot. > > Logs show nothing. > > Any idea if a commit between these 2 versions can cause it? Any chance if you can obtain the crash dump? https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#kerneldebug-obtain ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Anyone else seeing hangs at "Trying to mount root" after recent commits?
Yes, I upgraded 2 systems and both experience the same behavior Dell R610 and Dell 7010 here. Afraid to upgrade any others On Tue, Sep 10, 2019 at 8:25 PM Terry Kennedy wrote: > > I have a system I updated from r352025 (which worked fine) to r352200. > Any attempt to boot r352200 results in the system just sitting there after > displaying the normal "Trying to mount root from ufs:/dev/da0p3 [rw]..." > message. Nothing further, not even after a half hour. The console is non- > responsive (not that I'd really expect anything, but...). > > This persists across multiple resets, power cycles, etc. Booting the > previous r352025 works fine, as expected. > > Before I start trying to bisect this, is anyone else seeing this? amd64 > on a standard Dell PowerEdge R730 if that matters. > > Terry Kennedy http://www.glaver.org New York, NY USA > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: crash after revision 352091
I didn't have dumpdev enabled. I now add it to a test server: dumpdev="AUTO" then I reboot it and then I run: sysctl debug.kdb.panic=1 After it came back online it doesn't have the dump in /var/crash Do I miss something? > On 11 Sep 2019, at 11:29, Li-Wen Hsu wrote: > > On Wed, Sep 11, 2019 at 2:12 PM Christos Chatzaras > wrote: >> >> Few hours ago I upgrade FreeBSD-12.0-STABLE (revision 351639) to >> FreeBSD-12.0-STABLE (revision 352091). >> >> After running the new version for few hours 2 of my servers crashed and >> auto-reboot. >> >> Logs show nothing. >> >> Any idea if a commit between these 2 versions can cause it? > > Any chance if you can obtain the crash dump? > > https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#kerneldebug-obtain > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ixv + RSS
Has anyone ever tested a kernel with option RSS and an ixv interface? Just looking for some data points. Thanks! -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Anyone else seeing hangs at "Trying to mount root" after recent commits?
On Wed, Sep 11, 2019 at 01:38:14AM -0700, Jack L. wrote: > Yes, I upgraded 2 systems and both experience the same behavior > Dell R610 and Dell 7010 here. Afraid to upgrade any others For what it's worth, I have a Dell Optiplex 9020 booting r352118: FreeBSD FreeBSD 12.1-PRERELEASE #105 r352118+b6945c1f5542(stable/12) That's at least after r352025, which may help your bisect. Currently crunching r352202. I boot off of ZFS (vs UFS), but that might be another data point for someone. > On Tue, Sep 10, 2019 at 8:25 PM Terry Kennedy wrote: > > I have a system I updated from r352025 (which worked fine) to r352200. > > Any attempt to boot r352200 results in the system just sitting there after > > displaying the normal "Trying to mount root from ufs:/dev/da0p3 [rw]..." > > message. Nothing further, not even after a half hour. The console is non- > > responsive (not that I'd really expect anything, but...). > > > > This persists across multiple resets, power cycles, etc. Booting the > > previous r352025 works fine, as expected. > > > > Before I start trying to bisect this, is anyone else seeing this? amd64 > > on a standard Dell PowerEdge R730 if that matters. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Anyone else seeing hangs at "Trying to mount root" after recent commits?
On Wed, Sep 11, 2019 at 08:59:58AM -0700, John Kennedy wrote: > For what it's worth, I have a Dell Optiplex 9020 booting r352118: > > FreeBSD 12.1-PRERELEASE #105 r352118+b6945c1f5542(stable/12) > > That's at least after r352025, which may help your bisect. Currently > crunching r352202. I boot off of ZFS (vs UFS), but that might be another > data point for someone. I paid attention to bug 240487 and saw the "Fix miss merge in r352179" r352217 patch land and just booted with that. Looks good to me so far. FreeBSD 12.1-PRERELEASE #106 r352217+0e6a9a9426c7(stable/12) ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD CI Weekly Report 2019-09-08
(Please send the followup to freebsd-testing@ and note Reply-To is set.) FreeBSD CI Weekly Report 2019-09-08 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-09-02 to 2019-09-08. During this period, we have: * 2122 builds (99.4% (+2) passed, 0.6% (-2) failed) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 373 test runs (59.6% (-0.2) passed, 39.1% (-1.1) unstable, 1.3% (+1.3) exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 50 doc builds (100% (+2) passed) Test case status (on 2019-09-08 23:59): | Branch/Architecture | Total | Pass | Fail | Skipped | | --- | -- | -- | - | | | head/amd64 | 7556 (+6) | 7495 (+11) | 0 (-1)| 61 (-4) | | head/i386 | 7554 (+6) | 7484 (+7) | 2 (0) | 68 (-1) | | 12-STABLE/amd64 | 7393 (+1) | 7341 (-7) | 11 (+11) | 41 (-3) | | 12-STABLE/i386 | 7391 (+1) | 7329 (-10) | 11 (+11) | 51 (0) | | 11-STABLE/amd64 | 6846 (+1) | 6802 (+4) | 0 (0) | 44 (-3) | | 11-STABLE/i386 | 6844 (+1) | 6767 (-7) | 34 (0)| 43 (-6) | (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-20190908 and archive is available at https://hackmd.io/@FreeBSD-CI/, any help is welcome. ## News * Weekly CI report archive has been moved to https://hackmd.io/@FreeBSD-CI * [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. ## Fixed Tests * https://ci.freebsd.org/job/FreeBSD-head-amd64-test/ * (flakey) usr.bin.procstat.procstat_test.environment * (flakey) usr.bin.procstat.procstat_test.command_line_arguments Fixed in https://svnweb.freebsd.org/changeset/base/351819 ## Failing Tests * https://ci.freebsd.org/job/FreeBSD-stable-12-amd64-test/ * https://ci.freebsd.org/job/FreeBSD-stable-12-i386-test/ * sys.netipsec.tunnel.aes_cbc_128_hmac_sha1.v6 * sys.netipsec.tunnel.aes_cbc_256_hmac_sha2_256.v6 * sys.netipsec.tunnel.aes_gcm_128.v6 * sys.netipsec.tunnel.aes_gcm_256.v6 * sys.netipsec.tunnel.aesni_aes_cbc_128_hmac_sha1.v6 * sys.netipsec.tunnel.aesni_aes_cbc_256_hmac_sha2_256.v6 * sys.netipsec.tunnel.aesni_aes_gcm_128.v6 * sys.netipsec.tunnel.aesni_aes_gcm_256.v6 * sys.netipsec.tunnel.empty.v6 * sys.netpfil.pf.fragmentation.v6 * sys.netpfil.pf.pass_block.v6 * https://bugs.freebsd.org/240511 * 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 (updating net/scapy to 2.4.3 may fix this) * 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.or
12.1-PRE-RELEASE, 352114 is ok but 352202 is bad
Hi, After updating from 352114 to 352202 on 12/stable, 12.1-PRE-RELEASE, my kernel stopped booting. This one runs on Parallels VM. Looking at boot message, I seeswap init is passed. Then, after printing the following 2 lines, it doesn't proceed further. uhub0: 2 ports with 2 removables, self powered uhub1: 15 ports with 15 removables, self powered As 13-CURRENT with the last night's code boots okay, I suspect some merge error to the branch. Hiro ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
