[Bug 193235] basename(3) potentially failing with ENOMEM, etc is not documented
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193235 Oleksandr Tymoshenko changed: What|Removed |Added CC||d...@freebsd.org Component|Documentation |Manual Pages Assignee|d...@freebsd.org |b...@freebsd.org Yuri Pankov changed: What|Removed |Added CC||yur...@freebsd.org --- Comment #1 from Yuri Pankov --- Note that basename(3) was reimplemented in FreeBSD 12, and correctly doesn't have any errors defined, so this only applies to 11.2/11-STABLE at the moment. -- 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 232838] syslogd(8) should auto-reload config files when they change
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232838 sig...@gmail.com changed: What|Removed |Added CC||sig...@gmail.com --- Comment #1 from sig...@gmail.com --- (In reply to Yuri Victorovich from comment #0) newsyslog doesn't "reload" its config files, it loads them every time it runs. It is run every hours by default. You're right that there is a discrepancy between newsyslog and syslogd there though. But most daemons do not reload their config files automatically and doing so would break expectations I would say. cron is a notable exception. -- 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 232800] Processes killed out of swap space
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232800 --- Comment #2 from teksim...@gmail.com --- (In reply to Mark Millard from comment #1) Thank you for your feedback. I've added vm.pageout_oom_seq=120 to sysctl.conf. Both of the following messages have been logged; Oct 30 23:08:20 host kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1143, size: 16384 Oct 30 23:16:52 host kernel: swap_pager: I/O error - pageout failed; blkno 477,size 69632, error 12 swap is filebacked; [user@host /var/log]$ cat /etc/fstab # DeviceMountpoint FStype Options DumpPass# ... md99noneswapsw,late,file=/usr/swap0 0 0 the swap file is in /usr which is the same fs as / (it was provisioned this way by the cloud provider.) I can roll back the vm to a 10.4 snapshot. I'm confident the issue wouldnt be present. The 10.4 install has been solid, and this began /immediately/ after the upgrade. Reboot 1 [user@host /var/log]$ sudo less all.log ... Oct 30 23:05:58 host kernel: Starting jails: Oct 30 23:08:20 host kernel: Oct 30 23:08:20 host kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1143, size: 16384 Oct 30 23:08:20 host last message repeated 2 times Oct 30 23:08:20 host kernel: pid 2532 (mysqld), uid 88, was killed: out of swap space Oct 30 23:08:20 host kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1143, size: 16384 Oct 30 23:08:20 host last message repeated 2 times Oct 30 23:08:20 host kernel: pid 791 (ntpd), uid 0, was killed: out of swap space Oct 30 23:08:20 host kernel: Oct 30 23:08:20 host kernel: pid 2532 (mysqld), uid 88, was killed: out of swap space Oct 30 23:08:20 host kernel: Oct 30 23:08:20 host kernel: pid 791 (ntpd), uid 0, was killed: out of swap space ... [user@host /var/log]$ uname -a FreeBSD host.domain.com 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 #0: Thu Sep 27 08:16:24 UTC 2018 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 [user@host /var/log]$ swapinfo Device 1K-blocks UsedAvail Capacity /dev/md99 524288 5296 518992 1% [user@host /var/log]$ uptime 11:13PM up 8 mins, 2 users, load averages: 0.06, 0.11, 0.08 [user@host /var/log]$ sudo service ntpd start Starting ntpd. [user@host /var/log]$ sudo jail -c sql sql: created [user@host /var/log]$ swapinfo Device 1K-blocks UsedAvail Capacity /dev/md99 52428859912 46437611% [user@host /var/log]$ jls JID IP Address Hostname Path 2 127.0.0.253 php.domain.com /usr/local/jails/php 3 127.0.0.254 www.domain.com /usr/local/jails/www 4 127.0.0.252 sql.domain.com /usr/local/jails/sql Reboot 2 [user@host /var/log]$ sudo less all.log Oct 30 23:16:50 host kernel: Starting jails: Oct 30 23:16:52 host kernel: Oct 30 23:16:52 host kernel: swap_pager: I/O error - pageout failed; blkno 445,size 131072, error 12 Oct 30 23:16:52 host kernel: swap_pager: I/O error - pageout failed; blkno 477,size 69632, error 12 Oct 30 23:16:52 host kernel: swap_pager: I/O error - pageout failed; blkno 494,size 8192, error 12 ... Oct 30 23:16:52 host kernel: swap_pager: I/O error - pageout failed; blkno 946,size 69632, error 12 Oct 30 23:16:52 host kernel: swap_pager: I/O error - pageout failed; blkno 963,size 36864, error 12 Oct 30 23:16:52 host kernel: swap_pager: I/O error - pageout failed; blkno 972,size 12288, error 12 Oct 30 23:18:12 host kernel: pid 2532 (mysqld), uid 88, was killed: out of swap space Oct 30 23:18:12 host kernel: Oct 30 23:18:12 host kernel: pid 2532 (mysqld), uid 88, was killed: out of swap space [user@host ~]$ uptime 11:18PM up 2 mins, 1 user, load averages: 0.23, 0.25, 0.11 [user@host ~]$ jls JID IP Address Hostname Path 2 127.0.0.253 php.domain.com /usr/local/jails/php 3 127.0.0.254 www.domain.com /usr/local/jails/www [user@host ~]$ swapinfo Device 1K-blocks UsedAvail Capacity /dev/md99 524288 5752 518536 1% [user@host ~]$ sudo jail -c sql sql: created [user@host ~]$ swapinfo Device 1K-blocks UsedAvail Capacity /dev/md99 52428854272 47001610% -- 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 232838] syslogd(8) should auto-reload config files when they change
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232838 Bug ID: 232838 Summary: syslogd(8) should auto-reload config files when they change Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: y...@freebsd.org Currently syslogd(8) doesn't reload its config files when they change. Reasons for the change: 1. When new packages are installed and place new config files, these files aren't automatically enabled which can always be used as an argument against even using such config files, like it was done in this bug: bug#232813. 2. newsyslog(8) does automatically reload its configuration when it changes, but syslogd(8) doesn't, which isn't logical because they work in the same field (manage logs). So it appears that it would be much more natural and convenient if syslog(8) would auto-load/unload config files when they are added/installed/uninstalled. -- 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 207359] head -r339076 TARGET_ARCH=powerpc64 via powerpc64-gcc : some or all c++ exceptions unbounded loop in _Unwind_RaiseException
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207359 Mark Millard changed: What|Removed |Added Summary|projects/clang380-import|head -r339076 |for TARGET_ARCH=powerpc64 |TARGET_ARCH=powerpc64 via |via powerpc64-gcc : c++ |powerpc64-gcc : some or all |exceptions unbounded loop |c++ exceptions unbounded |in _Unwind_RaiseException |loop in |(9 line program)|_Unwind_RaiseException -- 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 207359] projects/clang380-import for TARGET_ARCH=powerpc64 via powerpc64-gcc : c++ exceptions unbounded loop in _Unwind_RaiseException (9 line program)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207359 --- Comment #11 from Mark Millard --- (In reply to Mark Millard from comment #10) Testing with a build based on head -r339076 shows this still happens. Both clang code generation and devel/powerpc64-xtoolchain-gcc code generation have examples of hitting the mishandling in libgcc_s.so and so __Unwind_RaiseException looping on the same stack frame over and over. -- 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 232458] jevents: Program terminated with signal 11, Segmentation fault when build word of 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232458 --- Comment #1 from iron.ud...@gmail.com --- I did clean install of 12-BETA2 and tried run buildworld of 12-STABLE: ===> lib/ofed/libopensm (all) ===> lib/libpcap (all) ===> lib/libpjdlog (all) ===> lib/libpmc (all) ./pmu-events/jevents "x86" /usr/src/lib/libpmc/pmu-events/arch libpmc_events.c *** Error code 127 Stop. make[5]: stopped in /usr/src/lib/libpmc *** Error code 1 Stop. make[4]: stopped in /usr/src/lib *** Error code 1 -- 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 232835] [gmirror] gmirror fails to recover from degraded mirror sets in some circumstances (2/n)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232835 Conrad Meyer changed: What|Removed |Added CC|g...@freebsd.org| Assignee|b...@freebsd.org|g...@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 232835] [gmirror] gmirror fails to recover from degraded mirror sets in some circumstances (2/n)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232835 Bug ID: 232835 Summary: [gmirror] gmirror fails to recover from degraded mirror sets in some circumstances (2/n) Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: c...@freebsd.org CC: g...@freebsd.org, ma...@freebsd.org Depends on: 232671 Blocks: 232683, 232684 This is related to bug 232671 , but not identical. Here is the example scenario: 1. I start with a GMIRROR with three ACTIVE disks (sc_ndisks = md_all = 3) 2. I essentially disconnect one of the disks 3. The remaining mirrors lower md_all to 2 and the syncid / generation gets bumped 4. I reboot, and the removed disk reappears 5. Geom tastes the stale removed disk first, and populates sc_ndisks from its md_all (3) 6. The two valid mirrors are tasted afterwards and the gmirror rejects both as having invalid metadata (md_all=2), despite their having a higher generation / sync id The problem is basically that gmirror doesn't "upgrade" its metadata to the newest valid mirrorset it finds -- it just sticks with whatever it found first. I think the solution is being a bit clever about detecting the latest mirror generation while a gmirror is still in the STARTING state; and also perhaps a little more clever about when we transition from STARTING to RUNNING (at which point a newer generation mirror showing up means we have corruption). Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232671 [Bug 232671] [gmirror] gmirror fails to recover from degraded mirror sets in some circumstances https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232683 [Bug 232683] [gmirror] gmirror could provide much better administrative introspection into decision-making processes https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232684 [Bug 232684] [gmirror] gmirror overly aggressive provider destruction -- 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 169339] panic while " : > /etc/123"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169339 w.schwarzenf...@utanet.at changed: What|Removed |Added Resolution|--- |Overcome By Events Assignee|b...@freebsd.org|w.schwarzenf...@utanet.at Status|Open|Closed -- 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 169339] panic while " : > /etc/123"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169339 w.schwarzenf...@utanet.at changed: What|Removed |Added CC||w.schwarzenf...@utanet.at --- Comment #5 from w.schwarzenf...@utanet.at --- Stable 8.3 is long "over". I close this. -- 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 232829] Kernel debugger only reads .dynsym even if .symtab exists
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232829 --- Comment #2 from Conrad Meyer --- A related but tangential is GNU hash support for symbol lookup by name and/or linking. amd64 .ko's are weird and not "finished" objects, so binutils doesn't generate a ".gnu.hash" section for them, but there's no reason we couldn't do so in elftoolchain or some trivial build tool. -- 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 232829] Kernel debugger only reads .dynsym even if .symtab exists
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232829
--- Comment #1 from Conrad Meyer ---
Seems like a good idea to me.
On my local amd64 kernels, I see SYMTAB in the stripped binary (objdump -x) and
not in the corresponding .debug file in /usr/lib/debug.
(Conditional on MK_DEBUG_FILES, bsd.lib.mk splits full objects, including
kernels, into stripped and debuginfo with:
296 ${SHLIB_NAME}: ${SHLIB_NAME_FULL} ${SHLIB_NAME}.debug
297 ${OBJCOPY} --strip-debug --add-gnu-debuglink=${SHLIB_NAME}.debug \
298 ${SHLIB_NAME_FULL} ${.TARGET}
...
303 ${SHLIB_NAME}.debug: ${SHLIB_NAME_FULL}
304 ${OBJCOPY} --only-keep-debug ${SHLIB_NAME_FULL} ${.TARGET}
Apparently --strip-debug leaves SYMTAB if one was present.)
--
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 120780] [sound] [snd_hda] snd_hda doesn't work on Dell Latitutude D530
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=120780 s...@troutmask.apl.washington.edu changed: What|Removed |Added CC||s...@troutmask.apl.washingto ||n.edu --- Comment #5 from s...@troutmask.apl.washington.edu --- This should be closed. -- 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 232829] Kernel debugger only reads .dynsym even if .symtab exists
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232829 Alex Richardson changed: What|Removed |Added Severity|Affects Only Me |Affects Some People -- 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 232829] Kernel debugger only reads .dynsym even if .symtab exists
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232829 Bug ID: 232829 Summary: Kernel debugger only reads .dynsym even if .symtab exists Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: arichard...@freebsd.org The .symtab section contains all symbols (but may be stripped so is not necessarily present) whereas .dynsym only contains the exported symbols (i.e. not static). This causes backtraces to report some_other_function+large_offset if the backtrace pc is inside static function. If .symtab is present, link_elf_search_symbol() should be checking .symtab instead of .dynsymtab. However, it seems like ef->ddbsymtab always points to .dynsym and since I am not familiar with that code I couldn't see an easy way of using .symtab instead if it is available. -- 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 232828] tools/tools/netmap/pkt-gen can not be built
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232828 Lev A. Serebryakov changed: What|Removed |Added 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 232828] tools/tools/netmap/pkt-gen can not be built
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232828 Lev A. Serebryakov changed: What|Removed |Added Summary|tools/tools/netmap can not |tools/tools/netmap/pkt-gen |be built|can not be built -- 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 232828] tools/tools/netmap can not be built
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232828 Bug ID: 232828 Summary: tools/tools/netmap can not be built Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: l...@freebsd.org On both 11.2-STABLE and 13-CURRENT "pkt-gen" from tools/tools/netmap can not be built: cc -O2 -pipe -Werror -Wall -Wextra -g -std=gnu99 -fstack-protector-strong -Qunused-arguments -Qunused-arguments -g -std=gnu99 -fstack-protector-strong -Qunused-arguments -Qunused-arguments -c /data/src/tools/tools/netmap/pkt-gen.c -o pkt-gen.o /data/src/tools/tools/netmap/pkt-gen.c:650:19: error: taking address of packed member 'ip' of class or structure 'pkt' may result in an unaligned pointer value [-Werror,-Waddress-of-packed-member] struct ip *ip = >ip; ^~~ /data/src/tools/tools/netmap/pkt-gen.c:651:24: error: taking address of packed member 'udp' of class or structure 'pkt' may result in an unaligned pointer value [-Werror,-Waddress-of-packed-member] struct udphdr *udp = >udp; ^~~~ /data/src/tools/tools/netmap/pkt-gen.c:745:8: error: taking address of packed member 'ip' of class or structure 'pkt' may result in an unaligned pointer value [-Werror,-Waddress-of-packed-member] ip = >ip; ^~~ /data/src/tools/tools/netmap/pkt-gen.c:762:9: error: taking address of packed member 'udp' of class or structure 'pkt' may result in an unaligned pointer value [-Werror,-Waddress-of-packed-member] udp = >udp; ^~~~ 4 errors generated. *** Error code 1 -- 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 232825] dtrace can not be built into kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232825 Bug ID: 232825 Summary: dtrace can not be built into kernel Product: Base System Version: 11.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: l...@freebsd.org On 11.2-STABLE (r )file "sys/cddl/contrib/opensolaris/uts/common/dtrace/dtrace_xoroshiro128_plus.c" is not included in "sys/conf/files" and kernel with device dtrace device dtraceall can not be built (linked) with diagnostic: dtrace.o: In function `dtrace_dif_subr': /usr/src/sys/cddl/contrib/opensolaris/uts/common/dtrace/dtrace.c:4142: undefined reference to `dtrace_xoroshiro128_plus_next' dtrace.o: In function `dtrace_state_create': /usr/src/sys/cddl/contrib/opensolaris/uts/common/dtrace/dtrace.c:14544: undefined reference to `dtrace_xoroshiro128_plus_jump' This file is included into "sys/modules/dtrace/Makefile". -- 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 228768] EARLY_AP_STARTUP causes panic on amd machines
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228768 John Baldwin changed: What|Removed |Added Status|New |In Progress Assignee|b...@freebsd.org|j...@freebsd.org --- Comment #5 from John Baldwin --- Created attachment 198774 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=198774=edit lock_delay.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 228768] EARLY_AP_STARTUP causes panic on amd machines
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228768 John Baldwin changed: What|Removed |Added CC||k...@freebsd.org, ||m...@freebsd.org --- Comment #4 from John Baldwin --- Oh, I think I have seen this once before. The issue is that the mtx_lock_spin() code tries to use DELAY(1) and DELAY() is trying to use the "clock_lock" in getit(). In your case, 'tsc_is_invariant' isn't true so DELAY() in sys/x86/x86/delay.c isn't using the TSC. I think the error is probably that we shouldn't be using DELAY(1) in our mutex code as it is too high level and/or we should special case DELAY(1) (vs DELAY(n)). Older versions of FreeBSD would map DELAY(1) to just 'inb(0x84)' without talking to the 8254 at all. It looks like i8254_delay() already does that when inside of KDB. Also, checking for tsc_is_invariant in DELAY is probably overly-correct. We aren't going to change P-states while we are spinning since we are actively spinning on the CPU. The worst that might happen is that if the CPU were running at a lower clock, we might wait too long. Given how DELAY is used, that's probably better than falling back to a slow timecounter with locks, etc. -- 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 232800] Processes killed out of swap space
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232800 Mark Millard changed: What|Removed |Added CC||marklmi26-f...@yahoo.com --- Comment #1 from Mark Millard --- [These notes are generated from activity with head. They in places presume that vm.pageout_oom_seq is available in 11.2 but that might not be the case. As I understand, the other aspects of the below notes apply.] Unfortunately some messages about "out of swap" can be misnomers, more tied to low free RAM after enough attempts to gain more free RAM (so after enough time). Real "out of swap" conditions tend to also have messages similar to: Aug 5 17:54:01 sentinel kernel: swap_pager_getswapspace(32): failed If you are not seeing such messages, then it is likely that the mount of swap space still free is not the actual thing driving the kills. Poor I/O performance for paging and/or swapping can contribute to the kills happening. But I've no clue if such is an issue for your context. The default vm.pageout_oom_seq=12 can be increased to increase how long a low free RAM condition is tolerated. (It increases how many attempts to free RAM are made first.) I assign vm.pageout_oom_seq in /etc/sysctl.conf --but that may not be the best for your context. vm.pageout_oom_seq=120 has proved useful. In some extreme situations (buildworld buildkernel in a low RAM, slow context, including long I/O latencies) vm.pageout_oom_seq=1024 or more has been used to avoid kills when there was plenty of swap space. -- 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 231827] unzip sync with NetBSD upstream
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231827 Dag-Erling Smørgrav changed: What|Removed |Added Assignee|d...@freebsd.org |b...@freebsd.org --- Comment #1 from Dag-Erling Smørgrav --- I don't maintain unzip. -- 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 228768] EARLY_AP_STARTUP causes panic on amd machines
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228768 --- Comment #3 from Roger Hammerstein --- (In reply to John Baldwin from comment #2) With DDB and WITNESS, MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic3 irqs 24-47 on motherboard ioapic0 irqs 0-23 on motherboard ioapic1 irqs 48-54 on motherboard ioapic2 irqs 56-62 on motherboard lapic: Divisor 2, Frequency 99737090 Hz cpu0 BSP: ID: 0x VER: 0x80050010 LDR: 0x DFR: 0x lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff timer: 0x000100ef therm: 0x0001 err: 0x00f0 pmc: 0x00010400 AMD ext features: 0x00010003 AMD elvt0: 0x0001 SMP: AP CPU FtKernel page fault with the following non-sleepable locks held: exclusive spin mutex clk (clk) r = 0 (0x81e70d78) locked @ /usr/src/sys/x86/isa/clock.c:209 exclusive spin mutex ap boot (ap boot) r = 0 (0x81fc4788) locked @ /usr/src/sys/x86/x86/mp_x86.c:1013 stack backtrace: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0xf80080054000 fault code = supervisor read instruction, protection violation instruction pointer = 0x20:0xf80080054000 stack pointer = 0x28:0xfe0002a8f8b0 frame pointer = 0x28:0x0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 11 (idle: cpu1) [ thread pid 11 tid 14 ] Stopped at 0xf80080054000 db> trace Tracing pid 11 tid 14 td 0xf80080054580 ??() at 0xf80080054000 db> Any other commands to run? db> show locks exclusive spin mutex clk (clk) r = 0 (0x81e70d78) locked @ /usr/src/sys/x86/isa/clock.c:209 exclusive spin mutex ap boot (ap boot) r = 0 (0x81fc4788) locked @ /usr/src/sys/x86/x86/mp_x86.c:1013 db> db> show alllocks Process 0 (kernel) thread 0x81e8a3e0 (10) exclusive sleep mutex Giant (Giant) r = 0 (0x818020c0) locked @ /usr/src/sys/kern/kern_module.c:116 db> db> bt Tracing pid 11 tid 14 td 0xf80080054580 ??() at 0xf80080054000 db> db> ps pid ppid pgrp uid state wmesg wchan cmd 12 0 0 0 WL (threaded) [intr] 18 I [swi6: task queue] 19 I [swi6: Giant taskq] 100011 I [swi5: fast taskq] 11 0 0 0 RL (threaded) [idle] 13 CanRun [idle: cpu0] 14 CanRun [idle: cpu1] 15 CanRun [idle: cpu2] 16 CanRun [idle: cpu3] 1 0 0 0 ?L [kernel] 10 0 0 0 RL [audit] 0 0 0 0 RLs (threaded) [kernel] 10 Run CPU 0 [swapper] 17 RunQ[aiod_kick taskq] 100010 RunQ[thread taskq] 100012 RunQ[config_0] 100013 RunQ[kqueue_ctx taskq] db> db> show pcpu cpuid= 1 dynamic pcpu = 0xfe0081100ec0 curthread= 0xf80080054580: pid 11 tid 14 "idle: cpu1" curpcb = 0 fpcurthread = none idlethread = 0xf80080054580: tid 14 "idle: cpu1" curpmap = 0x81e8aaa8 tssp = 0x81fb5e88 commontssp = 0x81fb5e88 rsp0 = 0x0 gs32p= 0x81fbcac0 ldt = 0x81fbcb00 tss = 0x81fbcaf0 curvnet = 0 spin locks held: exclusive spin mutex clk (clk) r = 0 (0x81e70d78) locked @ /usr/src/sys/x86/isa/clock.c:209 exclusive spin mutex ap boot (ap boot) r = 0 (0x81fc4788) locked @ /usr/src/sys/x86/x86/mp_x86.c:1013 db> db> show reg cs0x20 ds0x28 ll+0x7 es0x28 ll+0x7 fs0x28 ll+0x7 gs0x28 ll+0x7 ss0x28 ll+0x7 rax 0xf80080054580 rcx 0x5a8 ll+0x587 rdx 0x811b4939 do_execve.fexecv_proc_title+0x98a5 rbx 0 rsp 0xfe0002a8f8b0 rbp 0 rsi0x8 rdi 0x81d93998 w_mtx r8 0x811bd5a6 r90x6c ll+0x4b r10 0xf800dfd79600 r11 0 r12 0x81dd7718 r13
[Bug 232800] Processes killed out of swap space
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232800 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 232807] contrib/tzdata needs to be updated
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232807 --- Comment #2 from Kristof Provost --- Philip already imported the update to head in r339848. It'll likely be merged into stable/12 in the next day or two. -- 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 232807] contrib/tzdata needs to be updated
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232807 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org Assignee|b...@freebsd.org|phi...@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 232807] contrib/tzdata needs to be updated
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232807 Mateusz Piotrowski <0...@freebsd.org> changed: What|Removed |Added CC||0...@freebsd.org Status|New |Open --- Comment #1 from Mateusz Piotrowski <0...@freebsd.org> --- I think it was done in r339848. -- 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 232807] contrib/tzdata needs to be updated
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232807 Bug ID: 232807 Summary: contrib/tzdata needs to be updated Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: arr...@freebsd.org At 28 October Volgograd city (Russia) switched from MSK timezone to MSK+1. This change is already present in the latest tzdata release 2018g. Can we get our contrib/tzdata updated, so clock on my laptop are again correct? -- 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"
