Created attachment 42395 [details] X configuration file Video playback has started causing random reboots. To rule out hardware failures (memory, CPU, GPU), I ran four different stress test (listed below), all of which completed without errors. Reboots occurred from few minutes to up to 30 to 40 minutes from the start of the video. They have occurred both with mplayer and Adobe Flash Player plugin. Usually there has been no log files. However, in one occurrence mplayer simply crashed and the machine didn't reboot. I'll attach those logs in case they are relevant. Motherboard: Gigabyte MA790XT-UD4P Chipset: North Bridge AMD 790X / South Bridge AMD SB750 Processor: AMD Phenom II X3 720 Display adapter: Club 3D HD 4770 512MB (RV740) Display: HP Pavilion f1940 (1280x1024) Stress tests: Memory: Memtest86+ durating ca. 6 hours, no errors CPU: StressCPU2 from Phoronix Test Suite, 6 hours, completed successfully GPU: 1) 3DMark 2000 v1.1 build 340, Game 1 & Game 2 with High Detail, in continuous loop for ca. 6 hours, no errors 2) Nexuiz test from Phoronix Test Suite, 6 hours, no errors Distribution: ArchLinux x86-64 (rolling release, up to date) Installed packages: kernel: 2.6.36.3-1 xorg-server: 1.9.2-2 xf86-video-ati: 6.13.2-2 xf86-input-evdev: 2.5.0-1 libdrm: 2.4.22-3 mesa: 7.9.0.git20101207-2 ati-dri: 7.9.0.git20101207-2 libgl: 7.9.0.git20101207-2
Created attachment 42398 [details] Output of 'lspci -vvnn'
Created attachment 42399 [details] Xorg.0.log after boot
Created attachment 42400 [details] A more comprehensive list of X related packages
Created attachment 42401 [details] Output of 'glxinfo'
Created attachment 42402 [details] Output of 'glxinfo32'
Created attachment 42403 [details] The relevant parts of 'everything.log' from the mplayer crash
Created attachment 42405 [details] The relevant parts of 'kernel.log' from the mplayer crash
(In reply to comment #8) > Video playback has started causing random reboots. What component(s) changed between the problem not occurring and occurring?
(In reply to comment #8) > (In reply to comment #8) > > Video playback has started causing random reboots. > > What component(s) changed between the problem not occurring and occurring? If I can remember correctly, the first reboots (a few times) occurred some time last year (can't remember the exact time). But because the problem went away I didn't investigate it any further back then. The reboots reoccurred about two weeks ago, around the 12th January, I can't remember the exact date. Again, the reboots went away for a while, only to come back last Thursday (20th January). I looked from pacman's log file for updates that might have caused this. I limited this to updates that took place this year. The log file goes back to January 2010, so if needed I can post the whole thing. [2011-01-11 10:35] upgraded kernel26 (2.6.36.2-1 -> 2.6.36.3-1) [2011-01-12 21:20] upgraded kernel26 (2.6.36.3-1 -> 2.6.36.2-1) [2011-01-13 00:49] upgraded kernel26 (2.6.36.2-1 -> 2.6.36.3-1) [2011-01-19 19:18] upgraded xf86driproto (2.1.0-1 -> 2.1.1-1) [2011-01-19 19:18] upgraded xf86vidmodeproto (2.3-1 -> 2.3.1-1) [2011-01-01 17:48] upgraded xorg-iceauth (1.0.3-1 -> 1.0.4-1) [2011-01-01 17:48] upgraded xorg-utils (7.6-5 -> 7.6-6) [2011-01-18 20:14] upgraded mplayer (32663-1 -> 32792-1) [2011-01-18 20:14] upgraded ffmpeg (25679-1 -> 26387-1) [2011-01-21 20:08] upgraded ffmpeg (26387-1 -> 20110121-1) [2011-01-13 11:49] Running 'pacman -S lib32-ati-dri' [2011-01-13 11:49] installed lib32-ati-dri (7.9.0.git20101207-2) [2011-01-24 04:15] Running 'pacman -R lib32-ati-dri' [2011-01-24 04:15] removed lib32-ati-dri (7.9.0.git20101207-2) [2011-01-24 04:16] Running 'pacman -S lib32-ati-dri' [2011-01-24 04:16] installed lib32-ati-dri (7.9.0.git20101207-2) [2011-01-18 20:14] upgraded x264 (20101013-1 -> 20110115-1) Reboots have occurred both with xvideo and opengl as mplayer's video out device. However, I believe I have found a work around that works. When I force mplayer to do software color conversion from yuv420p (yv12 ?) to yuyv422 (yuy2) no reboots have occurred with xvideo as output device. Opengl works also when I force it to do software color conversion. I hope that helps.
(In reply to comment #9) > > Reboots have occurred both with xvideo and opengl as mplayer's video out > device. > However, I believe I have found a work around that works. When I force mplayer > to do software color conversion from yuv420p (yv12 ?) to yuyv422 (yuy2) no > reboots have occurred with xvideo as output device. Opengl works also when I > force it to do software color conversion. > Apparently, I was wrong about the software color conversion workaround. I have now tried doing software color conversion to all different types of color spaces that xvideo accepts (YUY2, YV12, YV12 and UYVY), and they all cause reboots. I'll check whether this also applies to opengl as video output device.
Do you have a lot of devices (USB devices, harddrives, DVD, etc.) connected to your system? What size power supply? There was another similar bug that was due to an inadequate power supply.
(In reply to comment #11) > Do you have a lot of devices (USB devices, harddrives, DVD, etc.) connected to > your system? What size power supply? There was another similar bug that was > due to an inadequate power supply. I have a 600 W power supply. I have three harddrives, DVD-writer and a LPT-adapter (PCI).
(In reply to comment #12) > (In reply to comment #11) > > Do you have a lot of devices (USB devices, harddrives, DVD, etc.) connected to > > your system? What size power supply? There was another similar bug that was > > due to an inadequate power supply. > > I have a 600 W power supply. I have three harddrives, DVD-writer and a > LPT-adapter (PCI). Any chance you could test with some of that hw temporarily disconnected just to be sure?
(In reply to comment #13) > (In reply to comment #12) > > (In reply to comment #11) > > > Do you have a lot of devices (USB devices, harddrives, DVD, etc.) connected > > > to your system? What size power supply? There was another similar bug > > > that was due to an inadequate power supply. > > > > I have a 600 W power supply. I have three harddrives, DVD-writer and a > > LPT-adapter (PCI). > > Any chance you could test with some of that hw temporarily disconnected just to > be sure? I have now disconnected all non-essential devices (LPT-adapter, two harddrives, DVD-writer and a memory card reader), leaving just one hard drive connected. I'll post a message if the machine reboots again. Or if it doesn't, I'll post a message conforming that in a week or two.
(In reply to comment #14) > (In reply to comment #13) > > (In reply to comment #12) > > > (In reply to comment #11) > > > > Do you have a lot of devices (USB devices, harddrives, DVD, etc.) connected > > > > to your system? What size power supply? There was another similar bug > > > > that was due to an inadequate power supply. > > > > > > I have a 600 W power supply. I have three harddrives, DVD-writer and a > > > LPT-adapter (PCI). > > > > Any chance you could test with some of that hw temporarily disconnected just to > > be sure? > > I have now disconnected all non-essential devices (LPT-adapter, two harddrives, > DVD-writer and a memory card reader), leaving just one hard drive connected. > > I'll post a message if the machine reboots again. Or if it doesn't, I'll post a > message conforming that in a week or two. It took a little bit over two weeks, but a reboot has occurred (I was already about to order a new power suply). And I had removed all extra devices (just M/B, processor, memory, display adapter, one harddrive and fans were connected).
(In reply to comment #15) > (In reply to comment #14) > > (In reply to comment #13) > > > (In reply to comment #12) > > > > (In reply to comment #11) > > > > > Do you have a lot of devices (USB devices, harddrives, DVD, etc.) > > > > > connected to your system? What size power supply? There was another > > > > > similar bug that was due to an inadequate power supply. > > > > > > > > I have a 600 W power supply. I have three harddrives, DVD-writer and a > > > > LPT-adapter (PCI). > > > > > > Any chance you could test with some of that hw temporarily disconnected > > > just to be sure? > > > > I have now disconnected all non-essential devices (LPT-adapter, two > > harddrives, DVD-writer and a memory card reader), leaving just one hard > > drive connected. > > > > I'll post a message if the machine reboots again. Or if it doesn't, I'll > > post a message conforming that in a week or two. > > It took a little bit over two weeks, but a reboot has occurred (I was already > about to order a new power suply). And I had removed all extra devices (just > M/B, processor, memory, display adapter, one harddrive and fans were > connected). I have now also tested the closed source Catalyst-drivers for a week. I know you guys don't handle Catalyst bugs, I just thought it would be interesting to see whether or not the reboots occur also with Catalyst-drivers. Besides some other bugs, there has been one reboot during video playback (flash video). The hardware configuration was the same, only one harddisk was connected.
(In reply to comment #16) > I have now also tested the closed source Catalyst-drivers for a week. I know > you guys don't handle Catalyst bugs, I just thought it would be interesting to > see whether or not the reboots occur also with Catalyst-drivers. > > Besides some other bugs, there has been one reboot during video playback (flash > video). The hardware configuration was the same, only one harddisk was > connected. Sounds like a hw issue.
I changed the power supply about two weeks ago to a Nexus RX-1K 1000W power supply. Despite this, a reboot has occured. This time it was during flash video plaback this time.
I have now also tested a BIOS update (from F4 to F8G) and a different graphics card (NVIDIA GeForce 7600GT, nvidia closed-source drivers). In both cases reboots didn't stop occurring.
(In reply to comment #19) > I have now also tested a BIOS update (from F4 to F8G) and a different graphics > card (NVIDIA GeForce 7600GT, nvidia closed-source drivers). In both cases > reboots didn't stop occurring. Sounds like a motherboard problem.
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.
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.