Here's an interesting one that I just noticed in dmesg on a Linux 2.6.10
traffic accounting machine. Not sure if it's caused by pmacctd, network
conditions, or a bad kernel... but a bit scary anyhow :-)
pmacctd: page allocation failure. order:0, mode:0x20
[<c012f582>] __alloc_pages+0x1c2/0x370
[<c0133af6>] __kmalloc+0x66/0x80
[<c012f755>] __get_free_pages+0x25/0x40
[<c01329e2>] kmem_getpages+0x22/0xc0
[<c01335d9>] cache_grow+0x99/0x130
[<c01337bd>] cache_alloc_refill+0x14d/0x1f0
[<c0133b04>] __kmalloc+0x74/0x80
[<c023301f>] pskb_expand_head+0x5f/0x150
[<c02329a7>] __kfree_skb+0xa7/0x150
[<c0250b59>] ip_forward+0xf9/0x2b0
[<c024f694>] ip_rcv+0x324/0x480
[<c0238ad7>] netif_receive_skb+0x1b7/0x220
[<c01ea6c3>] e1000_clean_rx_irq+0x123/0x400
[<c01ea593>] e1000_clean_tx_irq+0x1d3/0x1e0
[<c01ea33f>] e1000_clean+0x4f/0xd0
[<c0238cb4>] net_rx_action+0x74/0x100
[<c0115b3b>] __do_softirq+0x7b/0x90
[<c0115b77>] do_softirq+0x27/0x30
[<c0103ebe>] do_IRQ+0x1e/0x30
[<c0102602>] common_interrupt+0x1a/0x20
Wim
