Date: Sat, 28 Jul 2012 06:36:13 -0400 From: Carmel <carmel_ny@hotmail.com> To: freebsd-emulation@freebsd.org Subject: Re: become worse now - Re: one virtualbox vm disrupts all vms and entire network - finally fixed now Message-ID: <BLU0-SMTP18631EAE44B128E0DCF4EB593C00@phx.gbl> In-Reply-To: <CAEXKtDo--vefivg6AJij7d0V2KHACR6f6ff9BLnGTbeO9YEBeQ@mail.gmail.com> References: <CAEXKtDo--vefivg6AJij7d0V2KHACR6f6ff9BLnGTbeO9YEBeQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 27 Jul 2012 22:05:27 -0400 Steve Tuts articulated: > finally fixed now, see fully reply in the end. Seriously, couldn't you have stripped out all of the redundant data before continuing? > It turned out this might not be a virtualbox problem, as searching > "freebsd network problem" has quite some problem, especially this > page shows theBroadcom bce card problem (which is what we have) and > the solution. After > adding > > kern.ipc.nmbclusters="131072" > hw.bce.tso_enable=0 > hw.pci.enable_msix=0 > > to /boot/loader.conf.local and reboot, no network problem has occured > for 3.5 days, while there were 3-7 occurrance of the network problem > every day. So consider this problem finally solved. > > So it appears to be a Broadcom driver issue and probably system > tuning issue. Have you filed a PR against it? -- Carmel ✌ carmel_ny@hotmail.com Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the "Reply-To" header.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BLU0-SMTP18631EAE44B128E0DCF4EB593C00>