Re: 2.4.16 / 2.4.17pre6 hang when loading agpgart

Reid Hekman (reid.hekman@ndsu.nodak.edu)
09 Dec 2001 17:40:30 -0600


On Sun, 2001-12-09 at 18:00, Roel Teuwen wrote:
> On my HP Omnibook 4150, 2.4.16 and 2.4.17-pre6 hang on boot right after
> the messages below.
> I need to press the reset button and load a kernel without agpgart
> compiled in to boot. When compiled as a module, the machine hangs after
> printing these lines when loading the module.
>
> "
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory : 96M
> agpgart: Detected Intel 440BX chipset
> "
>
> I selected the agpgart "440BX" option in menuconfig.
> AGP information :
>
> 00:01.0 PCI bridge: Intel Corp. 440BX/ZX - 82443BX/ZX AGP bridge (rev
> 02) (prog-if 00 [Normal decode])
> Flags: bus master, 66Mhz, medium devsel, latency 128
> Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
> Memory behind bridge: fe700000-fecfffff
> Prefetchable memory behind bridge: fd000000-fe3fffff

I had the same problem after upgrading the BIOS on a Trigem Napoli-2
mainboard with a 440BX (eMachine 500a). Tested with kernels 2.4.5-RH
through 2.4.13-ac7. With Bios image v1.12 it hangs with agpgart built in
or on module load exactly as you described, it also fails when I use
nvidia's NVdriver agp support. After upgrading to Bios 1.13 the problem
went away.

Something to check for anyway...

For completeness, my working setup displays the normal kernel apggart
info and shows this:

00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge
(rev 03) (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fc600000-fe6fffff
Prefetchable memory behind bridge: f0400000-f44fffff

Regards,
Reid

-
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/