Kernel cannot allocate resource region

[tahoward at ntrnet.net]

I tried miboot, and it worked, but everything was VERY slow.  After
thinking about it, I realized my G3 processor was not enabled.  My machine
has a Sonnet G3 upgrade in its L2 cache slot, and it needs a MacOS
extension to enable it.

Then, I tried using BootX with the extension disabled, and 2.4 booted.  In
both cases, I still got the "cannot allocate resource region" message, but
video and ethernet both work fine.  I'm guessing this may be a red herring.

I'm wondering if it's significant that the last message printed before the
hang (it's not a panic, no reboot after 180 seconds) is "Macinto"?  When
I boot without the G3 enabled, the full line is:
Macintosh CUDA driver v0.5 for Unified ADB.

Tony

On Fri, 2 Nov 2001, Michael Schmitz wrote:

>
> > PCI: Cannot allocate resource region 0 of device 00:11.0
> > 00:0e.0 VGA compatible controller: ATI Technologies Inc Rage 128 RE
> > (prog-if 00 [VGA])
> >         Subsystem: Unknown device b530:0408
> >         Flags: bus master, stepping, medium devsel, latency 32, IRQ 25
> >         Memory at 84000000 (32-bit, prefetchable)
> >         I/O ports at 0400
> >         Memory at 80804000 (32-bit, non-prefetchable)
> >         Expansion ROM at 80820000 [disabled]
> >         Capabilities: [5c] Power Management version 1
> >
> > 00:11.0 Ethernet controller: Digital Equipment Corporation DECchip
> > 21142/43 (rev 30)
> >         Subsystem: Standard Microsystems Corp [SMC]: Unknown device 2401
> >         Flags: bus master, medium devsel, latency 32, IRQ 22
> >         I/O ports at 0400
> >         Memory at 80800000 (32-bit, non-prefetchable) [disabled]
> >         Expansion ROM at 80840000 [disabled]
> >
> > I'm guessing that there is a conflict between my ethernet and video cards,
>
> Yep, it seems like the MMIO aperture for the video card might overlap the
> ethernet controller memory resource (depending on the size of that memory
> resource).
>
> It should never hang in that case though. And I thought the initial PCI
> resource allocation takes care of resolving overlaps?
>
> Can you boot some other way (i.e. no BootX)?
>
> 	Michael
>
>
>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/