On 02/14/2012 06:00 AM, Johnny Hughes wrote:
CentOS Errata and Bugfix Advisory 2012:0124
Upstream details at :https://rhn.redhat.com/errata/RHBA-2012-0124.html
The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename )
i386: 73849c1b3103e62ef1f469d189d36e306b2a5c38ac1e03a23bb82ca569f33ded kernel-2.6.32-220.4.2.el6.i686.rpm 283cf06274026bbce4894aaa46cf3a7b8eb3d950e707bce79df1b4744c2256fe kernel-debug-2.6.32-220.4.2.el6.i686.rpm ccacf5db5d9ec3c08ab9b1cf913ccc19c2cf638570d5b304bab10fb0379e682c kernel-debug-devel-2.6.32-220.4.2.el6.i686.rpm 3e4059a495c06656f9366c168899da4f7b9be2d4dd7d5b3b85b181d5bec1c8a6 kernel-devel-2.6.32-220.4.2.el6.i686.rpm 15eedf5373ef236ccd3f359dddf98a79bab7d6d73303207ecb8c1d8ad047ba55 kernel-doc-2.6.32-220.4.2.el6.noarch.rpm c415cdb090b59dcc80e13054012e45f23bf8e3cc1245a1f85aaf5d1cc791bc86 kernel-firmware-2.6.32-220.4.2.el6.noarch.rpm 7a9d72cd977f044ea24eba24a46bee0dedb112fe19d7f3aa6b9fe945d61663d5 kernel-headers-2.6.32-220.4.2.el6.i686.rpm 125120985bd7d7a83b4ccd9330affa64ace446f96b2a9a2121219745afdf621e perf-2.6.32-220.4.2.el6.i686.rpm 925edef043f1f863ddf8d6b55040e7fce58c3185e276c33953a754a6c64116a1 python-perf-2.6.32-220.4.2.el6.i686.rpm
x86_64: e7c8f813ef1ebc783811894d3143c3965c20c3312ad65fc4e1cf73f9afc29155 kernel-2.6.32-220.4.2.el6.x86_64.rpm 4e2c367554292ed66d991b24917948001877a995f50d03c54047c57cee470377 kernel-debug-2.6.32-220.4.2.el6.x86_64.rpm 58631186f2babbc46918e67f91760663f85235dc837b5695efbd97696b59c158 kernel-debug-devel-2.6.32-220.4.2.el6.x86_64.rpm 78b63a80fd7a8af3083d5b07e35ddd74cd9993c38ac1a67240774b08954f38a0 kernel-devel-2.6.32-220.4.2.el6.x86_64.rpm b69c65bad8e5bc58f9128d893b1a3e93c3dcc1e633b70fbeaa88c70f9568b510 kernel-doc-2.6.32-220.4.2.el6.noarch.rpm a0b8dadc909efb4d7b832bff405fd8c255bc0401a6123c96b3421c5c9600eb0b kernel-firmware-2.6.32-220.4.2.el6.noarch.rpm 4bb63941d75b8c3334e2d9da2a4df1b812de1cb308bcaafd6161a06eba5d0469 kernel-headers-2.6.32-220.4.2.el6.x86_64.rpm 89612ecf638034983e045e978fada0b9885eec21fae3cd59ad714c06fb4b8936 perf-2.6.32-220.4.2.el6.x86_64.rpm de66cf4e775d1f4f8b652780c5d9c05bed629e3911696ffad03baeb891a22c20 python-perf-2.6.32-220.4.2.el6.x86_64.rpm
Source: f412dbb7b1e7b0061c68fd6ad84960a47d0270fec644071ebd9583fc7a1b3290 kernel-2.6.32-220.4.2.el6.src.rpm
Anyone know how to tell if your system is using: "This overflow led to a kernel panic on the systems using the Time Stamp Counter (TSC) or Virtual Machine Interface (VMI) clock source"
On 02/14/2012 09:14 AM, Steve Clark wrote:
On 02/14/2012 06:00 AM, Johnny Hughes wrote:
CentOS Errata and Bugfix Advisory 2012:0124
Upstream details at :https://rhn.redhat.com/errata/RHBA-2012-0124.html
The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename )
i386: 73849c1b3103e62ef1f469d189d36e306b2a5c38ac1e03a23bb82ca569f33ded kernel-2.6.32-220.4.2.el6.i686.rpm 283cf06274026bbce4894aaa46cf3a7b8eb3d950e707bce79df1b4744c2256fe kernel-debug-2.6.32-220.4.2.el6.i686.rpm ccacf5db5d9ec3c08ab9b1cf913ccc19c2cf638570d5b304bab10fb0379e682c kernel-debug-devel-2.6.32-220.4.2.el6.i686.rpm 3e4059a495c06656f9366c168899da4f7b9be2d4dd7d5b3b85b181d5bec1c8a6 kernel-devel-2.6.32-220.4.2.el6.i686.rpm 15eedf5373ef236ccd3f359dddf98a79bab7d6d73303207ecb8c1d8ad047ba55 kernel-doc-2.6.32-220.4.2.el6.noarch.rpm c415cdb090b59dcc80e13054012e45f23bf8e3cc1245a1f85aaf5d1cc791bc86 kernel-firmware-2.6.32-220.4.2.el6.noarch.rpm 7a9d72cd977f044ea24eba24a46bee0dedb112fe19d7f3aa6b9fe945d61663d5 kernel-headers-2.6.32-220.4.2.el6.i686.rpm 125120985bd7d7a83b4ccd9330affa64ace446f96b2a9a2121219745afdf621e perf-2.6.32-220.4.2.el6.i686.rpm 925edef043f1f863ddf8d6b55040e7fce58c3185e276c33953a754a6c64116a1 python-perf-2.6.32-220.4.2.el6.i686.rpm
x86_64: e7c8f813ef1ebc783811894d3143c3965c20c3312ad65fc4e1cf73f9afc29155 kernel-2.6.32-220.4.2.el6.x86_64.rpm 4e2c367554292ed66d991b24917948001877a995f50d03c54047c57cee470377 kernel-debug-2.6.32-220.4.2.el6.x86_64.rpm 58631186f2babbc46918e67f91760663f85235dc837b5695efbd97696b59c158 kernel-debug-devel-2.6.32-220.4.2.el6.x86_64.rpm 78b63a80fd7a8af3083d5b07e35ddd74cd9993c38ac1a67240774b08954f38a0 kernel-devel-2.6.32-220.4.2.el6.x86_64.rpm b69c65bad8e5bc58f9128d893b1a3e93c3dcc1e633b70fbeaa88c70f9568b510 kernel-doc-2.6.32-220.4.2.el6.noarch.rpm a0b8dadc909efb4d7b832bff405fd8c255bc0401a6123c96b3421c5c9600eb0b kernel-firmware-2.6.32-220.4.2.el6.noarch.rpm 4bb63941d75b8c3334e2d9da2a4df1b812de1cb308bcaafd6161a06eba5d0469 kernel-headers-2.6.32-220.4.2.el6.x86_64.rpm 89612ecf638034983e045e978fada0b9885eec21fae3cd59ad714c06fb4b8936 perf-2.6.32-220.4.2.el6.x86_64.rpm de66cf4e775d1f4f8b652780c5d9c05bed629e3911696ffad03baeb891a22c20 python-perf-2.6.32-220.4.2.el6.x86_64.rpm
Source: f412dbb7b1e7b0061c68fd6ad84960a47d0270fec644071ebd9583fc7a1b3290 kernel-2.6.32-220.4.2.el6.src.rpm
Anyone know how to tell if your system is using: "This overflow led to a kernel panic on the systems using the Time Stamp Counter (TSC) or Virtual Machine Interface (VMI) clock source"
This:
[johnny@m4500n corp]$ cat /sys/devices/system/clocksource/clocksource0/available_clocksource tsc hpet acpi_pm
[johnny@m4500n corp]$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc
If you can not use the new kernel, you can change the clocksource by adding this to your kernel line in /boot/grub/grub.conf:
clocksource=acpi_pm
(or clocksource=hpet, you should research which to use if you do not want tsc)
On 02/15/2012 04:52 AM, Johnny Hughes wrote:
On 02/14/2012 09:14 AM, Steve Clark wrote:
On 02/14/2012 06:00 AM, Johnny Hughes wrote:
CentOS Errata and Bugfix Advisory 2012:0124
Upstream details at :https://rhn.redhat.com/errata/RHBA-2012-0124.html
The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename )
i386: 73849c1b3103e62ef1f469d189d36e306b2a5c38ac1e03a23bb82ca569f33ded kernel-2.6.32-220.4.2.el6.i686.rpm 283cf06274026bbce4894aaa46cf3a7b8eb3d950e707bce79df1b4744c2256fe kernel-debug-2.6.32-220.4.2.el6.i686.rpm ccacf5db5d9ec3c08ab9b1cf913ccc19c2cf638570d5b304bab10fb0379e682c kernel-debug-devel-2.6.32-220.4.2.el6.i686.rpm 3e4059a495c06656f9366c168899da4f7b9be2d4dd7d5b3b85b181d5bec1c8a6 kernel-devel-2.6.32-220.4.2.el6.i686.rpm 15eedf5373ef236ccd3f359dddf98a79bab7d6d73303207ecb8c1d8ad047ba55 kernel-doc-2.6.32-220.4.2.el6.noarch.rpm c415cdb090b59dcc80e13054012e45f23bf8e3cc1245a1f85aaf5d1cc791bc86 kernel-firmware-2.6.32-220.4.2.el6.noarch.rpm 7a9d72cd977f044ea24eba24a46bee0dedb112fe19d7f3aa6b9fe945d61663d5 kernel-headers-2.6.32-220.4.2.el6.i686.rpm 125120985bd7d7a83b4ccd9330affa64ace446f96b2a9a2121219745afdf621e perf-2.6.32-220.4.2.el6.i686.rpm 925edef043f1f863ddf8d6b55040e7fce58c3185e276c33953a754a6c64116a1 python-perf-2.6.32-220.4.2.el6.i686.rpm
x86_64: e7c8f813ef1ebc783811894d3143c3965c20c3312ad65fc4e1cf73f9afc29155 kernel-2.6.32-220.4.2.el6.x86_64.rpm 4e2c367554292ed66d991b24917948001877a995f50d03c54047c57cee470377 kernel-debug-2.6.32-220.4.2.el6.x86_64.rpm 58631186f2babbc46918e67f91760663f85235dc837b5695efbd97696b59c158 kernel-debug-devel-2.6.32-220.4.2.el6.x86_64.rpm 78b63a80fd7a8af3083d5b07e35ddd74cd9993c38ac1a67240774b08954f38a0 kernel-devel-2.6.32-220.4.2.el6.x86_64.rpm b69c65bad8e5bc58f9128d893b1a3e93c3dcc1e633b70fbeaa88c70f9568b510 kernel-doc-2.6.32-220.4.2.el6.noarch.rpm a0b8dadc909efb4d7b832bff405fd8c255bc0401a6123c96b3421c5c9600eb0b kernel-firmware-2.6.32-220.4.2.el6.noarch.rpm 4bb63941d75b8c3334e2d9da2a4df1b812de1cb308bcaafd6161a06eba5d0469 kernel-headers-2.6.32-220.4.2.el6.x86_64.rpm 89612ecf638034983e045e978fada0b9885eec21fae3cd59ad714c06fb4b8936 perf-2.6.32-220.4.2.el6.x86_64.rpm de66cf4e775d1f4f8b652780c5d9c05bed629e3911696ffad03baeb891a22c20 python-perf-2.6.32-220.4.2.el6.x86_64.rpm
Source: f412dbb7b1e7b0061c68fd6ad84960a47d0270fec644071ebd9583fc7a1b3290 kernel-2.6.32-220.4.2.el6.src.rpm
Anyone know how to tell if your system is using: "This overflow led to a kernel panic on the systems using the Time Stamp Counter (TSC) or Virtual Machine Interface (VMI) clock source"
This:
[johnny@m4500n corp]$ cat /sys/devices/system/clocksource/clocksource0/available_clocksource tsc hpet acpi_pm
[johnny@m4500n corp]$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc
If you can not use the new kernel, you can change the clocksource by adding this to your kernel line in /boot/grub/grub.conf:
clocksource=acpi_pm
(or clocksource=hpet, you should research which to use if you do not want tsc)
Thanks for the info, it is much appreciated. Looks like out boxes are using hpet so we should be okay, correct?
-
Johnny Hughes -
Steve Clark