From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 13:07:20 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2AC703EE for ; Thu, 4 Dec 2014 13:07:20 +0000 (UTC) Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE761FDE for ; Thu, 4 Dec 2014 13:07:18 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id k14so22302176wgh.24 for ; Thu, 04 Dec 2014 05:07:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=k47pWZSr1iKmiu9PUYXgPyMy9jCIGJX4DLQGUy8gnt8=; b=Fz4XAmKUr+Ar/N0+TCFBQBTqdpHUHSuZ4pGYKms7ckWNypIyZPwD7lZvy1JBk+tm1G dN4j3o0222Y9vmomfTGgpBU6655itsmSTmFnYv0vrl4puMjvXuvnxY+BHJXxq5xxbBVj Ys2Zd1em67jCcxNKLNwUEEPQ5Is+AKbiK2j+4Hlgqq4iWbI504R195DyCYn2NBZtv/S+ V3kjI3YauTgUjikE6EkDEKOwe+F0RuobvB5jkKtJHJI6tmU+DBF1z4z3cTIcTi2awDPL dxyVSsi9dtn5+PLJYblRVZNIZ7rZnBDHENr/Uht/GS0aCfDinf5VAEHHKtaWDDEZPmNZ wcNA== X-Gm-Message-State: ALoCoQkYuVyoqWbq34AjSWHQX2GzJPUDX97oG3W3D4BHkDj3HWMGHzQkXT8igTLGFU+dUcyL6wUO X-Received: by 10.180.96.42 with SMTP id dp10mr101081254wib.38.1417698431051; Thu, 04 Dec 2014 05:07:11 -0800 (PST) Received: from sigil.instinctive.eu ([2001:758:f00:340:78:41:233:119]) by mx.google.com with ESMTPSA id a14sm11709685wib.22.2014.12.04.05.07.10 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 04 Dec 2014 05:07:10 -0800 (PST) Date: Thu, 4 Dec 2014 13:06:58 +0000 From: Natacha =?iso-8859-1?Q?Port=E9?= To: Shane Ambler Subject: Re: Need help with unexpected reboot in 10.1-RELEASE Message-ID: <20141204130658.GA38683@nat.rebma.instinctive.eu> References: <20141126082923.GA87180@nat.rebma.instinctive.eu> <547601F4.2040005@ShaneWare.Biz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <547601F4.2040005@ShaneWare.Biz> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: FreeBSD stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 13:07:20 -0000 Hello, on Thursday 27 November 2014 at 03:08, Shane Ambler wrote: > On 26/11/2014 18:59, Natacha Porté wrote: > > Hello, > > > > last week, I updated my main personal computer from 9.2-RELEASE to > > 10.1-RELEASE. Since then, I experienced four sudden and unexpected > > reboots (is that what is called "crashes"?). They were immediate, so > > it's not a kernel panic (which keeps the system unusable for 15s before > > rebooting). Nothing appears in the logs, but who knows what could be in > > the uncommitted buffers? > > I haven't had reboots but my machine has hung, forcing me to reset > nearly every day. When it doesn't hang the usb system fails to create > new devices forcing me to restart to access a disk. So for the record, in case anyone stumbles back here, I noticed that nVidia proprietary drivers were upgraded in the ports (relatively) close to the release of 10.1-RELEASE, so I happened to have simultaneously upgraded FreeBSD base from 9.2 to 10.1 and nVidia drivers from 331 to 340. Since I downgraded the drivers to 331 (the exact variant installed in my 9.2-RELEASE setup), I haven't experienced a single crash, despite a heavy use of World of Warcraft. So I guess the culprit is very likely to be nVidia proprietary drivers, which makes the problem out-of-topic for this ML. However I did experience one freeze (which I believe designates the same reality as "my machine has hung), during a poudriere run. Unfortunately I wasn't home when it happened, so I can only describe a sudden loss of network connectivity (other hosts saying "host is down" when trying to ping it), and when I got physical access, I couldn't make the screen leave stand-by mode, and the keyboard LED didn't toggle. I'm afraid that without network, screen or keyboard LED there is nothing left to judge whether there is still any activity going on. When I have time to babysit a poudriere run I will try again, that's a completely different problem but I would love to see it solved too (assuming it is indeed reproducible). Considering all that, I'm not sure the questions below are still relevant, but I will answer them in case it is somehow useful. > > I run with a ZFS root, and the zpool is directly on the unsliced disk. > > I have a nVidia graphics card, with the proprietary driver, on two > > screens with two displays (":0" and ":0.1") and two window managers. > > It's an amd64 platform. > > How much ram? one disk in zpool? 8 GB for RAM, one disk (half a TB) for the system and one SSD (107GB) for game installations, each of them alone in their dedicated zpool. > > I doubt this is a purely hardware issue, since I generally choose my > > hardware for its reliability, and I regularly reached three-digit days > > of uptime with 9.2-RELEASE. > > I used to install updates and restart monthly on 9.2. I tend to keep an unhealthy amount of state in the various programs I have opened, so I find seldom convenient to reboot. I might even be a few CVE's late because of that. > > I did take a snapshot of my 9.2-RELEASE, so I'm one zfs rollback away > > from checking whether it sill happens with 9.2-RELEASE. However, if as > > is likely it does work around the problem, I will probably have a hard > > time motivating myself to come back to the problem, rather than just > > waiting for the next release to see whether it has been magically solved > > without me. > > CAUTION - If you performed a zpool upgrade after upgrading to 10.1 then > you can't read the zpool in 9.x so the rollback will fail. The way back > will involve creating a new pool and transferring data. I'm aware of the non-reversibility of zpool upgrades, which is why I usually wait a few months before upgrading the zpool (when I don't forget it altogether). On top of that I can't seem to remember how to install the new bootloader, which is necessary before upgrading the pool too because I have a ZFS root. So I won't upgrade the pool before looking up (again) how to upgrade the bootloader of a mounted disk. Thanks for your help, Natacha