Announcement

Collapse
No announcement yet.

Input freezing and/or crashing

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    What version of KDE are you using?
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #32
      I am using KDE 4.13.3

      Comment


        #33
        Originally posted by azwli View Post
        I spoke too soon. I was just working with GIMP and it froze up again. I actually wonder if GIMP may be the problem as this is the first time I have used it for anything extensively all week.
        I do not think it is a software specific issue. It happens randomly. In my case I have experinced it while in system settins doing configuration or while playing card game Aiselriot, etc.

        Comment


          #34
          What is the chance this is a hardware issue? I am back to crashing several times a day. I have run Memory tests with no results. Could it be the HDD freezing up or the motherboard going bad? I have some other problems with the system. I have discovered that a couple of the USB ports are not functioning properly and for some reason it won't boot from a live disk any more. Should I just start looking for a new machine?

          Comment


            #35
            In my case, I do not think it is hardware related. Because It never occurs in Windows. Also, for USB, you need to set the order of booting media in the system set-up (BIOS).

            Comment


              #36
              The most recent description of your issue indicates the motherboard is having problems.
              Multiple interfaces on it are showing signs.

              If you have spare parts try another power supply to see if it helps or confirms the mb.
              Kubuntu 18.04 on AMD

              Comment


                #37
                The system just crashed again and this time it went to a black screen. After a minute or so I got this message:

                INFO: rcu_sched detected stalls on CPUs/task {1} (detected by 0, t=15002 jiffies, g=484436, c=484435, q=9)

                I googled it and read the kernel doc page, but I didn't really understand it. It seems like that could be caused by either hardware or software.

                I am suspecting the MB also. I don't have another power supply to charge, how does that test the MB?

                I am on a search for a replacement computer. Wasn't expecting the expense at this time

                Comment


                  #38
                  I looked in the system log for the exact time of the last crash and this is all that was there:

                  09/18/14 01:03:31 PM ********* whoopsie[1222] message repeated 3560 times: [ online]

                  Comment


                    #39
                    I was thinking more in terms of a desktop there... as far as a power supply. Sorry a bit misleading.
                    However to further test the board try all the ports one at a time, then multiple ports at a time.
                    Different devices if possible as in: ones that use an additional power plug vs not.

                    Also while this can make it worse or completely finish the problem if you will... sometimes picking it up and bending a corner slightly may give additional indication if you see odd behaviors when "gently bending". Please use caution with this suggestion.
                    Kubuntu 18.04 on AMD

                    Comment


                      #40
                      Hi,

                      I am experiencing the same problems. After upgrading from 12.04 which worked perfect for me, 14.04, screen freezes and no reaction to input (mouse or keyborad). Sometimes the systems goes to new login screen, sometimes the systems hangs completely. This happens irregularly without any connection to resources demanding processes. Login from a other machine via ssh is still possible, but the original login-process seems to have been killed.

                      I'm using an older Fujitsi Siemes Lifebook with 8 GB RAM and a 256GB SSD.
                      The system is a Linux 3.2.0-29-generic-pae #46-Ubuntu on a i686 machine.

                      Comment


                        #41
                        I just inspected the systemlog after the last crash. These should be the last entries before I pushed the power-button. Any idea where it comes from?

                        01.10.2014 16:26:13 * acpid client 1296[0:0] has disconnected
                        01.10.2014 16:26:13 * acpid client connected from 4310[0:0]
                        01.10.2014 16:26:13 * acpid 1 client rule loaded
                        01.10.2014 16:26:13 * kernel [20248.491415] [drm:i915_gem_execbuffer2] *ERROR* copy 1 exec entries failed 56
                        01.10.2014 16:26:13 * kernel [20248.542155] soffice.bin[4198]: segfault at 4f364820 ip b43be090 sp bfb8ba50 error 4 in libc-2.19.so[b438b000+1a9000]
                        01.10.2014 16:26:13 * bluetoothd[549] Endpoint unregistered: sender=:1.47 path=/MediaEndpoint/HFPAG
                        01.10.2014 16:26:13 * bluetoothd[549] Endpoint unregistered: sender=:1.47 path=/MediaEndpoint/HFPHS
                        01.10.2014 16:26:13 * bluetoothd[549] Endpoint unregistered: sender=:1.47 path=/MediaEndpoint/A2DPSource
                        01.10.2014 16:26:13 * bluetoothd[549] Endpoint unregistered: sender=:1.47 path=/MediaEndpoint/A2DPSink
                        01.10.2014 16:26:14 * colord Automatic remove of icc-ab5a2fec685608b78b97c35ca144bad3 from xrandr-E24W-1SD-YE5V000244
                        01.10.2014 16:26:14 * colord Profile removed: icc-ab5a2fec685608b78b97c35ca144bad3
                        01.10.2014 16:26:14 * colord device removed: xrandr-LVDS1
                        01.10.2014 16:26:14 * colord device removed: xrandr-E24W-1SD-YE5V000244
                        01.10.2014 16:26:35 * rsyslogd [origin software="rsyslogd" swVersion="7.4.4" x-pid="658" x-info="http://www.rsyslog.com"] exiting on signal 15.

                        Comment


                          #42
                          After re-reading all the posts and problems I would be surprised if it turned out to be a hardware problem, especially since 12.04 ran nicely without problems and the problems began with the installation of 14.04. It suggests a couple of things.

                          First, the original install of 14.04 was from a defective ISO file or burned CD. This would suggest a fresh dl of the latest ISO (to avoid unnecessary updates), verification of both the ISO and the CD or USB stick that it is burned onto, and then a fresh install.

                          Or, secondly, the "drm:i915_gem_execbuffer2" suggests that you are having kernel a/o kernel object problems, i.e, i915 video driver problems. Are you using nouveau? Have you tried reverting to a previous kernel a/o i915 ko?
                          Last edited by GreyGeek; Oct 01, 2014, 10:26 AM.
                          "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                          – John F. Kennedy, February 26, 1962.

                          Comment


                            #43
                            Originally posted by GreyGeek View Post
                            After re-reading all the posts and problems I would be surprised if it turned out to be a hardware problem, especially since 12.04 ran nicely without problems and the problems began with the installation of 14.04. It suggests a couple of things.

                            First, the original install of 14.04 was from a defective ISO file or burned CD. This would suggest a fresh dl of the latest ISO (to avoid unnecessary updates), verification of both the ISO and the CD or USB stick that it is burned onto, and then a fresh install.

                            Or, secondly, the "drm:i915_gem_execbuffer2" suggests that you are having kernel a/o kernel object problems, i.e, i915 video driver problems. Are you using nouveau? Have you tried reverting to a previous kernel a/o i915 ko?
                            Hi, thanks for your suggestions. It's a GM965 gpu and I'm using the

                            /lib/modules/3.2.0-29-generic-pae/kernel/drivers/gpu/drm/i915/i915.ko

                            I'm trying now to use "uxa" acceleration in the /etc/X11/xorg.conf according http://wiki.ubuntuusers.de/Grafikkarten/Intel (German site).

                            Will see if it helps.

                            Comment


                              #44
                              Originally posted by thomas-r View Post
                              ...

                              I'm trying now to use "uxa" acceleration in the /etc/X11/xorg.conf according http://wiki.ubuntuusers.de/Grafikkarten/Intel (German site).

                              Will see if it helps.
                              I use the same driver, i915, and shortly after I installed 14.04 I had to switch to "UXA" to smooth out my video performance. I was having tearing, blockiness and other problems, including the occasional hang or crash.
                              "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                              – John F. Kennedy, February 26, 1962.

                              Comment


                                #45
                                I was convinced that it is a hardware issue when I experienced a crash while running from the live disk. But now that you mention it I was running from the same disk that I used to install from, so....

                                The parts for my new computer are arriving in the next couple days. I may have been able to make this one last a bit longer by following your suggestions, but it is a pretty old system. I will be sure to burn a new live disk before I install on the new device.

                                Comment

                                Working...
                                X