RE: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1
I have installed amd64 8.0 RC2 on Citrix Xenserver. GENREIC and XENHVM both booted without problems. I just checked the output of dmesg and I see the following error: lock order reversal: 1st 0xff8b0618 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2559 2nd 0xff00017a6000 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 = 0x80083757c, rsp = 0x7fffdb78, rbp = 0x8 --- -Original Message- From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org] On Behalf Of Hugo Silva Sent: 27 October 2009 06:47 PM To: freebsd-xen@freebsd.org Subject: Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 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 0xff8014810620 bufwait (bufwait) @ >> /usr/src/sys/kern/vfs_bio.c:2559 >> 2nd 0xff00015a7c00 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 = >> 0x7fffe608, 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-unsubscr...@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-unsubscr...@freebsd.org" ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1
I have two Citrix XenServer 5.5.0 servers. One with an Intel processor and one with an AMD processor. Current versions of FreebSD 8 and 9 run on the Intel processor. Both panic after displaying available memory on the AMD processor. Panic message is: panic: vm_fault: fault on nofault entry, addr: c428200 I guess I'll need to install FreeBSD 7 and then cvsup to FreeBSD 9 to really get any useful debug information. Larry -- Larry Baird| http://www.gta.com Global Technology Associates, Inc. | Orlando, FL Email: l...@gta.com | TEL 407-380-0220, FAX 407-380-6080 ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1
This sounds like you're running the domU with >1 CPU.. ? Adrian 2009/10/28 Hugo Silva : > 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 0xff8014810620 bufwait (bufwait) @ >>> /usr/src/sys/kern/vfs_bio.c:2559 >>> 2nd 0xff00015a7c00 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 = >>> 0x7fffe608, 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-unsubscr...@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-unsubscr...@freebsd.org" > ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1
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 0xff8014810620 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2559 2nd 0xff00015a7c00 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 = 0x7fffe608, 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-unsubscr...@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-unsubscr...@freebsd.org"
Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1
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 0xff8014810620 bufwait (bufwait) @ /usr/src/sys/kern/ vfs_bio.c:2559 2nd 0xff00015a7c00 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 = 0x7fffe608, 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-unsubscr...@freebsd.org"
Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1
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 0xff8014810620 bufwait (bufwait) @ /usr/src/sys/kern/ vfs_bio.c:2559 2nd 0xff00015a7c00 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 = 0x7fffe608, 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-unsubscr...@freebsd.org"
Problem: Xen 3.3.1 with FreeBSD 8.0 RC1
Hi guys, I don't know really when the bug was introduced, but maybe I can help narrowing it down. I have similar problems as others reported: Running FreeBSD 8.0-RC1 as a guest in a Xen 3.3.1 environment fails with either "kernel trap 12" in an endless loop (using amd64) or "kernel trap 9" (using i386). For 8.0-RC1 it doesn't make a difference if it's a clean install, in which case I wouldn't even be able to start the installer, or a "freebsd-update upgrade -r 8.0-RC1" from 7.2-RELEASE, in which case it wouldn't reboot with the newly compiled kernel. Funnily one of the earlier betas (not sure which one it exactly was, and can't reproduce any more, as they are not available on any mirrors), and 8.0-SNAPSHOT-200906 (tested today) both work without any problems. With the snapshot, I was also able to build a XENHVM kernel, which boots fine, and offers the XENHVM network and block devices. The environment I'm testing on is: - Intel i7 920, 12 GB RAM - Dom0 is running on CentOS 5.2 and Xen 3.3.1 (Citrix XenServer 5.5) Is there any way to extract relevant information, which would help you to fix it? I'd really like to see FreeBSD 8.0-RELEASE working on Xen! So if there is anything you need to know, please tell me what it is, and how I can gather it. Cheers Carsten ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
