From owner-freebsd-questions@freebsd.org Sat Nov 9 21:04:07 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 9D19E17D289 for ; Sat, 9 Nov 2019 21:04:07 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 479V4Q5V6Vz49C5 for ; Sat, 9 Nov 2019 21:04:06 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: by mail-wr1-x42d.google.com with SMTP id r10so10712927wrx.3 for ; Sat, 09 Nov 2019 13:04:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=QjFp+GMlVJU7ANpQNsp1LZFjDY/Rkaz3pIpcdh0p1/c=; b=hYsYvGF7qdHvJI4LUZQPST12HrPqrF59jPj28Sk7jOrkSqSJUUtTGsAIsv9Vu/uFfV tU9eY/A5I/WhcezOlBzfz1Ff7DI5U86sxiaC6h+e97ftO0K3FpwBNvbVl2J+v0YLvTu2 pyqxtEbayPsPI3CbfBe+H09sWtX36y4YEvOHT+C9ka4/vNfWzn6Gpk7VLBUQDt+DCSj2 JzTZu87v/cQxjq/PXZO0H2EfxqcGHY8vI0wSWx1m8ECTebEwkG6yToZA9rSVH+RRMkC7 3U9esIMQdHM7rtC/18E2ve5cSh7dW9hexhusEgIQSrt0qFKHy90u4B5kXII7u9z9OxRf 9kSA== X-Gm-Message-State: APjAAAUjew1PjAkbs8zQI+cQKuaXqOwAR1azqC8UYMk3Q8mt91FzZaCA nwcWX478iaHsNVymiPOS/x8LjqSs X-Google-Smtp-Source: APXvYqy96R7U4x9UOJ05YGu68WQDzb2V5eBxznO3uB2vfEtVpb9U9+uQGz7hGjrA5lZx/TRN/Db83w== X-Received: by 2002:a5d:4d4a:: with SMTP id a10mr15122087wru.35.1573333444876; Sat, 09 Nov 2019 13:04:04 -0800 (PST) Received: from [192.168.42.14] ([90.255.178.147]) by smtp.gmail.com with ESMTPSA id l18sm11353972wrn.48.2019.11.09.13.04.04 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 09 Nov 2019 13:04:04 -0800 (PST) Subject: Re: kernel bug in 11.3-STABLE causes frequent crashes (Scott Bennett) To: freebsd-questions@freebsd.org References: From: Dave B Message-ID: <0d281f8d-02b6-e0b1-2b6c-b1ed7ebdcaec@googlemail.com> Date: Sat, 9 Nov 2019 21:04:03 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Content-Language: en-GB X-Rspamd-Queue-Id: 479V4Q5V6Vz49C5 X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[googlemail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-8.76), ipnet: 2a00:1450::/32(-2.75), asn: 15169(-2.00), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[d.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] 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 21:04:07 -0000 Personally, with old hardware, I'd be inclined to check the power supplies and mobo' for decoupling/storage capacitor problems (bad-cap issues) and rectify them. The power supply is the real heart of any system, not the CPU.  Plus, that in turn relies on reliable memory, that in turn relies on clean power.  Get the picture.   Similarly, the associated cooling systems, keep fans and filters clean, and heatsink fins clear.  On very old systems (10 years or more) the thermal bonding between CPU and heatsink could be also failing.  I've even seen the heatsink partly hanging off the board, as a plastic clip had failed with age (and heat, due to a blocked filter.) Then if the trouble still persists, boot a current copy of memtest86, and let it run the full gamut of tests for several rounds, without fail, just to know the basic hardware is OK. Of course, if memtest86 croaks in odd ways before it really gets going then you may have a failing CPU.  But swap some memory modules around, so that where it's first loaded into uses "different" chips than it was before, before you point fingers at the processor. AMD processors don't like heat (they die.)  Intel at least just slow down (to a crawl) to prevent them cooking themselves. Hope you get to the bottom of things. Dave B. On 09/11/2019 12:00, freebsd-questions-request@freebsd.org wrote: > kernel bug in 11.3-STABLE causes frequent crashes (Scott Bennett) -- Created on and sent from a Unix like PC running and using free and open source software: