From owner-freebsd-questions@freebsd.org Sat Nov 9 10:57:19 2019 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 48DD81A5DDE for ; Sat, 9 Nov 2019 10:57:19 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from mx.sdf.org (mx.sdf.org [205.166.94.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.sdf.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 479DcG23Jzz4cBd for ; Sat, 9 Nov 2019 10:57:17 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from sdf.org (IDENT:bennett@miku.sdf.org [205.166.94.6]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id xA9AvGFn019968 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Sat, 9 Nov 2019 10:57:17 GMT Received: (from bennett@localhost) by sdf.org (8.15.2/8.12.8/Submit) id xA9AvGjx028838 for freebsd-questions@freebsd.org; Sat, 9 Nov 2019 04:57:16 -0600 (CST) From: Scott Bennett Message-Id: <201911091057.xA9AvGjx028838@sdf.org> Date: Sat, 09 Nov 2019 04:57:16 -0600 To: freebsd-questions@freebsd.org Subject: kernel bug in 11.3-STABLE causes frequent crashes User-Agent: Heirloom mailx 12.5 6/20/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 479DcG23Jzz4cBd X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of bennett@sdf.org has no SPF policy when checking 205.166.94.20) smtp.mailfrom=bennett@sdf.org X-Spamd-Result: default: False [-1.43 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.988,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(-0.34)[ip: (-1.09), ipnet: 205.166.94.0/24(-0.54), asn: 14361(-0.03), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.996,0]; DMARC_NA(0.00)[sdf.org]; RCVD_IN_DNSWL_NONE(0.00)[20.94.166.205.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14361, ipnet:205.166.94.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Nov 2019 10:57:19 -0000 I have had to waste a great deal of time lately in recovering my system from crashes due to a kernel bug. At present, my system is FreeBSD hellas 11.3-STABLE FreeBSD 11.3-STABLE #12 r352571: Sat Sep 21 11:39:52 CDT 2019 bennett@hellas:/usr/obj/usr/src/sys/hellas amd64 There are actually at least two problems, but this particular one has been causing a large portion of my forced reboots. It usually fails to produce a dump and freezes right after the panic and backtrace messages, as it did earlier tonight, but Wednesday night it did create a dump, which I am keeping in case it should prove helpful in getting the bug identified and solved. I copied the console messages to paper painstakingly by hand. They appear to be identical each time, except, of course, for the messages that a dump is produced when, indeed, it does produce one. I am omitting those fairly standard messages. Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 02 fault virtual address = 0x3b8 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80a4b14c stack pointer = 0x0:0xfffffe012a60ea50 frame pointer = 0x0:0xfffffe012a60eae0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 28 (flowcleaner) trap number = 12 panic: page fault cpuid = 2 KDB: stack backtrace: #0 0xffffffff80a94707 at kdb_backtrace+0x67 #1 0xffffffff80a4fa2e at vpanic+0x17e #2 0xffffffff80a4f8a3 at panic+0x43 #3 0xffffffff80f3a4d0 at trap_pfault+0 #4 0xffffffff80f3a519 at trap_pfault+0x49 #5 0xffffffff80f39bad at trap+0x29 #6 0xffffffff80f19f33 at calltrap+0x8 #7 0xffffffff80b3bb8d at flowtable_clean_vnet+0x43d #8 0xffffffff80b3c758 at flowtable_cleaner+0xc8 #9 0xffffffff80a12ea2 at fork_exit+0x82 #10 0xffffffff80flaf4e at fork_trampoline+0xe The machine is ancient. The CPU is a QX9650 (last group of Core 2 Quads) with 8 GB of DDR3 memory. If this can be identified as a known bug and a clue provided to a patch or a safer version to upgrade to, I would be grateful. I am getting very, very tired of these crashes. The other forced reboots I will describe in a separate message, but that problem has existed since the time of 11.2-RELEASE and apparently was never investigated, much less fixed, although people began complaining on this list and possibly -questions within the first few days after the release date. Thanks in advance for any help with this problem! Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************