From: "John W. Linville" <linville@tuxdriver.com>
To: Antonio Quartulli <ordex@autistici.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwlwifi warn_slowpath with 3.*
Date: Mon, 30 Apr 2012 13:03:37 -0400 [thread overview]
Message-ID: <20120430170337.GA2560@tuxdriver.com> (raw)
In-Reply-To: <20120430145803.GE2630@ritirata.org>
On Mon, Apr 30, 2012 at 04:58:04PM +0200, Antonio Quartulli wrote:
> On Sun, Apr 22, 2012 at 08:29:29PM +0200, Antonio Quartulli wrote:
> > Hello,
> >
> > 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.
Just for the record, we are seeing a similar problem on RHEL 6.3
(which has an iwlwifi driver derived from linux-3.2).
https://bugzilla.redhat.com/show_bug.cgi?id=815998
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-04-30 17:17 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 [this message]
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
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=20120430170337.GA2560@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=ordex@autistici.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 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.