[Bug 241581] PCIe passthrough is broken in QEMU 4 due to PCI Device ID conflict
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241581 Vincenzo Maffione changed: What|Removed |Added CC||vmaffi...@freebsd.org Assignee|b...@freebsd.org|vmaffi...@freebsd.org -- 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 243482] Link state change does not logged
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243482
Bug ID: 243482
Summary: Link state change does not logged
Product: Base System
Version: 12.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: t.wi...@m3connect.de
Hello,
Our System state:
FreeBSD M3CTESTLABO-SAG01 12.1-RELEASE-p1 FreeBSD 12.1-RELEASE-p1 GENERIC
amd64
Following Problem:
if we disconnect the LAN cable or shutdown the switchport, the system does not
logging the information about link state change e.g. Links igb0 goes down
(IFNET igb0 LINK_DOWN)
on the interface the state does not change into no carrier
igb0: flags=8843 metric 0 mtu 1500
description: PUBLIC
options=e527bb
ether ac:1f:6b:1a:88:ba
inet XXX.XXX.XXX.XXX netmask 0xff00 broadcast XXX.XXX.XXX.XXX
media: Ethernet autoselect (1000baseT )
status: active
nd6 options=29
in this situation it isn't possible to track the changes from the Link with
devd to handle something like e.g.
notify 0 {
match "system""IFNET";
match "subsystem" "(igb0)";
match "type""LINK_DOWN";
action "logger $subsystem is DOWN by devd";
};
notify 0 {
match "system""IFNET";
match "subsystem" "(igb0)";
match "type""LINK_UP";
action "logger $subsystem is UP by devd";
};
Network Adapter:
port 0xe000-0xe01f mem
0xdf40-0xdf47,0xdf48-0xdf483fff irq 16 at device 0.0 on pci1
If you need more information, please let me know
Regards
Toto
--
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 243482] Link state change does not logged
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243482 Toto changed: What|Removed |Added Alias||LinkStateIssue -- 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 234455] CPU frequency scaling fails for multiple cores
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455 Dave Green changed: What|Removed |Added CC||d...@fastmail.co.uk --- Comment #4 from Dave Green --- Still present in 12.1-RELEASE-p1 -- 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 234455] CPU frequency scaling fails for multiple cores
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455 --- Comment #5 from Conrad Meyer --- @Dave, did you try debug.acpi.disabled="thermal"? It seems bizarre that the default dev.cpu.0.freq is 800. Is that the case at boot, or was your initial description after running, say, powerd? It might be that Coffeelake does not really support est and needs Intel Speed Shift instead. That is not yet in tree but there is a work-in-progress patch: https://reviews.freebsd.org/D18028 @Erich, I suspect these are unrelated issues in that a different cpufreq driver is used on Zen (hwpstate) and Intel (est). But maybe there is some relation. I do not recommend powerd and would suggest disabling it. In fact, we should probably remove it from FreeBSD. It is extremely legacy and only really works correctly on ancient single core devices. I also don't recommend manual p-state setting via sysctl. Modern CPUs do a fantastic job of power saving with C states alone — P-state throttling doesn't get you much anymore. -- 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 234455] CPU frequency scaling fails for multiple cores
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455
--- Comment #6 from Dave Green ---
CPU is 800 at boot either with or without powerd.
Temperature is always stable at 25 degrees.
I'll retry debug.acpi.disabled="thermal" but I don't recall it having any
effect for 11.2-RELEASE.
If I comment out the conditional in cf_set_method() at kern/kern_cpu.c:291 then
both sysctl and powerd can be used to adjust the frequency.
>if (priority < sc->curr_priority) {
>CF_DEBUG("ignoring, curr prio %d less than %d\n", priority,
>sc->curr_priority);
>error = EPERM;
>goto out;
>}
--
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 234733] Setting CPU frequency with sysctl dev.cpu.0.fr slows a Ryzen 2700X down
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733 --- Comment #2 from Conrad Meyer --- Can both of you try: Adding 'debug.hwpstate_verbose="1"' in /boot/loader.conf and checking dmesg for boot-time messages about hwpstate? This can also be sysctl'd at runtime to see what gets logged when 'sysctl dev.cpu.0.freq=foo' is invoked, for example. Second, if possible can you share the output of 'acpidump -dt'? It will be fairly large and you might have to compress it to attach it to bugzilla. It should not contain especially sensitive information — it's BIOS data and code provided to the operating system to understand system devices. I'll add: the method hwpstate(4) uses to set the current p-state is documented on Zen PPR as: *** "Writes to this field cause the core to change to the indicated __non-boosted__ P-state number…" (emphasis added) *** So, e.g., writing P0 (unlimited) still disables boost, I guess. Interestingly, the documentation on the boost enable/disable bit (HWCR::CpbDis) also mentions boosted / non-boosted P-states: "If core performance boost is disabled while a core is in a boosted P-state, the core automatically transitions to the highest performance non-boosted P-state." So... perhaps hwpstate(4) should explicitly check and enable CPB (boost) when "P0" is selected. Or we could synthesize an extra P-state, e.g., "3701" which when selected sets P0 and also boost. IMO, that's more effort than it's worth because manual P-state setting is silly on these CPUs. Here's a test you could do to confirm. Set dev.cpu.0.freq=3700, or whatever the maximum is. Then run (needs root): 'cpucontrol -m 0xc0010015 /dev/cpuctl0'. This reads the HWCR MSR from CPU0. The output will look something like: MSR 0xc0010015: 0x 0x0911 If the bit:0x0200 is set, it indicates that CPB is *disabled*. If that bit is set, you could try: "cpucontrol -m '0xc0010015&=~0x0200' /dev/cpuctl0" and see if it restores boost-level performance. (I don't know if you would have to clear it on all CPUs, or if it is globally cleared by the cpu0 command.) -- 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 234733] Setting CPU frequency with sysctl dev.cpu.0.fr slows a Ryzen 2700X down
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733 --- Comment #3 from Conrad Meyer --- I tried the following test: $ cpuset -l 0 time sha1 <~200MBfile> (burn one result for caching, then repeat 3 trials) I got average 0.24 real, 0.22 user. You might pick a slightly larger file for bigger and more obvious differences at different steppings. Then I set CPBDis: cpucontrol -m '0xc0010015|=0x0200' /dev/cpuctl0 and repeated the tests; I got average 0.29 real, 0.26 user. I ran "cpucontrol -m '0xc0010015&=~0x0200' /dev/cpuctl0" and got 0.24/0.22 again. I also tried sysctl dev.cpu.0.freq=3400 (on my system, dev.cpu.0.freq_levels: 3400/3825 2800/2765 2200/1952). cpucontrol -m '0xc0010015' did not show CPBDis. Also, SHA1 timings remained ~0.24/0.22. I tried dev.cpu.0.freq=2800, waited a few seconds, and restored dev.cpu.0.freq=3400. cpucontrol -m '0xc0010015' still did not show CPBDis. SHA1 timings seemed to show the expected boosted performance. My CPU is a Zen1 Threadripper 1950x; perhaps this behavior is different on Zen+ (Ryzen 2xxx), or there is some difference due to BIOSes. But you might be interested in running the same tests and seeing what you find. -- 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 234455] CPU frequency scaling fails for multiple cores
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455 --- Comment #7 from Conrad Meyer --- I wonder where those bogus priorities are coming from, though. I thought I recall looking and seeing acpi_thermal as the only possible source, but I might be mistaken. -- 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 234455] CPU frequency scaling fails for multiple cores
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455 --- Comment #8 from Conrad Meyer --- Also: 800 at boot sounds like a BIOS bug. -- 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 243500] segfault in libcrypto at ssleay_rand_bytes ()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243500 Bug ID: 243500 Summary: segfault in libcrypto at ssleay_rand_bytes () Product: Base System Version: 11.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: adamrosas1...@gmail.com when building UnrealIRCd from source on FreeBSD 11.2, 11.3 or in a FreeNAS jail upon running the program segfaults, installing pkg openssl-1.1.1d and rebuilding fixes the segfault. Starting program: /usr/home/ircd/src/src/ircd Breakpoint 1, main (argc=1, argv=0x7fffeae0) at ircd.c:945 945 gettimeofday(&timeofday_tv, NULL); Current language: auto; currently minimal (gdb) n 946 timeofday = timeofday_tv.tv_sec; (gdb) n 948 safe_strdup(configfile, CONFIGFILE); (gdb) n 950 init_random(); /* needs to be done very early!! */ (gdb) n Program received signal SIGSEGV, Segmentation fault. 0x000800d0ee6e in ssleay_rand_bytes () from /lib/libcrypto.so.8 -- 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 242212] usr.sbin/mergemaster/mergemaster.sh: There is no logic to handle symbolic links
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242212
Yasuhiro KIMURA changed:
What|Removed |Added
Attachment #210786|0 |1
is obsolete||
--- Comment #8 from Yasuhiro KIMURA ---
Created attachment 210946
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=210946&action=edit
Updated patch file
* Change and/or fix some messages.
* Don't delete ${TEMPROOT} without confirmation when symbolic links are left in
it.
* Delete temp symbolic link when it is successfully installed.
So please review/test attached patch instead of original one.
--
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 243500] segfault in libcrypto at ssleay_rand_bytes ()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243500 Kubilay Kocak changed: What|Removed |Added CC||sect...@freebsd.org Keywords||crash, needs-qa Flags||maintainer-feedback?(sectea ||m...@freebsd.org) Status|New |Open -- 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 242212] usr.sbin/mergemaster/mergemaster.sh: There is no logic to handle symbolic links
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242212 Kubilay Kocak changed: What|Removed |Added Keywords||feature, needs-qa Severity|Affects Many People |Affects Some People Status|New |Open Flags||mfc-stable12?, ||mfc-stable11? -- 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 243453] Log duplication
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243453 --- Comment #1 from Michael --- Experimenting with different options from Google, I found a temporary solution to the problem. But it is not so logical. FreeBSD designers must do something about it! We modify the standard configuration file /etc/syslog.conf: $FreeBSD$ # # Spaces ARE valid field separators in this file. However, # other *nix-like systems still insist on using tabs as field # separators. If you are sharing this file between systems, you # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. # openvpn: /%regex 'ovpn[1-9]'/ !-ovpn1,ovpn2,ovpn3,ovpn4, . . . cut here (very! long string) . . . ,ovpn158 *.err;kern.warning;auth.notice;mail.crit/dev/console *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security auth.info;authpriv.info /var/log/auth.log mail.info /var/log/maillog cron.* /var/log/cron !-devd *.=debug/var/log/debug.log *.emerg * daemon.info /var/log/daemon.log # uncomment this to log all writes to /dev/console to /var/log/console.log # touch /var/log/console.log and chmod it to mode 600 before it will work #console.info /var/log/console.log # uncomment this to enable logging of all log messages to /var/log/all.log # touch /var/log/all.log and chmod it to mode 600 before it will work #*.*/var/log/all.log # uncomment this to enable logging to a remote loghost named loghost #*.*@loghost # uncomment these if you're running inn # news.crit /var/log/news/news.crit # news.err /var/log/news/news.err # news.notice /var/log/news/news.notice # Uncomment this if you wish to see messages produced by devd # !devd # *.>=notice/var/log/devd.log !* include /etc/syslog.d include /usr/local/etc/syslog.d -- 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"
