Running Windows 10 on my laptop (with a compatible GPU) and just started using tensorflow-gpu 2 days ago. Every time I close the lid to put the laptop to sleep, it restarts when I wake it up. This never happened when I was just running normal tensorflow. I thought I'd see here if this is normal or known before running it up the flagpole on their git repo.
Related
I thought ColabPro+ would allow me to run on a GPU for longer than 24hr, but the VM is getting killed right at 24hrs, while the (Chrome) browser is open, and a python program has been running the whole time using the GPU. I tried running in background mode and in this case it killed the VM in about an hour. What am I missing?
I recently switched out my AMD Ryzen 7 3800x for a Ryzen 9 5950x. I also purchase and M.2.
I got these today and installed them on my computer. I have an SSD, a hard Drive and now an M.2
I deleted Fortnite from my hard drive and then installed it on my M.2 the game started up fine it played okay no problems
Then I uninstalled Call of duty modern warfare. I reinstalled it along with its launcher on the new M.2
After installation I went to start the game and check out how it runs with the new stuff.
My problem is that every time I try to start the game it loads for 10 seconds then my computer reboots. I cannot even load into the game because the computer just reboots itself.
I have tried uninstalling and reinstalling again,
I tried running as Administrator,
I attempted to reset the M.2 and see is that was the issue,
I also uninstalled and reinstalled fortnite and it worked perfectly fine.
Does anyone have any tips on what to check or what to do? Everything is up to date. I also reset my bios just in case my old overclock settings for the old CPU had something to do with the crashing of this new one, but nothing happened it kept crashing.
I also attempted to install call of duty vanguard and call of duty cold war. Same thing happened with those as well. I then installed a free to play game and it also happened with that.
I am not sure where to go from here. If anyone has any tips on how to fix this I would be more than pleased. Thank you so much
I have a boot2docker version of minishift installed on my laptop. Since I am using Windows 10 Home edition, I am forced to use Virtual box to run the minishift OS. However, every time I have to load the OS, minishift takes ages to boot up.
It takes almost 15 minutes to fully start the system. Plus I have to rsync my changes again as they are lost every time I stop the machine. Is there any solution to this?
Ever since I have upgraded my laptop (Click here for hardware specs.) my screen usually freezes. Mostly in chrome or Firefox browser. I am pretty sure this is a Nvidia driver problem but I can't seem to find the solution. I am running a Nvidia Quadro K2100M.
I am currently running Nvidia 361.42. I have tried using open source Xorg server without any luck.
The only solution I have found so far is forcefully turning off the computer by holding down the power button.
Things that I have tried:
I got keyboard input
I cannot switch to another terminal to restart lightdm
This problem came to me occasionally, making me really annoyed.
As illustrated in many blogs, this may be caused by graphic driver problem. For me, my desktop has a NVIDIA video card, you can run lspci | grep VGA to see what type of your video type, in my case, it returned:
02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1)
I followed the instruction on jiakai zhang's blog to reinstall proper drivers for the desktop, hope this will help you.
The key steps in [1] are to reinstall the ubuntu desktop and nvidia drivier by:
$ sudo su
$ apt-get update
$ apt-get install --reinstall ubuntu-desktop
$ apt-get install unity
$ apt-get remove --purge nvidia*
$ reboot
$ sudo apt-get install nvidia-current
$ sudo reboot
Updating the grub settings worked for me! Do the following:
1. Open the GRUB configuration
sudo vi /etc/default/grub
2. Change the value of GRUB_CMDLINE_LINUX_DEFAULT from "quiet splash" to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1"
and save the file.
3. Update & Reboot
sudo update-grub
sudo reboot
More info:
This is a bug in the processor, known as the c-state bug. It causes total freezes when the CPU tries to enter an unsupported sleep state. It's a problem for many Bay Trail devices especially with newer (4.*) kernels. There is a simple workaround until it gets properly fixed upstream. You just need to pass a kernel boot parameter and the random freezing stops completely. The parameter may increase battery consumption slightly, but it will give you a usable system. You do this by editing the configuration file for GRUB as described above.
GRUB - boot loader package from the GNU Project, which provides a user the choice to boot one of multiple operating systems
installed on a computer or select a specific kernel configuration available on a particular operating system's partitions;
Intel Bay Trail - new Atom Processors from Intel. Atom is Intel's family of x86 and x86-64 processors that are optimized
for small computing devices, such as smartphones and mobile Internet devices;
C-States - used to optimize optimize or reduce power consumption in idle mode (i. e. when no code is executed) - (C0 to C8)
Reference: here.
I have since fixed this problem by re-installing Ubuntu 16.04 and not switching from the nouveau video driver. I also disable updates and everything been working good for about 2 months now.
Gaming is pretty good but I usually play steam games so doesn't push any kinda hard core graphics
Well, I had the same problem: My PC was freezing randomly. I tried Ubuntu 16, 17 and 18.04 and everything was the same. I tried several drivers and didn't get a solution. I tried several solutions that I found in the forums (including this) and got bad and harmful results.
My solution was: I stopped using the graphical nvidia card, removed it and now I'm using the integrated Intel HD graphics card (Intel® HD Graphics 530 card (Skylake GT2)) and all the problems were solved!
I fixed mine using a few commands from #Qoros solution above. i just ran apt-get update, apt-get install nvidia-current, and sudo reboot. cheers to #Qoros btw!
For me, none of the approaches described in rest of the answers worked.
I was opening multiple terminal tabs running some heavy processes and ubuntu used to freeze when I had 6-7 tabs. I tried monitoring the resources used while I was starting my processes in terminal tabs. You can do it by opening System Monitor app and going to Resources tab.
What I noticed is that when my RAM(8GB) and my swap space(1GB) were completely used up, ubuntu would freeze.
As a solution, I increased my swap space and made it 16GB. After this memory never gets used completely and ubuntu doesn't freeze.
https://askubuntu.com/questions/178712/how-to-increase-swap-space decsibes how to increase swap space.
I am using OMXPlayer to play some HD videos on my RaspberryPi 3 with latest Raspbian Jessie image. It run perfectly for some time (sometimes 20 minutes, sometimes 3 hours, sometimes 5 hours) but then it freezes. CPU and RAM values are normal. I am running OMXPlayer with this command:
/usr/bin/omxplayer --no-osd --loop myVideo.mp4
and after OMXPlayer freezes I get this message in console:
omxplayer.bin: OMXCore.cpp:785 OMX_ERRORTYPE COMXCoreCOmponent:FreeInputBuffers(): Assertion 'm_omx_input_buffers.size() == m_omx_input_available.size()' failed.
Googled and only advice that I found to solve this problem is to set GPU memory to 128 instead to default 64, I did it, but nothing changed.
Anybody here had similar experience with OMXPlayer ? Is there any way to fix this ?
It was because old raspberry pi firmware and old omxplayer version, so I recommend you to update firmware by:
sudo rpi-update
and to install and download OMXPlayer version 6c90c75 from this link to avoid freezing problems:
http://omxplayer.sconde.net/
Based on this thread, I discovered that installing an old version of Omxplayer (from Mar 9, 2014) solved my freezing issue. You can download old versions of Omxplayer here and install the downloaded .deb file using:
sudo dpkg -i /path/to/your_install_file.deb
I had a similar problem here... in my case, I was pushing a video from a nodeJS server on the local network. If I changed the video at the server, OMXPlayer would just crash.
I removed the OMXPlayer --loop flag. Instead, perform a while loop in a bash script. This solution fixed it for me...
#!/bin/bash
sleep .5
while [1]
do
omxplayer -b -r -live http://192.168.1.16:3000/fileserver/channelA
done