Hello, Eugene.
You wrote 19 января 2011 г., 12:50:25:
Yes, I've missed it's PRERELEASE already.
Backtrace points to the problem in em_local_timer() fixed in CURRENT
7 days ago, take a look:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/e1000/if_em.c#rev1.65
I run my servers with this
Hi Jack,
I was hoping to pull down the latest em drivers from HEAD to stable to
see if it will help with the one issue I am seeing still as well as fix
the tftp issue with small UDP packets (kern/152853. Apart from removing
the sysctl changes (SVN rev 217556 on 2011-01-18 21:14:23Z by mdf)
NO, and i was rather irritated by a checkin that broke backward
compatibility without
even asking me first btw. That should be the only issue however, and it can
be fixed
by a define. I'll get there soon.
Jack
On Thu, Jan 20, 2011 at 9:00 AM, Mike Tancsa m...@sentex.net wrote:
Hi Jack,
Hello,
Currently our buildworld relies on groff(1) and vgrind(1) being present
in the host system. I have a patch ready that at least makes sure these
are built during bootstrap-tools and completes the WITHOUT_GROFF flag.
vgrind(1) is only used for two papers under share/doc and we could
easily
On Thu, 20 Jan 2011 21:17:40 +0100
Ulrich Spörlein u...@freebsd.org wrote:
Hello,
Currently our buildworld relies on groff(1) and vgrind(1) being
present in the host system. I have a patch ready that at least makes
sure these are built during bootstrap-tools and completes the
WITHOUT_GROFF
On Thu, 20.01.2011 at 15:31:03 -0500, Alexander Kabaev wrote:
On Thu, 20 Jan 2011 21:17:40 +0100
Ulrich Spörlein u...@freebsd.org wrote:
Hello,
Currently our buildworld relies on groff(1) and vgrind(1) being
present in the host system. I have a patch ready that at least makes
sure
On Jan 20, 2011, at 12:31 PM, Alexander Kabaev wrote:
On Thu, 20 Jan 2011 21:17:40 +0100
Ulrich Spörlein u...@freebsd.org wrote:
Hello,
Currently our buildworld relies on groff(1) and vgrind(1) being
present in the host system. I have a patch ready that at least makes
sure these are
