Bug 73814 - Machine Locks up when playing tuxracer
Summary: Machine Locks up when playing tuxracer
Keywords:
Status: CLOSED DUPLICATE of bug 73733
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 7.3
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-11 11:41 UTC by Ted Kaczmarek
Modified: 2007-04-18 16:46 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-09-11 11:41:41 UTC
Embargoed:


Attachments (Terms of Use)

Description Ted Kaczmarek 2002-09-11 11:41:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020408

Description of problem:
Kernel 2.4.9.X with tyan 2462 SMP athlon was ok, but with 2.4.18.X kernel my box
will lock up.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Get tyan 2462 with smp
2.Install nvidia drivers
3.Play tuxracer, will lock after short time playing
	

Actual Results:  Machine will almost always lock after 1st race in tuxracer.
Occasionally you will make into the 2nd race. One in a while screensaver would
cause it lock up as well.

Expected Results:  Game plays out.

Additional info:

In IRC someone else said they had the same problem with all their newer Athlons.
Common demonimator seems to be the 3Com nics. He stated  he switched to Intel
nic cards and no longer has any problems. His history was the same as mine,
meaning with the 2.4.9.X series both he and I had no problems, but with 2.4.18
we both have the problem. My motherboard has two built in nics so switching to
Intel nic in not an option for me.

Comment 1 Mike A. Harris 2002-09-15 05:42:03 UTC
Nvidia binary drivers are unsupported by Red Hat.  Please contact
Nvidia for support if you encounter any system instabilities while
using their drivers.

*** This bug has been marked as a duplicate of 73733 ***


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