From owner-freebsd-xen@FreeBSD.ORG Sat Jul 27 07:30:02 2013 Return-Path: Delivered-To: freebsd-xen@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0E576C81 for ; Sat, 27 Jul 2013 07:30:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D56652AD1 for ; Sat, 27 Jul 2013 07:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r6R7U0xZ071017 for ; Sat, 27 Jul 2013 07:30:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6R7U0Mn071016; Sat, 27 Jul 2013 07:30:00 GMT (envelope-from gnats) Date: Sat, 27 Jul 2013 07:30:00 GMT Message-Id: <201307270730.r6R7U0Mn071016@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org Cc: From: =?KOI8-R?B?4czFy9PBzsTSIOLSz9fJy8/X?= Subject: Re: kern/180788: [xen] [panic] XEN PV kernel 9.2-BETA1 panics on boot X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: =?KOI8-R?B?4czFy9PBzsTSIOLSz9fJy8/X?= List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jul 2013 07:30:02 -0000 The following reply was made to PR kern/180788; it has been noted by GNATS. From: =?KOI8-R?B?4czFy9PBzsTSIOLSz9fJy8/X?= To: bug-followup@FreeBSD.org, alexander@brovikov.ru Cc: Subject: Re: kern/180788: [xen] [panic] XEN PV kernel 9.2-BETA1 panics on boot Date: Sat, 27 Jul 2013 13:24:38 +0600 --047d7b2e4228ecaa4b04e2792619 Content-Type: text/plain; charset=ISO-8859-1 Confirm: workaround worked. --047d7b2e4228ecaa4b04e2792619 Content-Type: text/html; charset=ISO-8859-1
Confirm: workaround worked.
--047d7b2e4228ecaa4b04e2792619--