On Wed, Jan 20, 2010 at 03:42:08PM -0800, Pyun YongHyeon wrote:
> On Wed, Jan 20, 2010 at 03:12:51PM -0800, Erik Klavon wrote:
> > On Thu, Jan 14, 2010 at 03:26:18PM -0800, Erik Klavon wrote:
> > > On Wed, Jan 13, 2010 at 06:06:40PM -0800, Pyun YongHyeon wrote:
> > > > On Wed, Jan 13, 2010 at 05:47
On Wed, Jan 20, 2010 at 03:12:51PM -0800, Erik Klavon wrote:
> On Thu, Jan 14, 2010 at 03:26:18PM -0800, Erik Klavon wrote:
> > On Wed, Jan 13, 2010 at 06:06:40PM -0800, Pyun YongHyeon wrote:
> > > On Wed, Jan 13, 2010 at 05:47:19PM -0800, Erik Klavon wrote:
> > > > One of my amd64 machines running
On Thu, Jan 14, 2010 at 03:26:18PM -0800, Erik Klavon wrote:
> On Wed, Jan 13, 2010 at 06:06:40PM -0800, Pyun YongHyeon wrote:
> > On Wed, Jan 13, 2010 at 05:47:19PM -0800, Erik Klavon wrote:
> > > One of my amd64 machines running 8.0p1 acting as a NAT system for many
> > > network clients dropped
On Wed, Jan 13, 2010 at 06:06:40PM -0800, Pyun YongHyeon wrote:
> On Wed, Jan 13, 2010 at 05:47:19PM -0800, Erik Klavon wrote:
> > One of my amd64 machines running 8.0p1 acting as a NAT system for many
> > network clients dropped into kdb today. tr indicates a problem in
> > bge.
> >
> > Tracing p
On Wed, Jan 13, 2010 at 05:47:19PM -0800, Erik Klavon wrote:
> Hi
>
> One of my amd64 machines running 8.0p1 acting as a NAT system for many
> network clients dropped into kdb today. tr indicates a problem in
> bge.
>
> Tracing pid 12 tid 100033 td 0xff0001687000
> pmap_kextract() at pmap_kex