From: Antonio Quartulli <ordex@autistici.org>
To: "Venkataraman, Meenakshi" <meenakshi.venkataraman@intel.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Emmanuel Grumbach (egrumbach@gmail.com)" <egrumbach@gmail.com>
Subject: Re: iwlwifi warn_slowpath with 3.*
Date: Tue, 1 May 2012 20:33:22 +0200 [thread overview]
Message-ID: <20120501183322.GF4316@ritirata.org> (raw)
In-Reply-To: <4595B4D22AB93C4FABBA84AAD5AA37FD143115@ORSMSX103.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
On Tue, May 01, 2012 at 04:52:23PM +0000, Venkataraman, Meenakshi wrote:
> Hi John, Antonio,
>
> Emmanuel found a race condition in rx buffer allocation/deallocation, and attached is a patch that fixes it.
>
> >> > since linux-3.0 (I don't remember if it was the case even before),
> >> > I'm getting this output in dmesg:
> >> >
> >> > [ 53.662990] ------------[ cut here ]------------
> >> > [ 53.663016] WARNING: at drivers/iommu/intel-iommu.c:2911
> >> > intel_unmap_page+0x14b/0x180()
> >> > [ 53.663047] Hardware name: Latitude E5420
> >> > [ 53.663066] Driver unmaps unmatched page at PFN ffd1a000
> >>
> >>
> >> I see that I always get the same addr passed to the unmap function:
> >>
> >> [ 23.950535] Driver unmaps unmatched page at PFN ffd1a000
> >>
> >> is it a coincidence?
> >> I'm running linux-3.3.3 right now. I can try wireless-testing if it would help.
>
> [MV] Antonio -- can you try out the patch attached and let us know if you continue to see the problem?
Ok, I will first try with a plain wireless-testing kernel and then I will apply
the patch.
Thanks!
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2012-05-01 19:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 18:29 iwlwifi warn_slowpath with 3.* Antonio Quartulli
2012-04-30 14:58 ` Antonio Quartulli
2012-04-30 17:03 ` John W. Linville
2012-04-30 20:12 ` Emmanuel Grumbach
2012-04-30 20:13 ` Emmanuel Grumbach
2012-05-01 16:52 ` Venkataraman, Meenakshi
2012-05-01 17:13 ` Emmanuel Grumbach
2012-05-01 18:34 ` Antonio Quartulli
2012-05-01 20:56 ` Antonio Quartulli
2012-05-01 21:19 ` Venkataraman, Meenakshi
2012-05-02 7:08 ` Emmanuel Grumbach
2012-05-02 15:31 ` Antonio Quartulli
2012-05-02 15:39 ` John W. Linville
2012-05-02 16:12 ` Antonio Quartulli
2012-05-02 16:21 ` Antonio Quartulli
2012-05-03 6:53 ` Antonio Quartulli
2012-05-03 19:04 ` Emmanuel Grumbach
2012-05-03 19:55 ` Emmanuel Grumbach
2012-05-03 20:09 ` Antonio Quartulli
2012-05-03 20:17 ` Emmanuel Grumbach
2012-05-04 0:21 ` Antonio Quartulli
2012-05-04 5:11 ` Emmanuel Grumbach
2012-05-04 6:36 ` Antonio Quartulli
2012-05-04 6:58 ` Emmanuel Grumbach
2012-05-04 7:28 ` Antonio Quartulli
2012-05-04 14:20 ` Antonio Quartulli
2012-05-05 18:49 ` Emmanuel Grumbach
2012-05-06 5:49 ` Emmanuel Grumbach
2012-05-06 7:54 ` Antonio Quartulli
2012-05-06 8:26 ` Emmanuel Grumbach
2012-05-06 8:56 ` Antonio Quartulli
2012-05-06 9:15 ` Antonio Quartulli
2012-05-06 9:25 ` Emmanuel Grumbach
2012-05-06 9:26 ` Emmanuel Grumbach
2012-05-06 9:40 ` Antonio Quartulli
2012-05-06 9:57 ` Antonio Quartulli
2012-05-06 9:58 ` Emmanuel Grumbach
2012-05-06 8:59 ` Antonio Quartulli
2012-05-06 9:23 ` Emmanuel Grumbach
2012-05-01 18:33 ` Antonio Quartulli [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=20120501183322.GF4316@ritirata.org \
--to=ordex@autistici.org \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=meenakshi.venkataraman@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.