I'm having this odd error running the 2.6 kernel series on my main server machine. It has four network cards and routes between two networks. On each network there are two NICs bonded together. eth0 and eth1 are slaved to bond0 using balance-xor and eth2 and eth3 are bound to bond1 using active-backup. Every second or so I get the following messages in the system log (got it through dmesg): Debug: sleeping function called from invalid context at arch/i386/lib/usercopy.c:623 in_atomic():1, irqs_disabled():0 Call Trace: [<c0117127>] __might_sleep+0xb7/0xf0 [<c0237617>] copy_from_user+0x27/0x90 [<c028570e>] netdev_ethtool_ioctl+0x4e/0x100 [<c013cdc8>] cache_flusharray+0xd8/0x100 [<c013ad8d>] test_clear_page_writeback+0x7d/0xc0 [<c0134c8b>] end_page_writeback+0x3b/0x70 [<c0137de6>] mempool_free+0x56/0xc0 [<c0137de6>] mempool_free+0x56/0xc0 [<c0274c66>] as_put_request+0x76/0xd0 [<c0137de6>] mempool_free+0x56/0xc0 [<c026dcb2>] freed_request+0xb2/0xc0 [<c02857c0>] private_ioctl+0x0/0x370 [<fda93939>] bond_update_speed_duplex+0x109/0x120 [bond1] [<c0115683>] try_to_wake_up+0xa3/0x160 [<fda958ac>] bond_mii_monitor+0x1ac/0x4d0 [bond1] [<c02f7572>] i8042_interrupt+0x162/0x170 [<fda95700>] bond_mii_monitor+0x0/0x4d0 [bond1] [<c012180c>] run_timer_softirq+0xcc/0x1b0 [<c011d565>] __do_softirq+0x85/0x90 [<c011d597>] do_softirq+0x27/0x30 [<c0107cb7>] do_IRQ+0x107/0x140 [<c0105fa8>] common_interrupt+0x18/0x20 [<c013a527>] background_writeout+0xe7/0x120 [<c013afed>] __pdflush+0xcd/0x1d0 [<c013b0f0>] pdflush+0x0/0x30 [<c013b118>] pdflush+0x28/0x30 [<c013a440>] background_writeout+0x0/0x120 [<c013b0f0>] pdflush+0x0/0x30 [<c012bf6a>] kthread+0xaa/0xb0 [<c012bec0>] kthread+0x0/0xb0 [<c0103f35>] kernel_thread_helper+0x5/0x10 I dunno how to fix it. Everything works just fine, but it makes debugging server configuration a real pain in the kneck cause I have to grep a 1.5gb syslog in order to find what I want, which takes a good bit of time. Not to mention the 5gb of rotated syslogs I had to delete. I'm pulling some iptables stuff out the log right now, and it's been about five minutes or so since it started... Anybody got any ideas on this? I'd like to at least get it to stop logging... -ryan -- huh? ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
