Date: Fri, 25 May 2012 08:54:04 +1200 From: dane foster <dene@ilovedene.com> To: Mark Felder <feld@feld.me> Cc: freebsd-hackers@freebsd.org, Adrian Chadd <adrian@freebsd.org>, freebsd-questions@freebsd.org Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash Message-ID: <62F1D149-FC1C-4E00-98FD-DF6C46A5DC55@ilovedene.com> In-Reply-To: <op.wete9wbq34t2sn@tech304> 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> <op.wete9wbq34t2sn@tech304>
next in thread | previous in thread | raw e-mail | index | archive | help
Hey all, On 25/05/2012, at 1:47 AM, Mark Felder wrote: > On Wed, 23 May 2012 17:30:40 -0500, Adrian Chadd <adrian@freebsd.org> = wrote: >=20 >> Hi, >>=20 >> can you please, -please- file a PR? And place all of the above >> information in it so we don't lose it? >>=20 >=20 > 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 :-) >=20 > 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. >=20 > 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=3D"1" ? >=20 The situation I've got that's stable now is: hw.pci.enable_msi=3D"0" hw.pci.enable_msix=3D"0" in /boot/loader.conf and: samael:~:% vmstat -i [ = 6:31PM] interrupt total rate irq1: atkbd0 6 0 irq18: em0 mpt0 3061100 15 irq19: em1 6891706 35 cpu0: timer 166383735 868 cpu1: timer 166382123 868 cpu3: timer 166382123 868 cpu2: timer 166382121 868 Total 675482914 3525 Not using em0. This works for 8 (FreeBSD samael.slush.ca 8.3-STABLE = FreeBSD 8.3-STABLE #1: Mon May 7 11:51:03 NZST 2012 = root@samael.slush.ca:/usr/obj/usr/src/sys/DENE amd64). Neither of those settings on their own seem to stop it from happening. The 9 box I've tried this on still hangs almost every time i run = handbrake, no matter whether MSI/MSIX is enabled, or I have separate = IRQs for mpt0 and em0/1 I can cause the hang mostly on demand, but not quite sure what = information to provide from the hung system. If somebody can let me know = what they need, including root access, I can make that happen. Cheers, Dane >=20 > Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?62F1D149-FC1C-4E00-98FD-DF6C46A5DC55>