Date: Thu, 29 Mar 2012 11:53:02 -0500 From: Alan Cox <alan.l.cox@gmail.com> To: Mark Felder <feld@feld.me> Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org, Hans Petter Selasky <hselasky@c2i.net> Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash Message-ID: <CAJUyCcNn%2B8uDrWGJMUD8vmmJKLA0iJjy6bhDSZvGB82X6awAPw@mail.gmail.com> In-Reply-To: <op.wbxxb9cz34t2sn@tech304> References: <201203291549.q2TFnUc7080406@aurora.sol.net> <201203291755.36651.hselasky@c2i.net> <op.wbxxb9cz34t2sn@tech304>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 29, 2012 at 11:27 AM, Mark Felder <feld@feld.me> wrote: > On Thu, 29 Mar 2012 10:55:36 -0500, Hans Petter Selasky <hselasky@c2i.net> > wrote: > >> >> It almost sounds like the lost interrupt issue I've seen with USB EHCI >> devices, though disk I/O should have a retry timeout? >> >> What does "wmstat -i" output? >> >> --HPS >> > > > Here's a server that has a week uptime and is due for a crash any hour now: > > root@server:/# vmstat -i > interrupt total rate > irq1: atkbd0 34 0 > irq6: fdc0 9 0 > irq15: ata1 34 0 > irq16: em1 778061 1 > irq17: mpt0 19217711 31 > irq18: em0 283674769 460 > cpu0: timer 246571507 400 > Total 550242125 892 > > Not so long ago, VMware implemented a clever scheme for reducing the overhead of virtualized interrupts that must be delivered by at least some (if not all) of their emulated storage controllers: http://static.usenix.org/events/atc11/tech/techAbstracts.html#Ahmad Perhaps, there is a bad interaction between this scheme and FreeBSD's mpt driver. Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJUyCcNn%2B8uDrWGJMUD8vmmJKLA0iJjy6bhDSZvGB82X6awAPw>