From owner-freebsd-current@FreeBSD.ORG Mon Feb 4 20:46:20 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3BA4D392 for ; Mon, 4 Feb 2013 20:46:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9CBAAD36 for ; Mon, 4 Feb 2013 20:46:19 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id ADE37B9AC; Mon, 4 Feb 2013 15:46:18 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: CURRENT: Broken on > r246222? Date: Mon, 4 Feb 2013 14:50:59 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: <510E8FCD.1040701@zedat.fu-berlin.de> In-Reply-To: <510E8FCD.1040701@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201302041450.59809.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 04 Feb 2013 15:46:18 -0500 (EST) Cc: "O. Hartmann" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Feb 2013 20:46:20 -0000 On Sunday, February 03, 2013 11:26:53 am O. Hartmann wrote: > CURRENT, as of recent Revision 246285 (see below) fails and > crashes/reboots on an Ivy-Bridge platform (see below). Since the box > does not have debugging switched on (not yet, will do eventually > Monday), Last thing I see on screen is > > p4tcc3: on cpu3 > > then the system run dark and reboots without any notice (kernel doesn't > have debugging switched on so far, will do this after Monday). I don't think there are any known issues. Can you narrow it down to a specific commit? -- John Baldwin