> > Jun 5 22:07:26 dreamscape kernel: IP: queue_glue: no memory for gluing queue c1c75080
> > Jun 5 22:07:35 dreamscape kernel: IP: queue_glue: no memory for gluing queue c1c753e0
> > Jun 5 22:08:38 dreamscape kernel: IP: queue_glue: no memory for gluing queue c14b27e0
> > Jun 5 22:08:42 dreamscape kernel: IP: queue_glue: no memory for gluing queue c1c75320
> > Jun 5 22:08:45 dreamscape kernel: IP: queue_glue: no memory for gluing queue c1c75500
> > Jun 5 22:08:47 dreamscape kernel: IP: queue_glue: no memory for gluing queue c1c75aa0
> > Jun 5 22:08:53 dreamscape last message repeated 3 times
> > Jun 5 22:09:12 dreamscape kernel: IP: queue_glue: no memory for gluing queue c1e56020
> > Jun 5 22:09:34 dreamscape last message repeated 4 times
>
> That looks like very heavy NFS traffic and a need to up the vm limits. Ok
> thats showing 2.0.31pre2 still has some vm balancing issues
I get that a lot at work on my 2.1.42 machine. It causes me to need to
either reboot it or shut down whatever is causing the traffic. It seems
to have the effect of locking AMD on the 2.0.30 machine which it's doing
NFS xfers with...
-bp
-- B. James Phillippe Seattle Software Labs, Inc Network Administrator Phone: (206) 521-8346 NIC Handle: BJP4 Fax: (206) 521-8340 http://w3.terran.org/~bryan http://www.sealabs.com