Bug 956732

Summary: tulip: WARNING: at lib/dma-debug.c:937 check_unmap+0x47d/0x930()
Product: [Fedora] Fedora Reporter: dlelliott99
Component: kernelAssignee: Neil Horman <nhorman>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, nhorman
Target Milestone: ---Keywords: Patch, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1a86e7973a0239c91e688e6ca7c9cb9f0eeda550
Fixed In Version: kernel-3.9.8-300.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-01 01:39:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg
none
patch to error check dma mapping none

Description dlelliott99 2013-04-25 13:56:01 UTC 
Description of problem:
During update of initial Fedora 19 alpha installation

Additional info:
WARNING: at lib/dma-debug.c:937 check_unmap+0x47d/0x930()
Hardware name: System Product Name
tulip 0000:03:07.0: DMA-API: device driver failed to check map error[device address=0x00000000c42bfcd2] [size=90 bytes] [mapped as single]
Modules linked in:
 ipt_MASQUERADE nf_conntrack_netbios_ns nf_conntrack_broadcast ip6table_nat nf_nat_ipv6 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 ebtable_filter ebtables ip6table_filter ip6_tables snd_hda_codec_realtek snd_hda_intel acpi_cpufreq mperf snd_hda_codec sp5100_tco snd_hwdep snd_seq snd_seq_device snd_pcm ppdev kvm snd_page_alloc edac_core edac_mce_amd snd_timer i2c_piix4 snd microcode k10temp tulip r8169 mii parport_pc parport asus_atk0110 soundcore dm_crypt ata_generic pata_acpi pata_atiixp nouveau video mxm_wmi i2c_algo_bit drm_kms_helper ttm drm i2c_core wmi uinput
Pid: 1341, comm: dbus-daemon-lau Not tainted 3.9.0-0.rc6.git2.3.fc19.x86_64 #1
Call Trace:
 <IRQ>  [<ffffffff81069106>] warn_slowpath_common+0x66/0x80
 [<ffffffff8106916c>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffff8138151d>] check_unmap+0x47d/0x930
 [<ffffffff81021d69>] ? sched_clock+0x9/0x10
 [<ffffffff81381a2f>] debug_dma_unmap_page+0x5f/0x70
 [<ffffffffa01f4050>] tulip_interrupt+0x6f0/0x1040 [tulip]
 [<ffffffff81119636>] handle_irq_event_percpu+0x56/0x390
 [<ffffffff811199ad>] handle_irq_event+0x3d/0x60
 [<ffffffff8111cb6a>] handle_fasteoi_irq+0x5a/0x100
 [<ffffffff8101c36f>] handle_irq+0xbf/0x150
 [<ffffffff81073b10>] ? irq_enter+0x50/0xa0
 [<ffffffff8172738d>] do_IRQ+0x4d/0xc0
 [<ffffffff8171c6b2>] common_interrupt+0x72/0x72
 <EOI>  [<ffffffff8136eaf4>] ? find_next_bit+0x94/0xe0
 [<ffffffff8130cfe4>] mls_level_isvalid+0xd4/0x150
 [<ffffffff8130d094>] mls_range_isvalid+0x34/0x60
 [<ffffffff8130d0ec>] mls_context_isvalid+0x2c/0xb0
 [<ffffffff81304aa0>] policydb_context_isvalid+0x90/0xb0
 [<ffffffff8130753f>] security_compute_sid.part.13+0x3ef/0x530
 [<ffffffff813076ce>] security_compute_sid+0x4e/0x50
 [<ffffffff8130964d>] security_transition_sid+0x2d/0x40
 [<ffffffff812face0>] selinux_bprm_set_creds+0x1a0/0x3c0
 [<ffffffff812edf53>] security_bprm_set_creds+0x13/0x20
 [<ffffffff811e0c58>] prepare_binprm+0xc8/0x200
 [<ffffffff811e2bd0>] do_execve_common.isra.26+0x5e0/0x710
 [<ffffffff811e2702>] ? do_execve_common.isra.26+0x112/0x710
 [<ffffffff811e3006>] sys_execve+0x36/0x50
 [<ffffffff81725cc9>] stub_execve+0x69/0xa0
Comment 1 dlelliott99 2013-04-25 13:56:05 UTC 
Created attachment 739907 [details]
File: dmesg
Comment 2 Neil Horman 2013-04-25 14:15:48 UTC 
Created attachment 739922 [details]
patch to error check dma mapping

please build and test a kernel with this patch, it should solve your problem. 

Thanks!
Comment 3 Neil Horman 2013-05-08 20:04:29 UTC 
ping, any feedback here?
Comment 4 Neil Horman 2013-06-13 19:32:08 UTC 
This is pretty straightforward, so I've just sent it  upstream
Comment 5 Neil Horman 2013-06-18 17:29:04 UTC 
upstream commit 2087ac1fc6fd9bbb1f7e16889e984e0af0510b4b
Comment 6 Fedora Update System 2013-06-27 22:15:09 UTC 
kernel-3.9.8-300.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/kernel-3.9.8-300.fc19
Comment 7 Fedora Update System 2013-06-29 15:24:20 UTC 
Package kernel-3.9.8-300.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.9.8-300.fc19'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-11901/kernel-3.9.8-300.fc19
then log in and leave karma (feedback).
Comment 8 Fedora Update System 2013-07-01 01:39:40 UTC 
kernel-3.9.8-300.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.