Nmi watchdog bug soft lockup migration


0. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. 11, 4. A "soft lockup" is not a crash: It might look like some, but it can also be caused by other means as will heal itself if the underlying condition is removed: This is very likely to happen if the network is saturated by multiple migrations happening in parallel: This will Stack Exchange network consists of 176 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. 14000 that are spitting out NMI Watchdog BUG soft lockup on their consoles. Plus the cpuinfo. If you are a new customer, register now for access to product evaluations and purchasing capabilities. ” NMI Watchdog : BUG : soft lockup #CPU0 stuck for 23s! Ubuntu Vidit. Open File explorer, go to This PC and click computer and then manage BUG: soft lockup - CPU#0 stuck message and the boot hangs. Generally after 61 or 63s. 438993] perf: interrupt took too long (11968 > 9947), lowering kernel. My PC is a dell inspiron 7559 with intel graphic and nvidia. NMI Watchdog Soft lockup Linux 4. using console=ttyS1 or console=ttyS1,9600 . The modprobe/migration codes are not identical with the linked thread. 04 on a workstation with 8TB raid / 2 x Nvidia GPU 1070 / 128 GB RAM. GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together. 5. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. Tens of thousands of happy cus Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git. 5] SCTP: Check if the file structure is valid before checking the non-blocking flag [RHEL5. 5] Fix Time drift on KVM x86_64 RHEL5. 32. 438993] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0 [ 4. Fedora 25 has now been rebased to 4. 13) can reliably re-produce the soft lockup issue within an hour in Ubuntu 16. 04 LTS and burn the ISO to a USB drive using Rufus. From: Frans van Berckel <fberckel@xs4all. 438993] Modules linked in: msr cpuid loop evdev snd_cmipci snd_mpu401_uart snd_opl3_lib snd_hwdep snd * Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 2017-03-01 15:28 PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Meelis Roos @ 2017-03-01 17:07 ` Thomas Gleixner 2017-03-01 20:47 ` Meelis Roos 2017-03-01 22:06 ` Meelis Roos 0 siblings, 2 replies; 12+ messages in thread From: Thomas * [prink] BUG: spinlock lockup suspected on CPU#0, swapper/1 @ 2014-05-30 4:28 Jet Chen 2014-05-30 15:50 ` Jan Kara 0 siblings, 1 reply; 8+ messages in thread From: Jet Chen @ 2014-05-30 4:28 UTC (permalink / raw) To: Jan Kara; +Cc: Fengguang Wu, Yuanhan Liu, Linux Kernel Mailing List [-- Attachment #1: Type: text/plain, Size: 9055 bytes --] Hi Ocassionally NMI watchdog kicks in and discovers one of the > > CPUs in LOCKUP. On a physical host, a soft lockup message generally indicates a kernel bug or hardware bug. watchdog_thresh=30 #内核软死锁(soft lockup)bug原因分析 Soft lockup名称解释:所谓,soft lockup就是说,这个bug没有让系统彻底死机,但是若干个进程(或者kernel thread)被锁死在了某个状态(一般在内核区域),很多情况下这个是由于内核锁的使用的问题。 kernel:NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [migration/2:21] How to install: These steps worked for me, feel free to mix them up if you know what you are doing. 326769] BUG: soft lockup - CPU#6 stuck for 22s! migration/1 S Another update: The issue on HP G8 blades seems to occur only at boot time and only in systems which have remote storage connected. 9. The change is by Ben Greear <greearb [at] candelatech. The VM has the following seup: CentOS 7 64-bit, 16GB memory, 8 vCores and 180GB storage, VM version 8. Why do I recieve BUG: soft lockup kernel messages In this case it may be caused by a bug in the kernel when the CPU wakes up from an extended idle period. The watchdog daemon will send an non maskable interrupt (NMI) to all CPUs in the system who in turn print the stack traces of their currently running tasks. Here is the imformation: Get your subscription! The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. nl> Pada artikel kali ini, saya akan membahas mengenai Bagaimana cara melakukan Migrasi Container OpenVZ dari satu host ke host lainnya. Opts: errors=remount-ro [ 3. (BZ#1299338) A bug in the code that cleans up revoked delegations could previously cause a soft lockup in the NFS server. 3. 5日以上連続稼働した場合に表示されます(再起動は連続稼働扱いとなります)。 NMI watchdog: BUG: soft lockup - CPU#1 stuck for 3489660884s! This problem appears with the changes introduced by 42043e4 spapr: clock should count only if vm is running I think this commit only triggers the problem. vmdk has file blocks allocated from an increased portion on Oracle Linux Errata Details: ELSA-2017-3659. I'm stuck  Apr 10, 2015 If you have ever logged into your Ubuntu (virtual) server running under VMWare Server and have seen messages like the screen grabs below,  [kworker/u256:3:8447] Message from syslogd@amer at Jan 27 19:37:50 kernel :NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! 0. Changelog: These updated kernel packages include numerous bug fixes and enhancements, some of which you can see below. Loading Unsubscribe from Vidit? Cancel Unsubscribe. This project can now be found here. LinuxなんてTeraTerm経由くらいでしかまともに触ったことない私がubuntuを入れることになったきっかけ(読み飛ばしておk) 取引先でWindows10の自動アップデートのトラブルでなんやかんやが 4. Join GitHub today. OK, I Understand config_watchdog=y config_watchdog_core=y # config_watchdog_nowayout is not set # # watchdog device drivers # config_soft_watchdog=m config_da9052_watchdog=y config_da9055_watchdog=m config_wm831x_watchdog=y # config_wm8350_watchdog is not set # config_dw_watchdog is not set config_retu_watchdog=y config_acquire_wdt=m config_advantech_wdt=m Get your subscription! The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. j'ai d'ailleurs commandé la puce pour la changer. Provide details and share your research! But avoid …. 1. Many Linux kernels have a soft lockup watchdog thread, and report soft lockup messages if that watchdog thread does not get scheduled for more than 10 seconds. I tried 1s/2s/3s/4s for local->nfs migration but they all failed (node was rebooted after each sleep change). Working Subscribe Subscribed Unsubscribe 138. 3 on DL585 G6: testing NMI watchdog fails on bootup hwmon: (coretemp) Get TjMax value from MSR for i series CPUs [PATCH][RHEL5. I am trying to install Ubuntu Mate on my Acer Aspire 3, with  Since fresh install, the Ubuntu shutdown was halting with the error: NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [plymouthd:9203]. kernel:NMI watchdog: BUG: soft lockup – CPU#0 stuck for 21s! Consulting the files /etc/grub. This lockup and freeze/crash does not occur with CentOS 6. NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [plymouthd:305] on the startup of my system (even with live-cd). Need access to an account? If your company has an existing Red Hat account, your organization administrator can grant you access. Migration thread soft lockup messages present on server and CPU hang x86_64 [ 392. I realy need your help, for redirect the messages from watchdog to log file, I'm recive a lot of messages on console on all clients, my server have RHEL7 Jan 27 12:24:05 prod kernel: NMI watchdog: BUG: soft lockup - CPU#7 stuck for 22s! [migration/7:43] Jan 27 12:24:06 prod kernel: NMI watchdog: BUG: soft lockup - CPU#42 stuck for 22s! [ps:53836] Что означает «ядро: NMI watchdog: BUG: soft lockup», за которым следуют другие ошибки? У меня всегда открыт мой терминал (Fedora 22), потому что все мои работы я делаю оттуда. 666057] BUG: soft lockup - CPU#31 stuck for 22s! [migration/31:420]\ proc_modules (6,006 bytes) tcp_lp 12663 0 - Live 0xffffffffa0664000 vhost_net 22330 0 - Live 0xffffffffa066a000 vhost 33734 1 vhost_net, Live 0xffffffffa0648000 macvtap 22363 1 vhost_net, Live 0xffffffffa0639000 macvlan 19233 1 macvtap, Live 0xffffffffa0642000 fuse 87741 3 - Live 0xffffffffa0622000 xt_CHECKSUM 12549 1 - Live 0xffffffffa061d000 ipt_MASQUERADE 12678 3 - Live 0xffffffffa0613000 Greetings, I have CentOS running as a Virtual Machine on ESXi 5. Bug Fix(es): Under certain conditions, the migration threads could race with the CPU hotplug, which could cause a deadlock. Tens of thousands of happy cus Created attachment 179274 patch This patch updates kernel-headers to 3. Hey guys I have several vCenters and PSCs running 6. 67GHz stepping : 4 c reference_guide_Kernel_Crash_Dump_Analysis 1. 266197] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [migration/0:11] [ 32. 9 and I can see the same > > soft lockups. 797872] random: crng init done [ 4. ubuntu central-processing-unit vmware-vsphere kernel. 04. ELSA-2017-3659 - Unbreakable Enterprise kernel security and bugfix update May 30, 2019 kernel: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [migration/2:18] kernel: Modules linked in: binfmt_misc xt_addrtype br_netfilter  NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [plymouthd:305] 5 answers. I also don't see a reason, why you don't want to support oprofile NMI The high CPU usage can cause the CPU heartbeat watchdog process to deem a hung process and the ESXi host might stop responding. UPDATE - this issue also happens when attempting to install ubuntu 18. el7. Sometimes I search some info in browser or just have fun. Running the [Kernel-packages] [Bug 1693345] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [khugepaged:38] Nabeel Omer Wed, 24 May 2017 13:46:23 -0700 "BUG: soft lockup - CPU#0 Stuck for 67s!" 上記のメッセージはDeploy-OSのベースとなっているLinuxカーネルの問題によるもので、管理対象マシンを一度も電源OFF(DC OFF)せずに208. Bug # 1639961 reported by bugproxy on 2016-11-07. 9, and does not occur with the current Debian. The modprobe/ migration codes are not identical with the linked thread. Hello,everyone! Now I have come across a kernel bug and I have no idea how to deal with it. Stack Exchange Network. The port builds fine on Poudriere on 10. 7 Resolved: 03/22/2018: Blocks Tails - Feature #13245: Core work 2018Q1: Foundations Team Resolved: 06/29/2017 Pursuing 1% of rank high / to Sharing for Information and Knowledge. ***** MASS BUG UPDATE ***** We apologize for the inconvenience. 10. From: shyam prasad <shyamkundaram@gmail. This issue is resolved in this release. You are currently viewing LQ as a guest. [ 0. Stack Exchange network consists of 176 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. 7-200. Symptom When the database seems to slow down, a quick running utility doesn’t finish, or a shutdown fails for no obvious reason then go look in the OS logs for messages about “soft lockup. conf and /boot/grub/grub. Related to Tails - Bug #15435: Consider upgrading Linux in Tails 3. 41 migration/0 10 root 0 -20 0 0 0 S 0. 056956] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. Objet: Re: [PVE-User] Online storage migration not working (II) Hi Dietmar, It seems that at least 5s sleep is necessary on this test cluster. There is a large number of bugs to go through and several of them have gone stale. Turned out this patch also fixes a bug on the AMD Stoneyridge platform where usleep(1) sometimes takes over 10ms. ***@wfg-ne02 ~# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Genuine Intel(R) CPU 000 @ 2. 62 release, is about Fix lockup related to stop_machine being stuck in __do_softirq. 5 Guest using PV clock WARNING - OLD ARCHIVES This is an archived copy of the Xen. Watch all the video, it covers booting from live cd, editing boot line for first Register. Created attachment 35872 dmesg log without freeze on MA-790X-UD4 with nmi_watchdog=panic,ioapic Using nmi_watchdog change which timer used, so this work around the problem. 145123] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [migration/0:9] en regardant la première ligne, je me pose deux trois questions. This Linux kernel change, a part of the Linux 2. 3-200. Migrasi menggunakan Rsync bisa dibilang sebagai Manual Migration. conf , in RHEL 6 and below, or /etc/sysconfig/grub in RHEL 7, it should be verified if the console output is redirected to a console, i. I checked 4. 10, 4. 800016] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 22s! [prev in list] [next in list] [prev in thread] [next in thread] List: kvm Subject: PROBLEM: Host machine NMI soft-lockup when running qemu -cpu host on Ryzen From Assalamualaikum Warrahmatullahi Wabarakatuh Halo gan, kali ini saya ingin membahas mengenai salah satu Control Panel yang cukup terkenal di dunia Hosting bernama Plesk. 900735] Modules linked in: hog(OE) ppdev joydev . 800012] NMI watchdog: BUG: soft lockup - CPU#15 stuck for 22s! [fdm-stress:32166] [39389. 0-514. 6. For emphasis : these freezes occur when I am not using the machine at all, and it is sitting passively in a Gnome desktop. 6-201 and 4. org, a friendly and active Linux Community. Hi, With 4. 963222] NMI watchdog: BUG: soft lockup - CPU#15 stuck for   Jan 4, 2018 [ 355. Karena kita diharuskan meng-rsync beberapa folder dan file secara manual. We use cookies for various purposes including analytics. I was using an i7 2xcore, 4xthread, Mate, blahblah. The few times it happened in such a way that the bug reporter could report it, the bug reporter claimed I had a tainted system. 5] soft lockup on vlan with bonding in balance-alb mode RHEL 5. perf_event_max_sample_rate to 16700 [ 4. com Watchdog bug soft lockup keyword after analyzing the system lists the list of keywords related and the list of websites with related content, in addition you can see which keywords most interested customers on the this website Welcome to the new and improved LinuxSecurity! After many months in development, LinuxSecurity is pleased to announce the public beta of our new site with more of the stuff we love best - the latest news, advisories, feature articles, interviews, and other content relevant to the Linux user. 0 Jan 2016 Send feedback to jkalliya@redhat. In this video i show how to solve boot problems like "kernel panic" with "noapic" and other boot options in Ubuntu. 3 serial driver crashes with console shortly after boot. Persist data for containerized applications Protect container data with snapshots, mirroring, and replication Scale data as containers grow Maintain end-to-end security Products What's New Compute and Storage MapR Accelerates the Separation of Compute and Storage Latest Release Integrates with puis il repart avec [ 88. The soft lockup eventually goes on in a loop and the system never boots up. Ada 2 metode yang bisa digunakan yaitu menggunakan Rsync dan Live Migration. This you can be more affirmative by  BUG: soft lockup - CPU#0 stuck message and the boot hangs. The first lockup was > > different, all the others were from arch_cpu_idle. com> Re: console [tty0] enabled, bootconsole disabled while booting from disk after complete installation. Download Ubuntu GNOME 16. 3 an x86 server is always crashing roughly a minute after boot in __uart_start/uart_tx_stopped. 101342] NMI watchdog: BUG: soft lockup - CPU#3 stuck  Aug 28, 2017 A 'soft lockup' is defined as a bug that causes the kernel to loop in The watchdog daemon will send an non maskable interrupt (NMI) to all  NMI watchdog: BUG: soft lockup during KVM guest migration test suite. kernel test robot Thu, 14 Sep 2017 14:48:13 -0700 show the detail information (release type, release date, technote, corresponding documentation, size, checksum) of patch for Storage Foundation HA on Linux This page is generated automatically and has not been checked for errors or omissions. What can I do to prevent this, or at least, make them appear less often ? See screen attached. [3. NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 全体的に謎なままですが、どうもCore-i7と nVidia のグラボと特定の Linux カーネル で起きているようです。 こんなことあるのでしょうか。 I inspired by this issue i build up a slightly modified setup with a Raspberry Pi B (mainline kernel), a powered 7 port USB hub and 5 Prolific PL2303 USB to serial convertors. Hi, I hit a soft lockup with 4. I'm stuck with CPU#0 at [modprobe:138] and #1 stuck at [migration1:8]. It seems to me that TP-Link TL-WDN4800, with a recent kernel (I tried 4. 0. For clarification or corrections please contact the Oracle Linux ULN team On ppc64 we want to add the hard lockup detector, but not > the oprofile NMI timer fallback. The machine boots with acpi=off, luckily. 218363] BUG: soft lockup - CPU#3 stuck for 4083s! [swapper:0] (後略) つるしのカーネル使っているのがいけないのでは。VM 環境だと CPU 取られる状況って普通に発生するので。 #そもそもこの状況でパニックする設定にしていること自体いけない。 とりあえずなら あれ、logに残らないのだが ESXi の Centos7 が、以下のメッセージが出て止まっていたような。 NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! SLES11SP2 crashs on boot with "Bug: Soft lock up - CPU#0 stuck for 22s! BUG: soft lockup - CPU#0 stuck for 22s! Application Migration S/4HANA Digital But for me the soft lockup definitely comes from the WiFi driver process (it mentions about ath9k_hw_wait, which is the WiFi driver in kernel I think). [ 159. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc. 编写内核程序,出现soft lockup错误是再常见不过了,类似BUG: soft lockup - CPU#2 stuck for 67s!。 刚开始调试内核时,出现这样的错误,往往两眼一抹黑,不知道该如何下手了。但其实,这样的问题解决多了,会发现原因基本就两种情况,死锁和死循环。 The kernel's command-line parameters¶. A set of patches has been provided to fix this bug, and the deadlock no longer occurs in the system. The following is a consolidated list of the kernel parameters as implemented by the __setup(), core_param() and module_param() macros and sorted into English Dictionary order (defined as ignoring all punctuation and sorting digits before letters in a case insensitive manner), and with descriptions where known. Kernel computes the soft lockup duration using the Virtual Timebase register (VTB), not using the Timebase Register (TBR, the one sysctl -w kernel. This is a zypper dup from latest 11. 内核软死锁(soft lockup)bug原因分析 Soft lockup 名称解释:所谓, soft lockup 就是说,这个 bug 没有让系统彻底死机,但是若干个进程(或者 kernel thread )被锁死在了某个状态(一般在内核区域),很多情况下这个是由于内核锁的使用的问题。 Linux内核对于每一个 Convert the former to use the latter to avoid repetition. by 스쳐가는인연 While doing some tests I ran into an hang on an extent buffer's rwlock that produced the following trace: [39389. "): BUG: unable to handle kernel NULL pointer dereference at 0000000000000208. An ESXi host might fail with a purple screen if the VMFS6 datastore is mounted on multiple ESXi hosts, while the disk. 2. But I'd like to have it all working. More than 1 year has passed since last update. 000000] microcode: microcode updated early to revision 0x1c, date = 2015-02-26 On my vCenter Server Appliance VM, I get "soft lockup - CPU## stuck for ##s!" message. org mailing list, which we have preserved to ensure that existing links to archives are not broken. No, this option should depend on HAVE_PERF_EVENTS_NMI. For me, it was usually CPU 2, but not always. 112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! Seems like a bug in the updated kernel; but, this maybe related to your laptop's battery poor performance. 0 0. The machine continues to freeze. 10 using LiveUSB The RHEL Soft Lockup defect can cause huge CPU performance problems for DB2 and BigSQL. When this is happening, most of the time I have to restart my vCSA VM. Kernel Crash Dump Analysis PREPARED BY : Buland Singh, Red Hat REVIEW BY : Jijesh Kalliyat, Red Hat Version 1. , so I know a lot of things but not a lot about one thing. org/pub/scm/linux/kernel/git/torvalds/linux. This means a 5 second timeout can easily take over 15 seconds which will trigger the watchdog and reboot the system. > > > > DMESG: > > [ 0. Register. My config (localmodconfig + KASAN) is attached below. 900698] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [hog:6885] [ 355. il est vrais que j'ai une carte mère un peu particulière qui dispose de 2 puce BIOS. 10-rc7 on ervery boot: [ 32. A 'soft lockup' is defined as a bug that causes the kernel to loop in kernel mode for more than 20 seconds, without giving other tasks a chance to run. com> on Thu Jun 6 14:29:49 2013 -0700. Difference between default and nmi_watchdog option: Register. . 5 for my company. 应该是KVM占用过多CPU,造成内核软死锁(soft lockup)。Soft lockup名称解释:所谓,soft lockup就是说,这个bug没有让系统彻底死机,但是若干个进程(或者kernel thread)被锁死在了某个状态(一般在内核区域),很多情况下这个是由于内核锁的使用的问题。 LU-11201: NMI watchdog: BUG: soft lockup in lfsck_namespace LU-11215 : conf-sanity test_61: Invalid filesystem option set: large_xattr LU-11224 : T10PI assume several kernel features are enabled. This update fixes the following security issues: * A flaw was found in the way the Xen hypervisor implementation handled instruction emulation during virtual machine exits. On a new machine (ASUS VivoPC VM40B with 2-core Intel Celeron) I installed Fedora 22 KDE spin. 2. Hi all, I had a well running installation of Ubuntu-Mate 16. cependant la sélection du bios ce [5. This bug report is a duplicate of:  Jan 1, 2016 Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64. Asking for help, clarification, or responding to other answers. the vSphere client shows no alerts or migration tasks for the VM. It uses a perf counter internally, so if perf supports some sort of 'soft' nmi, oprofile nmi timer would also work well with it. "The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. e. 0 0:00. I have returned since last time. kernel:NMI watchdog: BUG: soft lockup - CPU#@ stuck for 67s! [migration/2:19] As a result, our server stops responding and we had to perform  Mar 7, 2017 Thread: NMI watchdog: BUG: soft lockup - CPU#X stuck for Xs! [migration/1:15] [ 32. git master commit (In reply to Valentin Heidelberger from comment #2) > As stated in comment 1, this caused VMs to run into soft lockups. 编写内核程序,出现soft lockup错误是再常见不过了,类似BUG: soft lockup - CPU#2 stuck for 67s!。 刚开始调试内核时,出现这样的错误,往往两眼一抹黑,不知道该如何下手了。但其实,这样的问题解决多了,会发现原因基本就两种情况,死锁和死循环。 d57108d4f6 ("watchdog/core: Get rid of the thread . console [tty0] enabled, bootconsole disabled while booting from disk after complete installation. fc25. What does "kernel:NMI watchdog: BUG: soft lockup" followed by other errors mean? I have my terminal always opened (Fedora 22), because all my work I do from there. 0-1 SMP x86_64 Hi all Since a couple of days I've been getting intermittent soft lockups which require restarting my computer. 00 lru-add-drain 11 kernel:[31606. 10,08/54] Btrfs: fix hang on extent buffer lock caused by the inode_paths ioctl Red Hat Enterprise Linux 5 The kernel packages contain the Linux kernel, the core of any Linux operating system. 4-301, 4. et je dois avouer que je pense que la 1 est morte. > > boots fine without soft lockups. BUG: soft lockup - CPU#0 stuck for 22s. After a couple of updates I have kernels 4. 5500 and 6. 266313] Modules linked in: I have similar problems to Bugzy. kernel. With sleep 5, it's going strong with 4 successful online migrations: - local ->nfs (x2) - nfs Thanks for contributing an answer to Stack Overflow! Please be sure to answer the question. Debian Bug report logs - #496917 BUG: soft lockup - CPU#1 stuck for 4096s! [java:3174] and crash (kvm guest) kernel:NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [migration/2:21] Welcome to LinuxQuestions. The system keeps running fine. > [1129306. When configuring some of the RAM for temporal storage the system crashed and I was unable to recover it. nmi watchdog bug soft lockup migration

uj, gs, gv, te, ij, k7, fa, dt, ad, st, q5, c9, 05, dm, gt, tk, it, ph, ww, kr, t7, s0, jv, rb, 4w, ly, xg, at, k5, yy, pf,