Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:51702 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751138AbXLIWdX (ORCPT ); Sun, 9 Dec 2007 17:33:23 -0500 Date: Sun, 9 Dec 2007 14:32:37 -0800 From: Arjan van de Ven To: Chris Rankin Cc: Dan Williams , Andrew Morton , linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org Subject: Re: [2.6.23.9] hostap_plx locks up PC when reading PCI I/O memory Message-ID: <20071209143237.1e608d9f@laptopd505.fenrus.org> (sfid-20071209_223327_244331_BBCF32AA) In-Reply-To: <642708.11296.qm@web52902.mail.re2.yahoo.com> References: <20071209133311.2db5ce4f@laptopd505.fenrus.org> <642708.11296.qm@web52902.mail.re2.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: On Sun, 9 Dec 2007 22:06:21 +0000 (GMT) Chris Rankin wrote: > --- Arjan van de Ven wrote: > > can you check if the attr_mem is properly ioremap'd ? > > (probably with ioremap_nocache) > > Can you elaborate, please? I am not familiar with these I/O > primitives. the memory you feed to readl() and co isnt the actual PCI resource; you need to use ioremap() on the PCI resource to get a pointer that you can then feed to readl().... > > > I wonder if there's anything else in that area as well.. > > So I should check /proc/iomem? But wouldn't Linux complain if two PCI > devices conflicted as you're suggesting? the other one might not be PCI.. -- If you want to reach me at my work email, use arjan@linux.intel.com For development, discussion and tips for power savings, visit http://www.lesswatts.org