similar to: Back trace from rcutree.c after resuming from S3

Hey again, Am 2014-08-19 12:26, schrieb Jonas Meurer: > I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU with > the > stock kernel. The dom0 runs the same linux kernel and > xen/4.1.4-3+deb7u1. the bug is still reproducible with the latest kernel and Xen packages from Debian Wheezy. Unfortunately it seems like a corner case, somehow related to the hardware

And some more information ... Am 2014-10-13 12:04, schrieb Jonas Meurer: > Am 2014-08-19 12:26, schrieb Jonas Meurer: >> I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU >> with the >> stock kernel. The dom0 runs the same linux kernel and >> xen/4.1.4-3+deb7u1. > > the bug is still reproducible with the latest kernel and Xen packages >

Hello CentOS Xen Heroes, Yesterday, I have installed testing kernel 4.9.23-26.el6.x86_64 from virt-xen-testing repo. It crashed today morning. Hardware is a pretty ancient, testing machine (CO6 PV guests only), but had no problems yet. It was stable on 4.9*, including testing 4.9.15-22.el6.x86_64 Console output: [59826.069427] general protection fault: 0000 [#1] SMP [59826.069463] Modules

On Sat, 2020-10-24 at 10:22 +0800, Hillf Danton wrote: > > Looks like we can break the lock chain by moving ttm bo's release > method out of mmap_lock, see diff below. Ah, the perfect compliment to morning java, a patchlet to wedge in and see what happens. wedge/build/boot <schlurp... ahhh> Mmm, box says no banana... a lot. [ 30.456921] ================================ [

Hi! I''ve 5 DSL routers and a linux router in a switch. The linux router is doing NAT for a LAN network, but it freezes when I set up load balancing with this command: ip route add default proto static\ nexthop via 192.168.1.10 dev eth1\ nexthop via 192.168.1.20 dev eth1\ nexthop via 192.168.1.30 dev eth1\ nexthop via 192.168.1.40 dev eth1\ nexthop

On Fri, 23 Oct 2020 14:07:13 +0200 Mike Galbraith wrote: > On Fri, 2020-10-23 at 11:01 +0200, Sebastian Andrzej Siewior wrote: > > On 2020-10-22 07:28:20 [+0200], Mike Galbraith wrote: > > > I've only as yet seen nouveau lockdep gripage when firing up one of my > > > full distro KVM's. > > > > Could you please check !RT with the `threadirqs'

Hello, I''m running into some trouble with what appear on the surface to be OOM issues in Dom0, but I''m not seeing any other evidence. This typically happens during periods of high I/O, and has occurred during RAID initial sync, and mkfs.ext4ing (as a test, no intention to keep ext4 on this array). I''ve found some older posts citing very similar circumstances, however

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: normal Hello, I was running Xen for a few years and after a PSU failure I never got the system working stable again. I suspected damage to the board so I replaced everything in the system piece by piece but Xen enabled kernel always crashes even with only Dom0 running when moderate amount of IO happens on the box. kvm seems

This is a repost of the RCU patch I have posted some time ago. The only change from the previous post, was to move it to a more recent version of xen-unstable (changeset 13386). I am planning to submit the following additional patches, after this one is accepted: 1) rename_find_domain.patch: Rename find_domain_by_id() to get_domain_by_id() 2) add_find_domain.patch: Add new

This is a repost of the RCU patch I have posted some time ago. The only change from the previous post, was to move it to a more recent version of xen-unstable (changeset 13386). I am planning to submit the following additional patches, after this one is accepted: 1) rename_find_domain.patch: Rename find_domain_by_id() to get_domain_by_id() 2) add_find_domain.patch: Add new

Greetings, I got the below dmesg and the first bad commit is commit cf39c8e5352b4fb9efedfe7e9acb566a85ed847c Merge: 3398d25 23b7eaf Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Wed Sep 4 17:45:39 2013 -0700 Merge tag ''stable/for-linus-3.12-rc0-tag'' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip Pull Xen updates from Konrad

Hi Jens, I'm not very sure about this bisect, but anyway it'd be good to inform you of a possible problem on commit commit 3a02db083a78c9f3c9b69305ab513f9422d91b08 Author: Jens Axboe <axboe at kernel.dk> Date: Fri May 24 20:22:33 2013 +0200 virtio_blk: blk-mq support Pretend we have 4 issue queues. Signed-off-by: Jens Axboe <axboe at kernel.dk>

Hi Jens, I'm not very sure about this bisect, but anyway it'd be good to inform you of a possible problem on commit commit 3a02db083a78c9f3c9b69305ab513f9422d91b08 Author: Jens Axboe <axboe at kernel.dk> Date: Fri May 24 20:22:33 2013 +0200 virtio_blk: blk-mq support Pretend we have 4 issue queues. Signed-off-by: Jens Axboe <axboe at kernel.dk>

On Tue, 2011-09-20 at 14:20 +0100, Ben Hutchings wrote: > On Tue, 2011-09-20 at 10:12 +0400, rush wrote: > > Hi, > > > > There are several Not tainted lines in old messages file. There are all of them: > > > > Sep 10 22:35:33 xen-dom0 kernel: [24183.985513] Pid: 2605, comm: > > debootstrap Not tainted 3.0.0-1-amd64 #1 Intel Corporation > >

Greetings, I got the below dmesg and the first bad commit is commit 3ab098df35f8b98b6553edc2e40234af512ba877 Author: Jason Wang <jasowang at redhat.com> Date: Tue Oct 15 11:18:58 2013 +0800 virtio-net: don't respond to cpu hotplug notifier if we're not ready We're trying to re-configure the affinity unconditionally in cpu hotplug callback. This may lead the

Greetings, I got the below dmesg and the first bad commit is commit 3ab098df35f8b98b6553edc2e40234af512ba877 Author: Jason Wang <jasowang at redhat.com> Date: Tue Oct 15 11:18:58 2013 +0800 virtio-net: don't respond to cpu hotplug notifier if we're not ready We're trying to re-configure the affinity unconditionally in cpu hotplug callback. This may lead the

I''ve applied julian''s paches to a 2.6.14 gentoo kernel with the appropiate options enabled, and i''m using a modified version of the mpath2.sh script also available on julian''s site http://www.ssi.bg/~ja/ Overall everything works nearly perfectly. Incomming connections to either the fios (PPPoE) connection, or cable modem get routed back out correctly. The

https://bugs.freedesktop.org/show_bug.cgi?id=70354 Priority: medium Bug ID: 70354 Assignee: nouveau at lists.freedesktop.org Summary: Failed to initialise context object: 2D_NVC0 (0) (for my GeForce GT 750M) QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS:

Greetings, I got the below dmesg and the first bad commit is commit b70aa55ec9532d5f5d3e367e4cad8997b1135f86 Author: Jens Axboe <axboe at kernel.dk> Date: Fri May 24 20:22:33 2013 +0200 virtio_blk: blk-mq support Pretend we have 4 issue queues. Signed-off-by: Jens Axboe <axboe at kernel.dk> [ 277.857736] blk-mq: CPU -> queue map [ 277.871142] CPU 0

Greetings, I got the below dmesg and the first bad commit is commit b70aa55ec9532d5f5d3e367e4cad8997b1135f86 Author: Jens Axboe <axboe at kernel.dk> Date: Fri May 24 20:22:33 2013 +0200 virtio_blk: blk-mq support Pretend we have 4 issue queues. Signed-off-by: Jens Axboe <axboe at kernel.dk> [ 277.857736] blk-mq: CPU -> queue map [ 277.871142] CPU 0