Date: Sun, 20 Jan 2013 12:34:17 -0600 (CST) From: Larry Rosenman <ler@lerctr.org> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-emulation@freebsd.org, freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: My panic in amd64/pmap Message-ID: <alpine.BSF.2.00.1301201229460.92780@thebighonker.lerctr.org> In-Reply-To: <f70186b875feed59491b078fab2bdb06@webmail.lerctr.org> References: <38def6b37be1a3128fb1b64595e9044e@webmail.lerctr.org> <50F95964.6060706@FreeBSD.org> <6f1d46304fbcc6e32f51109f6ab4c60d@webmail.lerctr.org> <f70186b875feed59491b078fab2bdb06@webmail.lerctr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 18 Jan 2013, Larry Rosenman wrote: > Never mind, it's in VirtualBox itself. The line is at ~~line 8020 in the > same file. I've patched it and am recompiling > VirtualBox. > > If I don't see the panic for a few days, I'll submit a PR. > I've submitted the PR, because for nehalem class or better cpu's it's probably needed, however, I can still panic FreeBSD9 or FreeBSD10 with running a zpool scrub, sometimes :(. I have vmcores and kernels from both VM's available. Latest core.txts: http://www.lerctr.org/~ler/zfs10-core.txt.4 http://www.lerctr.org/~ler/zfs9-core.txt.4 I can still give ssh access to both VM's as well as the host. I'd really like to get to the bottom of this..... -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1301201229460.92780>