Find the answer to your Linux question:
Results 1 to 7 of 7
Like Tree2Likes
  • 1 Post By larrythethird`
  • 1 Post By ramin.honary
Hi Everyone: I have recently started using Fedora 14. However, I am unable to figure out that why my system keeps on crashing whenever I play some video using any ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jan 2008
    Posts
    28

    F14 Crash: System Hangs, Keyboard Doesn't Responod, Hard Reset Only?


    Hi Everyone:

    I have recently started using Fedora 14. However, I am unable to figure out that why my system keeps on crashing whenever I play some video using any media player. Moreover, system also hangs whenever I do an image search on Google images. Everythings hangs, keyboard does not respond, although cursor can be moved around but clicking does not do anything, and in the end i have no option but to do a HARD RESET.

    I have searched internet for possible solutions but all in vain. Can anybody help me out in this regard?

    I am quite new to linux, so kindly keep it simple.

    Regards,

  2. #2
    Just Joined!
    Join Date
    Jun 2004
    Location
    North Hollywood, CA
    Posts
    22
    With almost no information, to me it seams like a video driver issue. Since I have no idea about your hardware, that's where I would look first. Either a video driver issue or some type of memory mismatch or something is accessing a bad memory location. Since you said multimedia search, the only thing different in multimedia from basic programs is the graphics and sound.
    ehsanulhaq likes this.

  3. #3
    Linux User
    Join Date
    Nov 2008
    Location
    Tokyo, Japan
    Posts
    260
    Maybe just the GUI hangs, not the system itself.

    When the GUI hangs, can you still jump into the frame buffer TTY? To do this, try pressing CTRL+ALT+F1 or CTRL+ALT+F2 when the system crashes. If it kicks you into the a login terminal, then you know the system has not hung-up. You can then login with your ordinary user name and kill the X Windows processes. You can then re-launch GDM. Type CTRL+F7 to go back to the GUI.
    ehsanulhaq likes this.

  4. #4
    Just Joined!
    Join Date
    Jan 2008
    Posts
    28
    Thanks for taking time to reply. I have recently bought this Intel i3 system with single 4 GB memory chip on Intel's DH61WW mother board. I have not yet installed any external graphics card. Can you elaborate a bit more as how can I find out whether it is memory or graphics related issue? Does any log file created whenever my system crash?

  5. #5
    Just Joined!
    Join Date
    Jun 2004
    Location
    North Hollywood, CA
    Posts
    22
    As to the graphics, look and see what driver you are using. Linux video drivers have traditionally been a pain. Check in you /var/log/messages to see what errors are occurring. And as stated by ramin.honary, see if you can get to a second terminal window to see what the error was in the first window. Something has to be in a log file. That's the great thing about Linux, unlike Windows, something is going to get reported. It's a matter of finding the error and then figuring out what was the cause. Also, make sure of what is running. Do a ps -ef and see if there are things running you don't need. If you're not using bluetooth, disable it. Same with any other services and apps that are running. But only make one change at a time so you know how to fix what you just did, or that you just found your issue.

  6. #6
    Just Joined!
    Join Date
    Jan 2008
    Posts
    28
    My system crashed again few minutes ago. This time it happend when I started Audio chat with a friend. Following are the last few messages from /var/log/messages. Any idea what is causing my system to crash again and again?




    Apr 26 15:52:52 EhsanUlHaq dnsmasq[2013]: started, version 2.52 cachesize 150
    Apr 26 15:52:52 EhsanUlHaq dnsmasq[2013]: compile time options: IPv6 GNU-getopt DBus no-I18N DHCP TFTP
    Apr 26 15:52:52 EhsanUlHaq dnsmasq-dhcp[2013]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
    Apr 26 15:52:52 EhsanUlHaq dnsmasq[2013]: reading /etc/resolv.conf
    Apr 26 15:52:52 EhsanUlHaq dnsmasq[2013]: using nameserver 192.168.1.1#53
    Apr 26 15:52:52 EhsanUlHaq dnsmasq[2013]: read /etc/hosts - 2 addresses
    Apr 26 15:52:53 EhsanUlHaq kernel: [ 42.611394] Ebtables v2.0 registered
    Apr 26 15:52:59 EhsanUlHaq libvirtd: 15:52:59.009: warning : qemudStartup:1832 : Unable to create cgroup for driver: No such device or address
    Apr 26 15:53:00 EhsanUlHaq libvirtd: 15:53:00.172: warning : lxcStartup:1895 : Unable to create cgroup for driver: No such device or address
    Apr 26 15:53:02 EhsanUlHaq rtkit-daemon[2192]: Successfully made thread 2190 of process 2190 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11.
    Apr 26 15:53:02 EhsanUlHaq rtkit-daemon[2192]: Successfully made thread 2205 of process 2190 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
    Apr 26 15:53:02 EhsanUlHaq rtkit-daemon[2192]: Successfully made thread 2206 of process 2190 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
    Apr 26 15:53:03 EhsanUlHaq gdm-simple-greeter[2159]: Gtk-WARNING: gtkwidget.c:5691: widget not within a GtkWindow
    Apr 26 15:53:04 EhsanUlHaq gdm-simple-greeter[2159]: WARNING: Unable to load CK history: no seat-id found
    Apr 26 15:53:07 EhsanUlHaq ntpd[1728]: 0.0.0.0 c016 06 restart
    Apr 26 15:53:07 EhsanUlHaq ntpd[1728]: 0.0.0.0 c012 02 freq_set kernel 18.277 PPM
    Apr 26 15:53:09 EhsanUlHaq ntpd[1728]: Listen normally on 6 virbr0 192.168.122.1 UDP 123
    Apr 26 15:53:15 EhsanUlHaq kernel: [ 64.905730] fuse init (API version 7.14)
    Apr 26 15:53:17 EhsanUlHaq rtkit-daemon[2192]: Successfully made thread 2359 of process 2359 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
    Apr 26 15:53:18 EhsanUlHaq pulseaudio[2359]: pid.c: Stale PID file, overwriting.
    Apr 26 15:53:18 EhsanUlHaq rtkit-daemon[2192]: Successfully made thread 2388 of process 2359 (/usr/bin/pulseaudio) owned by '500' RT at priority 5.
    Apr 26 15:53:18 EhsanUlHaq rtkit-daemon[2192]: Successfully made thread 2389 of process 2359 (/usr/bin/pulseaudio) owned by '500' RT at priority 5.
    Apr 26 15:53:19 EhsanUlHaq pulseaudio[2359]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.DBus.Error.Spawn.ChildExited
    Apr 26 15:53:19 EhsanUlHaq rtkit-daemon[2192]: Successfully made thread 2502 of process 2502 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
    Apr 26 15:53:19 EhsanUlHaq pulseaudio[2502]: pid.c: Daemon already running.
    Apr 26 15:53:19 EhsanUlHaq rtkit-daemon[2192]: Successfully made thread 2503 of process 2503 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
    Apr 26 15:53:19 EhsanUlHaq pulseaudio[2503]: pid.c: Daemon already running.
    Apr 26 15:53:21 EhsanUlHaq rtkit-daemon[2192]: Successfully made thread 2602 of process 2602 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
    Apr 26 15:53:21 EhsanUlHaq pulseaudio[2602]: pid.c: Daemon already running.
    Apr 26 15:53:35 EhsanUlHaq hp-systray: hp-systray[2600]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
    Apr 26 15:53:36 EhsanUlHaq dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.58" (uid=500 pid=2346 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.19" (uid=0 pid=2047 comm="/usr/sbin/console-kit-daemon))
    Edit/Delete Message

  7. #7
    Linux User Krendoshazin's Avatar
    Join Date
    Feb 2005
    Location
    London, England
    Posts
    471
    There could be a lot of things causing your system to crash. I would start at the bottom and work your way from the ground up:

    1. run memtest86 and test your CPU and RAM for any problems. You can burn an ISO of this which is available from www.memtest86.com
    2. use smartctl from smartmontools to assess the health of the hard drive and run tests on it.
    3. try a generic video driver, such as VESA, in order to see how stable the system is with it.
    4. try a different graphics card

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •