Bug 19004 - time gets reset to current-5hrs after idle time
Summary: time gets reset to current-5hrs after idle time
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-12 22:45 UTC by Need Real Name
Modified: 2008-08-01 16:22 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2004-09-30 15:38:50 UTC

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

Description Need Real Name 2000-10-12 22:45:52 UTC 
I reported in an earlier bug report (#17897) that I could not get my
internal SCSI zip drive
to work correctly with my Adaptec Ultra-SCSI card using kernel 2.2.16-3. I
therefore went
back to using kernel 2.2.14-5.0 (the default on my v6.2 installation
CD-ROM), and updated
the aic7xxx.o driver to version 5.1.31 which I downloaded from 

http://people.redhat.com/dledford/aic7xxx.html

This seems to fix the zip drive problem. However, I find when I have left
my machine for long 
enough that the monitor power-down kicks in that when I log back in the
time has been reset
to 5 hours earlier. Curiously, if I telnet in from another machine this
problem does not arise, it only seems to arise if I log in on the console
(either in X-windows or terminal mode), but as soon as I log in on the
terminal the time does reset, even if I am logged in via a telnet session.
Comment 1 Bugzilla owner 2004-09-30 15:38:50 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.