Hi Thierry,
Sorry for taking so long to respond - I usually am not able to catch up
with the Red Hat mailing list on a day-to-day basis, but since you haven't
gotten much response (only 1 that I can see) I thought I may weigh in with
what I know.
What kind of NIC card do you have? I ran into the kind of freeze you
mentioned (on a Red Hat 7.2 system), and it turned out to be a driver
problem with the NIC card, specifically the Intel NIC card, which is
integrated into the motherboard. To find out what kind of NIC card you
have, type:
/sbin/lspci
which will list all the boards in the PCI slots (including the integrated
cards). This is what I got for my system:
02:08.0 Ethernet controller: Intel Corporation 82801BA(M) Ethernet
(rev 03)
Now, if you do have this Intel NIC card, then do this:
/sbin/lsmod
this will list all the driver modules that are currently loaded. If you
have the Intel NIC card, it will say:
eepro100 17680 1
and if that is the case, then you have the same problem that I have. It
appears that the eepro100 driver has a bug which will cause the computer to
hang. When this occurs, it will not even answer a "ping" from another machine.
What I do learn is that before Red Hat 7.2, the driver for the Intel NIC
card is the "e100" driver instead of the "eepro100" driver, but then in Red
Hat 7.2 it was changed, and apparently not for the better. Luckily, the
"e100" driver is still around, and you can manually use this driver instead
of the "eepro100". You can do that by going into "linuxconf", and follow
these navigation scheme:
Click on the "Config" tab -> Networking -> Client tasks ->
Hostnaem and IP devices
then on the right hand side click "Adaptor 1" (assuming you only have 1 NIC
card), use the scroll bar on the right to scroll down to the field named
"Kernel module". If I am correct in my theory, this field would have the
value of "eepro100". Click on the drop-down arrow key, scroll down and
select "e100". Then click "Accept", and then quit out of
"linuxconf". Reboot to make sure that the new driver (e100) is being used
instead of the old one (eepro100). That should solve your freezing problem
on your server.
... Edwin
At 08:17 AM 9/26/02 +0000, you wrote:
> >I have a RedHat 7.2 (2.4.7-10 kernel) server that has constantly been
>freezing. The machine will be on, but its as good as its turned off. When
>I go to the console, there is no video signal, and all I can do at that
>point is a cold reboot. I have replaced the NIC, changed the HD but to no
>luck. It is on a Dell 4300. I am beginning to think that it may just be
>some incompatibility that is causing these random freezes. I am
>considering upgrading to a newer kernel, or may be even upgrading to 7.3.
>Has anyone experienced such phenomena?
>
>it's very likely, IMHO, that this problem is related to APM
>try disabling apm in bios and deactivate apmd in startup scripts, try also
>to recompile your kernel with apm unconfigured
> - * - * - * - * - * - * -
>Bien sûr que je suis perfectionniste !
>Mais ne pourrais-je pas l'être mieux ?
> Thierry ITTY
>eMail : [EMAIL PROTECTED] FRANCE
>
>
>
>--
>redhat-list mailing list
>unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
>https://listman.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
