Description of problem: When I try to play a video with xine I have a system crash and only reset helps as keyboard is inactive. Version-Release number of selected component (if applicable): xine-lib-1.1.16.3-5.fc12.i686 How reproducible: always Steps to Reproduce: 1. xine filename 2. 3. Actual results: Expected results: Additional info:
Created attachment 400913 [details] dmesg
Created attachment 400914 [details] xorg.log
VLC and mplayer run fine, only xine crashes whole system. This might be related to my intel video card 845G.
Looks like a driver bug, reassigning.
This bug is probably related to kernel mode settings and intel driver as it repeats in Ubuntu and Slackware with KMS. Without KMS in Slackware xine worked perfectly.
Of course, variant is that it is a bug in xine libs, but let's try xorg first. Could you confirm please, that both attachment in comment 1 and comment 2 are collected AFTER the Xorg crashed? They look too clean to me. Thank you for helping to make Fedora awesome!
They are collected after the crash and they were intended just to give some info about my machine. As I said before when system crashes I am unable to use keyboard, nor switch virtual terminals, even magic SysRq is dead. Thus I`m unable to get any data about the crash when it happens. I`ll try to look deeper into logs but I guess the intel driver crashes the kernel and the logs won`t have anything useful. There is another problem under Fedora 12, namely X crashes randomly from time to time and I don`t know what is the cause. I thought it is yum, then firefox, but It happened also with kmail so I guess this happens randomly or when system resources are extensively used. I haven`t reported a bug because I don`t know what is the cause of this crashes. Slackware and Ubuntu don`t crash that way.
How would a bug in xine-lib ou xine-ui crash the whole system? This is almost definitely an X11 or kernel bug.
I`ll try to test the logs and redirect xine output to a file, maybe it`ll be helpfull. As soon I find something I`ll add a comment
I made test crash and found that xorg generated 5 log files, all same size and content. One is attched. Also I found some info in log/messages: Mar 19 22:09:03 wm pulseaudio[1634]: ratelimit.c: 3 events suppressed Mar 19 22:09:04 wm kernel: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Mar 19 22:09:04 wm kernel: render error detected, EIR: 0x00000000 Mar 19 22:09:04 wm kernel: [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 389586 at 389585) Mar 19 22:09:05 wm abrt[2103]: saved core dump of pid 1402 (/usr/bin/Xorg) to /var/cache/abrt/ccpp-1269032944-1402.new/coredump (1 6576512 bytes) Mar 19 22:09:05 wm abrtd: Directory 'ccpp-1269032944-1402' creation detected Mar 19 22:09:07 wm abrt[2124]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:07 wm gdm-binary[1350]: WARNING: GdmDisplay: display lasted 1,945026 seconds Mar 19 22:09:07 wm abrtd: Crash is in database already (dup of /var/cache/abrt/ccpp-1268867757-1486) Mar 19 22:09:07 wm abrtd: Deleting crash ccpp-1269032944-1402 (dup of ccpp-1268867757-1486), sending dbus signal Mar 19 22:09:09 wm abrt[2146]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:09 wm gdm-binary[1350]: WARNING: GdmDisplay: display lasted 1,747457 seconds Mar 19 22:09:09 wm abrt[2151]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:09 wm gdm-binary[1350]: WARNING: GdmDisplay: display lasted 0,424226 seconds Mar 19 22:09:10 wm abrt[2156]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:10 wm gdm-binary[1350]: WARNING: GdmDisplay: display lasted 0,506159 seconds Mar 19 22:09:10 wm abrt[2161]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:10 wm gdm-binary[1350]: WARNING: GdmDisplay: display lasted 0,443766 seconds Mar 19 22:09:11 wm abrt[2166]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:11 wm gdm-binary[1350]: WARNING: GdmDisplay: display lasted 0,427383 seconds Mar 19 22:09:11 wm gdm-binary[1350]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors Mar 19 22:09:11 wm init: prefdm main process (1350) terminated with status 1 Mar 19 22:09:11 wm init: prefdm main process ended, respawning Mar 19 22:09:11 wm abrt[2194]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:11 wm gdm-binary[2167]: WARNING: GdmDisplay: display lasted 0,414237 seconds Mar 19 22:09:12 wm abrt[2199]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:12 wm gdm-binary[2167]: WARNING: GdmDisplay: display lasted 0,412428 seconds Mar 19 22:09:12 wm abrt[2204]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:12 wm gdm-binary[2167]: WARNING: GdmDisplay: display lasted 0,413122 seconds Mar 19 22:09:13 wm abrt[2209]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:13 wm gdm-binary[2167]: WARNING: GdmDisplay: display lasted 0,413315 seconds Mar 19 22:09:13 wm abrt[2214]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:13 wm gdm-binary[2167]: WARNING: GdmDisplay: display lasted 0,416515 seconds Mar 19 22:09:13 wm abrt[2219]: not dumping repeating crash in '/usr/bin/Xorg' Mar 19 22:09:13 wm gdm-binary[2167]: WARNING: GdmDisplay: display lasted 0,413375 seconds Mar 19 22:09:13 wm gdm-binary[2167]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
Created attachment 401353 [details] xorg.log during crash
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.