Kali Randomly Freezes

[UseLinux]

Before anyone says anything, yes, I have consulted the Google Gods. Nearly every search result was in regards to Kali freezing during the installation process, this is after installation.

I have 64bit Kali Linux installed on an Asus VivoBook Q200E, after some minor user-related installation issues, a new/fresh install went flawlessly.

The issue is pretty basic, it just randomly freezes/hangs, and I have to do a hard reset to get it working again. At first it seemed to be happening within 10 or so minutes after I logged in, so I just tailed pretty much every log in the /var/log directory, and waited for it to hang, thus (in theory) showing the a message in one of the log files related to whats causing it to hang, but then it never froze!

I thought maybe it had something to do with it going into idle, because the first couple times it happened, I was distracted and watching TV, thus it went without any movement for a little bit. So I booted it up, logged in, and let it go into idle multiple times... never hung.

I thought that maybe it happened when there was a specific process running, but after further troubleshooting, that has nothing to do with it.

Thinking that maybe it was just something running in the background that would hang it for a bit, and I would just have to be patient, I would wait for it to freeze, then wait a long while to see if it would come back, never did. (Longest I waited was it froze in the morning, I went to work, and it was still hung when I got back)

So basically... I just cant figure out whats causing it to hang. I can't find anything in any of the messages in /var/log/*, I installed SAR to see if it was related to resource usage, and its not.... And all though this is a little embarrassing to admit (Im a lvl2 Linux Engineer)... I don't even know where else to start looking. I do mostly code and server management/automation, I try to stay away from the desktop distros of Linux, so I don't have a terrible amount of troubleshooting when it comes to this kinda thing.

Any help or pointers would be greatly appreciated. Doesn't have to be a guess to an answer or anything, just even some tips on trying to diagnose it. If you want/need any log messages or anything to assist, just ask!

Thanks!

[soxrok2212]

Is it installed as a virtual machine or on your hard drive?

[UseLinux]

Its on the HDD, I used the entire disk, no dual boot.

[UseLinux]

Bump? Really starting to get annoying. I seriously would use this as my primary machine, but this random rebooting totally cripples its usage.

[charonsecurity]

It may be hardware related. I recommend running a barrage of tests on your system, starting off with the memory, afterwards check the drive for physical errors. Also, if you have any peripherals you may want to disconnect them to see if they are causing any trouble. It can be done from the command line, but I recommend to use a live CD/USB to do the test. Also, if you are not sure exactly the best way to go about doing these task, a very user friendly way of going about it is by making an Ultimate Boot CD, that has a bunch of great tools to do just that. http://www.ultimatebootcd.com/

I once had a situation like yours, and it ended up being a bad memory module.

[UseLinux]

I have UBCD burnt to a disk already, so ill give that a shot.

Keep in mind, this had Windows, then Mint, then BackTrack, then Kali installed on it, all worked fine, except for Kali

[uwnthesis]

Bump? Really starting to get annoying. I seriously would use this as my primary machine, but this random rebooting totally cripples its usage.

Hi UL,

This might be more of a generic Debian hiccup.
http://serverfault.com/questions/402...r-a-week-or-so

The causes each time seem different; RAM does appear as a potential cause, but I can understand that if it works with multiple other OS's then that's unlikely.
Sorry that I could help you more.

[UseLinux]

So I ran all of the memory tests and CPU tests in UBCD, all passed with flying colors.

Also Installed MINT on dual boot.. and it works flawlessly.

[UseLinux]

So I ran all of the memory tests and CPU tests in UBCD, all passed with flying colors.

Also Installed MINT on dual boot.. and it works flawlessly...

So what in Kali would make it randomly freeze.. (Completely random, as in even at the login prompt, or 2 hours later after im doing some heavy workload stuff), but a very similar distro, on the same HDD, same memory, etc..

[uwnthesis]

So what in Kali would make it randomly freeze.. (Completely random, as in even at the login prompt, or 2 hours later after im doing some heavy workload stuff), but a very similar distro, on the same HDD, same memory, etc..

I found this on the Debian server pages. One guy had Python scripts - which caused it to hang. This was the advice given - so I'm cutting and pasting it in, as it may help you diagnose it further.

Please show relevant content of /var/log/messages and/or /var/log/kern.log it's possible the kernel logged some crash reports or something else that could shed some light. When I experienced such unexplained hangs it was due to a bad driver, because logging isn't very verbose I wasn't able to find out the exact driver.
In my case there were soft lockups (kernel: [XXXX] BUG: soft lockup - CPU#X). After some research I found http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556030 and the last comment provided some insight and a way to make logging more verbose. It's an easy kernel modification but if you don't feel comfortable compiling your own kernel it may not be the best thing to do.
Just updating the kernel or installing a newer version and rebooting may fix the problem.
Quoting:

We extensively researched the problem.
The TLB flush softlockup is only a CONSEQUENCE of a deadlock.
Background: The TLB flush is issued by a CPU to a number of other CPUs using inter-processor interupts to progagate paging changes. Then the issuing CPU loops until all processor acknowledge the change. If such processor is in deadlock on a spinlock, this never hapens, then the softlockup triggers. The deadlock arise on a spinlock, this lock may be held by user code sometimes (through /proc or /sys interfaces of modules).
The only way to identify the root cause (i.e. which driver is causing problems) is to dump ALL CPU stacks in the soft lockup code.
One way to do that is to modifiy the kernel and add
arch_trigger_all_cpu_backtrace()
in the
kernel/softlockup.c:softlockup_tick()
function.
This is based on NMI IPI which ensure all stacks are dump, even in the case of deadlock (well don't expect the impossible to happen either).
You should easily find the faulty driver and post the relevant bug.

[UseLinux]

@uwnthesis: Ill look into that next, and post an update. Thank you!

A co-worker of mine stated that it may be related to the drivers, usually video drivers can cause this, apparently.

Nothing on the lsmod really jumps out at me that I can see... Figured id post it for you guys to review tho. (Along with the Linux Mint lsmod output, on the same machine)

Linux Mint 15 lsmod

Module Size Used by
nls_iso8859_1 12713 1
usb_storage 57204 1
parport_pc 28152 0
ppdev 17073 0
bnep 18036 2
rfcomm 42641 0
bluetooth 228619 10 bnep,rfcomm
binfmt_misc 17500 1
asus_nb_wmi 12854 0
asus_wmi 24213 1 asus_nb_wmi
sparse_keymap 13890 1 asus_wmi
coretemp 13355 0
kvm_intel 132891 0
kvm 443165 1 kvm_intel
ghash_clmulni_intel 13259 0
cryptd 20373 1 ghash_clmulni_intel
snd_hda_codec_hdmi 36913 1
dm_multipath 22843 0
scsi_dh 14843 1 dm_multipath
hid_multitouch 17366 0
snd_hda_codec_realtek 78399 1
snd_hda_intel 61623 1
snd_hda_codec 136453 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_i ntel
snd_hwdep 13602 1 snd_hda_codec
snd_pcm 97451 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 18710 2 snd_pcm,snd_hda_intel
snd_seq_midi 13324 0
uvcvideo 80847 0
videobuf2_vmalloc 13056 1 uvcvideo
videobuf2_memops 13202 1 videobuf2_vmalloc
snd_seq_midi_event 14899 1 snd_seq_midi
joydev 17377 0
videobuf2_core 40513 1 uvcvideo
videodev 129260 2 uvcvideo,videobuf2_core
snd_rawmidi 30180 1 snd_seq_midi
snd_seq 61554 2 snd_seq_midi_event,snd_seq_midi
microcode 22881 0
snd_seq_device 14497 3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer 29425 2 snd_pcm,snd_seq
arc4 12615 2
ath9k 149924 0
ath9k_common 14055 1 ath9k
ath9k_hw 413680 2 ath9k_common,ath9k
snd 68876 10 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_ codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_cod ec,snd_hda_intel,snd_seq_device
ath 23827 3 ath9k_common,ath9k,ath9k_hw
mac80211 606457 1 ath9k
mac_hid 13205 0
cfg80211 510937 3 ath,ath9k,mac80211
mei 41158 0
lpc_ich 17061 0
psmouse 95870 0
alx 67960 0
mdio 13807 1 alx
serio_raw 13215 0
soundcore 12680 1 snd
lp 17759 0
parport 46345 3 lp,ppdev,parport_pc
btrfs 785967 0
zlib_deflate 26885 1 btrfs
libcrc32c 12615 1 btrfs
dm_raid45 76725 0
xor 17116 1 dm_raid45
dm_mirror 21946 0
dm_region_hash 20820 1 dm_mirror
dm_log 18529 3 dm_region_hash,dm_mirror,dm_raid45
hid_generic 12540 0
usbhid 47074 1 hid_multitouch
hid 101002 3 hid_multitouch,hid_generic,usbhid
i915 600351 3
wmi 19070 1 asus_wmi
i2c_algo_bit 13413 1 i915
video 19390 2 i915,asus_wmi
ahci 25731 2
libahci 31364 1 ahci
drm_kms_helper 49394 1 i915
drm 286313 4 i915,drm_kms_helper

Kali Linux lsmod

Module Size Used by
nls_utf8 12457 1
nls_cp437 16554 1
vfat 17366 1
fat 46040 1 vfat
binfmt_misc 12958 1
loop 22955 0
dm_crypt 18373 0
uvcvideo 66708 0
videobuf2_vmalloc 12665 1 uvcvideo
videobuf2_memops 12563 1 videobuf2_vmalloc
videobuf2_core 26705 1 uvcvideo
videodev 92071 2 uvcvideo,videobuf2_core
media 18185 2 uvcvideo,videodev
hid_multitouch 13058 0
joydev 17318 0
i915 448745 2
iTCO_wdt 12832 0
iTCO_vendor_support 12705 1 iTCO_wdt
drm_kms_helper 27236 1 i915
drm 202248 3 i915,drm_kms_helper
snd_hda_codec_hdmi 31480 1
arc4 12544 2
asus_nb_wmi 12473 0
ath9k 83773 0
ath9k_common 12729 1 ath9k
ath9k_hw 328776 2 ath9k_common,ath9k
lpc_ich 16758 0
ath 21418 3 ath9k_common,ath9k,ath9k_hw
acpi_cpufreq 13355 0
mac80211 348666 1 ath9k
mfd_core 12602 1 lpc_ich
asus_wmi 18804 1 asus_nb_wmi
snd_hda_codec_realtek 55447 1
mperf 12454 1 acpi_cpufreq
coretemp 12855 0
mei 31840 0
i2c_algo_bit 12842 1 i915
i2c_i801 17046 0
evdev 17651 12
battery 13147 0
i2c_core 24042 6 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,vide odev
sparse_keymap 12761 1 asus_wmi
video 17687 2 i915,asus_wmi
psmouse 69191 0
snd_hda_intel 30803 3
snd_hda_codec 88216 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_i ntel
kvm_intel 118161 0
snd_hwdep 13190 1 snd_hda_codec
snd_pcm 68524 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 13019 2 snd_pcm,snd_hda_intel
snd_timer 22813 1 snd_pcm
ac 12625 0
cfg80211 144106 3 ath,ath9k,mac80211
wmi 13244 1 asus_wmi
rfkill 19167 4 cfg80211,asus_wmi
serio_raw 12941 0
snd 53078 13 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_ codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
processor 28456 1 acpi_cpufreq
kvm 309830 1 kvm_intel
button 12945 1 i915
soundcore 13027 1 snd
hid_generic 12386 0
usbhid 40793 1 hid_multitouch
hid 81617 3 hid_multitouch,hid_generic,usbhid
ext4 371544 1
crc16 12344 1 ext4
jbd2 71913 1 ext4
mbcache 13115 1 ext4
dm_mod 63778 1 dm_crypt
usb_storage 48070 1
sg 26096 0
sd_mod 40550 5
crc_t10dif 12349 1 sd_mod
crc32c_intel 12748 0
thermal 17426 0
thermal_sys 22342 3 video,thermal,processor
ahci 25061 2
libahci 22919 1 ahci
ghash_clmulni_intel 13063 0
cryptd 14561 1 ghash_clmulni_intel
microcode 30457 0
xhci_hcd 78154 0
ehci_hcd 40532 0
libata 141636 2 ahci,libahci
scsi_mod 162399 4 sg,usb_storage,libata,sd_mod
usbcore 134001 6 hid_multitouch,uvcvideo,usb_storage,ehci_hcd,usbhi d,xhci_hcd
usb_common 12355 1 usbcore

[toasty]

Hi, I'm experiencing something very similar. I'm using a Dell Vostro-3300. I've copied kali-linux-1.0.6-i386.iso onto an 8GB USB thumb drive and I'm running Kali from there. I have Linux Mint installed on my HDD and I don't want to wipe it off just yet, so I'm planning to just run Kali from the 8GB thumbdrive. I added persistence as explained here:
http://docs.kali.org/installation/ka...ve-usb-install

I boot both with and without persistence enabled from the splash screen. Both times, after maybe 1 or 2 minutes Kali hanged. It was a kind of soft-hang in that the mouse would still move a bit, but become less and less responsive until it eventually stopped moving altogether. I didn't connect to the wifi network, I didn't enable anything. It just hangs.

I reboot Kali in failsafe mode, however and Kali has yet to hang now. So the cause is something in the difference between failsafe and normal mode that is causing it. I notice the screen is not at the native resolution so if I were to hazard a guess at this time, it might caused by the screen resolution?