On Sun, Jul 13, 2008 at 01:02:22PM +0200, Francois Romieu wrote:
> Alex Samad <alex@samad.com.au> :
> [...]
> > For a while now I have been receiving page swap allocation failures
> > 
> > 
> > Similar to http://lkml.org/lkml/2008/6/10/3 and
> 
> Order 0 failure. Your is an order 2 one.
> 
> > http://lkml.org/lkml/2008/2/19/298
> 
> Order 3 failure which was fixed with the e1000e driver.


not sure about these, I will take your word for it.

> 
> > and I have filed a bug with debian (Bug#486300)
> > 
> > 
> > It seems like any time I put the system under load, transferring large
> > files across the network  (1G nic, a r8186 and forcedeth and a
> > broadcom).  I keep getting these errors
> 
> May I assume that you are working with a MTU greater than 1500 bytes on
> each interface ? If so plese add netdev@vger.kernel.org to the Cc: and
> remove linux-kernel@ from the Cc:.

I have 3 boxes, 2 are setup with > 1500 mtu and 1 isn't (the one with
the r8186 driver), I have tested with >1500 mtu and with mtu = 1500 with
the same result.

> 
> [...]
> > Jul 13 13:28:30 nas kernel: [  648.120756]  [<ffffffff881b525f>]
> > :r8168:rtl8168_rx_fill+0x64/0x106
> 
> It looks more like Realtek's out-of-tree driver than like the in-kernel
> one. Is it a customised kernel ?
The kernel is a stock debian amd64 kernel, not customised by me.

I did build the r8168 from the realtek site.

bit more info on the setup

I have 2 laptops (both HP's), 1(A) running Vista 1(B) running Debian lenny/sid
(2.6.25). I have three servers 2 shuttles (forcedeth) (multimedia & hufpuf ) 1 gigabyte
(realtek) (nas).

The nas box is the one I coped the error from the syslog. it is
primarily a nfs nas.  Hufpuf is the samba box, it used to be the nas
box. it currently mounts a few (large) shares from nas.  Multimedia is a
backup server.

A & B & NAS have 1500 MTU

multimedia and hufpuf can run with 9100 mtu

I have tried
i) coping files from A to hufpuf (smb) which then sends it on to nas via
nfs
ii) copy files from B to nas (nfs)
iii) scp from B to hufpuf and then on to nas via nfs
iv) scp from B to nas
v) scp from hufpuf to nas
vi) scp from hufpuf to multimedia
vii) scp from multimedia to nas
viii) hufpuf nfs to nas
ix) multimedia nfs to nas

all of these have caused these errors.

when I was testing again today, I noticed when I was coping from A to
hufpuf and then onto nas. that smaller files say < 200M would go okay,
anything greater (or if the total of the files was greater) then I would
start to get the errors.
 

> 
> [...]
> > Help
> 
> Don't panic.
not panicing yet but I am a bit concerned. the data seems to be okay
even after these errors


> 
> -- 
> Ueimor
> 

-- 
"You see, the Senate wants to take away some of the powers of the administrative branch."

	- George W. Bush
09/19/2002
Washington, DC