Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Complete Lock Up, where to start?

  1. #1
    Join Date
    Feb 2011
    Beans
    391

    Complete Lock Up, where to start?

    I had something odd happen yesterday and its the second time its happened to me, I figured the first time was a fluke, both times it's occurred I was using Gnome shell. Basically the system completely freezes up no keyboard to touch pad no nothing, basically I end up having to force a power down and restart by holding down the power key.

    Where do I begin to trouble shoot this issue, what log files should I take a peek at? I really don't even know where to begin with this one.

    I feel I should mention this as it could be related every once in a while I'll get a blank screen, or my open windows will reload, again this only seems to happen while using Gnome shell. It's as if it gets confused as to what it supposed to be displaying but then quickly figures it out puts everything right.
    What I'm dealin' with:
    HP Pavilion G6-1D60US, dual booted: Ubuntu 14.04 64bit, & Windows 7 Home Premium 64bit, 640 gig HDD, 4 gig RAM

  2. #2
    Join Date
    Jul 2011
    Beans
    3,037
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Complete Lock Up, where to start?

    Here is a list of the available log files:

    https://help.ubuntu.com/community/LinuxLogFiles

    You should start with systemlog, Xorg.0.log.

  3. #3
    Join Date
    Feb 2011
    Beans
    391

    Re: Complete Lock Up, where to start?

    Ok I dug through the logs a bit but didn't find anything, I need a little more help on what to look for? I've been using unity lately and it's been flawless so I think the issue has something to do with gnome shell.

    I doing a thread in desktop environments that seemed like a similar issue, without the screen blanking and window reloading. Their issue was solved by turning off "disable touch pad while typing", I'll give that a whirl tonight, but that is a feature I actually use so it's not really a great fix for me.

    Any help with this is appreciated.
    What I'm dealin' with:
    HP Pavilion G6-1D60US, dual booted: Ubuntu 14.04 64bit, & Windows 7 Home Premium 64bit, 640 gig HDD, 4 gig RAM

  4. #4
    Join Date
    May 2008
    Location
    UK
    Beans
    1,450
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Complete Lock Up, where to start?

    The "disable touchpad when typing" setting is not as bad as you think - you can still use the touch pad - it just stops you inadvertantly "tap clicking" or "cursor moving" while you are actually typing on the keyboard. Stop typing for a second (well less than that), and you can use the touchpad.
    Tony - Happy to try to help.
    Unless otherwise stated - all code posted by me is untested. Remember to Mark the Thread as Solved.
    Ubuntu user number # 24044 Projects : TimeWarp - on the fly Backups

  5. #5
    Join Date
    Nov 2008
    Beans
    Hidden!

    Re: Complete Lock Up, where to start?

    I wonder if the package "lightdm" is giving you trouble.

    https://wiki.ubuntu.com/LightDM

  6. #6
    Join Date
    Feb 2011
    Beans
    391

    Re: Complete Lock Up, where to start?

    Quote Originally Posted by Tony Flury View Post
    The "disable touchpad when typing" setting is not as bad as you think - you can still use the touch pad - it just stops you inadvertantly "tap clicking" or "cursor moving" while you are actually typing on the keyboard. Stop typing for a second (well less than that), and you can use the touchpad.
    Sorry I may not have explained myself right. I'm a chronic tap clicker/courser mover so I need to use the disable touchpad. The other thread suggested disabling it as a fix to a similar issue.
    What I'm dealin' with:
    HP Pavilion G6-1D60US, dual booted: Ubuntu 14.04 64bit, & Windows 7 Home Premium 64bit, 640 gig HDD, 4 gig RAM

  7. #7
    Join Date
    Feb 2011
    Beans
    391

    Re: Complete Lock Up, where to start?

    Quote Originally Posted by jerrrys View Post
    I wonder if the package "lightdm" is giving you trouble.

    https://wiki.ubuntu.com/LightDM
    So how can or should I trouble shoot it? I read the wiki but there's no info on common issues. I could switch back to gdm but what issues will that cause.

    Being a rather random problem makes it hard to track down.
    What I'm dealin' with:
    HP Pavilion G6-1D60US, dual booted: Ubuntu 14.04 64bit, & Windows 7 Home Premium 64bit, 640 gig HDD, 4 gig RAM

  8. #8
    Join Date
    Feb 2009
    Beans
    36
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Complete Lock Up, where to start?

    You might try the skinny elephant trick. It is a way to regain control of a frozen system.

    look at step 5 of this post:
    http://lxtips.posterous.com/recover-...ystem-with-alt


    Sometimes you can also get to a virtual terminal by pressing ctrl-alt-F1 and then using ps or top to kill the offending process(es), and then pressing ctrl-alt-F7 to get back to your desktop. maybe this trick will let you see what process is causing the problem.
    Last edited by bronquel; March 8th, 2012 at 09:43 PM.

  9. #9
    Join Date
    Jan 2007
    Location
    the outer rim
    Beans
    367
    Distro
    Kubuntu 12.04 Precise Pangolin

    Re: Complete Lock Up, where to start?

    Are any of the lights flashing on the machine? This usually indicates "kernel panic". The most common cause I've seen with Linux is graphics driver issues. try turning of the desktop effects.
    Also if you can do: Ctrl+Alt+F1
    and it drops to tty1 then that means X is crashing (also gpu related) not kernel panic.
    What is the make and model??
    illegitimi non carborundum

  10. #10
    Join Date
    Feb 2012
    Beans
    121
    Distro
    Lubuntu 11.10 Oneiric Ocelot

    Re: Complete Lock Up, where to start?

    Quote Originally Posted by bronquel View Post
    You might try the skinny elephant trick. It is a way to regain control of a frozen system.

    look at step 5 of this post:
    http://lxtips.posterous.com/recover-...ystem-with-alt


    Sometimes you can also get to a virtual terminal by pressing ctrl-alt-F1 and then using ps or top to kill the offending process(es), and then pressing ctrl-alt-F7 to get back to your desktop. maybe this trick will let you see what process is causing the problem.
    I wish I would have seen this a while ago, I was having this issue recurring on a old load of Ubuntu 11.10. Eventually I have had to reload (due to other reasons) and it has not resurfaced yet. This will be very useful if I run into it again.

Page 1 of 2 12 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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