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 have seen on screen after crash, all other registers, call trace, code bytes identical to my case) , but that was on a different CPU.
On the other hand, I run CentOS upgraded to 5.2 on a home PC with PIII (single CPU, Abit motherboard with i440BX chipset) with no problem.
Is it normal, that powernowk8_init gets called on PIII CPU?
Best regards,
Wojtek
On Wed, Jun 25, 2008 at 9:36 AM, Wojtek Pilorz wpilorz@bdk.pl wrote:
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
...snip...
You are definitalty not alone on this. See http://bugs.centos.org/view.php?id=2912. Maybe add a note there that you have the same issue and report your system config. It looks likes it only happens on older PII and PIII machines.
Regards, Tim
On Wed, Jun 25, 2008 at 09:49:08AM +0200, Tim Verhoeven wrote:
On Wed, Jun 25, 2008 at 9:36 AM, Wojtek Pilorz wpilorz@bdk.pl wrote:
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.
...snip...
You are definitalty not alone on this. See http://bugs.centos.org/view.php?id=2912. Maybe add a note there that you have the same issue and report your system config. It looks likes
I have added a note about the problem on ProLiant3000 machine and dmesg output from working kernel.
it only happens on older PII and PIII machines.
And then only some of them - home home PC with PIII runs fine with the new kernel. I will upgrade 2 more machines with PII or PIII and see what will happen.
Thank you,
Wojtek
Regards, Tim
-- Tim Verhoeven - tim.verhoeven.be@gmail.com - 0479 / 88 11 83
On Wed, Jun 25, 2008 at 11:59:36AM +0200, Wojtek Pilorz wrote:
On Wed, Jun 25, 2008 at 09:49:08AM +0200, Tim Verhoeven wrote:
On Wed, Jun 25, 2008 at 9:36 AM, Wojtek Pilorz wpilorz@bdk.pl wrote:
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.
...snip...
You are definitalty not alone on this. See http://bugs.centos.org/view.php?id=2912. Maybe add a note there that you have the same issue and report your system config. It looks likes
I have added a note about the problem on ProLiant3000 machine and dmesg output from working kernel.
it only happens on older PII and PIII machines.
And then only some of them - home home PC with PIII runs fine with the new kernel. I will upgrade 2 more machines with PII or PIII and see what will happen.
Thank you,
Added to the bug also, my guests kernel panics in Qemu (P/PII/PIII).
-- Fridh
On Wed, Jun 25, 2008 at 11:59:36AM +0200, Wojtek Pilorz wrote:
On Wed, Jun 25, 2008 at 09:49:08AM +0200, Tim Verhoeven wrote:
On Wed, Jun 25, 2008 at 9:36 AM, Wojtek Pilorz wpilorz@bdk.pl wrote:
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.
...snip... You are definitalty not alone on this. See http://bugs.centos.org/view.php?id=2912.
[...]
it only happens on older PII and PIII machines.
And then only some of them - home home PC with PIII runs fine with the new kernel. I will upgrade 2 more machines with PII or PIII and see what will happen.
OK, just for the record, I have upgraded 3 more machines to CentOS5.2 - a P4 Compaq D51S - new kernel runs OK - a PII Compaq Deskpro EN - new kernel runs OK - another 2*PIII Compaq ProLiant 3000 server - kernel crashes (somewhat expected, as the machine is almost identical to that I initially reported)
Best regards,
Wojtek
I get kernel panic at powernowk8_init+0x05e/0x1c3.
I don't have the necessary knowledge to evaluate kernel related issues, but it seems to me that there's some kind of confusion involved here. People are reporting problems with Intel Pentium II and III machines yet PowerNow is a speed throttling </wiki/CPU_throttling> and power saving technology used in AMD processors. Should powernowk8 be called when Intel processors are present?
http://en.wikipedia.org/wiki/PowerNow!
No virus found in this outgoing message. Checked by AVG. Version: 8.0.101 / Virus Database: 270.4.1/1517 - Release Date: 24-06-2008 20:41
On Wed, Jun 25, 2008 at 12:04 PM, Miguel Medalha miguelmedalha@sapo.pt wrote:
I get kernel panic at powernowk8_init+0x05e/0x1c3.
I don't have the necessary knowledge to evaluate kernel related issues, but it seems to me that there's some kind of confusion involved here. People are reporting problems with Intel Pentium II and III machines yet PowerNow is a speed throttling </wiki/CPU_throttling> and power saving technology used in AMD processors. Should powernowk8 be called when Intel processors are present?
In theory you are correct. The problems seems to be that upstream has decided to make that module part of the kernel itself and not as a seperate module. This means that it is always loaded and that is probably the reason why ther are issues on none-AMD hardware.
Regards, Tim
On Wed, Jun 25, 2008 at 2:36 AM, Wojtek Pilorz wpilorz@bdk.pl wrote:
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 have seen on screen after crash, all other registers, call trace, code bytes identical to my case) , but that was on a different CPU.
On the other hand, I run CentOS upgraded to 5.2 on a home PC with PIII (single CPU, Abit motherboard with i440BX chipset) with no problem.
Is it normal, that powernowk8_init gets called on PIII CPU?
Best regards,
Wojtek
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Is this the same issue I am having on my Celeron 2.6 GHz box, where the new Kernel dies, after "starting udev" is shown on the CRT? Warm reboot, after "yum update" yesterday worked fine, but, after powering down the box and powering up, I cannot boot into the new Kernel. New Kernel is booting perfectly, on a P4 1.6 GHz box.
Wojtek Pilorz wrote:
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 have seen on screen after crash, all other registers, call trace, code bytes identical to my case) , but that was on a different CPU.
On the other hand, I run CentOS upgraded to 5.2 on a home PC with PIII (single CPU, Abit motherboard with i440BX chipset) with no problem.
Is it normal, that powernowk8_init gets called on PIII CPU?
We have created a new test kernel that has an upstream patch to fix this issue, please test this and see if it fixes your issues:
Johnny Hughes wrote:
Wojtek Pilorz wrote:
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 have seen on screen after crash, all other registers, call trace, code bytes identical to my case) , but that was on a different CPU.
On the other hand, I run CentOS upgraded to 5.2 on a home PC with PIII (single CPU, Abit motherboard with i440BX chipset) with no problem.
Is it normal, that powernowk8_init gets called on PIII CPU?
We have created a new test kernel that has an upstream patch to fix this issue, please test this and see if it fixes your issues:
I have heard off list that this kernel does solve the problem with powernow-k8.
As always though, this kernel will be available to people with the problem (at the above link), however we won't officially release it as a replacement until it is in an upstream kernel and released into the tree by them.
This is even worse because it renders the install media worthless on these machines, and I am sorry, but upstream needs to initiate things in the main tree.
On Friday 27 June 2008 02:36, Johnny Hughes wrote:
Johnny Hughes wrote:
Wojtek Pilorz wrote:
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 have seen on screen after crash, all other registers, call trace, code bytes identical to my case) , but that was on a different CPU.
On the other hand, I run CentOS upgraded to 5.2 on a home PC with PIII (single CPU, Abit motherboard with i440BX chipset) with no problem.
Is it normal, that powernowk8_init gets called on PIII CPU?
We have created a new test kernel that has an upstream patch to fix this issue, please test this and see if it fixes your issues:
I have heard off list that this kernel does solve the problem with powernow-k8.
As always though, this kernel will be available to people with the problem (at the above link), however we won't officially release it as a replacement until it is in an upstream kernel and released into the tree by them.
This is even worse because it renders the install media worthless on these machines, and I am sorry, but upstream needs to initiate things in the main tree.
I have an Athlon 64 X2 4200+, and that hit the powernow-k8 problem too. I installed your test kernel which has cured it. Thanks
Anne
On Fri, Jun 27, 2008 at 10:51 AM, Anne Wilson cannewilson@googlemail.com wrote:
I have an Athlon 64 X2 4200+, and that hit the powernow-k8 problem too. I installed your test kernel which has cured it. Thanks
Interesting - I have an Athlon 64 x2 4200+ that had no problems booting the 5.2 kernel after an update, nor downloading and installing the 92.1.6 source, nor rebuilding it with NTFS support added, nor booting there, either.
I'll check when I get home to see what happened, but it all looks kosher.
Of course, I'm quite a bit behind in my emails, having been on the vacation from hell last week, so I could be responding to a fixed issue....
Ciao.
mhr
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf
Of
MHR Sent: Tuesday, July 01, 2008 3:14 AM To: CentOS mailing list Subject: Re: [CentOS] CentOS 5.2 kernel [2.6.18-92.1.1.el5] crashes on
dual-PIII
Compaq ProLiant 3000
I have an Athlon 64 X2 4200+, and that hit the powernow-k8 problem too. I installed your test kernel which has cured it. Thanks
Interesting - I have an Athlon 64 x2 4200+ that had no problems booting the 5.2 kernel after an update, nor downloading and installing the 92.1.6 source, nor rebuilding it with NTFS support added, nor booting there, either.
I run CentOS x86 and x64 versions both at home and at work as virtual machines under VMware Server v1.0.6 using Amd Athlon64 X2 4400+ CPU:s. No problems detected.
What's supposed to be problem? I missed the previous mails in this thread, but the Amd X2 caught my eye. 8-}
Sorin Srbu wrote:
What's supposed to be problem? I missed the previous mails in this thread, but the Amd X2 caught my eye. 8-}
at the bottom of every email on this list is a url pointing to the archieves, is there something preventing you from clicking through ?
on 7-3-2008 3:27 PM Karanbir Singh spake the following:
Sorin Srbu wrote:
What's supposed to be problem? I missed the previous mails in this thread, but the Amd X2 caught my eye. 8-}
at the bottom of every email on this list is a url pointing to the archieves, is there something preventing you from clicking through ?
Not on this one!
Not on this one! _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Yes it does. :) That URL has a link to the archives.
On Thu, Jun 26, 2008 at 06:56:12PM -0500, Johnny Hughes wrote:
Wojtek Pilorz wrote:
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.
[...]
We have created a new test kernel that has an upstream patch to fix this issue, please test this and see if it fixes your issues:
Yes,
the problem machine (Compaq ProLiant 3000) boots fine with this test kernel.
Thank you very much!
Wojtek
2008/6/26 Johnny Hughes johnny@centos.org:
We have created a new test kernel that has an upstream patch to fix this issue, please test this and see if it fixes your issues:
So this is for those who already have a booting Centos. Is there a work-around for those trying to install on a Powernow system with a 5.2 media? Or do they have to have to revert to trying a 5.1 media?
-Mauriat
on 7-9-2008 12:24 PM Mauriat spake the following:
2008/6/26 Johnny Hughes johnny@centos.org:
We have created a new test kernel that has an upstream patch to fix this issue, please test this and see if it fixes your issues:
So this is for those who already have a booting Centos. Is there a work-around for those trying to install on a Powernow system with a 5.2 media? Or do they have to have to revert to trying a 5.1 media?
-Mauriat
Right now you will have to install with either 5.1 media and update, and don't reboot with the bad kernel selected. Maybe the CentOS team will post a fixed install disk, maybe not. I doubt that RedHat will fix it until 5.3, but maybe they will.
-
Anne Wilson -
Johnny Hughes -
Karanbir Singh -
Lanny Marcus -
Mauriat -
MHR -
Miguel Medalha -
Mikael Fridh -
Scott Silva -
Sorin Srbu -
Spiro Harvey, Knossos Networks Ltd -
Tim Verhoeven -
Wojtek Pilorz