[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080325202954.GA22007@elte.hu>
Date: Tue, 25 Mar 2008 21:29:54 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Thomas Meyer <thomas@...3r.de>
Cc: Stefan Richter <stefanr@...6.in-berlin.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
"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)
* Ingo Molnar <mingo@...e.hu> wrote:
> > Modprobing either ohci1394 or firewire_ohci seems to lock up the
> > system.
>
> that's weird. If you do the modprobe from a VGA console and do a
> 'dmesg -n 8', do you get any ioremap printk shortly before the hard
> lockup?
basically, old ioremap did this:
[ 162.485605] ACPI: PCI Interrupt 0000:0c:03.0[A] -> GSI 19 (level, low) -> IRQ 19
[ 162.485695] ioremap: 00000000(00000800) => f8978000
the theory (fact?) was that the zero physical address there (the
'00000000') was some 4GB+ address truncated down to 32-bits.
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?
so the question is - what physical address did that ioremap do in 2.6.24
(which presumly had a working ohci1394, right?), and why did it change
to something else in -git?
Ingo
--
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