Bug 50936 - Networking stops after time change during kernel upgrade
Summary: Networking stops after time change during kernel upgrade
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
(Show other bugs)
Version: 7.1
Hardware: i686 Linux
medium
low
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-05 06:30 UTC by Stephen Vance
Modified: 2008-08-01 16:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-30 15:39:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Stephen Vance 2001-08-05 06:30:28 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
Updating kernel from base RH 7.1 to 2.4.3-12 with up2date (only kernel and 
kernel-header).  I don't specifically know that the time was correctly set 
before the upgrade, but I am pretty sure and did not consciously change 
it.  After the upgrade, networking did not work.  Interface was correctly 
configured, routed were correct, and localhost and host's IP all worked, 
but any other host resulted in "network unreachable" and no other hosts 
could ping it.  Networking is Xircom CEM100 PCMCIA in Gateway Solo 5100.  
After the reboot, clock was exactly 12 hours ahead of where it should have 
been.

How reproducible:
Didn't try

Steps to Reproduce:
1. Install kernel-2.4.3-12
2. Check clock.
3. If not already done, set clock 12 hours ahead
	

Additional info:
Comment 1 Bugzilla owner 2004-09-30 15:39:06 UTC 
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/
Note You need to log in before you can comment on or make changes to this bug.