* Re: syslinux-1.43 bug [and possible PATCH]
@ 1999-09-24 10:05 Javan Dempsey
0 siblings, 0 replies; 9+ messages in thread
From: Javan Dempsey @ 1999-09-24 10:05 UTC (permalink / raw)
To: kanoj, nconway.list, raz; +Cc: syslinux, linux-mm, linux-kernel
OOOOPSSSS! did I say 768k? I meant mem=768M sorry about that people. I've been awake entirely too long
---------- Original Message ----------------------------------
From: "Javan Dempsey" <raz@mailhost.directlink.net>
Reply-To: <raz@mailhost.directlink.net>
Date: Fri, 24 Sep 1999 04:04:09 -0500
>mem=768k is what I've had to use to get linux to install on our Dell PowerEdge boxen with >1GB of mem. I've noticed the same problem with each of those machines.
Javan.D
Senior Systems Admin.
iCelebrate.Com Inc. (raz@icelebrate.com)
---------- Original Message ----------------------------------
From: Neil Conway <nconway.list@UKAEA.ORG.UK>
Date: Fri, 24 Sep 1999 09:48:36 +0100
>Kanoj Sarcar wrote:
> 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.
Yup...
> 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).
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 majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syslinux-1.43 bug [and possible PATCH]
1999-09-24 8:55 ` H. Peter Anvin
1999-09-24 9:43 ` Neil Conway
@ 1999-09-24 16:30 ` Stephen C. Tweedie
1 sibling, 0 replies; 9+ messages in thread
From: Stephen C. Tweedie @ 1999-09-24 16:30 UTC (permalink / raw)
To: H. Peter Anvin
Cc: Neil Conway, Kanoj Sarcar, syslinux, linux-mm, linux-kernel
Hi,
In article <37EB3C86.F17CC25A@transmeta.com>, "H. Peter Anvin"
<hpa@transmeta.com> writes:
> Neil Conway wrote:
>> 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 majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syslinux-1.43 bug [and possible PATCH]
1999-09-24 8:55 ` H. Peter Anvin
@ 1999-09-24 9:43 ` Neil Conway
1999-09-24 16:30 ` Stephen C. Tweedie
1 sibling, 0 replies; 9+ messages in thread
From: Neil Conway @ 1999-09-24 9:43 UTC (permalink / raw)
To: H. Peter Anvin; +Cc: syslinux, linux-mm, linux-kernel
H. Peter Anvin wrote:
>
> Neil Conway wrote:
> > 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 majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syslinux-1.43 bug [and possible PATCH]
@ 1999-09-24 9:04 Javan Dempsey
0 siblings, 0 replies; 9+ messages in thread
From: Javan Dempsey @ 1999-09-24 9:04 UTC (permalink / raw)
To: kanoj, nconway.list; +Cc: syslinux, linux-mm, linux-kernel
mem=768k is what I've had to use to get linux to install on our Dell PowerEdge boxen with >1GB of mem. I've noticed the same problem with each of those machines.
Javan.D
Senior Systems Admin.
iCelebrate.Com Inc. (raz@icelebrate.com)
---------- Original Message ----------------------------------
From: Neil Conway <nconway.list@UKAEA.ORG.UK>
Date: Fri, 24 Sep 1999 09:48:36 +0100
>Kanoj Sarcar wrote:
> 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.
Yup...
> 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).
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 majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syslinux-1.43 bug [and possible PATCH]
1999-09-24 8:48 ` Neil Conway
@ 1999-09-24 8:55 ` H. Peter Anvin
1999-09-24 9:43 ` Neil Conway
1999-09-24 16:30 ` Stephen C. Tweedie
0 siblings, 2 replies; 9+ messages in thread
From: H. Peter Anvin @ 1999-09-24 8:55 UTC (permalink / raw)
To: Neil Conway; +Cc: Kanoj Sarcar, syslinux, linux-mm, linux-kernel
Neil Conway wrote:
>
> > 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).
>
> I don't think "mem=" would help at all but I could be wrong.
>
It works; both SYSLINUX and the kernel with honour it.
> 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 majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syslinux-1.43 bug [and possible PATCH]
1999-09-23 21:09 Kanoj Sarcar
1999-09-23 21:30 ` Matt Wilson
1999-09-23 21:55 ` H. Peter Anvin
@ 1999-09-24 8:48 ` Neil Conway
1999-09-24 8:55 ` H. Peter Anvin
2 siblings, 1 reply; 9+ messages in thread
From: Neil Conway @ 1999-09-24 8:48 UTC (permalink / raw)
To: Kanoj Sarcar; +Cc: syslinux, linux-mm, linux-kernel
Kanoj Sarcar wrote:
> 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.
Yup...
> 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).
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 majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syslinux-1.43 bug [and possible PATCH]
1999-09-23 21:09 Kanoj Sarcar
1999-09-23 21:30 ` Matt Wilson
@ 1999-09-23 21:55 ` H. Peter Anvin
1999-09-24 8:48 ` Neil Conway
2 siblings, 0 replies; 9+ messages in thread
From: H. Peter Anvin @ 1999-09-23 21:55 UTC (permalink / raw)
To: Kanoj Sarcar; +Cc: syslinux, linux-mm, linux-kernel
This is an old bug; it has been fixed since 1.44 or 1.45. The current
version is 1.47.
-hpa
On Thu, 23 Sep 1999, Kanoj Sarcar wrote:
> I have a possible problem to report with syslinux, and a suggested
> fix. Please send me comments and feedback at kanoj@engr.sgi.com,
> 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
> kanoj@engr.sgi.com
>
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syslinux-1.43 bug [and possible PATCH]
1999-09-23 21:09 Kanoj Sarcar
@ 1999-09-23 21:30 ` Matt Wilson
1999-09-23 21:55 ` H. Peter Anvin
1999-09-24 8:48 ` Neil Conway
2 siblings, 0 replies; 9+ messages in thread
From: Matt Wilson @ 1999-09-23 21:30 UTC (permalink / raw)
To: Kanoj Sarcar, syslinux, linux-mm, linux-kernel
This was fixed in 1.44, AFAIK. HIGHMEM_MAX is now 38000000h.
We're using 1.45 for our next release.
Matt
msw@redhat.com
On Thu, Sep 23, 1999 at 02:09:58PM -0700, Kanoj Sarcar wrote:
> I have a possible problem to report with syslinux, and a suggested
> fix. Please send me comments and feedback at kanoj@engr.sgi.com,
> 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
> kanoj@engr.sgi.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
^ permalink raw reply [flat|nested] 9+ messages in thread
* syslinux-1.43 bug [and possible PATCH]
@ 1999-09-23 21:09 Kanoj Sarcar
1999-09-23 21:30 ` Matt Wilson
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Kanoj Sarcar @ 1999-09-23 21:09 UTC (permalink / raw)
To: syslinux, linux-mm, linux-kernel; +Cc: Kanoj Sarcar
I have a possible problem to report with syslinux, and a suggested
fix. Please send me comments and feedback at kanoj@engr.sgi.com,
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
kanoj@engr.sgi.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~1999-09-24 16:30 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-09-24 10:05 syslinux-1.43 bug [and possible PATCH] Javan Dempsey
-- strict thread matches above, loose matches on Subject: below --
1999-09-24 9:04 Javan Dempsey
1999-09-23 21:09 Kanoj Sarcar
1999-09-23 21:30 ` Matt Wilson
1999-09-23 21:55 ` H. Peter Anvin
1999-09-24 8:48 ` Neil Conway
1999-09-24 8:55 ` H. Peter Anvin
1999-09-24 9:43 ` Neil Conway
1999-09-24 16:30 ` Stephen C. Tweedie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox