Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756869AbYCWGg0 (ORCPT ); Sun, 23 Mar 2008 02:36:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752722AbYCWGgT (ORCPT ); Sun, 23 Mar 2008 02:36:19 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:55966 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751975AbYCWGgS (ORCPT ); Sun, 23 Mar 2008 02:36:18 -0400 Date: Sun, 23 Mar 2008 07:35:24 +0100 From: Ingo Molnar To: Stefan Richter Cc: Linus Torvalds , Thomas Gleixner , Ivan Kokshaysky , Thomas Meyer , "Rafael J. Wysocki" , LKML , Adrian Bunk , Andrew Morton , Natalie Protasevich Subject: Re: ohci1394 problem (MMIO broken) (was 2.6.25-rc6-git6: Reported regressions from 2.6.24) Message-ID: <20080323063524.GA13018@elte.hu> References: <200803220259.48534.rjw@sisk.pl> <47E5350D.101@s5r6.in-berlin.de> <47E540E7.7030108@m3y3r.de> <47E54FA6.3060809@s5r6.in-berlin.de> <47E557D5.9020604@s5r6.in-berlin.de> <47E59B39.90306@s5r6.in-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47E59B39.90306@s5r6.in-berlin.de> User-Agent: Mutt/1.5.17 (2007-11-01) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1392 Lines: 35 * Stefan Richter wrote: > On my x86-32 test system, none of the devices gets an MMIO region > above the 4G map. (Reconfigured with CONFIG_RESOURCES_64BIT=y while > having CONFIG_HIGHMEM4G=y, like in Thomas M's .config.) 64-bit ioremap on x86 never worked AFAIK, the whole API is using 32-bit physical addresses which is limited to 4GB. But ... this bug does have the feeling of the wrong IO side physical memory being mapped. (0xff data means there's no device there - typical of non-existent RAM/IO) could you please pull the x86/latest tree to do a kernel pagetable dump for us? You can pull it via the instructions here: http://people.redhat.com/mingo/x86.git/README then enable CONFIG_DEBUG_KERNEL=y and CONFIG_X86_PTDUMP=y boot the kernel so that ohci1394 doesnt work. Then dump the pagetables and other hw info via: http://people.redhat.com/mingo/cfs-scheduler/tools/cfs-debug-info.sh send us the cfs-debug-info file that gets generated. We'll be able to tell from that whether your ioremap's are OK. (x86/latest will also printk all ioremap()s and results that are done) thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/