Additional info: WARNING: at lib/dma-debug.c:933 check_unmap+0x47b/0x950() Hardware name: VirtualBox e1000 0000:00:03.0: DMA-API: device driver failed to check map error[device address=0x000000000017d1ce] [size=1241 bytes] [mapped as page] Modules linked in: tcp_diag udp_diag inet_diag rfcomm nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack bnep bluetooth rfkill ebtable_filter ebtables ip6table_filter ip6_tables snd_intel8x0 snd_ac97_codec ac97_bus snd_seq snd_seq_device ppdev snd_pcm microcode parport_pc parport snd_page_alloc snd_timer joydev i2c_piix4 i2c_core snd soundcore uinput btrfs zlib_deflate libcrc32c dm_crypt e1000 sunrpc Pid: 21718, comm: tor Not tainted 3.8.0-0.rc6.git0.1.fc19.x86_64 #1 Call Trace: <IRQ> [<ffffffff81065ed0>] warn_slowpath_common+0x70/0xa0 [<ffffffff81065f4c>] warn_slowpath_fmt+0x4c/0x50 [<ffffffff81364cfb>] check_unmap+0x47b/0x950 [<ffffffff810d37bd>] ? mark_held_locks+0x9d/0x100 [<ffffffff8136522f>] debug_dma_unmap_page+0x5f/0x70 [<ffffffffa005ff21>] e1000_unmap_and_free_tx_resource.isra.39+0x81/0x110 [e1000] [<ffffffffa0061a5a>] e1000_clean+0xfa/0x8e0 [e1000] [<ffffffff8159ddb2>] net_rx_action+0x172/0x370 [<ffffffff810703bf>] __do_softirq+0xef/0x3d0 [<ffffffff816e4ebc>] call_softirq+0x1c/0x30 <EOI> [<ffffffff8101c485>] do_softirq+0x85/0xc0 [<ffffffff815e10be>] ? ip_finish_output+0x2ee/0x7f0 [<ffffffff8106f70b>] local_bh_enable+0xdb/0xf0 [<ffffffff815e10be>] ip_finish_output+0x2ee/0x7f0 [<ffffffff815e0f08>] ? ip_finish_output+0x138/0x7f0 [<ffffffff815e2d2c>] ip_output+0x5c/0x100 [<ffffffff815e20b9>] ip_local_out+0x29/0x90 [<ffffffff815e2543>] ip_queue_xmit+0x1b3/0x670 [<ffffffff815e2395>] ? ip_queue_xmit+0x5/0x670 [<ffffffff815fc846>] tcp_transmit_skb+0x3e6/0xa60 [<ffffffff815fd056>] tcp_write_xmit+0x196/0xaf0 [<ffffffff815fdc1e>] __tcp_push_pending_frames+0x2e/0xc0 [<ffffffff815ed8cd>] tcp_sendmsg+0x11d/0xe00 [<ffffffff8161d497>] inet_sendmsg+0x117/0x230 [<ffffffff8161d385>] ? inet_sendmsg+0x5/0x230 [<ffffffff8158055a>] sock_sendmsg+0xaa/0xe0 [<ffffffff810d3f9d>] ? __lock_acquire+0x2bd/0x1910 [<ffffffff81582e96>] sys_sendto+0x126/0x1c0 [<ffffffff816e3b45>] ? sysret_check+0x22/0x5d [<ffffffff810d391d>] ? trace_hardirqs_on_caller+0xfd/0x190 [<ffffffff813509ce>] ? trace_hardirqs_on_thunk+0x3a/0x3f [<ffffffff816e3b19>] system_call_fastpath+0x16/0x1b
Created attachment 694809 [details] File: dmesg
Running rawhide in VirtualBox.
There should have been some additional logging right after that stack trace that points to where the offending dma range was mapped. do you still have that information? I'd look for it right in dmesg, but something seems to have happened to the file during upload and its corrupt.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
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.