Using the 2.4.0 kernel and a kernel compiled with support for 4GB of
memory, mounting of the initial ramdisk fails when 1GB or more
of memory is installe dint he system.
There is no OOPS, it simply says, unable to mount root vfs, I ma
thinking the INITRD system cant handle the offset's involved
Using the 2.4.0 kernel and a kernel compiled with support for 4GB of
memory, mounting of the initial ramdisk fails when 1GB or more
of memory is installe dint he system.
There is no OOPS, it simply says, unable to mount root vfs, I ma
thinking the INITRD system cant handle the offset's involved
installed.
I would appreciate any help I can get on this, thanks in advance.
-Adam Scislowicz <[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/
installed.
I would appreciate any help I can get on this, thanks in advance.
-Adam Scislowicz [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/
I have had no luck finding a bigmem patch for the 2.0.x kernel. I am in
the situation where I would rather not update the kernel, do I have
any options?
-Adam Scislowicz <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
I have had no luck finding a bigmem patch for the 2.0.x kernel. I am in
the situation where I would rather not update the kernel, do I have
any options?
-Adam Scislowicz [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
I Previously Wrote:
> Could someone explain why send is failing with EPIPE on the 2.4.x
> kernel, while it is working with the 2.2.x kernels.
It turns our the socket family was not being set to AF_INET :/
It was working in 2.2.x because in our situation the sock family was being
initialized to
I Previously Wrote:
Could someone explain why send is failing with EPIPE on the 2.4.x
kernel, while it is working with the 2.2.x kernels.
It turns our the socket family was not being set to AF_INET :/
It was working in 2.2.x because in our situation the sock family was being
initialized to
> From your subject you seem not to.
>
Im sorry for the subject I just wanted to give the environmental factors, and it is a
non-blocking socket. At this point I am not sure if that is relavent or not.
> To the best of my knowledge the receiver side EPIPE reporting has not changed,
> so it must
We understand the meaning of EPIPE, the question is why 2.4.x is returning EPIPE,
while 2.2.x is succeeding in sending
the data to thttpd. Using the 2.2.x kernel our proxy functions, and I can access
thttpd directly. In 2.4.x I can access thttpd
directly but the proxy does not function.
I have
Could someone explain why send is failing with EPIPE on the 2.4.x
kernel, while it is working with the 2.2.x kernels.
The PsuedoCode:
sock = socket(AF_INET, SOCK_STREAM, 0)
buf = fcntl(sock, F_GETFL)
fcntl(sock, F_SETFL, buf | O_NONBLOCK) // we check the SETFL return
value, it succeeds
while
Could someone explain why send is failing with EPIPE on the 2.4.x
kernel, while it is working with the 2.2.x kernels.
The PsuedoCode:
sock = socket(AF_INET, SOCK_STREAM, 0)
buf = fcntl(sock, F_GETFL)
fcntl(sock, F_SETFL, buf | O_NONBLOCK) // we check the SETFL return
value, it succeeds
while
We understand the meaning of EPIPE, the question is why 2.4.x is returning EPIPE,
while 2.2.x is succeeding in sending
the data to thttpd. Using the 2.2.x kernel our proxy functions, and I can access
thttpd directly. In 2.4.x I can access thttpd
directly but the proxy does not function.
I have
From your subject you seem not to.
Im sorry for the subject I just wanted to give the environmental factors, and it is a
non-blocking socket. At this point I am not sure if that is relavent or not.
To the best of my knowledge the receiver side EPIPE reporting has not changed,
so it must be
14 matches
Mail list logo
