From owner-freebsd-stable@freebsd.org Mon Apr 2 12:27:16 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2AC6F51F59 for ; Mon, 2 Apr 2018 12:27:16 +0000 (UTC) (envelope-from lists@knigma.org) Received: from shrewd.pub.knigma.org (shrewd.ipv6.pub.knigma.org [IPv6:2001:8b0:b0:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 28CAD7C1C8 for ; Mon, 2 Apr 2018 12:27:15 +0000 (UTC) (envelope-from lists@knigma.org) Received: from dhcp13.wireless.knigma.org (localhost [127.0.0.1]) (authenticated bits=0) by shrewd.pub.knigma.org (8.15.2/8.15.2) with ESMTPSA id w32CRCs2001875 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 2 Apr 2018 13:27:12 +0100 (BST) (envelope-from lists@knigma.org) Reply-To: markk@knigma.org Subject: Re: FreeBSD 10.4 kernel breaks on i7-7700 / PRIME H270M-PLUS To: Eugene Grosbein , freebsd-stable@freebsd.org References: <5AC1C628.6030309@grosbein.net> From: Mark Knight Message-ID: <3c184bf8-8651-22a7-a040-8260b44647da@knigma.org> Date: Mon, 2 Apr 2018 13:27:12 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <5AC1C628.6030309@grosbein.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (shrewd.pub.knigma.org [127.0.0.1]); Mon, 02 Apr 2018 13:27:13 +0100 (BST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Apr 2018 12:27:16 -0000 On 02/04/2018 06:56, Eugene Grosbein wrote: > What does it show if you press "CTRL-T" to see a status of "hung" process? Typically CTRL-T shows [sysctl mem]. In some circumstances I can CTRL-C (e.g. if su hangs), in others I cannot (e.g. with sudo). > Does it help if you comment out the line mentioning /dev/console in the /etc/syslog.conf > and apply the change with killall -1 syslogd ? Doing that "killall -HUP syslogd" hangs with (sysctl mem) - as does "service syslogd restart" but after a fresh reboot, no - removing that line didn't help at all. Thanks for getting my hopes up :) Moving ~/myuser/.bashrc out of the way (it really doesn't contain much apart from setting a bunch of aliases), allows me to login as myself, but "sudo -u myuser -s" still hangs. I just got a truss output of "sudo -u myuser -s" per the file below, perhaps that contains a clue? # sudo -u myuser -s >& sudo.truss.log http://www.knigma.org/scratch/sudo.truss.log Flipping back to a 10.3 kernel makes everything happy (just as well, as the machine in question is my main router/firewall, so it's a right pain when it's not working). Thanks in advance for any fresh ideas; I'm really not sure where to go with this! -- Mark Knight