Hi, This is in no way a complaint or accusation, but something I feel I should report. I have been using the nv driver for roughly 14 months, and switched to xorg about 7 months ago. I switched to nv from the proprietary Nvidia driver when I found nv supported swsusp. I have a Toshiba Satellite 5100-501 laptop (UK version of the US 5105-s607), with an NV17M chip. The laptop is just over 3 years old. The video card is beginning to fail on me; the screen fills with noise, and X may or may not crash. Sometimes I can cause the problem by tapping on the case or keys, but it will often occur randomly, without fan or disk activity starting up. I can definitely cause the problem by opening the case and tapping on the NV17M itself. The problem also occurs (now) under the fb console and when booted from the memtest86 disk (also linux based, haven't tried much else). Occurence of the problem seems to be heat related: the longer the display is powered on, the more likely it is to happen. I have now switched back to the proprietary Nvidia driver, and the problem is substantially reduced. I suspect different, non-damaged, circuit paths are being accessed under the proprietary driver, e.g. AGP. I intend to get an image of the problem up at the URL above within a few hours. So, could be (have been) a problem with my xorg.conf settings, could be random hardware failure, or could be an nv problem. I only wish to report it as a data point.
Created attachment 2900 [details] [review] Don't call _cairo_ft_unscaled_font_init_key in the from_face case. This seems better than waiting for me to set up the web page. The pattern is similar across occurrences of the event.
Three-year-old laptop hardware is not exactly the most resilient to failure; I suppose that it's well out of the warranty period? In any case, I'm not sure that this is really a bug in the software, so unless there's some conclusive proof that this was caused by X.org's nv driver, I'm going to mark this as 'NOTOURBUG'
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.