Date: Thu, 24 May 2012 08:47:46 -0500 From: Mark Felder <feld@feld.me> To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Cc: Adrian Chadd <adrian@freebsd.org>, dene@ilovedene.com Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash Message-ID: <op.wete9wbq34t2sn@tech304> In-Reply-To: <CAJ-Vmoneopo8xNpThbewfE2tg6HrdH74DXurO38P_aVs=YS9%2BA@mail.gmail.com> References: <op.wbwe9s0k34t2sn@tech304> <op.wen3bwws34t2sn@tech304> <490F2075-3E4D-4F85-9935-937CED8FB10B@averesystems.com> <op.wen42clw34t2sn@tech304> <CAJ-Vmoneopo8xNpThbewfE2tg6HrdH74DXurO38P_aVs=YS9%2BA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 May 2012 17:30:40 -0500, Adrian Chadd <adrian@freebsd.org> wrote: > Hi, > > can you please, -please- file a PR? And place all of the above > information in it so we don't lose it? > I'd be glad to post a PR and assist in helping to get it permanently fixed. I certainly don't want this data to get lost and honestly our business uses FreeBSD on VMWare so much that we really need a permanent fix as much as anyone else :-) The reason I've hesitated to post a PR so far is that I didn't have any truly useful or concrete evidence of where the problem lies. After Dane Foster contacted me and told me he could recreate the crash on demand with his workload it was easier to narrow things down. The suggestion that it was an interrupts issue (by possibly Bjoern Zeeb?) and Dane's discovery that his crashes ceased when em0 and mpt0 share an IRQ, but em0 is completely unused was starting to prove there is some strong evidence here in favor of the interrupts issue. Dane, what's the status on your end? Has your fix still been successful? Is it also stable if you simply set hint.mpt.0.msi_enable="1" ? Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wete9wbq34t2sn>