From owner-freebsd-stable@FreeBSD.ORG Wed Nov 26 08:29:45 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87779314 for ; Wed, 26 Nov 2014 08:29:45 +0000 (UTC) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) (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 1FB6A2DA for ; Wed, 26 Nov 2014 08:29:44 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id l15so11691527wiw.2 for ; Wed, 26 Nov 2014 00:29:37 -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:subject:message-id:mime-version :content-type:content-disposition:content-transfer-encoding :user-agent; bh=v3EJ+BPGUZSO3f+9pFR6f5bNZ+K5I/9UA1BeA+VlbT4=; b=apPevuUWAuDFm3j4IAuhiQmMwF8Yd8SLdbZMN/xf6megebYxzv1XWk2rKgqBnCZ1Af 62YjHDjAoYVP2T0SKtypU6CTyKv19RZQsTJPNvQC3XR65YsOMeqUYkEd90M41p8GYg04 cgtD5V3vqTkh5sxh583ur9W05Sqplq45/Pim6kUzgGt6qkPGQx0graJPW9025vUpq2lr a0ZbJKu6M+AZacxuB3qst3QBdrI2VGoJIWHjBSHZRYj1Rgi8CDiQP5oxdXGdCV8rX79u csKDPlJttlIDajrhi/25lkMia6jLCDGpMB/L1KaEzQdhHqt0G6/50fC19ZLTkPBBBLMo qUyQ== X-Gm-Message-State: ALoCoQlFWs67NoDcroObpR6mkSFlttZdy6HV4AKivN8qwAs+ufAvGWJoE60Pn5zXcoevppXQgZJY X-Received: by 10.194.119.99 with SMTP id kt3mr36234228wjb.14.1416990577130; Wed, 26 Nov 2014 00:29:37 -0800 (PST) Received: from sigil.instinctive.eu ([2001:758:f00:340:78:41:233:119]) by mx.google.com with ESMTPSA id td9sm6248008wic.15.2014.11.26.00.29.35 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 26 Nov 2014 00:29:36 -0800 (PST) Date: Wed, 26 Nov 2014 08:29:23 +0000 From: Natacha =?iso-8859-1?Q?Port=E9?= To: FreeBSD stable Subject: Need help with unexpected reboot in 10.1-RELEASE Message-ID: <20141126082923.GA87180@nat.rebma.instinctive.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.23 (2014-03-12) 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: Wed, 26 Nov 2014 08:29:45 -0000 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 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, but I have a i386 chroot from where I run Wine. The latest two reboots happened exactly when I closed World of Warcraft. I don't remember anything from the second reboot, and the very first one didn't involve Wine, but it may have been close to watching a YouTube video directly in Firefox. But on the other hand, there has been several instances of closing World of Warcraft or watching YouTube without triggering the reboot. So at this point, and considering the relatively slow rate of acquiring data, I would consider something related to the video to be the best suspect. 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 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. So before rolling back to 9.2-RELEASE, I would like to try diagnosing the problem as much as possible, as one of the few ways a humble user like me can contribute. Is there anything I can do to gather more information about the problem? Would you need extra information about my setup first (lspci, dmidecode, ports options, etc)? Someone has already suggested me to disable APIC (not ACPI), but that causes a kernel panic early in the boot because of lack of event timer. Thanks in advance for your help, Natacha Porté