Return-path: Received: from mail-we0-f174.google.com ([74.125.82.174]:60032 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756658Ab2D3UML convert rfc822-to-8bit (ORCPT ); Mon, 30 Apr 2012 16:12:11 -0400 Received: by wejx9 with SMTP id x9so2024195wej.19 for ; Mon, 30 Apr 2012 13:12:09 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20120430170337.GA2560@tuxdriver.com> References: <20120422182928.GA2854@ritirata.org> <20120430145803.GE2630@ritirata.org> <20120430170337.GA2560@tuxdriver.com> Date: Mon, 30 Apr 2012 23:12:09 +0300 Message-ID: (sfid-20120430_221232_466252_1EDB0A5A) Subject: Re: iwlwifi warn_slowpath with 3.* From: Emmanuel Grumbach To: "John W. Linville" Cc: Antonio Quartulli , linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Apr 30, 2012 at 20:03, John W. Linville wrote: > 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 I want to hope that this bugzilla would be solved by Johannes rework of the locks: 08ae86ac3f9d9c9a60d2883c82cd72a5c66b94db in wireless-next. There are a few patches that completely rewrite the locking model of the driver.