From owner-freebsd-current@freebsd.org Wed Oct 25 11:26:32 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A1D0E47040; Wed, 25 Oct 2017 11:26:32 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 4ED4368877; Wed, 25 Oct 2017 11:26:31 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id A7081260BDC; Wed, 25 Oct 2017 13:26:29 +0200 (CEST) Subject: Re: Okular or any pdf reader To: blubee blubeeme Cc: FreeBSD Ports , FreeBSD current References: <090f8659-b88b-dc6d-ea8d-de6ee4661fc2@selasky.org> <9b7e2698-444c-585e-e11a-b24ab5afdb17@selasky.org> From: Hans Petter Selasky Message-ID: <180f8f8d-3d2b-ecc8-5548-4057806f3227@selasky.org> Date: Wed, 25 Oct 2017 13:23:51 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Oct 2017 11:26:32 -0000 On 10/25/17 13:15, blubee blubeeme wrote: > Okay, I tried using chatbot for android to ssh into this laptop and that > works just fine. > Then when I launch okular the computer had locks up and the ssh dies on the > phone as well. So it seems not even ssh works when this this freezes up. > > Any other suggestions? Try to set: sysctl net.inet.tcp.per_cpu_timers=1 Before connecting via SSH. Does the same happen when using VESA driver or is this specific to using the NVIDIA driver. If the NVIDIA is at cause, I cannot help. --HPS