Additional info: WARNING: at lib/list_debug.c:33 __list_add+0xde/0xf0() Hardware name: Presario C300 (RM444EA#ABF) list_add corruption. prev->next should be next (c0d2d1f4), but was 10101010. (prev=f49f34c4). Modules linked in: fuse ebtable_nat ipt_MASQUERADE nf_conntrack_netbios_ns nf_conntrack_broadcast ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 bnep iptable_nat nf_nat_ipv4 nf_nat iptable_mangle bluetooth nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi snd_hda_codec_conexant snd_hda_intel snd_hda_codec snd_hwdep snd_seq arc4 b43 snd_seq_device snd_pcm bcma iTCO_wdt snd_page_alloc mac80211 snd_timer joydev i2c_i801 coretemp iTCO_vendor_support lpc_ich snd hp_wmi microcode serio_raw sparse_keymap of_i2c soundcore cfg80211 rfkill binfmt_misc uinput i915 i2c_algo_bit drm_kms_helper 8139too drm 8139cp ssb mii mmc_core i2c_core wmi video sunrpc Pid: 4, comm: kworker/0:0 Not tainted 3.8.1-201.fc18.i686 #1 Call Trace: [<c043e8b2>] warn_slowpath_common+0x72/0xa0 [<c068cade>] ? __list_add+0xde/0xf0 [<c068cade>] ? __list_add+0xde/0xf0 [<c043e983>] warn_slowpath_fmt+0x33/0x40 [<c068cade>] __list_add+0xde/0xf0 [<c044c5d7>] __internal_add_timer+0x77/0xc0 [<c044cc8a>] internal_add_timer+0x1a/0x40 [<c044dcf5>] mod_timer+0xe5/0x1b0 [<c08b3bd5>] ? nlmsg_notify+0x45/0xb0 [<c044ddd6>] add_timer+0x16/0x20 [<c0459515>] __queue_delayed_work+0xa5/0x1c0 [<c0459725>] queue_delayed_work_on+0x65/0x70 [<c045976c>] queue_delayed_work+0x1c/0x20 [<c0459786>] schedule_delayed_work+0x16/0x20 [<c0898c50>] neigh_periodic_work+0x120/0x170 [<c04577e9>] process_one_work+0x119/0x3c0 [<c044dcff>] ? mod_timer+0xef/0x1b0 [<c0898b30>] ? __neigh_for_each_release+0xa0/0xa0 [<c0459979>] worker_thread+0x119/0x3b0 [<c0459860>] ? busy_worker_rebind_fn+0xd0/0xd0 [<c045e1f4>] kthread+0x94/0xa0 [<c09829f7>] ret_from_kernel_thread+0x1b/0x28 [<c045e160>] ? kthread_create_on_node+0xc0/0xc0
hmm, looks kind of like we got some list poisoning there in the entry behind the timer we were modifying (although thats not actually the LIST_POISON1 macro that should go there). Is it possible for you to get a vmcore, or add some debug code to __list_add that dumps out the timer callback function pointers of each element in the list? With luck that would tell you where the previous (corrupted) entry on the timer list came from.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.