Description of problem: System locks up during boot, after 3 agp messages. WHen booting with the original fc5 kernel, the next messages is 'i8042.c: No controller found'. Version-Release number of selected component (if applicable): 2.6.16-1.2080_FC5 How reproducible: Always. Steps to Reproduce: 1. boot machine 2. 3. Actual results: lockup Expected results: system boots Additional info: adding 'debug' (suggested by the very helpful dwmw2 in #fedora-ppc) to the kernel params allows the system to boot.
From dmesg after booting 2080 with 'debug': agpgart: AGP aperture is 16M @ 0x0 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 IN from bad port 60 at c01a2444 IN from bad port 64 at c01a24b0 i8042.c: No controller found.
This is fixed in devel with 2.6.17-rc2 (kernel-2.6.16-1.2141_FC6) Commit: f39224a8c1828bdd327539da72a53d8a13595838 Summary: Use correct sequence for putting CPU into nap mode Discussion: http://ozlabs.org/pipermail/linuxppc-dev/2006-April/022034.html The messages from comment #1 are unrelated. Still see them.
closing.. 2.6.16-1.2096 boots find