I'm not sure if this helps and I'm not sure how to tell anyone what I found, but was a problem in Fedora 10 and 11 were VM's running in KVM would lockup due to (disk or network) IO activity. The problem silently vanished as soon as I installed Fedora 12 as my VM. I upgraded my VM to Fedora 13 and the problem re-surfaced. Oddly, no other distributions seem to have this problem any more judging from Google. My configuration:Host = x86_64, 4 cores, Fedora 11VM = i686, 2 virtual cores, Fedora 10, 11, or 13 (Fedora 12 works)What worked for me was using only one core in my VM. Things have been stable for a few days now
I'm using fedora12 with KVM. I'm also using iptables for filtering and nat. Problem is when I start libvirtd, it overwrites my current iptables and iptables config file (/etc/sysconfig/iptables).
Ok it leaves an old copy in /etc/sysconfig/iptables.old, but the main problem is that it removes also all my custom settings from filter and my full nat. I would like the keep control on my iptables and like to manage them on my own. But I cant find an option in the libvirtd config files and/or the libvirtd startup scripts to prevent libvirt from changing my iptables. how I can make libvirtd stop tempering with my iptables?
I have a fedora 13 rc3. The problem is that boot the system stops here Starting libvirtd daemon Prior to that, stop at this point registering binary handler for windows application. I got up to enter the tty2 to remove Wine This time to stop here Starting libvirtd daemon
Unfortunately accidentaly I disconnected my usb drive my computer and my VMs run from so I just rebooted for a quick fix Now I can't open virt-manager locally and the VM's can't get network connections I see this in the logs after the last two reboots
Code:
grep lxc /var/log/messages |tail -n 2 Jan 7 00:45:04 F820 libvirtd: 00:45:04.524: warning : lxcStartup:1895 : Unable to create cgroup for driver: No such device or address Jan 7 11:52:53 F820 libvirtd: 11:52:53.325: warning : lxcStartup:1895 : Unable to create cgroup for driver: No such device or address
[code]...
I tried restarting libvirtd after with no love so I rebooted and cgroup was gone this was a clean install of F14, after this started I brought the system current, I can provide the packages installed but they errors didnt change
I have a new Fedora 11 install with all updates working on my: Dell XPS M1330 laptop with nVidia GeForce 8400M GS
I wanted to install compiz fusion on Gnome so I followed these step by step instructions from:
Fedora refused to boot, locking up during the process.
Here is what happens...
After updates I had 3 options at boot up:
A) If I choose the TOP one (newest) it will boot up to a black screen and nothing else, I get a white block which moves with mouse. I cant get a shell and any key I hit just echoes back...ctr-alt-del will result in normal shutdown process displaying.
If I watch the services start (F1) I see all -OK- except: nvidia.ko: Driver already enabled
The boot continues with all OK until it gets to: STARTING atd: at which time the screen flashes for about 7 seconds and locks up.
B) If I choose MIDDLE boot option and watch the boot process I see most services start OK except:
-[OK]
Checking for module nvidia.ko [FAILED] nvidia.ko for kernel 2.6.30.8-64.fc11.i686.PAE was not found [WARNING] The nvidia driver will not be enabled until found [WARNING] Driver already disabled
-[OK]
Then the services continue on with [OK] until a few seconds later the screen halts with a mess of colors and symbols on screen and system stops booting. Any key pressed simply echoes back with no other result. Again ctrl-alt-del refreshes screen and shutdown of services proceeds normally.
Here is the scenario: I load hundreds of h264/ac3 video clips from my HD video camera onto a four disk software raid stripe under Fedora 14 running the 2.6.38.3-15.rc1.fc15.x86_64 kernel. I then run a python script I've written to do batch process transcoding on the clips so that I can then edit them in cinelerra. FWIW, the transcode command is: nice ffmpeg -i infile.MTS -y -deinterlace -s hd720 -r 29.97 -acodec pcm_s16be -ar 48000 -ac 2 -vcodec mjpeg -qscale 2 out.mov. The python script batches these commands until they are all completed.
The system is capable of 16 concurrent threads and I set up 8 concurrent run queues to do the processing. Occasionally (about one in every 7 runs), the system will hard lockup during the batch. The X screens are still visible, but the mouse and keyboard are dead and the onscreen clocks freeze. The network io led still flashes but the hard disk io led is on solid at that point, leading me to theorize a kernel bug in the software raid handling. I am not able to remote log in and the system must be then hard rest with the reset button. After the reset there is no useful information in the system logs. this is a pretty uber SMP machine: two westmere quad core cpus, 24GB of ram and a four WD disk software stripe array running under the Intel ICH10 controller. I also have a RocketRaid controller installed but no disks are currently attached to it, and I disabled its bios in the setup. Additional disks under the ICH10 are an SSD system disk, and a sata insertion caddy that I usually have occupied with a disk I do backups to. So, all 6 channels on the ICH are usuallt occupied. General output from hdparm -i is:
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory,nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps (I suspect also boot but I can't be sure; it just occasionally stalls part way through the boot display).
Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports: Thread 1 (<main task>): Cannot access memory at address 0xffff880028025b70I am in the process of running memtest86+ right now. It's been through several passes without errors. I'm going to let it run some more, but if that is dependable it's looking like the RAM sticks are not the problem.
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory,HDPVR,nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps (I suspect also boot but I can't be sure; it just occasionally stalls part way through the boot display).
Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports:
Thread 1 (<main task>): Cannot access memory at address 0xffff880028025b70
I am in the process of running memtest86+ right now, and it's been through several passes without errors. I know it needs to run more, but given the reliability of this problem with MythTV video playback I am wondering if the problem could be in the video card memory.
Does anyone know of a linux (or bootable) tester for video memory? All I am able to find are some things for windoze like this.
Also is there any way to track that address from the core dump back to a physical location?
I've been running F@H on my system for a while now, these specs:
ASUS Rampage Formula Q9450 @ 3.6Ghz 4GB DDR2 8800GT 512MB Fedora 12
Running various different nvidia drivers, with working 3D, and running the latest nvidia drivers with cuda for GPU2 folding + SMP folding.
I decided to add a 9800GT to the machine for more folding PPD, and I've run into some issues.
Firstly there were problems starting X, it would hang as it started or even before it started, so I switched to RPMFusion's repo drivers which have the VGA_ARB patch applied. This now gets me into X and working 2D.
The problem I have is, although the system is completely stable running folding on all four cores, SMP, 24/7, as soon as I start anything involving 3D (such as glxgears) it will run for 3 seconds then hardlock the machine. I mean seriously lock it, no switching to terminals, and an ssh session into it from another PC dies.
Its the same with any other driver that will boot into X with the VGA_ARB patch (talking nvidia binary here).
Both cards work perfectly individually, AND both cards work, including full 3D in Windows 7 when together, which would tend to rule out a hardware fault.
i'm having some issues trying to get the oSUSE 11.3 x64 hypervisor working, these are the errors im getting when i've opened the virtual machine manager, and clicked on one of the 2 options.
verify that 'libvirtd' daemon has been started:
Unable to open connection to hypervisor URI 'qemu:///system': unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: No such file or directory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 971, in _try_open None], flags)
Where does one look in terms of diagnostics after a system lockup and hard reset? For example, one of my computers, running Fedora 14 i686, has taken to locking up quite a bit lately. My only way out is a hard reset. Now, once the thing is booted back up I'd like to try to figure out where the problem lies. Where do I look? Will any of the log files reveal anything relevant to me? If so, what sort of things would I be looking for. Keywords?
This same box also locked up when I had Fedora 14 x86_64 installed. I had read that there were some issues with the newer 64 bit kernels that were causing lockups and / or extremely high loads. This is why I switched back to the 32 bit version, 2 days ago to be exact. The box gets little use. It's a toy really and not my main "daily use" computer. It is, however, running folding@home. Maybe that's where the problem is. About 15 minutes ago I called home and had my wife reset the box, then I logged in from work and stopped the folding service. I'll have to see if it locks up without folding running. Folding was running on this box when I had the 64 bit version installed also.
when trying to choose the Linux partition, I found that it would just hang at a blank screen. Looking further into the problem, I had booted with the Linux Rescue and checked the /boot/grub/grub.conf file. It appeared to be that the menu was set to hidden. I got rid of that line, and checked the boot arguments. It still had acpi=off set with the kernel and everything else seems to be in order. Root is set to root (hd0,2) which should be correct.
I downloaded the Fedora 11 KDE livecd, installed it, and after the reboot when I get to that "firstboot" screen, I can't move the mouse, the keyboard doesn't work, I have to hold down the power button to turn off the computer.
It complains that it can't connect to localhost because probably libvirtd is not running. Well it is running, so please share your wisdom with me. Here is error message:
I have a problem that I'm not sure how best to debug. About every other time when I boot my system, I get a condition where listing the files in /root locks up that xterm session.This can be cleared by opening another xterm window and killing the listing command. This happens on "ls -a", "find", "tar" and I think "stat" also. The locked up xterm echo's chararcters but does not respond to any control sequences. This is new with FC11.This has only been seen to happen for root. And once a system is booted with this problem it seems to persist until you get it booted without the problem.
I have a tested and working ssh connection with my local network server. On Ubuntu it was simple to just add an ssh connection to Virtual Machine Manager to connect to 'hippopatamous.local' (yes thats the name of my server :P) but now that I'm in arch its different. I connect to the server using just 'hippopatamous' and on top of that its like the Virtual machine manager can't connect.
All it says is to make sure that libvirtd is running. I ssh-ed in to the server and make sure it was running. I even ran it on my local computer (this was before I remembered/realized this would be a server type daemon so running it locally wouldn't do anything)
I recently installed 10.4 on my laptop and I love it, so I wanted to install it on my desktop. It's a somewhat older computer, AMD3000+ nForce 2, 1.5 gigs of Ram and a Radeon x1650. Whenever I try to start the Live CD I get the error soft lockup - CPU#0 stuck for 61s and it doesn't continue.
There is a bad bug in OpenOffice that keeps giving me a hard lock. I can not even shut down the program, I need to force a reboot. I can make it happen repetitively. Anytime I am working on a presentation in OpenOffice Impress an am working with sound files this happens. If I am moving the sound file icon around on the slide it randomly locks up the file I have open. Another way is resizing the icon and it will also lock it up.
After updating to 10.10, I started getting hard freezes on a regular (read: every 10 min.during use) basis. A bit of diagnosis showed me that it was only a problem during periods of intensive I/O activity (moving files, downloading, etc.).A bug report started with:BUG: soft lockup - CUP#0 stuck for 61s! [kswapd0:26]I reinstalled 9.04, and was able to successfully copy 15gb from one drive to another. I upgraded to 9.10, and copied it back.Upgraded to 10.04 and copied it again. 10.10, it copied a few mb and froze.
I cannot boot into Ubuntu at all. I have two kernels installed, 2.6.35-28 and 2.6.35-30. The first thing that happened today was that I wasn't able to boot into the latter. I was shown the (in)famous "BUG: soft lockup - CPU#0 stuck for 61s". At this point I could still boot into the 2.6.35-28 kernel. But after shutting down and starting again an hour later, I got the same message when trying to boot into 2.6.35-28. I have tried leaving out the boot options "splash" and "quiet" on both kernels and also adding in "noapic". No combination helps. Needless to say, booting into recovery mode doesn't work either. Up until today, I have been able to boot into both kernels with no problems.
Slackware 12.2.0, 2.6.27.7,ibm thinkpad a21m, current patches, xfce 4.6 laptop runs continuously uptime 261 days once till power outage it was running, opened the lid, couldnt get any response from xfce, tried to ssh but couldnt, checked logs after reboot, couldnt see anything weird, message log set a mark a few minutes before i powered down and rebooted is there anything else i can check for possible lock up?
I've been running a Dell Latitude D600 laptop on -current for a couple of months. After the last kernel update, I needed to switch to the non-SMP huge kernel due to lack of pae instructions.Since then, I've seen 2 complete lockups. They've both happened when it was sitting idle, and in both cases, Xfce is gone, and the console is spewing kernel messages faster than I can possibly read.
I am running Centos 5.5 on a IBM Think Centre. I am using it for File sharing Samba and one moment it would be working find then the external 1TB HDD would lockup and I would have to reformat it in order for it to work. I don't really have and other information but that is basicallly what happen even if i manually go to the Centos server it would not allow and thing to be created.
Running 5.5 64bit. Same machine has been running since release of 5.0. Normally the machine runs the nvidia driver from elrepo but I switched back to vesa (thinking the Nvidia driver was the problem, no go). Machine starts up normally and everything is fine until when the login screen should appear. Instead of the normal login screen I have a black screen with the mouse swirly going round and round(which normally occurs for a second or so). This all started when I went out for dinner. When I came back and wiggled the mouse all I got was the swirly. Rebooted, same thing. I can switch to a tty and log in normally. xorg log looks clean. Both drives are accessible via cli (/home is on a separate drive).
i'm trying to Debian 8.1.0 on my notebook Acer Travelmate 2200. Currently i have very outdated version of Linux Mint. It works fine but I prefer keeping system updated. Only way to get updated system now is install new one, and here i have a problem. After CD/ISO booting, installation looking for a mountd devices, etc. then i got statement that CPU stuck for x sec. The same statement appears every 20sec. I was trying it on other linux distr's they give the same error. I didn't overclocked my notebook, his temp is ok. I'm working on it few hours each day, it didn't overheat. Someone told me thats bug of 2.6.x kernel but I'm trying install new system with 3.16.x.
I've just installed OpenSuse 11.3 on my two Sony Vaio VPCF11Z1E machines (which have a Geforce GT 330M graphics card).Both machines appear to setup correctly and behave normally, but at seemingly random intervals (of the order of magnitude of 15-30 minutes) the whole system locks up for no readily apparent reason. I can still move the mouse pointer around the screen, but I cannot click on anything, and the whole keyboard is unresponsive (including any reasonable ctrl-alt-xxx which might normally help). The only way to get out of this seems to be to press and hold the power button to shut the whole machine off (which is not ideal!)
I am not sure of which LibreOffice version I am using because I can't open the ****ed program. So here's what's happening: I start LibreOffice, my screen looks unusual (it tiles a section of the screen that is the same size as the LibreOffice window (I think) across both of my monitors) and my system locks up. I am unable to use Ctrl+Alt+Backspace, Ctrl+Alt+Delete, Ctrl+Alt+F1-F8, or any other keyboard combination. No mouse click registers and the cursor acts as if the mouse is in one location (if the system locked up with my cursor over a link, the cursor stays like that) BUT the mouse still moves. Also, if I am playing music when it locks up, I can continue to hear the music and the music continues to shuffle through my playlist.
I am able to access my machine normally through ssh and the only way I've been able to fix this is to hold down the power button or pull the power. I have not identified what action causes the system to lock up, the only thing I've noticed is that LibreOffice is open every time this happens (It's happened no matter if Writer or Calc is open). The system almost always locks up upon startup of LibreOffice if the recovery window pops up, otherwise it locks up at some point during my LibreOffice session no matter what. I have not touched LibreOffice on my other machine's openSUSE installation, so I don't know how reproducible the problem is. Let me know if you need any extra information or if there are any diagnostic commands I could run.
11.4 Boot Freeze That is there is a BUG: soft lockup - CPU#0 stuck message and the boot hangs.The modprobe/migration codes are not identical with the linked thread. I'm stuck with CPU#0 at [modprobe:138] and #1 stuck at [migration1:8]. Generally after 61 or 63s.
This is a zypper dup from latest 11.3.The machine boots with acpi=off, luckily. But I'd like to have it all working.The forum says I can't post attachments; hwinfo output seems a bit copious to quote inline. But I'd be happy to provide any additional info obviously.
I'm putty'd into an Ubuntu server box and have EDITOR=emacs set. However whenever I run crontab -e my shell locks up.
I can use emacs normally by typing emacs from the command line, so I'm not sure what problem is. If I set EDITOR=vi I can run crontab -e and it opens in vi
