Date: Wed, 28 Oct 2009 01:57:40 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Hugo Silva <hugo@barafranca.com> Cc: freebsd-xen@freebsd.org Subject: Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 Message-ID: <d763ac660910271057j4471a8e1v643035c609950ff2@mail.gmail.com> In-Reply-To: <4AE723F4.10606@barafranca.com> References: <850CF1B7-499E-4468-9045-19A2803E6D05@ossafe.org> <3941E1B9-6CD6-4D9A-AF1C-93401F571FCE@heesch.me.uk> <8C3C0877-F36E-45D1-BDEE-4EE22BD45205@ossafe.org> <4AE723F4.10606@barafranca.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This sounds like you're running the domU with >1 CPU.. ? Adrian 2009/10/28 Hugo Silva <hugo@barafranca.com>: > Carsten Heesch wrote: >> >> 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 >>> >>> >>> >> >> _______________________________________________ >> freebsd-xen@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > > > I grabbed the 8.0-RC2/amd64iso to give this a spin; no luck here, it hangs > after "Trying to mount root from ufs:/dev/md0". Also, I confirm the panics > on boot with RC1. It's gone with RC2, but as I said, it gets stuck (for me, > at least). > > My dom0 is NetBSD 5 / amd64. > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d763ac660910271057j4471a8e1v643035c609950ff2>