search for: powernowk8

I have a bunch of DecTOPs. Use the AMD Geode chip. Yesterday I upgraded one of them, and got the dreaded Kernel panic. Something about powernowk8. I could boot up with the old kernel, though. I know I have to put in a bug report on this, will do shortly, but first wanted to try a fresh install on another DecTOP. At the prompt, I specified: linux askmethod After it loaded the kernel, it died with the same Kernel panic. This is bad....

I had been running a system on Centos 5.1 at INIT 3. I did the upgrade to Centos 5.2 with the aid of the powernowk8 patch. Previously I would VNC into the unit when I needed to do admin stuff with a GUI. Well I noticed that I was NOT getting GNOME via VNC since the upgrade (worked before just fine with 5.1). So I tried an INIT 5 from the command line (always worked before), but the system seemed to hang....

I'm unable to get much past the "boot:" prompt in the installer. The panic appears to be in powernowk8_init which according to http://rhn.redhat.com/errata/RHSA-2008-0612.html has a recently-fixed null-pointer dereference. That errata is from August 4; the latest CentOS install ISOs are from June. I tried the agp=off suggestion from e.g. http://www.centos.org/modules/newbb/viewtopic.php?topic_id=1...

After yum upgrade, the new CentOS5 kernel [ kernel-2.6.18-92.1.1.el5.i686 ] crashes each time early in boot process on Compaq ProLiant 3000 with dual Pentium3 CPU (600 MHz, CPU0: Intel Pentium III (Katmai) stepping 03, CPU1 the same). I get kernel panic at powernowk8_init+0x05e/0x1c3. The previous kernel [ kernel-2.6.18-53.1.21.el5.i686 ] seems to work fine. I am wondering if anyone has met this on PIII CPU ? I have found 99.9% identical problem on http://www.nabble.com/net-5501-and-RHEL5.2-td18024549.html (only esp and task slightly different from what I h...