From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 1/5] iwlwifi: fix dma mappings and skbs leak
Date: Mon, 28 Feb 2011 07:15:22 -0800 [thread overview]
Message-ID: <1298906122.5082.74.camel@wwguy-huron> (raw)
In-Reply-To: <1298899997-2372-1-git-send-email-sgruszka@redhat.com>
On Mon, 2011-02-28 at 05:33 -0800, Stanislaw Gruszka wrote:
> Since commit commit 470058e0ad82fcfaaffd57307d8bf8c094e8e9d7
> "iwlwifi: avoid Tx queue memory allocation in interface down" we do
> not unmap dma and free skbs when down device and there is pending
> transfer. What in consequence may cause that system hung (waiting
> for free skb's) when performing shutdown at iptables module unload.
>
> DMA leak manifest itself following warning:
>
> WARNING: at lib/dma-debug.c:689 dma_debug_device_change+0x15a/0x1b0()
> Hardware name: HP xw8600 Workstation
> pci 0000:80:00.0: DMA-API: device driver has pending DMA allocations while released from device [count=240]
> Modules linked in: iwlagn(-) aes_x86_64 aes_generic fuse cpufreq_ondemand acpi_cpufreq freq_table mperf xt_physdev ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 ext3 jbd dm_mirror dm_region_hash dm_log dm_mod uinput hp_wmi sparse_keymap sg wmi microcode serio_raw tg3 arc4 ecb shpchp mac80211 cfg80211 rfkill ext4 mbcache jbd2 sr_mod cdrom sd_mod crc_t10dif firewire_ohci firewire_core crc_itu_t mptsas mptscsih mptbase scsi_transport_sas pata_acpi ata_generic ata_piix ahci libahci floppy nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded: iwlagn]
> Pid: 9131, comm: rmmod Tainted: G W 2.6.38-rc6-wl+ #33
> Call Trace:
> [<ffffffff810649ef>] ? warn_slowpath_common+0x7f/0xc0
> [<ffffffff81064ae6>] ? warn_slowpath_fmt+0x46/0x50
> [<ffffffff812320ab>] ? dma_debug_device_change+0xdb/0x1b0
> [<ffffffff8123212a>] ? dma_debug_device_change+0x15a/0x1b0
> [<ffffffff8149dc18>] ? notifier_call_chain+0x58/0xb0
> [<ffffffff8108e370>] ? __blocking_notifier_call_chain+0x60/0x90
> [<ffffffff8108e3b6>] ? blocking_notifier_call_chain+0x16/0x20
> [<ffffffff812f570c>] ? __device_release_driver+0xbc/0xe0
> [<ffffffff812f5808>] ? driver_detach+0xd8/0xe0
> [<ffffffff812f45d1>] ? bus_remove_driver+0x91/0x100
> [<ffffffff812f6022>] ? driver_unregister+0x62/0xa0
> [<ffffffff8123d5d4>] ? pci_unregister_driver+0x44/0xa0
> [<ffffffffa05632d1>] ? iwl_exit+0x15/0x1c [iwlagn]
> [<ffffffff810ab492>] ? sys_delete_module+0x1a2/0x270
> [<ffffffff81498da9>] ? trace_hardirqs_on_thunk+0x3a/0x3f
> [<ffffffff8100bf42>] ? system_call_fastpath+0x16/0x1b
>
> I still can observe above warning after apply patch, but it is very
> hard to reproduce it, and have count=1. Whereas that one is easy to
> reproduce using debugfs force_reset while transmitting data, and have
> very big counts eg. 240, like quoted here. So count=1 WARNING seems
> to be different issue that need to be resolved separately.
>
> v1 -> v2: fix infinity loop bug I made during "for" to "while" loop transition.
> v2 -> v3: remove unneeded EXPORT_SYMBOL
>
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Acked-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
prev parent reply other threads:[~2011-02-28 15:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 13:33 [PATCH v3 1/5] iwlwifi: fix dma mappings and skbs leak Stanislaw Gruszka
2011-02-28 13:33 ` [PATCH v3 2/5] iwlegacy: " Stanislaw Gruszka
2011-02-28 15:16 ` Guy, Wey-Yi
2011-02-28 13:33 ` [PATCH v3 3/5] iwlwifi: add {ack,plpc}_check module parameters Stanislaw Gruszka
2011-02-28 15:17 ` Guy, Wey-Yi
2011-02-28 13:33 ` [PATCH v3 4/5] iwlwifi: move check health code into iwl-rx.c Stanislaw Gruszka
2011-02-28 15:18 ` Guy, Wey-Yi
2011-02-28 13:33 ` [PATCH v3 5/5] iwlwifi: move remaining iwl-agn-rx.c " Stanislaw Gruszka
2011-02-28 15:19 ` Guy, Wey-Yi
2011-03-02 20:00 ` Guy, Wey-Yi
2011-03-03 9:19 ` Stanislaw Gruszka
2011-03-03 15:19 ` Guy, Wey-Yi
2011-03-03 15:44 ` Stanislaw Gruszka
2011-02-28 15:15 ` Guy, Wey-Yi [this message]
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=1298906122.5082.74.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.com \
/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).