This is a multi-part message in MIME format.
------=_NextPart_000_0032_01C1C0AC.BF85A800
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I am having the exact same problems with my linux box.
I have a 486, 24Mb of ram, and a RAID 1 partition. The box runs =
dhcp, xinetd, telnetd, and samba. It currently only serves the RAID 1 =
partition via samba to a single Win98 box.
Under any large file transfer to the linux box, regardless of which =
machine initiates the x-fer, the linux box kernel panics and dies. =
Currently, I have tried running many kernels, upgrading to a different =
glibc and rawhide kernel, and even scrapped RH and made an LFS =
partition. I have also used multiple versions of samba and I have tried =
using 3com's driver instead of the kernel driver. Nothing has fixed this =
problem. Recently, I thought the network load was filling the physical =
memory because the error was usually a "Unable to handle kernel virtual =
memory paging request," however, I have tried both stock kernels and RH =
kernels with the rmap VM system and both crash. I also increased =
/proc/sys/vm/freepages to such large numbers that there was always over =
a meg of free mem while a file transfer was going, but the box still =
crashed.
The stack dump used to be from many different programs, but, after I =
increased freepages, it seems to always be from the 3c59x module. I have =
tried 3com's driver instead. It held up better under load, but still =
crashed after about 15 minutes of file transfer via samba.
I do not believe this is a RAID problem as I get the same problem =
with RAID turned off and sharing a regular non-RAID directory with =
samba.
I now feel that, because two seperate drivers fail, this must be =
some issue with the hardware. As I just found this problem and it seems =
as if you have 3com card in the same family as mine, I am very confidant =
now. If you search the mail list archives for the 3c59x driver, you will =
find this problem many times over. I don't yet know the solution, but, =
if you can, you might try a different networking card. I am going to =
switch out the NIC cards between my Linux box and Win98 box and see how =
that does. Hopefully it's not an issue between the two cards.
------=_NextPart_000_0032_01C1C0AC.BF85A800
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I am having the exact same problems =
with my linux=20
box.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2> I have a 486, 24Mb =
of ram, and a=20
RAID 1 partition. The box runs dhcp, xinetd, telnetd, and samba. It =
currently=20
only serves the RAID 1 partition via samba to a single Win98 =
box.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Under any large file transfer to the =
linux=20
box, regardless of which machine initiates the x-fer, the linux box =
kernel=20
panics and dies. Currently, I have tried running many kernels, =
upgrading to=20
a different glibc and rawhide kernel, and even scrapped RH and made an=20
LFS partition. I have also used multiple versions of samba and I =
have tried=20
using 3com's driver instead of the kernel driver. Nothing has =
fixed=20
this problem. Recently, I thought the network load was filling the =
physical=20
memory because the error was usually a "Unable to handle kernel virtual =
memory=20
paging request," however, I have tried both stock kernels and RH kernels =
with=20
the rmap VM system and both crash. I also increased =
/proc/sys/vm/freepages to=20
such large numbers that there was always over a meg of free mem while a =
file=20
transfer was going, but the box still crashed.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> The stack dump =
used to be=20
from many different programs, but, after I increased freepages, it =
seems to=20
always be from the 3c59x module. I have tried 3com's driver instead. It =
held up=20
better under load, but still crashed after about 15 minutes of file =
transfer via=20
samba.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> I do not believe =
this is a RAID=20
problem as I get the same problem with RAID turned off and sharing a =
regular=20
non-RAID directory with samba.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> I now feel that, =
because two=20
seperate drivers fail, this must be some issue with the hardware. As I =
just=20
found this problem and it seems as if you have 3com card in the same =
family as=20
mine, I am very confidant now. If you search the mail list archives for =
the=20
3c59x driver, you will find this problem many times over. I don't yet =
know the=20
solution, but, if you can, you might try a different networking card. I =
am going=20
to switch out the NIC cards between my Linux box and Win98 box and see =
how that=20
does. Hopefully it's not an issue between the two cards.</FONT></DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_0032_01C1C0AC.BF85A800--
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
