Jesper Dangaard Brouer writes: > I have tried to track down the problem, and I think I have narrowed it > a bit down. My theory is that it is related to the route cache > (ip_dst_cache) or FIB, which cannot dealloacate route cache slab > elements (maybe RCU related). (I have seen my route cache increase to > around 520k entries using rtstat, before dying). > > I'm using the FIB trie system/algorithm (CONFIG_IP_FIB_TRIE). Think > that the error might be cause by the "fib_trie" code. See the syslog, > output below. > Syslog#1 (indicating a problem with the fib trie) > -------- > Mar 20 18:00:04 hostname kernel: Debug: sleeping function called from invalid context at mm/slab.c:2472 > Mar 20 18:00:04 hostname kernel: in_atomic():1, irqs_disabled():0 > Mar 20 18:00:04 hostname kernel: [<c0103d9f>] dump_stack+0x1e/0x22 > Mar 20 18:00:04 hostname kernel: [<c011cbe1>] __might_sleep+0xa6/0xae > Mar 20 18:00:04 hostname kernel: [<c014f3e9>] __kmalloc+0xd9/0xf3 > Mar 20 18:00:04 hostname kernel: [<c014f5a4>] kzalloc+0x23/0x50 > Mar 20 18:00:04 hostname kernel: [<c030ecd1>] tnode_alloc+0x3c/0x82 > Mar 20 18:00:04 hostname kernel: [<c030edf6>] tnode_new+0x26/0x91 > Mar 20 18:00:04 hostname kernel: [<c030f757>] halve+0x43/0x31d > Mar 20 18:00:04 hostname kernel: [<c030f090>] resize+0x118/0x27e Hello! Out of memory? Running BGP with full routing? And large number of flows. Whats your normal number of entries route cache? And how much memory do you have? From your report problems seems to related to flushing either rt_cache_flush or fib_flush (before there was dev_close()?) so all associated entries should freed. All the entries are freed via RCU which due to the deferred delete can give a very high transient memory pressure. If we believe it's memory problem we can try something out... Cheers. --ro - : send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
