From owner-freebsd-stable@FreeBSD.ORG Mon Jun 27 19:44:35 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5ED5106566C; Mon, 27 Jun 2011 19:44:35 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.ip6.digiware.nl [IPv6:2001:4cb8:1:106::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3EF1E8FC21; Mon, 27 Jun 2011 19:44:35 +0000 (UTC) Received: from rack1.digiware.nl (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 8D0D6153434; Mon, 27 Jun 2011 21:44:33 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CpNS-CV4Kt4R; Mon, 27 Jun 2011 21:44:31 +0200 (CEST) Received: from [IPv6:2001:4cb8:3:1:5dc6:fb01:d251:6852] (unknown [IPv6:2001:4cb8:3:1:5dc6:fb01:d251:6852]) by mail.digiware.nl (Postfix) with ESMTP id C1E42153433; Mon, 27 Jun 2011 21:44:31 +0200 (CEST) Message-ID: <4E08DDAA.5090309@digiware.nl> Date: Mon, 27 Jun 2011 21:44:42 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: Mike Tancsa References: <4E0674ED.5090502@digiware.nl> <4E073982.8050601@sentex.net> <4E088815.40306@sentex.net> In-Reply-To: <4E088815.40306@sentex.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: =?UTF-8?B?6buD5riF6ZqG?= , stable@freebsd.org, delphij@freebsd.org Subject: Re: arcmsr panic runnig 8.2 of 2011 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2011 19:44:35 -0000 On 2011-06-27 15:39, Mike Tancsa wrote: > Hi Ching, > Thanks very much for the quick turn around! The person who was having > the error is actually Willem, not me. All has been running fine for my > setup, but I will deploy it as well to test. Yup, And I've got my plate full with real-live job. So I've got to find a slot to tinker with the server. Probably again in the weekend. --WjW