From: Dave Jones <davej@redhat.com>
To: netdev@vger.kernel.org
Subject: e1000e failed to check map error
Date: Fri, 1 Mar 2013 00:30:07 -0500 [thread overview]
Message-ID: <20130301053007.GA14474@redhat.com> (raw)
Linus' current tree shows this shortly after boot for me..
WARNING: at lib/dma-debug.c:933 check_unmap+0x407/0x8a0()
Hardware name:
e1000e 0000:05:00.0: DMA-API: device driver failed to check map error[device address=0x000000005bd70000] [size=1376 bytes] [mapped as page]
Modules linked in:
ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_conntrack nf_conntrack ip6table_filter ip6_tables snd_emu10k1 coretemp snd_hwdep snd_util_mem snd_ac97_codec ac97_bus snd_rawmidi snd_seq snd_seq_device microcode snd_pcm pcspkr snd_page_alloc e1000e snd_timer snd soundcore ptp pps_core vhost_net tun macvtap macvlan kvm_intel kvm nfsd binfmt_misc auth_rpcgss nfs_acl lockd sunrpc btrfs libcrc32c lzo_compress zlib_deflate firewire_ohci ata_piix firewire_core sata_sil crc_itu_t radeon i2c_algo_bit hwmon drm_kms_helper ttm drm i2c_core floppy
Pid: 9, comm: rcuc/0 Not tainted 3.8.0+ #75
Call Trace:
<IRQ> [<ffffffff8104abe5>] warn_slowpath_common+0x75/0xa0
[<ffffffff8104acc6>] warn_slowpath_fmt+0x46/0x50
[<ffffffff8135caf7>] check_unmap+0x407/0x8a0
[<ffffffff8110457d>] ? call_rcu+0x1d/0x20
[<ffffffff8135d1ae>] debug_dma_unmap_page+0x5e/0x70
[<ffffffffa04552f1>] e1000_put_txbuf.isra.33+0x91/0x130 [e1000e]
[<ffffffffa045546b>] e1000_clean_tx_irq+0xdb/0x320 [e1000e]
[<ffffffffa045dbe1>] e1000e_poll+0x61/0x320 [e1000e]
[<ffffffff815677aa>] net_rx_action+0x16a/0x370
[<ffffffff81054780>] __do_softirq+0xf0/0x410
[<ffffffff816b3b3c>] call_softirq+0x1c/0x30
<EOI> [<ffffffff8100480d>] do_softirq+0x8d/0xc0
[<ffffffff81102555>] ? rcu_cpu_kthread+0x135/0x5f0
[<ffffffff81054045>] local_bh_enable+0x105/0x110
[<ffffffff81102555>] rcu_cpu_kthread+0x135/0x5f0
[<ffffffff81084730>] smpboot_thread_fn+0x170/0x2e0
[<ffffffff810845c0>] ? __smpboot_create_thread.part.2+0xe0/0xe0
[<ffffffff8107a62d>] kthread+0xed/0x100
[<ffffffff816a7062>] ? wait_for_completion+0xe2/0x110
[<ffffffff8107a540>] ? kthread_create_on_node+0x160/0x160
[<ffffffff816b279c>] ret_from_fork+0x7c/0xb0
[<ffffffff8107a540>] ? kthread_create_on_node+0x160/0x160
---[ end trace 3d84e8d9b678cf33 ]---
Mapped at:
[<ffffffff8135d269>] debug_dma_map_page+0xa9/0x150
[<ffffffffa045791c>] e1000_xmit_frame+0x69c/0xf10 [e1000e]
[<ffffffff81568cf0>] dev_hard_start_xmit+0x260/0x700
[<ffffffff8158b90e>] sch_direct_xmit+0xfe/0x2a0
[<ffffffff815693d6>] dev_queue_xmit+0x246/0x970
next reply other threads:[~2013-03-01 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 5:30 Dave Jones [this message]
2013-03-01 17:13 ` e1000e failed to check map error Allan, Bruce W
2013-03-12 18:51 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130301053007.GA14474@redhat.com \
--to=davej@redhat.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).