similar to: [patch 0/2] softlockup watchdog improvements

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,

The softlockup watchdog is currently a nuisance in a virtual machine, since the whole system could have the CPU stolen from it for a long period of time. While it would be unlikely for a guest domain to be denied timer interrupts for over 10s, it could happen and any softlockup message would be completely spurious. Earlier I proposed that sched_clock() return time in unstolen nanoseconds, which

The softlockup watchdog is currently a nuisance in a virtual machine, since the whole system could have the CPU stolen from it for a long period of time. While it would be unlikely for a guest domain to be denied timer interrupts for over 10s, it could happen and any softlockup message would be completely spurious. Earlier I proposed that sched_clock() return time in unstolen nanoseconds, which

Stamp softlockup thread earlier before do_timer, because the latter is the one to actually trigger lock warning for long-time offline. Or else, I obserevd softlockup warning easily at manual vcpu hot-remove/plug, or when suspend cancel into old context. One point here is to cover both stolen and blocked time to compare with offline threshold. vcpu hotplug falls into ''stolen''

On Thu, Dec 29, 2022 at 4:10 PM Michael S. Tsirkin <mst at redhat.com> wrote: > > On Thu, Dec 29, 2022 at 04:04:13PM +0800, Jason Wang wrote: > > On Thu, Dec 29, 2022 at 3:07 PM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > > > On Wed, Dec 28, 2022 at 07:53:08PM +0800, Jason Wang wrote: > > > > On Wed, Dec 28, 2022 at 2:34 PM Jason Wang

On Fri, Dec 30, 2022 at 11:43:08AM +0800, Jason Wang wrote: > On Thu, Dec 29, 2022 at 4:10 PM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > On Thu, Dec 29, 2022 at 04:04:13PM +0800, Jason Wang wrote: > > > On Thu, Dec 29, 2022 at 3:07 PM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > > > > > On Wed, Dec 28, 2022 at

Hi list, After a lot of testing + troubleshooting, I guess I'm observing what I am now calling a regression with zaptel 1.4.10 (is it?) As such I call for peer feedback, before either asking Digium install support or filing a bug. Thanks in advance! System: HP Proliant DL380 G5 with 2x PCI-X + 1x PCIe riser card OS: Centos 5 Kernel: 2.6.18-53.1.14.el5 (also tested under

We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Three platforms (32/PAE/32E) test all are based on SMP, It means that we boot up SMP guest OS in VMX. Here is the test summary: New issue ================================================ No new issue Issues List: ================================================ 1) IA32E/PAE: 32bit Vista RTM network doesn''t

On Mon, Jan 30, 2023 at 03:44:24PM +0800, Jason Wang wrote: > On Mon, Jan 30, 2023 at 1:43 PM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > On Mon, Jan 30, 2023 at 10:53:54AM +0800, Jason Wang wrote: > > > On Sun, Jan 29, 2023 at 3:30 PM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > > > > > On Sun, Jan 29, 2023 at

BUG: soft lockup detected on CPU#0! Pid: 2213, comm: smbiod EIP: 0061:[<f4990f2e>] CPU: 0 EIP is at smbiod+0x116/0x16d [smbfs] EFLAGS: 00000246 Tainted: GF (2.6.16-xen-automount #1) EAX: 00000000 EBX: f4996400 ECX: f2c99f68 EDX: f2c98000 ESI: f2c98000 EDI: c06f5780 EBP: f2c99fb8 DS: 007b ES: 007b CR0: 8005003b CR2: b7f77000 CR3: 326e2000 CR4: 00000640

The following changes since commit 33807f4f0daec3b00565c2932d95f614f5833adf: Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6 (2014-03-11 11:53:42 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git tags/virtio-next-for-linus for you to fetch changes up to fc4324b4597c4eb8907207e82f9a6acec84dd335:

The following changes since commit 33807f4f0daec3b00565c2932d95f614f5833adf: Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6 (2014-03-11 11:53:42 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git tags/virtio-next-for-linus for you to fetch changes up to fc4324b4597c4eb8907207e82f9a6acec84dd335:

I am using NFS over brtfs (vanilla 3.8.5) for heavy CoW to clone virtual disks with sizes 20-50GB. It worked OK for a couple of days, but yesterday it crashed. Reboot fixed the problem and I do not see any data corruption. I have a couple of different kdumps, I will include one as text and attach the other ones. I am using Fedora 18 with vanilla 3.8.5. The filesystem is created over a SAN volume

commit 3ab098df35f8b98b6553edc2e40234af512ba877 (virtio-net: don't respond to cpu hotplug notifier if we're not ready) tries to bypass the cpu hotplug notifier by checking the config_enable and does nothing is it was false. So it need to try to hold the config_lock mutex which may happen in atomic environment which leads the following warnings: [ 622.944441] CPU0 attaching NULL

commit 3ab098df35f8b98b6553edc2e40234af512ba877 (virtio-net: don't respond to cpu hotplug notifier if we're not ready) tries to bypass the cpu hotplug notifier by checking the config_enable and does nothing is it was false. So it need to try to hold the config_lock mutex which may happen in atomic environment which leads the following warnings: [ 622.944441] CPU0 attaching NULL

Hi, I'm trying to compile UML with LLVM. However, LLVM-LD hangs whiile linking modules. It's consuming 99% of the CPU llvm-ld -v -r -o kernel/built-in.o kernel/sched.o kernel/fork.o kernel/exec_domain.o kernel/panic.o kernel/printk.o kernel/profile.o kernel/exit.o kernel/itimer.o kernel/time.o kernel/softirq.o kernel/resource.o kernel/sysctl.o kernel/capability.o kernel/ptrace.o

I tried booting the paravirt patches on a real machine to see what would happen. It had worked OK under qemu, so I thought it would be worth it. It seems to boot OK, though perhaps fairly slowly, but once it hits usermode it gets into trouble. When starting udevd, the startup script runs MAKEDEV, which seems to get stuck in an infinite loop in userspace. It eventually gets past that part

Hello All. I've just started looking into Xen and have a test environment in place. I'm seeing an annoying problem that I thought worthy of a post. Config: I have 2 x HP DL585 servers each with 4 Dual core Opterons (non-vmx) and 16GB RAM configured as Xen servers. These run CentOS 5.1 with the latest updates applied. These system both attach to an iSCSI target which is an HP DL385

Hi all, This is my first post to the list, I hope someone out there can help! I am running xen 3.0.3, with CentOS 5.2 based Dom0 (kernel-xen-2.6.18-92.1.22.el5) Recently I have noticed some complete system lockups on a few different servers. Neither Dom0 or any of the guests respond to pings, connecting a keyboard and monitor to the system only shows a blank screen. Nothing is written to logs