Bug 9274 - Networking stops working after system is up for a couple of hours
Networking stops working after system is up for a couple of hours
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-02-09 14:20 EST by doug.kratky
Modified: 2014-01-23 04:04 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-12-13 21:35:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description doug.kratky 2000-02-09 14:20:30 EST
Everything works fine for a while after reboot.  After some amount of time
(less than a couple of hours), networking stops working.  Can't ping any
remote IP addresses by name or address.  Other systems on network (e.g.,
Solaris, NT., etc. are fine).

When problem happens, "netstat -in" output, ifconfig output, all looks
okay.  If I do "ifconfig eth0 down" and then "ifconfig eth0 up", then
networking starts working again.
Comment 1 Riley H Williams 2000-02-09 14:58:59 EST
Is this on a machine with an AMD processor? If so, it could be connected with
one of my systems with an AMD K6-2/350 processor that also locks up after a
couple of hours.
Comment 2 mark.seminatore 2000-02-25 00:17:59 EST
See my bug #6258. I have a number of machines locking up.  Thought it was the
NICS, replace em but it still happens.  I suspect SMP now and am running stock
2.2.12.  I have reports that ifconfig eth0 down up restored connectivity.
Comment 3 mark.seminatore 2000-02-25 00:19:59 EST
Sorry, it was bug #9258.
Comment 4 dch 2000-02-27 02:50:59 EST
I have a similar problem on two identical machines on different
networks, both stock redhat 6.1 installs with p-III and 3c509c
cards.  They stop talking through the gateway but can talk to
machines on the local network.  If left alone they will start
talking outbound after a random amount of time (10-60 minutes or
so).  If I drop the default route and add it back they start talking
to the gateway.  I'm not sure if it's the kernel since I have
6.0 machines that I've upgraded to 2.2.12 and don't have that
problem.

Note You need to log in before you can comment on or make changes to this bug.