Announcement

Collapse
No announcement yet.

kubuntu 9.04 Jaunty Jackalope randomly hungs

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

    kubuntu 9.04 Jaunty Jackalope randomly hungs

    Some days ago, it appeared the new version of kubunto. I unloaded
    the image iso by bitorrent and installed the system.

    The new version is faster and kde 4 seems work well. But I have a
    serious problem, which I do not know if it is bug or an
    installation error: the system randomly hangs and until now I
    have not identified a constant pattern. The mouse follows
    operative, but the desktop does not recognize any input; neither
    by mouse nor by the keyboard. The hard disk led shows activity;
    the ethernet led too, but I cannot ping from another machine. The
    gkrellm system monitor is frozen. The unique way to "recover" is
    to turn off the machine and to turn on it again.

    Many times it hangs very earlier, just five minutes after reboot.
    In fact, it is very exasperating and frustrating.

    Also I have problems with the wifi, but this is less serious.

    I verified the signatures of the iso in order to be sure of to
    have a correct distribution.

    My hardware is a laptop lenovo T61, 2 Gb ram, 250 Gb hd and an
    intel graphical card.

    Some information? Any help?

    Thanks in advance for any help.


    Leandro Leon

    #2
    Re: kubuntu 9.04 Jaunty Jackalope randomly hungs

    Time to check the logs. They are located in /var/log/ - of particular interest are Xorg.log and errors.log. Make a note of the time of the lockup and see whether there are any error messages (and post them )
    Once your problem is solved please mark the topic of the first post as SOLVED so others know and can benefit from your experience! / FAQ

    Comment


      #3
      Re: kubuntu 9.04 Jaunty Jackalope randomly hungs

      Thank very much to Toad by his suggestion.

      I already have reviewed the logs that there are in /var/log.

      It does not exist (still?) a log named "error" and Xorg.log seems
      ok. These files do not contain a line with the word "error".

      So I did grep - n [Eerror] *log messages boot btmp | less

      Essentially, there are two types of errors that I judge of
      interest and which I place them for your revision:

      1-. In auth.log:

      Apr 26 10:13:32 platon dbus-daemon: Rejected send message, 4 matched rules; type="error", sender=":1.11" (uid=0 pid=3457 comm="/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant") interface="(unset)" member="(unset)" error name="fi.epitest.hostap.WPASupplicant.InvalidInter face" requested_reply=0 destination=":1.8" (uid=0 pid=3447 comm="/usr/sbin/NetworkManager --pid-file /var/run/Netwo"))

      I do not believe that this error has relation with the one that
      causes the hang, since I have booted the machine with the switch
      of wifi turned off and even so the error happens. I present
      anyway because it appears too many times.


      2. In messages: here I present several instances, because perhaps
      it is a constant pattern that I note before the machine hangs:


      a:

      Apr 30 10:42:25 platon kernel: [ 368.834380] nepomukservices[3955]: segfault at 8999ffc ip b6a5431d sp bfb67228 error 4 in libc-2.9.so[b69db000+15c000]
      Apr 30 10:56:49 platon -- MARK --
      Apr 30 11:16:49 platon -- MARK --
      Apr 30 11:36:49 platon -- MARK --
      Apr 30 11:56:49 platon -- MARK --
      Apr 30 12:13:11 platon syslogd 1.5.0#5ubuntu3: restart.

      b:

      Apr 30 10:24:47 platon kernel: [ 81.583684] nepomukservices[3875]: segfault at 8378ffc ip b692931d sp bfb39a38 error 4 in libc-2.9.so[b68b0000+15c000]
      Apr 30 10:26:33 platon kernel: [ 187.144124] CE: hpet increasing min_delta_ns to 15000 nsec
      Apr 30 10:36:50 platon syslogd 1.5.0#5ubuntu3: restart.

      c:

      Apr 30 08:39:55 platon kernel: [ 87.716160] nepomukservices[3887]: segfault at 4 ip b7d12a02 sp bf83ce30 error 4 in libQtCore.so.4.5.0[b7cbf000+238000]
      Apr 30 08:39:57 platon kernel: [ 90.040850] nepomukservices[3875]: segfault at 9ee2ffc ip b699631d sp bfca7558 error 4 in libc-2.9.so[b691d000+15c000]
      Apr 30 08:41:22 platon kernel: [ 175.240126] CE: hpet increasing min_delta_ns to 15000 nsec
      Apr 30 08:59:07 platon -- MARK --
      Apr 30 09:10:37 platon kernel: [ 1930.592575] CE: hpet increasing min_delta_ns to 22500 nsec
      Apr 30 09:14:48 platon syslogd 1.5.0#5ubuntu3: restart.

      d:

      Apr 29 15:45:00 platon kernel: [ 71.004085] nepomukservices[3693]: segfault at 97b6ffc ip b6a6a31d sp bfd781c8 error 4 in libc-2.9.so[b69f1000+15c000]
      Apr 29 15:58:24 platon kernel: [ 875.608104] CE: hpet increasing min_delta_ns to 15000 nsec
      Apr 29 16:24:25 platon -- MARK --
      Apr 29 16:44:25 platon -- MARK --
      Apr 29 17:04:25 platon -- MARK --
      Apr 29 17:16:11 platon kernel: [ 5542.176516] CE: hpet increasing min_delta_ns to 22500 nsec
      Apr 29 17:44:25 platon -- MARK --
      Apr 29 18:04:25 platon -- MARK --
      Apr 29 18:24:25 platon -- MARK --
      Apr 29 18:44:25 platon -- MARK --
      Apr 29 19:04:25 platon -- MARK --
      Apr 29 19:24:25 platon -- MARK --
      Apr 29 19:44:23 platon syslogd 1.5.0#5ubuntu3: restart.


      This pattern (nepomukservices ... segfault and soon restart)
      often appears. Apparently -I am almost sure- the line "restart"
      corresponds with the powering off and after powering on of the
      machine after it hangs; although I believe that it can correspond
      also with reboot or resume after hivernation.

      There is a line (only one) in which appears segfault without
      "restart".

      As I do not have the sufficient knowledge, I cannot say that
      there is a causal relation between the segfault and the hang, but
      I already took the precaution to deactivate the akonadi server
      from system settings. Until now, the machine has not hanged. I
      believe, however, that it is still premature to conclude any
      thing.

      I will maintain you informed about that happens. I let you this
      post in order to see if somebody finds an explanation and
      a possible correction.

      Thanks for everything,


      Leandro

      Comment


        #4
        Re: kubuntu 9.04 Jaunty Jackalope randomly hungs

        Thanks, Leandro. You may want to try and run memtest86 overnight and see how reliable your RAM is - a segmentation fault points that way. And the other thing to try right now is to switch off the nepomuk semantic desktop in system settings - advanced tab - desktop search.

        Let us know how you get on
        Once your problem is solved please mark the topic of the first post as SOLVED so others know and can benefit from your experience! / FAQ

        Comment


          #5
          Re: kubuntu 9.04 Jaunty Jackalope randomly hungs

          It doesn't hurt to test the RAM, bur segfaulting from one application is an application bug. I expect that if you don't run nepomuk you won't see this problem.

          Comment

          Working...
          X