Can you post the IBM model (XXXX-YYY number) concerned please?
Cheers, John
···
-----Original Message-----
From: app_rpt-bounces@lists.illiana.net
[mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of Jon Rorke
Sent: Saturday, 11 October 2008 04:15
To: app_rpt@lists.illiana.net
Subject: Re: [App_rpt] Error on asterisk box
Hi All, I just wanted to let you know that adding the noapic to the
grub.conf file seems to have cured the lockup error issue I was
experiencing on my IBM box.
Also in the BIOS the APM mode was on.
Turning it off did not fix the problem but adding the noapic did the
trick!
By the way my Centos is
2.6.18-92.1.10.el5
So its been running nonstop now for over a day and a half with no
problems.
Thanks, for the help.
Jon VA3RQ
Jon,
This sounds to me like a problem in the PC itself.
This is a shot in the dark: the APIC's on on some PC's are flaky under
linux.
You could try adding noapic to the kernel boot line in /etc/grub.conf:
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to
> this file # NOTICE: You do not have a /boot partition. This means
that
> # all kernel and initrd paths are relative to /, eg.
> # root (hd0,0)
> # kernel /boot/vmlinuz-version ro root=/dev/hda1
> # initrd /boot/initrd-version.img
> #boot=/dev/hda
> default=0
> timeout=5
> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> hiddenmenu
> title CentOS (2.6.18-92.1.13.el5)
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.18-92.1.13.el5 ro noapic
The IBM machine I have is a Think Center model number MT-M 8084-Y11
Its a P4 3 gig machine with 1 gig of memory.
Regards,
Jon
John Yaldwyn wrote:
···
Hi John,
Can you post the IBM model (XXXX-YYY number) concerned please?
Cheers, John
-----Original Message-----
From: app_rpt-bounces@lists.illiana.net
[mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of Jon Rorke
Sent: Saturday, 11 October 2008 04:15
To: app_rpt@lists.illiana.net
Subject: Re: [App_rpt] Error on asterisk box
Hi All, I just wanted to let you know that adding the noapic to the
grub.conf file seems to have cured the lockup error issue I was
experiencing on my IBM box.
Also in the BIOS the APM mode was on.
Turning it off did not fix the problem but adding the noapic did the
trick!
By the way my Centos is
2.6.18-92.1.10.el5
So its been running nonstop now for over a day and a half with no
problems.
Thanks, for the help.
Jon VA3RQ
Jon,
This sounds to me like a problem in the PC itself.
This is a shot in the dark: the APIC's on on some PC's are flaky under
linux.
You could try adding noapic to the kernel boot line in /etc/grub.conf:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a /boot partition. This means
that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,0)
# kernel /boot/vmlinuz-version ro root=/dev/hda1
# initrd /boot/initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-92.1.13.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-92.1.13.el5 ro noapic