[Bug 196585] Regression in nsupdate, vendor patch available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196585 Andre Albsmeier changed: What|Removed |Added Status|New |Closed Resolution|--- |Overcome By Events -- 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 216606] kernel crashes early in pmap_map when pxe booted with rootfs in memory
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216606 Mark Linimon changed: What|Removed |Added CC|freebsd-i...@freebsd.org| 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 216610] TCP connections stuck forever in FIN_WAIT2 using IPFW
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216610 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-i...@freebsd.org CC|freebsd-am...@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 216611] feature request: add SUIDDIR In GENERIC kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216611 Mark Linimon changed: What|Removed |Added CC|freebsd-am...@freebsd.org | Summary|SUIDDIR In GENERIC kernel |feature request: add ||SUIDDIR In GENERIC kernel -- 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 216613] VIMAGE and TCP_RFC7413 panic: CURVNET_SET at /usr/src/sys/netinet/tcp_fastopen.c:270 tcp_fastopen_autokey_callout() curvnet=0 vnet=0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216613 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org CC|freebsd-am...@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 204340] [panic] nfsd, em, msix, fatal trap 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #21 from Rick Macklem --- Oh, and if you get a crash when shutting down the nfsd threads via "kill -USR1 ", then let us know, since something is still broken. (If you are curious, the "(master)" nfsd is the one that gets new TCP connections and it must stop doing that before the kernel threads are terminated. Otherwise you can easily get a socket upcall after the data structures have been free'd.) rick -- You are receiving this mail because: You are on the CC list 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 204340] [panic] nfsd, em, msix, fatal trap 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #20 from Rick Macklem --- Well, you should never kill the nfsd with SIGKILL. The way that is intended to be "safe" is to send SIGUSR1 to the "(master)" nfsd. It will shut things down and kill off the other threads. I'm not sure that I know of any way to make SIGKILL safe. I'm pretty sure "man nfsd" says this, but maybe it needs more emphasis? I also believe that /etc/rc.d/nfsd does this correctly. rick -- You are receiving this mail because: You are on the CC list 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 216613] VIMAGE and TCP_RFC7413 panic: CURVNET_SET at /usr/src/sys/netinet/tcp_fastopen.c:270 tcp_fastopen_autokey_callout() curvnet=0 vnet=0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216613 --- Comment #3 from alex.dei...@gmail.com --- Created attachment 179440 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179440&action=edit DDB show all vnets -- 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 216613] VIMAGE and TCP_RFC7413 panic: CURVNET_SET at /usr/src/sys/netinet/tcp_fastopen.c:270 tcp_fastopen_autokey_callout() curvnet=0 vnet=0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216613 --- Comment #2 from alex.dei...@gmail.com --- Unread portion of the kernel message buffer: panic: CURVNET_SET at /usr/src/sys/netinet/tcp_fastopen.c:270 tcp_fastopen_autokey_callout() curvnet=0 vnet=0 cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0456d9e7e0 vpanic() at vpanic+0x186/frame 0xfe0456d9e860 panic() at panic+0x43/frame 0xfe0456d9e8c0 tcp_fastopen_autokey_callout() at tcp_fastopen_autokey_callout+0x11b/frame 0xfe0456d9e900 softclock_call_cc() at softclock_call_cc+0x156/frame 0xfe0456d9e9b0 softclock() at softclock+0x94/frame 0xfe0456d9e9e0 intr_event_execute_handlers() at intr_event_execute_handlers+0x20f/frame 0xfe0456d9ea20 ithread_loop() at ithread_loop+0xc6/frame 0xfe0456d9ea70 fork_exit() at fork_exit+0x85/frame 0xfe0456d9eab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe0456d9eab0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KDB: enter: panic -- 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 216613] VIMAGE and TCP_RFC7413 panic: CURVNET_SET at /usr/src/sys/netinet/tcp_fastopen.c:270 tcp_fastopen_autokey_callout() curvnet=0 vnet=0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216613 --- Comment #1 from alex.dei...@gmail.com --- Created attachment 179439 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179439&action=edit text core dump -- 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 216613] VIMAGE and TCP_RFC7413 panic: CURVNET_SET at /usr/src/sys/netinet/tcp_fastopen.c:270 tcp_fastopen_autokey_callout() curvnet=0 vnet=0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216613
Bug ID: 216613
Summary: VIMAGE and TCP_RFC7413 panic: CURVNET_SET at
/usr/src/sys/netinet/tcp_fastopen.c:270
tcp_fastopen_autokey_callout() curvnet=0 vnet=0
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: kern
Assignee: freebsd-bugs@FreeBSD.org
Reporter: alex.dei...@gmail.com
CC: freebsd-am...@freebsd.org
CC: freebsd-am...@freebsd.org
Created attachment 179438
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179438&action=edit
kernel config
The most recent CURRENT [r312928] with enabled kernel options VIMAGE and
TCP_RFC7413 panics spontaneously:
(kgdb) where
#0 doadump (textdump=0) at pcpu.h:222
#1 0x803a152b in db_dump (dummy=, dummy2=, dummy3=,
dummy4=) at /usr/src/sys/ddb/db_command.c:546
#2 0x803a132f in db_command (cmd_table=) at
/usr/src/sys/ddb/db_command.c:453
#3 0x803a10a4 in db_command_loop () at
/usr/src/sys/ddb/db_command.c:506
#4 0x803a40ff in db_trap (type=, code=) at /usr/src/sys/ddb/db_main.c:248
#5 0x80b171e3 in kdb_trap (type=, code=, tf=)
at /usr/src/sys/kern/subr_kdb.c:654
#6 0x80f77bc9 in trap (frame=0xfe0456d9e710) at
/usr/src/sys/amd64/amd64/trap.c:537
#7 0x80f5a971 in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:236
#8 0x80b1690b in kdb_enter (why=0x814cc5c0 "panic", msg=) at cpufunc.h:63
#9 0x80acbd13 in vpanic (fmt=,
ap=0xfe0456d9e8a0) at /usr/src/sys/kern/kern_shutdown.c:772
#10 0x80acbb63 in panic (fmt=) at
/usr/src/sys/kern/kern_shutdown.c:710
#11 0x80cf945b in tcp_fastopen_autokey_callout (arg=0xfed25f10)
at /usr/src/sys/netinet/tcp_fastopen.c:270
#12 0x80ae5f36 in softclock_call_cc (c=, cc=, direct=)
at /usr/src/sys/kern/kern_timeout.c:729
#13 0x80ae64d4 in softclock (arg=) at
/usr/src/sys/kern/kern_timeout.c:867
#14 0x80a8696f in intr_event_execute_handlers (p=,
ie=)
at /usr/src/sys/kern/kern_intr.c:1262
#15 0x80a86f76 in ithread_loop (arg=) at
/usr/src/sys/kern/kern_intr.c:1275
#16 0x80a83545 in fork_exit (callout=0x80a86eb0 ,
arg=0xf80005493040, frame=0xfe0456d9eac0)
at /usr/src/sys/kern/kern_fork.c:1038
#17 0x80f5aeae in fork_trampoline () at
/usr/src/sys/amd64/amd64/exception.S:611
#18 0x in ?? ()
(kgdb)
(kgdb) up 11
#11 0x80cf945b in tcp_fastopen_autokey_callout (arg=0xfed25f10)
at /usr/src/sys/netinet/tcp_fastopen.c:270
270 CURVNET_SET(ctx->v);
(kgdb)
(kgdb) list
265 {
266 struct tcp_fastopen_callout *ctx = arg;
267
268 KASSERT(ctx != NULL, ("tcp_fastopen_autokey_callout: arg is
NULL"));
269
270 CURVNET_SET(ctx->v);
271 tcp_fastopen_autokey_locked();
272 callout_reset(&ctx->c, V_tcp_fastopen_autokey * hz,
273 tcp_fastopen_autokey_callout, ctx);
274 CURVNET_RESTORE();
(kgdb)
(kgdb) info local
saved_vnet = (struct vnet *) 0x81e64f38
saved_vnet_lpush = 0x0
(kgdb) print *saved_vnet
$2 = {vnet_le = {le_next = 0x1, le_prev = 0x0}, vnet_magic_n = 0, vnet_ifcnt =
0, vnet_sockcnt = 0, vnet_state = 0,
vnet_data_mem = 0x0, vnet_data_base = 256}
(kgdb)
Kernel config: GENERIC + VIMAGE and TCP_RFC7413 options
--
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 214545] freebsd-update erroneously reports mandoc.db databases need updating
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214545 --- Comment #7 from Petr Fischer --- You also have "freebsd-update cron" in cron on production servers? Nice feature. Time to change "Affects Some People" -> "Affects Many 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 216611] SUIDDIR In GENERIC kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216611 Bug ID: 216611 Summary: SUIDDIR In GENERIC kernel Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: free...@ihead.ru CC: freebsd-am...@freebsd.org CC: freebsd-am...@freebsd.org Feature request: add SUIDDIR option to GENERIC kernel. -- 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 216539] page fault in t4iov_attach during boot, on Dell CS23-SH motherboards
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216539 John Baldwin changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|j...@freebsd.org --- Comment #2 from John Baldwin --- Created attachment 179432 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179432&action=edit iov_attach.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 216539] page fault in t4iov_attach during boot, on Dell CS23-SH motherboards
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216539 John Baldwin changed: What|Removed |Added CC||n...@freebsd.org Status|New |In Progress --- Comment #1 from John Baldwin --- Hmm, I think I see the panic in that we don't check for pci_find_dbsf() returning NULL. However, I don't see how you have a matching PCI device that gets past the probe routine. Do you have 'pciconf -l' output? Oh, never mind. Somehow I missed checking the vendor ID. Please try the attached fix. -- 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 216610] TCP connections stuck forever in FIN_WAIT2 using IPFW
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216610 --- Comment #1 from Michael Ross --- Happens on 10.1-RELEASE, too -- 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 216610] TCP connections stuck forever in FIN_WAIT2 using IPFW
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216610 Bug ID: 216610 Summary: TCP connections stuck forever in FIN_WAIT2 using IPFW Product: Base System Version: 10.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: m...@ross.cx CC: freebsd-am...@freebsd.org CC: freebsd-am...@freebsd.org I had netstat list thousands of tcp connections in FIN_WAIT2, lingering for several weeks. Google-searching I found this: https://forums.freebsd.org/threads/56007/ I tested the suggested setting net.inet.ip.fw.dyn_keepalive=0, and since I use this setting, FIN_WAIT2 connections disappear within a few minutes. -- 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 209421] Processes hangs in D state, suspfs or vofflock wchan under FreeBSD 10.X
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209421 vvv changed: What|Removed |Added Version|10.3-RELEASE|11.0-RELEASE --- Comment #6 from vvv --- uname -a: FreeBSD hostname 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep 29 01:43:23 UTC 2016 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 ps auxwwO wchan: user123 21246 0,0 0,2 192920 45800 - D18:200:00,19 /usr/local/bin/p 21246 suspfs- D 0:00,19 /usr/local/bin/php-cgi root 21442 0,0 0,083962676 - Ds 18:210:00,01 find -H /tmp -na 21442 suspfs- Ds0:00,01 find -H /tmp -name sess_* -mtime +1h -delete user234 21669 0,0 0,0 115443420 - D18:210:00,02 unzip -ao /tmp/f 21669 suspfs- D 0:00,02 unzip -ao /tmp/fm/55BA42987CD9F1D024546F689963E25C/dist.zip -d /tmp/fm/55BA42987CD9F1D024546F689963E25C www 22188 0,0 0,2 146188 62200 - D18:230:00,24 /usr/local/sbin/ 22188 suspfs- D 0:00,24 /usr/local/sbin/httpd -f /usr/local/etc/apache24/httpd.conf -c PidFile /var/run/httpd.users.pid www 22439 0,0 0,2 146188 61772 - D18:240:00,03 /usr/local/sbin/ 22439 suspfs- D 0:00,03 /usr/local/sbin/httpd -f /usr/local/etc/apache24/httpd.conf -c PidFile /var/run/httpd.users.pid www 22442 0,0 0,2 146188 61768 - D18:240:00,02 /usr/local/sbin/ 22442 suspfs- D 0:00,02 /usr/local/sbin/httpd -f /usr/local/etc/apache24/httpd.conf -c PidFile /var/run/httpd.users.pid www 22789 0,0 0,2 146188 61780 - D18:260:00,03 /usr/local/sbin/ 22789 suspfs- D 0:00,03 /usr/local/sbin/httpd -f /usr/local/etc/apache24/httpd.conf -c PidFile /var/run/httpd.users.pid www 22790 0,0 0,2 146188 61772 - D18:260:00,02 /usr/local/sbin/ 22790 suspfs- D 0:00,02 /usr/local/sbin/httpd -f /usr/local/etc/apache24/httpd.conf -c PidFile /var/run/httpd.users.pid www 22799 0,0 0,2 146188 61800 - D18:260:00,03 /usr/local/sbin/ 22799 suspfs- D 0:00,03 /usr/local/sbin/httpd -f /usr/local/etc/apache24/httpd.conf -c PidFile /var/run/httpd.users.pid www 22802 0,0 0,2 146188 61764 - D18:260:00,02 /usr/local/sbin/ 22802 suspfs- D 0:00,02 /usr/local/sbin/httpd -f /usr/local/etc/apache24/httpd.conf -c PidFile /var/run/httpd.users.pid user345 22821 0,0 0,0 441483504 - Ds 18:260:00,12 ftpd: bzq-79-183 22821 range - Ds0:00,12 ftpd: ???.red.bezeqint.net: user/user345: STOR pack-473a0372073c2c7baee9ef960158fa0d3fa750e4.idx\r\n (ftpd) www 22834 0,0 0,2 146188 61764 - D18:260:00,02 /usr/local/sbin/ 22834 suspfs- D 0:00,02 /usr/local/sbin/httpd -f /usr/local/etc/apache24/httpd.conf -c PidFile /var/run/httpd.users.pid www 22935 0,0 0,2 146188 61828 - D18:260:00,04 /usr/local/sbin/ 22935 vofflock - D 0:00,04 /usr/local/sbin/httpd -f /usr/local/etc/apache24/httpd.conf -c PidFile /var/run/httpd.users.pid www 23009 0,0 0,2 146188 61772 - D18:270:00,01 /usr/local/sbin/ 23009 vofflock - D 0:00,01 /usr/local/sbin/httpd -f /usr/local/etc/apache24/httpd.conf -c PidFile /var/run/httpd.users.pid . procstat -kk 22188: PIDTID COMM TDNAME KSTACK 22188 100207 httpd-mi_switch+0xd2 sleepq_wait+0x3a _sleep+0x2a1 vn_start_write_locked+0xa6 vn_start_write+0xdf vn_close+0x5b vn_closefile+0x4a _fdrop+0x1a closef+0x2d4 closefp+0xb6 amd64_syscall+0x4ce Xfast_syscall+0xfb procstat -kk 22935: PIDTID COMM TDNAME KSTACK 22935 100997 httpd-mi_switch+0xd2 sleepq_wait+0x3a _sleep+0x2a1 foffset_lock+0xda vn_io_fault+0x5a dofilewrite+0x87 kern_writev+0x68 sys_write+0x84 amd64_syscall+0x4ce Xfast_syscall+0xfb -- 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 216606] kernel crashes early in pmap_map when pxe booted with rootfs in memory
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216606 Bug ID: 216606 Summary: kernel crashes early in pmap_map when pxe booted with rootfs in memory Product: Base System Version: 10.3-STABLE Hardware: i386 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: longw...@incore.de CC: freebsd-i...@freebsd.org CC: freebsd-i...@freebsd.org Sometimes I boot one of my servers via pxe and rootfs in memory. This works fine for all FreeBSD 8 Stable servers and all FreeBSD 10.3 Stable amd64 server. But for FreeBSD 10.3 r307955 i386 the kernel crashes early on boot. My loader.conf: # root partition in memory disk' mfsroot_load="YES" mfsroot_type="mfs_root" mfsroot_name="mfsroot" exec=".( setting vfs.root.mountfrom: ufs:/dev/md0) cr" vfs.root.mountfrom="ufs:/dev/md0" Size of kernel and mfsroot.gz: -r-xr-xr-x 1 root wheel 12043460 17 Jan 14:33 kernel -rw-r--r-- 1 root wheel 15508243 28 Jan 04:15 mfsroot.gz Some info of the server from a normal boot: FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2791.05-MHz 686-class CPU) Origin="GenuineIntel" Id=0xf29 Family=0xf Model=0x2 Stepping=9 Features=0xbfebfbff Features2=0x4400 real memory = 4294967296 (4096 MB) avail memory = 3936821248 (3754 MB) Output on serial console: DB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb MP Configuration Table version 1.4 found at 0xc00f1d40 Table 'FACP' at 0xefff0030 Table 'APIC' at 0xefff00b0 APIC: Found table at 0xefff00b0 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 6 ACPI ID 1: enabled SMP: Added CPU 6 (AP) MADT: Found CPU APIC ID 1 ACPI ID 2: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 7 ACPI ID 3: enabled SMP: Added CPU 7 (AP) Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.3-STABLE #2 r307955: Tue Jan 17 14:33:05 CET 2017 root@dssresv2.incore:/usr/obj/usr/src/sys/SERVER32 i386 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xbff22000 fault code = supervisor write, page not present instruction pointer = 0x20:0xc0b88660 stack pointer = 0x28:0xc4422c94 frame pointer = 0x28:0xc4422cac code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 0 () [ thread pid 0 tid 0 ] Stopped at pmap_map+0xb0: movl%ecx,PTmap(,%eax,4) db> bt Tracing pid 0 tid 0 td 0xc0e71510 pmap_map(c4422cd8,ebfba000,eff7a000,3,3fbf51c,...) at pmap_map+0xb0/frame 0xc4422cac vm_page_startup(c4594000,c0890706,c0e0279c,c0c8c4b1,0,...) at vm_page_startup+0x3a5/frame 0xc4422cec vm_mem_init(0,0,0,0,c0ccf2d8,...) at vm_mem_init+0x18/frame 0xc4422d10 mi_startup() at mi_startup+0xe7/frame 0xc4422d38 begin() at begin+0x22 db> reset The problem is easy reproducible. If necessary I can give more output from ddb. -- 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 210315] panic: destroying non-empty racct: 2113536 allocated for resource 4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210315 --- Comment #12 from Larry Rosenman --- I **WAS** running LOTS of Poudriere runs, ergo LOTS of jails, so yes. My one panic was at a shutdown -r. -- 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 210315] panic: destroying non-empty racct: 2113536 allocated for resource 4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210315 --- Comment #11 from Andriy Gapon --- (In reply to Edward Tomasz Napierala from comment #8) Yes, that must be true. It is impossible to get that problem for the process racct. I have one hypothesis now. Consider the following sequence of events: 0. the vm daemon gets a reference on a vm space of a process 1. the vm daemon invokes the first racct_set(p, RACCT_RSS, rsize) call for the process 2. the process exits and vmspace_exit() is called for the the vm space 3. the vm daemon calls racct_set(p, RACCT_RSS, rsize) within if (rsize > ravailable) block 4. the vm daemon releases the vm space I think that in this scenario we would do the following: 1. set RACCT_RSS of the process to X 2. set RACCT_RSS of the process to zero 3. set RACCT_RSS of the process (now a zombie) to Y I think that that last call would screw up the accounting for raccts that include the process. In fact, it also screws up the accounting for the process itself, but that is masked by the code in racct_proc_exit() that sets to zero all reclaimable resources. Ah, and because of what racct_proc_exit() does, we have this: 4. set RACCT_RSS of the process (now a zombie) to zero So, it looks like only the jail accounting is affected and we see it only in the window between exit1() dropping the reference to the jail and proc_reap(). So, to recap, the full sequence: 0. the vm daemon gets a reference on a vm space of a jailed process 1. the vm daemon invokes the first racct_set(p, RACCT_RSS, rsize) call for the process 2. the process exits and vmspace_exit() is called for the the vm space 3. the vm daemon calls racct_set(p, RACCT_RSS, rsize) within if (rsize > ravailable) block 4. the vm daemon releases the vm space 5. the process drops its reference to the jail 6. the jail gets destroyed <-- here we hit the problem I think that the above could explain the panics that I saw. Not sure if the Larry's panic can be fit into the hypothesis. -- 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 214545] freebsd-update erroneously reports mandoc.db databases need updating
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214545 everytrash changed: What|Removed |Added CC||everytr...@gmail.com --- Comment #6 from everytrash --- Same error! (11.0-RELEASE-p7 (amd64)) -- 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 216586] zfs panic: sa.sa_magic == 0x2F505A in zfs_space_delta_cb()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216586 Mark Linimon changed: What|Removed |Added CC|freebsd-am...@freebsd.org | Assignee|freebsd-bugs@FreeBSD.org|freebsd...@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 216587] cc should accept -pie argument
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216587 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-toolchain@FreeBSD.o ||rg -- 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 216590] clang 3.9.1 from (e.g.) head -r312942 fails to reject or even warn about some forms of assignments to const fields
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216590 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-toolchain@FreeBSD.o ||rg -- 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 216594] pw usernext ignores config option
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216594 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 216586] zfs panic: sa.sa_magic == 0x2F505A in zfs_space_delta_cb()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216586 Andriy Gapon changed: What|Removed |Added CC||a...@freebsd.org --- Comment #1 from Andriy Gapon --- Did you do 'zfs upgrade' any time recently? -- 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 204340] [panic] nfsd, em, msix, fatal trap 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #19 from Andriy Gapon --- (In reply to Rick Macklem from comment #18) > Andriy Gapon, did your crash occur when the machine was being shut down (or the nfsd threads were being killed off)? Yes, it did. I am told that this was easy to reproduce by SIGKILL to nfsd. -- You are receiving this mail because: You are on the CC list 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 216594] pw usernext ignores config option
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216594
Bug ID: 216594
Summary: pw usernext ignores config option
Product: Base System
Version: 10.3-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: bin
Assignee: freebsd-bugs@FreeBSD.org
Reporter: g...@greenie.muc.de
"pw usernext -C /my/pw.conf"
ignores the "-C" option, due to a bug in pw/pw_user.c, line 747 - the
"getopt()" statement has "Cq" as arguments, but it needs to be "C:q"
--- pw_user.c.orig 2017-01-30 09:28:02.620426968 +0100
+++ pw_user.c 2017-01-30 09:27:51.560428192 +0100
@@ -744,7 +744,7 @@
bool quiet = false;
uid_t next;
- while ((ch = getopt(argc, argv, "Cq")) != -1) {
+ while ((ch = getopt(argc, argv, "C:q")) != -1) {
switch (ch) {
case 'C':
cfg = optarg;
--
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"
