Date: Wed, 23 May 2012 15:30:40 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Mark Felder <feld@feld.me> Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash Message-ID: <CAJ-Vmoneopo8xNpThbewfE2tg6HrdH74DXurO38P_aVs=YS9%2BA@mail.gmail.com> In-Reply-To: <op.wen42clw34t2sn@tech304> References: <op.wbwe9s0k34t2sn@tech304> <op.wen3bwws34t2sn@tech304> <490F2075-3E4D-4F85-9935-937CED8FB10B@averesystems.com> <op.wen42clw34t2sn@tech304>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, can you please, -please- file a PR? And place all of the above information in it so we don't lose it? If this is indeed the problem then I really think we should root cause why the driver and/or interrupt handling code is getting angry with the shared interrupt. I'd also appreciate it if you and the other people who can reproduce this could work with the em/mpt driver people and root cause why this is going. I think having FreeBSD on vmware work stable out of the box without these kinds of tweaks is the way to go - who knows what else is lurking here.. I'm very very glad you've persisted with this and if I had them, I'd send you a "FreeBSD persistent bug reporter!" t-shirt. Thanks, Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmoneopo8xNpThbewfE2tg6HrdH74DXurO38P_aVs=YS9%2BA>