Bug 759957

Summary: computer randomly freezes
Product: [Fedora] Fedora Reporter: Sam Irlapati <irlapati>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: collura, dennis, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-01 16:06:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
var log messages from near one of freezes none

Description Sam Irlapati 2011-12-05 01:39:41 UTC
Description of problem :Computer randomly freezes. The keyboard and mouse will not respond. The clock on the screen stops.


Version-Release number of selected component (if applicable):
Fedora 16


How reproducible:
Happens all the time.


Steps to Reproduce:
1. boot computer and wait
2.
3.
  
Actual results:
Computer freezes


Expected results:
No computer freeze


Additional info:
The time of the previous reboot was 16:45:05. When the computer froze, the time of the clock on the screen was 17:26:27. So it stayed up for about 41 minutes. I was not doing anything on the computer. The last things in /var/log/messages was 
Dec  4 17:24:51 Salem kernel: [ 2441.316077] cfg80211: Calling CRDA for country: US
Dec  4 17:24:51 Salem NetworkManager[1072]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec  4 17:24:51 Salem NetworkManager[1072]: NetworkManager[1072]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec  4 17:24:52 Salem NetworkManager[1072]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec  4 17:24:52 Salem NetworkManager[1072]: NetworkManager[1072]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec  4 17:24:52 Salem NetworkManager[1072]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec  4 17:24:52 Salem NetworkManager[1072]: NetworkManager[1072]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec  4 17:24:52 Salem NetworkManager[1072]: <info> (wlan0): supplicant interface state: associating -> completed
Dec  4 17:24:52 Salem NetworkManager[1072]: NetworkManager[1072]: <info> (wlan0): supplicant interface state: associating -> completed
Dec  4 17:25:23 Salem kernel: [ 2473.304064] cfg80211: Calling CRDA to update world regulatory domain
Dec  4 17:25:23 Salem NetworkManager[1072]: <info> (wlan0): supplicant interface state: completed -> disconnected
Dec  4 17:25:23 Salem NetworkManager[1072]: NetworkManager[1072]: <info> (wlan0): supplicant interface state: completed -> disconnected
Dec  4 17:25:23 Salem kernel: [ 2473.315994] cfg80211: World regulatory domain updated:
Dec  4 17:25:23 Salem kernel: [ 2473.316090] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec  4 17:25:23 Salem kernel: [ 2473.316099] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 17:25:23 Salem kernel: [ 2473.316107] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec  4 17:25:23 Salem kernel: [ 2473.316115] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec  4 17:25:23 Salem kernel: [ 2473.316122] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 17:25:23 Salem kernel: [ 2473.316130] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 17:25:23 Salem kernel: [ 2473.316543] cfg80211: Calling CRDA for country: US
Dec  4 17:25:23 Salem NetworkManager[1072]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec  4 17:25:23 Salem NetworkManager[1072]: NetworkManager[1072]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec  4 17:25:24 Salem NetworkManager[1072]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec  4 17:25:24 Salem NetworkManager[1072]: NetworkManager[1072]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec  4 17:25:24 Salem NetworkManager[1072]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec  4 17:25:24 Salem NetworkManager[1072]: NetworkManager[1072]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec  4 17:25:24 Salem NetworkManager[1072]: <info> (wlan0): supplicant interface state: associating -> completed
Dec  4 17:25:24 Salem NetworkManager[1072]: NetworkManager[1072]: <info> (wlan0): supplicant interface state: associating -> completed

I am not sure if the messages are related or not.

Comment 1 Sam Irlapati 2011-12-06 14:36:15 UTC
I have tried logging in remotely and am unable to do it. So this not just a graphic issue. It could e maybe a powersave issue. I am just guessing. Is there anything else i can try?

Comment 2 collura 2011-12-08 10:14:30 UTC
Created attachment 542457 [details]
var log messages from near one of freezes

might not be related to this bug but same symptoms so for now adding to pile

Comment 3 collura 2011-12-08 10:30:31 UTC
i dont know cause but am having similar freezes.
for me think is busy with disk activity which might be one of the memory leak bugs floating around since system memory / paging memory seems to be on the high side sometimes.

seems to happen most from resuming from suspend but sometimes just while logged in and working.

one thing that i noticed is that in my case it seems to not occur with
  kernel-3.1.0-7.fc16 (x86_64)
but does seem to occur with 
  kernel-3.1.2-1.fc16 (x86_64)
  kernel-3.1.4-1.fc16 (x86_64)

similarly not sure if related but /var/log/mssages:

> 
> Dec  3 04:29:54 hostname kernel: [    5.660632] scsi 8:0:0:0: Direct-Access     Generic- Multi-Card       1.00 PQ:
 0 ANSI: 0 CCS
> Dec  3 04:29:54 hostname kernel: [    5.660942] scsi: killing requests for dead queue
> Dec  3 04:29:54 hostname kernel: [    5.661243] scsi: killing requests for dead queue
...
> Dec  3 04:29:54 hostname kernel: [    5.663563] sd 8:0:0:0: Attached scsi generic sg2 type 0
> Dec  3 04:29:54 hostname kernel: [    5.669472] sd 8:0:0:0: [sdb] Attached SCSI removable disk
> 

but the noteable part is that every few second/minute there is a group of these periodic errors: 

>
> Dec  3 04:30:58 hostname kernel: [  108.572533] sd 8:0:0:0: [sdb] Test WP failed, assume Write Enabled
> Dec  3 04:30:58 hostname kernel: [  108.575530] sd 8:0:0:0: [sdb] Asking for cache data failed
> Dec  3 04:30:58 hostname kernel: [  108.575539] sd 8:0:0:0: [sdb] Assuming drive cache: write through
>

there are so many of them that i wonder if that is part of the freeze.
its not that they just appear once at boot but rather they occur almost constantly.

related link: 
http://lists.us.dell.com/pipermail/linux-poweredge/2011-October/045467.html

wasnt able to get .xsession-errors last time but will try next time it happens.

Comment 4 Sam Irlapati 2011-12-19 01:21:37 UTC
Since updating the kernel to 3.1.5-2.fc16.x86_64 i have not been getting anymore of these freezes.

Comment 5 collura 2011-12-21 07:50:39 UTC
for me looks like a large part of freeze issue is the memory leak 
related to dynamic desktop background swapping on disk.

system seemed a lot more reliable without the dynamic background doh.

  https://bugzilla.redhat.com/show_bug.cgi?id=639732#c8
   "changing the background from the default dynamic version of it to a
    static background the leak has stopped"

think that nautilus and gdesklet leaks are smaller and not nearly as burdensome but still there for now.
 
improving :')