Date: Thu, 13 Sep 2012 20:47:47 -0400 From: Mark Saad <nonesuch@longcount.org> To: Mark Felder <feld@feld.me> Cc: "freebsd-hackers@FreeBSD.org" <freebsd-hackers@FreeBSD.org> Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash Message-ID: <FA5D6460-FCB1-4A9E-BC87-B8808F657723@longcount.org> In-Reply-To: <66357a32-b570-4dc3-a27c-d32903da41db@email.android.com> References: <op.wbwe9s0k34t2sn@tech304> <201205311157.42909.jhb@freebsd.org> <19d73256-b7c6-417e-a051-a5faeabf219d@email.android.com> <201209121520.26337.jhb@freebsd.org> <op.wkkwu1sx34t2sn@tech304> <5051F7A0.90901@FreeBSD.org> <op.wkk0qzwj34t2sn@tech304> <20120913162815.GA1219@pix.net> <op.wkla2ksa34t2sn@tech304> <50524C67.3040403@FreeBSD.org> <F19B7985-3286-4026-8106-66F3A3BB07AD@longcount.org> <66357a32-b570-4dc3-a27c-d32903da41db@email.android.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--- On Sep 13, 2012, at 7:45 PM, Mark Felder <feld@feld.me> wrote: > Changing timer source has not been tested. It doesn't crash in 7.x, so did= something timer related change in 8.x? >=20 Mark Yes the time counter choice priority changed , in 8 favoring higher precis= ion hardware like hpet over acpi-fast/safe . I am not sure why or when thus w= as done; or if this is a side effect of another change. Interestingly centos= /rhel/suse has made similar changes and VMware has odd issues with them as w= ell.=20 Can you boot up a 7 environment and get us the value sysctl kern.timecounter= . Then get that from an a 8 and 9 environment . Then if the 7 environment u= ses a different time counter can you try using that value on your crashing s= etup and report back what the result is .=20 --- Mark saad | mark.saad@longcount.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FA5D6460-FCB1-4A9E-BC87-B8808F657723>