From owner-freebsd-current@freebsd.org Mon Jul 25 16:10:52 2016 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 6591ABA48C6 for ; Mon, 25 Jul 2016 16:10:52 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2DF471E14 for ; Mon, 25 Jul 2016 16:10:51 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [89.204.139.224] (helo=[10.190.143.224]) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1bRiSn-0002jC-G0 for freebsd-current@freebsd.org; Mon, 25 Jul 2016 18:10:41 +0200 From: Matthias Apitz To: Subject: Re: seldom crashes on Dell E6330 with 12-CURRENT Date: Mon, 25 Jul 2016 18:10:39 +0200 User-Agent: Dekko/0.6.20; Qt/5.4.1; ubuntumirclient; Linux; MIME-Version: 1.0 Message-ID: <10392d5e-79ca-4f5f-b3ac-802cb4cdea17@unixarea.de> In-Reply-To: <551fda4a-4220-9be2-2409-9b8ad959827f@FreeBSD.org> References: <20160723072128.GA2136@c720-r292778-amd64> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.139.224 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Mon, 25 Jul 2016 16:10:52 -0000 On Monday, 25 July 2016 17:11:23 CEST, Eric van Gyzen=20 wrote: >=20 > What file system are you using? UFS; I followed the good instructions about new SSD disk configuration;=20 that's why I now have swap as plain file :-( > Do a full fsck (or zfs scrub). will do a full fsck; > Try moving swap to a raw (freebsd-swap) partition so that you might get > a kernel core dump. That will be the essential next step. ok, I will dump /usr to some external disk, shrink the partition, creat swap and re-create /usr >=20 > Without more details from a core dump or debugger, your best option is > to try a release or an older build. If that works, try to find the > commit that introduced the behavior. This will be very tedious and > time-consuming for your scenario, so definitely try getting a core dump > first. the problem is as well: until now no further crashes had occured, i.e. it'=20= difficult to see if it works or not; matthias --=20 Sent from my Ubuntu phone http://www.unixarea.de/