[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080326111204.GB9060@jurassic.park.msu.ru>
Date: Wed, 26 Mar 2008 14:12:04 +0300
From: Ivan Kokshaysky <ink@...assic.park.msu.ru>
To: Ingo Molnar <mingo@...e.hu>
Cc: Thomas Meyer <thomas@...3r.de>,
Stefan Richter <stefanr@...6.in-berlin.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
"Rafael J. Wysocki" <rjw@...k.pl>,
LKML <linux-kernel@...r.kernel.org>,
Adrian Bunk <bunk@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Natalie Protasevich <protasnb@...il.com>
Subject: Re: ohci1394 problem (MMIO broken) (was 2.6.25-rc6-git6: Reported
regressions from 2.6.24)
On Tue, Mar 25, 2008 at 09:29:54PM +0100, Ingo Molnar wrote:
> OTOH, before this system worked for you before, i start to suspect that
> ioremap is a red herring here and that it's the code that gets to that
> physical address (which is ioremap-ed) is at fault here.
>
> the hard hang might be your southbridge totally dumbfounded by the host
> OS attempting to do an MMIO access to an above-4GB address?
The Intel 94x chipsets must be OK wrt >4Gb MMIO accesses, as far as I know.
You should just get all 1s on read of non-existent MMIO address, as usual.
Not a hard hang.
So I suspect something is still broken in 64-bit ioremap... It would be nice
to sort that out, even though it seems to be unrelated to this particular
problem.
Ivan.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists