Messages in this thread | | | Date | Sat, 26 Jul 2008 12:33:52 +0200 | From | Udo van den Heuvel <> | Subject | Re: What to do with `kswapd0: page allocation failure. ` ? |
| |
KOSAKI Motohiro wrote: >>> no bug. >>> this stack trace speak to >>> >>> 1. memory pressure increased >>> 2. kswapd ran >>> 3. network packet received >>> 4. interrupt for network happend >>> 5. but can't allocate memory for network buffer(skb). >>> 6. Then, packet dropped >>> 7. Then, warning happend. >>> >>> your network peer may resend the same packet after few times. >>> no problem. >> Thanks. >> This was on a 4GB AMD X86_64 machine running Fedora 9. >> The memory was not loaded that much. (~2 GB) >> Or was the (largish) file being cached, filling up RAM? > > maybe..
I can reproduce this by wget'ing a 5.xGB file from my MythTV box. The receiving end is a Fedora 9, AMD x86_64 box with an Abit m56s-s3 board using nVidia Corporation MCP65 Ethernet (rev a3). It uses the forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
Should I forward this info to someone so this could be fixed? Someone doing the kernel memory management? Or forcedeth? Or?
Please let me know.
Thanks, Udo
| |