Bug 35965
Summary: | X freeze - Nvidia TNT 128 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Sam Varshavchik <mrsam> | ||||||||||
Component: | XFree86 | Assignee: | Mike A. Harris <mharris> | ||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> | ||||||||||
Severity: | medium | Docs Contact: | |||||||||||
Priority: | medium | ||||||||||||
Version: | 7.1 | ||||||||||||
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: | 2001-11-01 11:51:45 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: | |||||||||||||
Attachments: |
|
Description
Sam Varshavchik
2001-04-15 17:33:54 UTC
Well, now that I think about it, X *should*'ve been getting constant input, from xclock. All I saw was X sitting in a select() call, and not getting anything... Can you reproduce this behaviour at will? If so, please describe the exact steps to follow to reproduce this problem, what all software you are running, GNOME applets, etc.. (or KDE, etc..). Please create a file attachment of your X server logs as well. Particularly one from after a crash. You will likely need to grab the log from a ssh session if using gdm, because if you log back into X it will overwrite your old log with a new one. It's not reproducible - it locked up after being up continuously for about ~72 hours. I have two machines with the same TNT card up and running. I'll grab the log if and when I get another lockup. It blew up on me again. I came back to the machine after it was sitting idle for about six hours. The display was frozen in a middle of a screen saver, the machine did not respond to mouse or keyboard activity, nor CTRL-ALT-Fx. Logging into the box over the network revealed the fact that X wasn't running at all. It dumped core on me. After X crashed on me for the first time a week ago, I began booting in run level 4, then manually running startx. So, I checked, and there was a nice 37 MB core dump sitting in my home directory. Loading the core dump into gdb confirmed that it came out of X. I am attaching the XFree86.0.log file, which I saved. The timestamp on the XFree86.0.log file was about 15 minutes before the timestamp on the core dump file. Here is the core dump: http://www.email-scan.com/core.gz The gzipped file is about 4 megs, uncompressed it's about 37 megs, and it's against the server in XFree86-4.0.3-5 package. Created attachment 16305 [details]
XFree86.0.log file
Crashed again. Here's another core dump: http://www.email-scan.com/core2.gz Please reconfigure your server with DRI disabled - DRI is not supported in the NV driver. Xconfigurator --preferxf4 --nodri Does this solve the problem? Nope! Just had another crash. I'm seeing this on two machines with the same TNT 128 card. It looks like the following traceback indicates heap corruption. I have the core file, but I doubt that it would contain anything useful. Created attachment 20110 [details]
Traceback
Created attachment 20111 [details]
XFree86.0.log from this crash.
Created attachment 20112 [details]
XF86Config-4 - dri disabled, was running in 1280x1024
Can you update the report and let me know if this problem is still present in XFree86 4.1.0 as shipped with Red Hat Linux 7.2? If it is still present, attach any new information you may have, and I will send it upstream to Nvidia directly. Thanks. I have not yet had 4.1.0 bomb out on me. So far so good. |