Summary: | Hang ups on Gigabyte PCI-E NX66128DP-Geforce6600 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Dariusz J. Garbowski <thuforuk> | ||||||
Component: | Driver/nVidia (open) | Assignee: | Xorg Project Team <xorg-team> | ||||||
Status: | RESOLVED WORKSFORME | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | critical | ||||||||
Priority: | high | CC: | aplattner | ||||||
Version: | 7.0.0 | ||||||||
Hardware: | x86 (IA32) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Dariusz J. Garbowski
2006-02-25 06:17:04 UTC
I spent some time trying to identify which screensavers result in crash. I ended up trying lots of screensavers by running them for some period of time and noting how much time I ran them and whether they caused crash or not. The following definitely cause total hang up: Lorenz Atractor - crash in seconds Julia - crash in a second Fade Plot - crash in a second Discrete - crash in minutes Hopalong - crash in seconds The following did not result in crashes, however some were run only for about 20 seconds so there is no certainty they would not crash eventually: Anemotaxis Apollonian Barcode BlitSpin Blob Coral Drift Flame Forest Fractal Maps Iterated-function-system Images Kumppa Mismunch Moire Moire2 Mountain Pedal RD-Bomb Rorschach Sierpniski Strange Swirl Tornbird Vines Wander Xlyap Blaster WhirlwindWarp XRaySwarm Bubbles Fireworkx The following did not crash run for at least few minutes: Intermomentary Substrate ANd finally this one run for hours without crash: Sonar Hope this helps to identify some pattern and function that causes the hang up. For troubleshooting, try using Option "noaccel" in the device section of xorg.conf and restarting. If the problem is no longer reproduceable with that, try commenting out the noaccel, and using the XaaNo options in the xorg.conf manpage one at a time to narrow things down. TIA P.S. Please use bugzilla's "create file attachment" link to attach log files and other files in the future instead of pasting them into a huge comment. Huge logs in comments make bug reports less readable in general, which turns off many developers. HTH Created attachment 4805 [details]
Xorg.0.log with Option "noaccel"
I still get X crashing with Option "noaccel". Attached log file. I don't suppose there's any point in trying XaaNo? BTW: there's at least one person that can confirm seeing the same issue: https://www.redhat.com/archives/fedora-test-list/2006-February/msg02017.html Created attachment 4806 [details]
Original Xorg.0.log
Looking through the log, I notice DDC doesn't identify the monitor. In chasing an apparently unrelated bug, I see the vesa driver successfully getting all the modes via DDC, but the nv driver fails to get the information. Not a big problem in itself, but perhaps a clue to the real problem? Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. If you're still seeing hangs even with the NoAccel option, then it's unlikely that you're seeing an nv driver bug and more likely that you're just seeing general system instability. Please try a newer version of X and nv version 2.0.1 and see if you're still seeing problems. You could also try the screensavers with the vesa driver. No response in over a month. Closing. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.