From owner-freebsd-xen@FreeBSD.ORG Tue Oct 27 13:18:46 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00129106566B for ; Tue, 27 Oct 2009 13:18:45 +0000 (UTC) (envelope-from sysconfig@ossafe.org) Received: from mx2.the-ally.co.uk (mx2.the-ally.co.uk [95.154.227.236]) by mx1.freebsd.org (Postfix) with ESMTP id 8A1BB8FC22 for ; Tue, 27 Oct 2009 13:18:45 +0000 (UTC) Received: from mx2.the-ally.co.uk (localhost.localdomain [127.0.0.1]) by mx2.the-ally.co.uk (Postfix) with ESMTP id 8C8F4ED0997; Tue, 27 Oct 2009 13:18:43 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ossafe.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=89/nYt1DIN7aV1iYpsnLMkRfL9c=; b=PgEVMXiY4sv6mXQHfj jOB4BfZQLiVMaBS+GEbJDAP/vmItbRucVANze9eNSnB1YeHTixduPks0EttSx/Q1 jmxIHjIysfKAWJGo/UQEzS+gAc+hvtDiR9tl7nuuqgVR5fQBAxE0gqOujuucd/gZ uPuVEe1XXZf4KpKKDVnQqYDlY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=ossafe.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=e6rMuG+luFWyErPzK5IPmmAFB+sEglqNfatDx1uoYr3PvSOJIdi qQJAEDhE/+DkiBjaAVVs4Kf62nKpfSZPzF++eAawLP2J+yt5aE8X+qkzxNpsyKM7 4l571yds5XEmdWxZl2HgMHeHIoqOAOlE+B/kaem4fiClk97qkfWpRUs4= Received: from [10.2.2.20] (unknown [10.2.2.20]) by mx2.the-ally.co.uk (Postfix) with ESMTP id 4E01CED0994; Tue, 27 Oct 2009 13:18:43 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Carsten Heesch In-Reply-To: <3941E1B9-6CD6-4D9A-AF1C-93401F571FCE@heesch.me.uk> Date: Tue, 27 Oct 2009 13:18:43 +0000 Content-Transfer-Encoding: 7bit Message-Id: <8C3C0877-F36E-45D1-BDEE-4EE22BD45205@ossafe.org> References: <850CF1B7-499E-4468-9045-19A2803E6D05@ossafe.org> <3941E1B9-6CD6-4D9A-AF1C-93401F571FCE@heesch.me.uk> To: Carsten Heesch X-Mailer: Apple Mail (2.1076) Cc: freebsd-xen@freebsd.org Subject: Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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: Tue, 27 Oct 2009 13:18:46 -0000 Athough I seem to be talking to myself here, I have good news for RC2! It works! Just did an "freebsd-update -R 8.0-RC2 upgrade". Both GENERIC and XENHVM kernels work without any problems. Maybe somebody else can chime in an confirm that, too? Probably good for the developers to see positive feedback, while 8.0-RELEASE is coming closer :-) Cheers Carsten On 25 Oct 2009, at 00:31, Carsten Heesch wrote: > > I realised that it's still possible to use 8.0-BETA* as a target for > freebsd-update. So I investigated a bit further. For whatever it's > worth: > > The problems described earlier started with BETA-4. > > BETA-3 is fine with both GENERIC and XENHVM kernel, except that I > see this on the console and in dmesg every now and then (with both > kernels): > > > lock order reversal: > 1st 0xffffff8014810620 bufwait (bufwait) @ /usr/src/sys/kern/ > vfs_bio.c:2559 > 2nd 0xffffff00015a7c00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ > ufs_dirhash.c:285 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > _witness_debugger() at _witness_debugger+0x2e > witness_checkorder() at witness_checkorder+0x81e > _sx_xlock() at _sx_xlock+0x55 > ufsdirhash_acquire() at ufsdirhash_acquire+0x33 > ufsdirhash_add() at ufsdirhash_add+0x19 > ufs_direnter() at ufs_direnter+0x88b > ufs_makeinode() at ufs_makeinode+0x31c > VOP_CREATE_APV() at VOP_CREATE_APV+0x8d > vn_open_cred() at vn_open_cred+0x423 > kern_openat() at kern_openat+0x179 > syscall() at syscall+0x1af > Xfast_syscall() at Xfast_syscall+0xe1 > --- syscall (5, FreeBSD ELF64, open), rip = 0x800e32dfc, rsp = > 0x7fffffffe608, rbp = 0x1a4 --- > > > I though this might be XENHVM kernel related, but it happens with > GENERIC kernel as well. Not sure if this is related to XEN at all. > > > > Cheers > Carsten > > >