Description of problem: e100 triggers complaint from DMA-API checker. Version-Release number of selected component (if applicable): kernel-PAE-3.9.0-0.rc4.git0.1.fc19.i686 How reproducible: every time Steps to Reproduce: 1. boot to multi-user 2. 3. Actual results: kernel: [ 135.553283] ------------[ cut here ]------------ kernel: [ 135.554028] WARNING: at lib/dma-debug.c:937 check_unmap+0x493/0x950() kernel: [ 135.554028] Hardware name: System Name kernel: [ 135.554028] e100 0000:02:0a.0: DMA-API: device driver failed to check map error[device address=0x0000000025b31a12] [size=90 bytes] [mapped as single] kernel: [ 135.554028] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables iTCO_wdt iTCO_vendor_support gpio_ich microcode snd_cmipci snd_mpu401_uart snd_opl3_lib snd_hwdep gameport snd_rawmidi snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer snd soundcore i2c_i801 lpc_ich of_i2c uinput isofs squashfs radeon i2c_algo_bit drm_kms_helper ttm drm e100 mii i2c_core sunrpc kernel: [ 135.554028] Pid: 651, comm: nm-online Not tainted 3.9.0-0.rc4.git0.1.fc19.i686 #1 kernel: [ 135.554028] Call Trace: kernel: [ 135.554028] [<c0441aac>] warn_slowpath_common+0x6c/0xa0 kernel: [ 135.554028] [<c06ea623>] ? check_unmap+0x493/0x950 kernel: [ 135.554028] [<c06ea623>] ? check_unmap+0x493/0x950 kernel: [ 135.554028] [<c0441b13>] warn_slowpath_fmt+0x33/0x40 kernel: [ 135.554028] [<c06ea623>] check_unmap+0x493/0x950 kernel: [ 135.554028] [<c06eab47>] debug_dma_unmap_page+0x67/0x70 kernel: [ 135.554028] [<f7c42d78>] e100_tx_clean+0xc8/0x1c0 [e100] kernel: [ 135.554028] [<c047e08f>] ? sched_clock_cpu+0xdf/0x150 kernel: [ 135.554028] [<f7c43672>] e100_poll+0x482/0x560 [e100] kernel: [ 135.554028] [<c090df80>] net_rx_action+0x130/0x2e0 kernel: [ 135.554028] [<c044b6d9>] __do_softirq+0xc9/0x350 kernel: [ 135.554028] [<c047e08f>] ? sched_clock_cpu+0xdf/0x150 kernel: [ 135.554028] [<c044baf5>] irq_exit+0xa5/0xb0 kernel: [ 135.554028] [<c0404c65>] do_IRQ+0x45/0xb0 kernel: [ 135.554028] [<c04a92bc>] ? trace_hardirqs_on_caller+0xec/0x170 kernel: [ 135.554028] [<c0a39ff8>] common_interrupt+0x38/0x40 kernel: [ 135.554028] [<c04a007b>] ? print_tickdevice+0xcb/0x390 kernel: [ 135.554028] [<c0a31823>] ? _raw_spin_unlock_irqrestore+0x33/0x70 kernel: [ 135.554028] [<c0a28d9c>] __slab_free+0x5d/0x332 kernel: [ 135.554028] [<c08fcdf5>] ? skb_free_head+0x45/0x50 kernel: [ 135.554028] [<c04a934b>] ? trace_hardirqs_on+0xb/0x10 kernel: [ 135.554028] [<c04a9581>] ? debug_check_no_locks_freed+0xb1/0x150 kernel: [ 135.554028] [<c0561962>] kfree+0x262/0x290 kernel: [ 135.554028] [<c08fcdf5>] ? skb_free_head+0x45/0x50 kernel: [ 135.554028] [<c08fcdf5>] ? skb_free_head+0x45/0x50 kernel: [ 135.554028] [<c08fcdf5>] skb_free_head+0x45/0x50 kernel: [ 135.554028] [<c08fff34>] skb_release_data+0xb4/0xc0 kernel: [ 135.554028] [<c08fff57>] __kfree_skb+0x17/0x90 kernel: [ 135.554028] [<c090002b>] consume_skb+0x2b/0x120 kernel: [ 135.554028] [<c09bb0e3>] unix_stream_recvmsg+0x3b3/0x7c0 kernel: [ 135.554028] [<c066f602>] ? sock_has_perm+0x112/0x200 kernel: [ 135.554028] [<c08f4686>] sock_aio_read+0x106/0x140 kernel: [ 135.554028] [<c066a1b2>] ? avc_has_perm_flags+0x22/0x310 kernel: [ 135.554028] [<c0574c67>] do_sync_read+0x97/0xd0 kernel: [ 135.554028] [<c057538d>] vfs_read+0x12d/0x150 kernel: [ 135.554028] [<c0575541>] sys_read+0x41/0x80 kernel: [ 135.554028] [<c0a39acd>] sysenter_do_call+0x12/0x38 kernel: [ 135.554028] ---[ end trace b0a5e47c7942c78b ]--- kernel: [ 135.554028] Mapped at: kernel: [ 135.554028] [<c06e91a3>] debug_dma_map_page+0x63/0x130 kernel: [ 135.554028] [<f7c42385>] e100_xmit_prepare+0xf5/0x160 [e100] kernel: [ 135.554028] [<f7c40870>] e100_exec_cb+0x70/0x120 [e100] kernel: [ 135.554028] [<f7c42423>] e100_xmit_frame+0x33/0x170 [e100] kernel: [ 135.554028] [<c090ee5e>] dev_hard_start_xmit+0x21e/0x630 Expected results: no complaint Additional info: Probably same as bug 928024 but with different driver. [Yes, the machine is slow: that timestamp of 135 seconds from boot is Fedora Live Desktop on DVD running on 1.6GHz Pentium 4.]
*** This bug has been marked as a duplicate of bug 907694 ***