Re: ohci1394 problem (MMIO broken) (was 2.6.25-rc6-git6: Reportedregressions from 2.6.24)

[Thomas Meyer]

Linus Torvalds schrieb:
> On Tue, 25 Mar 2008, Thomas Meyer wrote:
>   
> > and compare lspci -vv from 2.6.25 and 2.6.24:
> >
> > 2.6.25:
> >
> >    Region 0: [virtual] Memory at 100000000 (32-bit, non-prefetchable) [size=4K]
> >
> > 2.6.24:
> >
> >    Region 0: Memory at 8c000000 (32-bit, non-prefetchable) [size=4K]
> >     
>
> Ok, so it didn't use to be at the 4GB mark.
>
> This seems to be a PCI and resource alloc issue. It would be really 
> interesting to see where the 4GB allocation started. Ie ignore anything 
> else (warnings, driver loadings etc), and _just_ look at lspci -vv output 
> for where the memory got allocated.
>
> Did you already bisect that and I just missed it?
>   
I didn't bisect this.But  I recompiled with CONFIG_RESOURCES_64BIT 
*unset* and everything is fine now, i.e. no error occurs anymore.

lspci -vv output:
0c:03.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 61) (prog-if 10 
[OHCI])
       Subsystem: Agere Systems FW323
       Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- 
ParErr- Stepping- SERR- FastB2B+ DisINTx-
       Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
       Latency: 248 (3000ns min, 6000ns max), Cache Line Size: 64 bytes
       Interrupt: pin A routed to IRQ 19
       Region 0: Memory at 94406000 (32-bit, non-prefetchable) [size=4K]
       Capabilities: [44] Power Management version 2
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0+,D1+,D2+,D3hot+,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME+
       Kernel driver in use: ohci1394
       Kernel modules: firewire-ohci, ohci1394

This is on ingo's git tree (branch: x86-latest) (commit 
0fef904c33841be92f5ebdbdb9339dd11a133c92 - x86: ioremap of 64-bit 
resource on 32-bit kernel fix)

mfg
thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/