Terry Barnaby
2004-Jan-07 10:19 UTC
[syslinux] Problem with Syslinux 2.07 and APM on SMP system
Hi,
We have a problem with Syslinux 2.07 and APM on an SMP system.
When either network booting with pxelinux.0 or CDROM booting
with isolinux we get a kernel error message:
Jan 7 09:59:51 ddcserver1 kernel: kernel BUG at apm.c:1756!
Jan 7 09:59:51 ddcserver1 kernel: invalid operand: 0000
Jan 7 09:59:51 ddcserver1 kernel:
Jan 7 09:59:51 ddcserver1 kernel: CPU: 1
Jan 7 09:59:51 ddcserver1 kernel: EIP: 0060:[<c0118d3e>] Not
tainted
Jan 7 09:59:51 ddcserver1 kernel: EFLAGS: 00010202
Jan 7 09:59:51 ddcserver1 kernel:
Jan 7 09:59:51 ddcserver1 kernel: EIP is at apm [kernel] 0x33e (2.4.20-24.9smp)
Jan 7 09:59:51 ddcserver1 kernel: eax: 00000001 ebx: c44c4000 ecx: c03c02a8
edx: c03c02ac
Jan 7 09:59:51 ddcserver1 kernel: esi: c027e933 edi: c44c4400 ebp: 00000000
esp: c44c5fd0
Jan 7 09:59:51 ddcserver1 kernel: ds: 0068 es: 0068 ss: 0068
Jan 7 09:59:51 ddcserver1 kernel: Process kapmd (pid: 7, stackpage=c44c5000)
Jan 7 09:59:51 ddcserver1 kernel: Stack: 00000000 00000000 00000000 00000000
00000068 c0118a00
00000000 00000000
Jan 7 09:59:51 ddcserver1 kernel: c010759d 00000000 00000000 00000000
Jan 7 09:59:51 ddcserver1 kernel: Call Trace: [<c0118a00>] apm [kernel]
0x0 (0xc44c5fe4))
Jan 7 09:59:51 ddcserver1 kernel: [<c010759d>] kernel_thread_helper
[kernel] 0x5 (0xc44c5ff0))
Jan 7 09:59:51 ddcserver1 kernel:
Jan 7 09:59:51 ddcserver1 kernel:
Jan 7 09:59:51 ddcserver1 kernel: Code: 0f 0b dc 06 85 e8 27 c0 e9 03 fd ff ff
90 8d 74 26 00 83 ec
The system runs fine but will not power off.
If the system boots from the hard disk using grub all is fine.
The kernel boot line is:
append ro ramdisk_size=6000 initrd=beamsys/beamsys-initrd apm=power-off
The OS is Redhat Linux 9 with kernel 2.4.20-24.9smp
The hardware is a Supermicro 6023P-i dual Xeon server.
Any ideas ?
Cheers
Terry
--
Dr Terry Barnaby BEAM Ltd
Phone: +44 1454 324512 Northavon Business Center, Dean Rd
Fax: +44 1454 313172 Yate, Bristol, BS37 5NH, UK
Email: terry at beam.ltd.uk Web: www.beam.ltd.uk
BEAM for: Visually Impaired X-Terminals, Parallel Processing, Software
"Tandems are twice the fun !"
Josef Siemes
2004-Jan-07 13:10 UTC
[syslinux] Problem with Syslinux 2.07 and APM on SMP system
Hi, Terry Barnaby <terry1 at beam.ltd.uk> schrieb am 07.01.04 11:29:20:> We have a problem with Syslinux 2.07 and APM on an SMP system. > When either network booting with pxelinux.0 or CDROM booting > with isolinux we get a kernel error message:[..]> The system runs fine but will not power off. > If the system boots from the hard disk using grub all is fine. > > The kernel boot line is: > append ro ramdisk_size=6000 initrd=beamsys/beamsys-initrd apm=power-off > > The OS is Redhat Linux 9 with kernel 2.4.20-24.9smp > The hardware is a Supermicro 6023P-i dual Xeon server.you don't have any problem with pxe/syslinux, since your kernel already booted and took over complete control on the system. Also syslinux doesn't do anything in regard to APM. So maybe your system doesn't have any apm bios (I've seen some laptops that only have ACPI, and no APM any more), or has a buggy bios. Complain to your vendor, or try using ACPI and see if this works better. Regards, Josef ______________________________________________________________________________ Erdbeben im Iran: Zehntausende Kinder brauchen Hilfe. UNICEF hilft den Kindern - helfen Sie mit! https://www.unicef.de/spe/spe_03.php
Josef Siemes
2004-Jan-07 14:33 UTC
[syslinux] Problem with Syslinux 2.07 and APM on SMP system
Hi, Terry Barnaby <terry at beam.ltd.uk> schrieb am 07.01.04 15:12:09:> The system boots fine using the standard Grub boot loader which loads > exactly the same kernel and initial RAM disk and APM works fine when > booted using Grub.Hmm. Grub does many things to the system (and I think it does way too much for the purpose it's needed for ...), and I AFAIK it also fiddles around with APM. Maybe it 'fixes' your bios to behave more sane to the kernel. Did you try lilo? It's similar to syslinux that it doesn't do too much to the system, and definitely doesn't touch APM either.> So there must be some difference between the way syslinux (pxe and iso) > boots Linux and Grub boots Linux that causes the failier. > > The code in the Linux kernal that prints the error message is attempting > to make sure the kernel is running on processor 0 as there are problems > with some BIOSes when other CPU's attempt to access the APM BIOS functions. > Could syslinux (pxe and iso) be booting using CPU 1 rather than CPU 0 ?Not that I know. AFAIK the BIOS (and that's what syslinux uses) runs on CPU 0, so there should be no problem with that. Since it seems to be a bios issue you could try to upgrade the bios to the latest version, if you didn't do that already. Since vitrually all installation CD's use syslinux (isolinux or syslinux itself) this should have happened to more people. hpa, any comments? Regards, Josef ______________________________________________________________________________ Nachrichten, Musik und Spiele schnell und einfach per Quickstart im WEB.DE Screensaver - Gratis downloaden: http://screensaver.web.de/?mc=021110