syslinux-1.43 bug [and possible PATCH]
I have a possible problem to report with syslinux, and a suggested fix. Please send me comments and feedback at [email protected], since I am not subscribed to the syslinux or kernel lists.
While installing linux (RedHat6.0, SuSe, Mandrake etc) on a ia32 Compaq box with 1.5Gb memory, I have observed kernel panics from mount_root. On further investigation, syslinux decides to put initrd at a high physical address, which the Linux kernel, compiled with PAGE_OFFSET=0xc0000000 can not access. The kernel can access at the most physical address 0x3c000000, whereas syslinux/ldlinux.asm can put initrd as high as HIGHMEM_MAX=0x3f000000. This leads setup_arch() to decide it can not use initrd, thus causing the kernel panic.
The easy fix to me seems to be to change HIGHMEM_MAX in syslinux/ldlinux.asm to 0x3c000000. In fact, I have verified on a couple of machines that this will let the installation proceed.
Have other people run into this problem and worked around it some other way? (One way would be to specify mem= at the boot: prompt from syslinux. Yet another way seems to be to specify mem= in the syslinux.cfg file. Changing HIGHMEM_MAX seems to be the cleanest, although I am not sure whether this will impact the capability of syslinux to install other os'es).
Thanks.
Kanoj
[email protected]
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
This was fixed in 1.44, AFAIK. HIGHMEM_MAX is now 38000000h. We're using 1.45 for our next release.
Quoted 27 lines · Kanoj Sarcar
I have a possible problem to report with syslinux, and a suggested fix. Please send me comments and feedback at [email protected], since I am not subscribed to the syslinux or kernel lists.
While installing linux (RedHat6.0, SuSe, Mandrake etc) on a ia32 Compaq box with 1.5Gb memory, I have observed kernel panics from
mount_root. On further investigation, syslinux decides to put initrd at a high physical address, which the Linux kernel, compiled with PAGE_OFFSET=0xc0000000 can not access. The kernel can access at the most physical address0x3c000000, whereas syslinux/ldlinux.asm can put initrd as high as HIGHMEM_MAX=0x3f000000. This leadssetup_arch()to decide it can not use initrd, thus causing the kernel panic.The easy fix to me seems to be to change
HIGHMEM_MAXin syslinux/ldlinux.asm to0x3c000000. In fact, I have verified on a couple of machines that this will let the installation proceed.Have other people run into this problem and worked around it some other way? (One way would be to specify mem= at the boot: prompt from syslinux. Yet another way seems to be to specify mem= in the syslinux.cfg file. Changing
HIGHMEM_MAXseems to be the cleanest, although I am not sure whether this will impact the capability of syslinux to install other os'es).Thanks.
Quoted 7 lines
Kanoj
[email protected]-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
This is an old bug; it has been fixed since 1.44 or 1.45. The current version is 1.47.
-hpa
Quoted 25 lines · Kanoj Sarcar
I have a possible problem to report with syslinux, and a suggested fix. Please send me comments and feedback at [email protected], since I am not subscribed to the syslinux or kernel lists.
While installing linux (RedHat6.0, SuSe, Mandrake etc) on a ia32 Compaq box with 1.5Gb memory, I have observed kernel panics from
mount_root. On further investigation, syslinux decides to put initrd at a high physical address, which the Linux kernel, compiled with PAGE_OFFSET=0xc0000000 can not access. The kernel can access at the most physical address0x3c000000, whereas syslinux/ldlinux.asm can put initrd as high as HIGHMEM_MAX=0x3f000000. This leadssetup_arch()to decide it can not use initrd, thus causing the kernel panic.The easy fix to me seems to be to change
HIGHMEM_MAXin syslinux/ldlinux.asm to0x3c000000. In fact, I have verified on a couple of machines that this will let the installation proceed.Have other people run into this problem and worked around it some other way? (One way would be to specify mem= at the boot: prompt from syslinux. Yet another way seems to be to specify mem= in the syslinux.cfg file. Changing
HIGHMEM_MAXseems to be the cleanest, although I am not sure whether this will impact the capability of syslinux to install other os'es).
Quoted 5 lines
Thanks.
Kanoj
[email protected]
<[email protected]> at work, <[email protected]> in private!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
Quoted 9 lines · Kanoj Sarcar
While installing linux (RedHat6.0, SuSe, Mandrake etc) on a ia32 Compaq box with 1.5Gb memory, I have observed kernel panics from
mount_root. On further investigation, syslinux decides to put initrd at a high physical address, which the Linux kernel, compiled with PAGE_OFFSET=0xc0000000 can not access. The kernel can access at the most physical address0x3c000000, whereas syslinux/ldlinux.asm can put initrd as high as HIGHMEM_MAX=0x3f000000. This leadssetup_arch()to decide it can not use initrd, thus causing the kernel panic.
Yup...
Quoted 6 lines
Have other people run into this problem and worked around it some other way? (One way would be to specify mem= at the boot: prompt from syslinux. Yet another way seems to be to specify mem= in the syslinux.cfg file. Changing
HIGHMEM_MAXseems to be the cleanest, although I am not sure whether this will impact the capability of syslinux to install other os'es).
I don't think "mem=" would help at all but I could be wrong.
My "easy" fix was to pull out a DIMM from each of our machines, leaving 3x256 :-) Not elegant, but fast!
Neil
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
Quoted 10 lines · Neil Conway
Quoted 7 lines
Have other people run into this problem and worked around it some other way? (One way would be to specify mem= at the boot: prompt from syslinux. Yet another way seems to be to specify mem= in the syslinux.cfg file. Changing
HIGHMEM_MAXseems to be the cleanest, although I am not sure whether this will impact the capability of syslinux to install other os'es).I don't think "mem=" would help at all but I could be wrong.
It works; both SYSLINUX and the kernel with honour it.
Quoted 2 lines
My "easy" fix was to pull out a DIMM from each of our machines, leaving 3x256 :-) Not elegant, but fast!
As already said, get SYSLINUX 1.44 or later...
-hpa
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
Quoted 4 lines · H. Peter Anvin
Quoted 1 line · Neil Conway
I don't think "mem=" would help at all but I could be wrong.
It works; both SYSLINUX and the kernel with honour it.
Darn - I assumed that SYSLINUX wouldn't parse it :-(
Neil
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
Hi,
In article <[email protected]>, "H. Peter Anvin"
Quoted 5 lines · <[email protected]> writes:
Quoted 2 lines · Neil Conway
My "easy" fix was to pull out a DIMM from each of our machines, leaving 3x256 :-) Not elegant, but fast!
As already said, get SYSLINUX 1.44 or later...
Which works nicely --- thanks Peter. The current Red Hat lorax snapshots use the later syslinux and for the first time they boot without messing about with kernel mem= parameters on the large-mem box here.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/