Find the answer to your Linux question:
Results 1 to 4 of 4
Hello everyone Fedora 11 is constantly freezing after a few minutes up. I run memtest but couldn't complete the test becuase the machine keeps freezing during the test. All fans ...
  1. #1
    Linux User
    Join Date
    Jul 2007
    Location
    Greece
    Posts
    277

    Fedora 11 freezes

    Hello everyone

    Fedora 11 is constantly freezing after a few minutes up. I run memtest but couldn't complete the test becuase the machine keeps freezing during the test. All fans are working and the CPU's temperature is normal (around 49C), so I don't think it overheats or something. I really don't know what is happening.

    I tailed the messages log:
    Code:
    tail -f /var/log/messages
    and waited for the machine to freeze again. A second before it froze I got the following message in the log.

    avahi-daemon[1498]: Invalid response packet from host 10.0.0.78

    Does anyone have any ideas/tips? Any suggestions please?

    Many thanks
    One Love!!!

  2. #2
    Linux User
    Join Date
    Jul 2007
    Location
    Greece
    Posts
    277
    I have now change the graphics card to a different bus on the motherboard. The machine hasn't hang yet. It seems to be working however I get the following in var/log/messages:

    Jul 8 12:13:50 sys15 kernel: set_rtc_mmss: can't update from 55 to 8
    Jul 8 12:13:51 sys15 kernel: set_rtc_mmss: can't update from 56 to 9
    Jul 8 12:13:52 sys15 kernel: set_rtc_mmss: can't update from 57 to 10
    Jul 8 12:13:53 sys15 kernel: set_rtc_mmss: can't update from 58 to 12
    Jul 8 12:13:54 sys15 kernel: set_rtc_mmss: can't update from 59 to 13
    Jul 8 12:13:54 sys15 acpid: client 2033[0:0] has disconnected
    Jul 8 12:13:54 sys15 acpid: client connected from 2033[0:0]
    Jul 8 12:13:54 sys15 acpid: 1 client rule loaded
    Jul 8 12:13:55 sys15 kernel: set_rtc_mmss: can't update from 59 to 13
    Jul 8 12:13:56 sys15 kernel: set_rtc_mmss: can't update from 59 to 13
    Jul 8 12:13:57 sys15 kernel: set_rtc_mmss: can't update from 59 to 13
    Jul 8 12:13:58 sys15 kernel: set_rtc_mmss: can't update from 59 to 13
    Jul 8 12:13:59 sys15 kernel: set_rtc_mmss: can't update from 59 to 13
    Jul 8 12:14:04 sys15 pulseaudio[2355]: pid.c: Stale PID file, overwriting.
    Jul 8 12:14:05 sys15 dbus-daemon: Rejected send message, 2 matched rules; type="method_call", sender=":1.31" (uid=42 pid=2355 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="org.bluez.Manager" member="ListAdapters" error name="(unset)" requested_reply=0 destination="org.bluez" (uid=0 pid=1819 comm="/usr/sbin/bluetoothd "))
    Jul 8 12:14:05 sys15 pulseaudio[2355]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.DBus.Error.AccessDenied
    Jul 8 12:14:23 sys15 pulseaudio[2699]: module-alsa-card.c: Card '0' doesn't exist: Permission denied
    Jul 8 12:14:23 sys15 pulseaudio[2699]: module.c: Failed to load module "module-alsa-card" (argument: "device_id=0 name=pci_10de_59_sound_card_0 card_name=alsa_card.pci_10de_59_sound_card_0 tsched=0"): initialization failed.
    Jul 8 12:14:43 sys15 pulseaudio[2781]: pid.c: Daemon already running.
    Jul 8 12:14:44 sys15 kernel: fuse init (API version 7.11)
    Jul 8 12:15:00 sys15 acpid: client 2033[0:0] has disconnected
    Jul 8 12:15:00 sys15 acpid: client connected from 2033[0:0]
    Jul 8 12:15:00 sys15 acpid: 1 client rule loaded
    Jul 8 12:16:34 sys15 kernel: npviewer.bin[3276]: segfault at ff99cd48 ip 00000000ff99cd48 sp 00000000fffec63c error 14
    Jul 8 12:17:05 sys15 avahi-daemon[1552]: Invalid query packet.
    Jul 8 12:17:06 sys15 avahi-daemon[1552]: Invalid query packet.
    Jul 8 12:17:06 sys15 avahi-daemon[1552]: Invalid query packet.


    It seems to be working now but the log above doesn't look healthy.
    One Love!!!

  3. #3
    Just Joined!
    Join Date
    Jul 2010
    Posts
    2
    the set_rtc_mmss section is telling you that it is trying to update the cmos time ... but it goes away later in the boot process.

    the avahi-daemon though.... could be improperly configured dhcp settings? or perhaps dns settings?

  4. #4
    Linux User
    Join Date
    Jul 2007
    Location
    Greece
    Posts
    277
    Sorry for my late reply. First of all thanks for your reply.

    After a lot of fiddling around, I noticed that with a different graphics card onboard the machine works fine. Don't know why and there was nothing in the log file about it.
    Weird?
    One Love!!!

Posting Permissions

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