FedoraForum.org - Fedora Support Forums and Community
Results 1 to 6 of 6
  1. #1
    Join Date
    Dec 2008
    Posts
    6

    Periodic, unpredictable freezes in Fedora 14

    I've got a Gateway NV52 laptop, dual boot with Windows 7 and Fedora 14. Everything works fine when I'm using Windows, but when using Fedora, everything seems to be working fine for hours, or days, until it isn't. The screen goes dark, and nothing works any more. The keyboard shortcuts to restart or shutdown do nothing, and using a different computer to either browse to a website hosted by this computer, or ssh into this computer both fail. It seems it is essentially dead, though still humming like nothing is wrong. The power button is the only way to turn it off at this point.

    I've been keeping track of the /var/log/messages file for the last several crashes, and everything is always the same for at least the last 50 messages. Obviously, the date/time are always different, and the last line isn't always there. It is the last message about 1/2 the time, but the previous messages are the same whether it is or not.

    Thank you very much for any help you can give me. I appreciate it


    ------------------------------------------------- /var/log/messages ---------------------------------------------------

    ...
    ...
    ...
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0/wireless): access point 'Auto Cisco01990' has security, but secrets are required.
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0/wireless): connection 'Auto Cisco01990' has security, and secrets exist. No new secrets needed.
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Config: added 'ssid' value 'Cisco01990'
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Config: added 'scan_ssid' value '1'
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Config: added 'psk' value '<omitted>'
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> Config: set interface ap_scan to 1
    Nov 28 01:54:15 boomer NetworkManager[1368]: <info> (wlan0): supplicant connection state: inactive -> scanning
    Nov 28 01:54:16 boomer NetworkManager[1368]: <info> (wlan0): supplicant connection state: scanning -> associating
    Nov 28 01:54:16 boomer kernel: [ 72.355170] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Nov 28 01:54:16 boomer NetworkManager[1368]: <info> (wlan0): supplicant connection state: associating -> associated
    Nov 28 01:54:16 boomer NetworkManager[1368]: <info> (wlan0): supplicant connection state: associated -> 4-way handshake
    Nov 28 01:54:18 boomer avahi-daemon[1388]: Registering new address record for fe80::721a:4ff:fe11:f8b5 on wlan0.*.
    Nov 28 01:54:18 boomer kernel: [ 74.334642] Intel AES-NI instructions are not detected.
    Nov 28 01:54:19 boomer kernel: [ 74.465599] padlock: VIA PadLock not detected.
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> (wlan0): supplicant connection state: 4-way handshake -> group handshake
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Cisco01990'.
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> (wlan0): device state change: 5 -> 7 (reason 0)
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
    Nov 28 01:54:19 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
    Nov 28 01:54:19 boomer avahi-daemon[1388]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.42.
    Nov 28 01:54:19 boomer avahi-daemon[1388]: New relevant interface wlan0.IPv4 for mDNS.
    Nov 28 01:54:19 boomer avahi-daemon[1388]: Registering new address record for 192.168.1.42 on wlan0.IPv4.
    Nov 28 01:54:20 boomer NetworkManager[1368]: <info> (wlan0): device state change: 7 -> 8 (reason 0)
    Nov 28 01:54:20 boomer NetworkManager[1368]: <info> Policy set 'Auto Cisco01990' (wlan0) as default for IPv4 routing and DNS.
    Nov 28 01:54:20 boomer NetworkManager[1368]: <info> Updating /etc/hosts with new system hostname
    Nov 28 01:54:21 boomer NetworkManager[1368]: <info> Activation (wlan0) successful, device activated.
    Nov 28 01:54:21 boomer NetworkManager[1368]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
    Nov 28 01:54:21 boomer nm-dispatcher.action: nm_dispatcher_action: Invalid connection: '(null)' / 'connection setting not found' invalid: 1
    Nov 28 01:54:21 boomer dbus: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.55" (uid=500 pid=2070 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.16" (uid=0 pid=1774 comm="/usr/sbin/console-kit-daemon))

  2. #2
    Join Date
    Mar 2009
    Location
    Norway
    Posts
    133

    Re: Periodic, unpredictable freezes in Fedora 14

    Me too

    Check this
    ---------------
    Dec 11 22:49:47 64bit pulseaudio[2032]: ratelimit.c: 155 events suppressed
    Dec 11 22:51:36 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 22:51:36 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 22:55:07 64bit pulseaudio[2032]: ratelimit.c: 73 events suppressed
    Dec 11 22:55:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 22:55:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 22:57:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 22:57:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 22:59:36 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 22:59:36 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 23:03:36 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 23:03:36 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 23:10:36 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 23:10:36 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 23:15:38 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 23:15:38 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 23:21:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 23:21:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 23:23:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 23:23:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 23:25:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 23:25:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 23:27:36 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 23:27:36 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 23:27:55 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 23:27:55 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 23:29:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 23:29:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 23:31:36 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: completed -> group handshake
    Dec 11 23:31:37 64bit NetworkManager[1274]: <info> (wlan0): supplicant connection state: group handshake -> completed
    Dec 11 23:36:06 64bit kernel: imklog 4.6.3, log source = /proc/kmsg started.
    ------------------------------

    The last line is after reboot.

  3. #3
    Join Date
    Dec 2008
    Posts
    6

    Re: Periodic, unpredictable freezes in Fedora 14

    Sorry, Mauser's reply made me think of something that I hadn't before. I think that what I had assumed were the last messages before crashing, were actually the first messages after a new startup . I no longer think that any of the messages that I posted are in any way relevant to the issue.

    Could someone advise me on how to get more useful info?

  4. #4
    Join Date
    Oct 2008
    Location
    Ol' US of A
    Posts
    74

    Re: Periodic, unpredictable freezes in Fedora 14

    Benr242,

    Do you still see this problem? Maybe you can try ssh from another
    machine, and then run 'top' and 'tail -f /var/log/messages' (in
    separate ssh sessions or using 'screen'), so you can see the last
    activities of your NV52 before you lose network connectivity? How
    about the content of dmesg? As root run this
    while true; do dmesg -c >> dmesg.txt; sleep 1; done
    After rebooting your NV52 from its hung state, you can examine
    dmesg.txt to see the last words from kernel, if any. You can also run
    while true; do date > date.txt; sleep 1; done
    So you know at what time your F14 is hung.

    > The screen goes dark, and nothing works any more.
    Are you using screen saver of any kind? If you turn off screen saver,
    does it still hang?

    Cheers,
    Tim Taiwanese Liim

  5. #5
    Join Date
    Dec 2008
    Posts
    6

    Re: Periodic, unpredictable freezes in Fedora 14

    Thank you very much for your reply, Tim. I appreciate it.

    Fortunately for me, my problem seems to have gone away. I didn't do anything to instigate that, tho, so it seems like regular updates fixed itself. It's been several weeks since that problem has occurred for me!

    I hadn't thought of your idea of tailing dmes or /var/log/messages from a different computer, but I will certainly do that if my problem recurs. Great idea... thanks!

  6. #6
    Join Date
    Oct 2008
    Location
    Ol' US of A
    Posts
    74

    Re: Periodic, unpredictable freezes in Fedora 14

    You are very welcome! Glad that your problem no longer shows up.

Similar Threads

  1. Replies: 2
    Last Post: 25th January 2010, 07:02 PM
  2. Fedora 7 periodic internet connection problem
    By danni_kremer in forum Servers & Networking
    Replies: 3
    Last Post: 21st August 2007, 02:32 AM
  3. Unpredictable startup of IBM Blade HS20 on FC4
    By tonyredink in forum Servers & Networking
    Replies: 0
    Last Post: 4th January 2006, 03:03 AM

Tags for this Thread

Posting Permissions

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