Bug 170479

Summary:	IBM Thinkcentre, 2.8GHz freezes after several hours of running
Product:	[Fedora] Fedora	Reporter:	peter hudak <hudis>
Component:	kernel	Assignee:	Dave Jones <davej>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	pfrields, pholland, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-05-05 01:45:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description peter hudak 2005-10-12 04:51:51 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Description of problem:
The IBM Thinkcentre with 2.8GHz HT CPU and 512M RAM and SATA disks freezes after 6-7 hours of work. however the system does not get completely unresponsible, so I'm enable to reproduce the bug anytime. First I thought it has something to do with software raid, because the problem arises when you want to do some disk operations. the operations (e.g. sync) complete after a long time (5-6 minutes), there is absolutely nothing written in dmesg. so I removed the raid disks and replaced them with simple ext3, with the same result. I upgraded the machine's bios to the latest and I upgraded the kernel to 2.6.13 both vanilla from kernel.org and fedora. the same results. when I run the uptime command, the load is below 1 and the time and uptime looks strange:
[root@ttserver ~]# uptime
 03:44:08 up 13:49,  1 user,  load average: 0.78, 0.24, 0.08
[root@ttserver ~]# hwclock
Wed Oct 12 06:42:59 2005  -0.700004 seconds
[root@ttserver ~]# date
Wed Oct 12 03:44:05 AST 2005
[root@ttserver ~]# date
Wed Oct 12 03:44:04 AST 2005
[root@ttserver ~]# date
Wed Oct 12 03:44:07 AST 2005
[root@ttserver ~]# date
Wed Oct 12 03:44:06 AST 2005
[root@ttserver ~]# date
Wed Oct 12 03:44:10 AST 2005
[root@ttserver ~]# date
Wed Oct 12 03:44:09 AST 2005
[root@ttserver ~]# uptime
 03:44:10 up 13:49,  1 user,  load average: 0.78, 0.24, 0.08
[root@ttserver ~]# uptime
 03:44:12 up 13:49,  1 user,  load average: 0.78, 0.24, 0.08
[root@ttserver ~]# uptime
 03:44:12 up 13:49,  1 user,  load average: 0.78, 0.24, 0.08
[root@ttserver ~]# uptime
 03:44:10 up 13:49,  1 user,  load average: 0.78, 0.24, 0.08
[root@ttserver ~]# uptime
 03:44:14 up 13:49,  1 user,  load average: 0.71, 0.23, 0.08

the clock seems to be running backwards!


Version-Release number of selected component (if applicable):
kernel-2.6.13-1.1526_FC4smp

How reproducible:
Always

Steps to Reproduce:
1.install a fresh FC4 without Xwindows to IBM Thinkcentre
2.wait 6 hours
3.type some commands
  

Actual Results:  machine slowness and unusability

Expected Results:  normal behaviour

Additional info:

Comment 1 Dave Jones 2005-11-10 19:35:53 UTC

2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.

Thank you.

Comment 2 Dave Jones 2006-02-03 06:51:32 UTC

This is a mass-update to all currently open kernel bugs.

A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

Thank you.

Comment 3 John Thacker 2006-05-05 01:45:39 UTC

Closing per previous comment.