[Bug 233699] [update] libutil/imsg api proposal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233699 Mark Linimon changed: What|Removed |Added Keywords||patch -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233682] 12.0-RC2 - /etc/rc.d/devd takes VERY long at boot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233682 Mark Linimon changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233699] [update] libutil/imsg api proposal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233699 --- Comment #1 from David Carlier --- Created attachment 199722 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=199722=edit Differential to update to 2017's version -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233699] [update] libutil/imsg api proposal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233699 David Carlier changed: What|Removed |Added Summary|[updte] libutil/imsg api|[update] libutil/imsg api |proposal|proposal -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233683] IPv6 ND neighbor solicitation messages fail to arrive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233683 --- Comment #2 from Philip Homburg --- I have a setup with a tp-link running openwrt as router, as small switch behind the wired ethernet ports of the tp-link and then a few freebsd hosts. One recently built ryzen2 system has an re0 interface. This system works perfectly fine under 11.2 and fails under 12.0 betas and RC1/RC2. With boot environments I can easily switch between the two versions. When I reported this bug, I just upgraded a Thinkpad x201 (em0 interface) to RC2. The thinkpad didn't report any neighbor solicitations even with tcpdump. At the same time, on the tplink they were visible in tcpdump. Also a ping6 from the ryzen2 system (running 11.2) to the thinkpad failed. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233683] IPv6 ND neighbor solicitation messages fail to arrive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233683 Bjoern A. Zeeb changed: What|Removed |Added CC||b...@freebsd.org --- Comment #1 from Bjoern A. Zeeb --- How do you determine they fail to arrive? Do you have a trace from other hosts? No filters in the network? In these cases, which NIC/driver are you using? What happens if you turn on PROMISC/MONITOR mode on the interface? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233693] [PowerPC64] Powerd unable to change cpu frequency
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233693 Conrad Meyer changed: What|Removed |Added Assignee|b...@freebsd.org|powe...@freebsd.org CC||c...@freebsd.org --- Comment #2 from Conrad Meyer --- It doesn't fix this issue, but I suspect there is an off-by-one bug in pmcr_set(): --- a/sys/powerpc/cpufreq/pmcr.c +++ b/sys/powerpc/cpufreq/pmcr.c @@ -189,7 +190,7 @@ pmcr_set(device_t dev, const struct cf_setting *set) if (set == NULL) return (EINVAL); - if (set->spec[0] < 0 || set->spec[0] > npstates) + if (set->spec[0] < 0 || set->spec[0] >= npstates) return (EINVAL); pmcr = ((long)pstate_ids[set->spec[0]] << PMCR_LOWERPS_SHIFT) & -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 231577] [PATCH] advice in sys/i386/i386/pmap.c is wrong
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231577 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: kib Date: Sat Dec 1 16:43:19 UTC 2018 New revision: 341374 URL: https://svnweb.freebsd.org/changeset/base/341374 Log: Correct the tunable name in the message. Submitted by: Andre Albsmeier PR: 231577 MFC after:1 week Changes: head/sys/arm/arm/pmap-v6.c head/sys/i386/i386/pmap.c -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 200663] zfs allow/unallow doesn't show numeric UID when the ID no longer exists in the password file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200663 Yuri Pankov changed: What|Removed |Added CC|yur...@yuripv.net |yur...@freebsd.org --- Comment #8 from Yuri Pankov --- Unfortunately, it's still waiting to be integrated in openzfs: https://github.com/openzfs/openzfs/pull/690 I wonder if I should just go with a FreeBSD review instead. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233693] [PowerPC64] Powerd unable to change cpu frequency
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233693 --- Comment #1 from Sean Bruno --- Created attachment 199712 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=199712=edit Kernel Config being used on this machine Just in case I'm missing something obvious to enable this support, I'm attaching the kernel config being used on this machine. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233693] [PowerPC64] Powerd unable to change cpu frequency
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233693 Bug ID: 233693 Summary: [PowerPC64] Powerd unable to change cpu frequency Product: Base System Version: CURRENT Hardware: powerpc OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: sbr...@freebsd.org The Tyan Power8 machines seem to need some kind of tweak to allow any powerd functionality. Starting powerd simply emits this repeatedly on the console: pmcr0: set freq failed, err 22 pmcr1: set freq failed, err 22 pmcr2: set freq failed, err 22 pmcr3: set freq failed, err 22 pmcr0: set freq failed, err 22 pmcr1: set freq failed, err 22 pmcr2: set freq failed, err 22 pmcr3: set freq failed, err 22 pmcr(8) seems to be detecting the following: r...@pylon.nyi:~ # sysctl dev.pmcr dev.pmcr.3.freq_settings: 4322/-1 4289/-1 4256/-1 4222/-1 4189/-1 4156/-1 4123/-1 4089/-1 4056/-1 4023/-1 3990/-1 3956/-1 3923/-1 3890/-1 3857/-1 3823/-1 3790/-1 3757/-1 3724/-1 3690/-1 3657/-1 3624/-1 3591/-1 3557/-1 3524/-1 3491/-1 3458/-1 3424/-1 3391/-1 3358/-1 3325/-1 3291/-1 3258/-1 3225/-1 3192/-1 3158/-1 3125/-1 3092/-1 3059/-1 3025/-1 2992/-1 2959/-1 2926/-1 2892/-1 2859/-1 2826/-1 2793/-1 2759/-1 2726/-1 2693/-1 2660/-1 2626/-1 2593/-1 2560/-1 2527/-1 2493/-1 2460/-1 2427/-1 2394/-1 2360/-1 2327/-1 2294/-1 2261/-1 2227/-1 2194/-1 2161/-1 2128/-1 2094/-1 2061/-1 dev.pmcr.3.%parent: cpu3 dev.pmcr.3.%pnpinfo: dev.pmcr.3.%location: dev.pmcr.3.%driver: pmcr dev.pmcr.3.%desc: Power Management Control Register dev.pmcr.2.freq_settings: 4322/-1 4289/-1 4256/-1 4222/-1 4189/-1 4156/-1 4123/-1 4089/-1 4056/-1 4023/-1 3990/-1 3956/-1 3923/-1 3890/-1 3857/-1 3823/-1 3790/-1 3757/-1 3724/-1 3690/-1 3657/-1 3624/-1 3591/-1 3557/-1 3524/-1 3491/-1 3458/-1 3424/-1 3391/-1 3358/-1 3325/-1 3291/-1 3258/-1 3225/-1 3192/-1 3158/-1 3125/-1 3092/-1 3059/-1 3025/-1 2992/-1 2959/-1 2926/-1 2892/-1 2859/-1 2826/-1 2793/-1 2759/-1 2726/-1 2693/-1 2660/-1 2626/-1 2593/-1 2560/-1 2527/-1 2493/-1 2460/-1 2427/-1 2394/-1 2360/-1 2327/-1 2294/-1 2261/-1 2227/-1 2194/-1 2161/-1 2128/-1 2094/-1 2061/-1 dev.pmcr.2.%parent: cpu2 dev.pmcr.2.%pnpinfo: dev.pmcr.2.%location: dev.pmcr.2.%driver: pmcr dev.pmcr.2.%desc: Power Management Control Register dev.pmcr.1.freq_settings: 4322/-1 4289/-1 4256/-1 4222/-1 4189/-1 4156/-1 4123/-1 4089/-1 4056/-1 4023/-1 3990/-1 3956/-1 3923/-1 3890/-1 3857/-1 3823/-1 3790/-1 3757/-1 3724/-1 3690/-1 3657/-1 3624/-1 3591/-1 3557/-1 3524/-1 3491/-1 3458/-1 3424/-1 3391/-1 3358/-1 3325/-1 3291/-1 3258/-1 3225/-1 3192/-1 3158/-1 3125/-1 3092/-1 3059/-1 3025/-1 2992/-1 2959/-1 2926/-1 2892/-1 2859/-1 2826/-1 2793/-1 2759/-1 2726/-1 2693/-1 2660/-1 2626/-1 2593/-1 2560/-1 2527/-1 2493/-1 2460/-1 2427/-1 2394/-1 2360/-1 2327/-1 2294/-1 2261/-1 2227/-1 2194/-1 2161/-1 2128/-1 2094/-1 2061/-1 dev.pmcr.1.%parent: cpu1 dev.pmcr.1.%pnpinfo: dev.pmcr.1.%location: dev.pmcr.1.%driver: pmcr dev.pmcr.1.%desc: Power Management Control Register dev.pmcr.0.freq_settings: 4322/-1 4289/-1 4256/-1 4222/-1 4189/-1 4156/-1 4123/-1 4089/-1 4056/-1 4023/-1 3990/-1 3956/-1 3923/-1 3890/-1 3857/-1 3823/-1 3790/-1 3757/-1 3724/-1 3690/-1 3657/-1 3624/-1 3591/-1 3557/-1 3524/-1 3491/-1 3458/-1 3424/-1 3391/-1 3358/-1 3325/-1 3291/-1 3258/-1 3225/-1 3192/-1 3158/-1 3125/-1 3092/-1 3059/-1 3025/-1 2992/-1 2959/-1 2926/-1 2892/-1 2859/-1 2826/-1 2793/-1 2759/-1 2726/-1 2693/-1 2660/-1 2626/-1 2593/-1 2560/-1 2527/-1 2493/-1 2460/-1 2427/-1 2394/-1 2360/-1 2327/-1 2294/-1 2261/-1 2227/-1 2194/-1 2161/-1 2128/-1 2094/-1 2061/-1 dev.pmcr.0.%parent: cpu0 dev.pmcr.0.%pnpinfo: dev.pmcr.0.%location: dev.pmcr.0.%driver: pmcr dev.pmcr.0.%desc: Power Management Control Register dev.pmcr.%parent: -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233682] 12.0-RC2 - /etc/rc.d/devd takes VERY long at boot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233682 Bug ID: 233682 Summary: 12.0-RC2 - /etc/rc.d/devd takes VERY long at boot Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: verma...@interia.pl The /etc/rc.d/devd takes VERY long at the boot (waiting for something?). This was not the case in 11.2-RELEASE. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233683] IPv6 ND neighbor solicitation messages fail to arrive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233683 Bug ID: 233683 Summary: IPv6 ND neighbor solicitation messages fail to arrive Product: Base System Version: 12.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: pch-freebsd-bug...@u-1.phicoh.com On 12.0-RC2 (and earlier) after a while, IPv6 ND neighbor solicitation messages fail to arrive. I guess it is a bug in multicast filtering. But I have no way to find out. Result is loss of IPv6 connectivity. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
