Bug#945912: Kernel 5.4 e1000e Detected Hardware Unit Hang

Package: linux-image-5.4.0-0.bpo.3-amd64 Severity: important Feb 21 18:44:31 vhost002 kernel: e1000e :00:19.0 eth1: Detected Hardware Unit Hang: TDH TDT

Bug#945912: Kernel 5.3 e100e Detected Hardware Unit Hang

Package: linux-image-5.3.0-0.bpo.2-amd64 Severity: important Dear Maintainer, * What led up to the situation? Installed kernel 5.2 and 5.3 on two physical hosts in a KVM virtual cluster, each host with two bonded Ethernet ports. After some random amount of time that ranges from right

Bug#939788: drbd-utils: Invalid argument with kernel 5.2

As far as I can tell, the updated version of drbd-utils is not in unstable or even testing. What is the process for getting the latest version of drbd-utils into stable? As mentioned previously, kernel 5.2 is useless on systems that use drbd. -- Russell Mosemann

Bug#939788: drbd-utils: Invalid argument with kernel 5.2

Package: drbd-utils Version: 9.5.0-1+b1 Severity: important Dear Maintainer, * What led up to the situation? Installed kernel 5.2. Works fine with 4.19. * What exactly did you do (or not do) that was effective (or ineffective)? drbd fails to mount devices with "Invalid argument." See

Bug#908216: btrfs blocked for more than 120 seconds

. There are hardly any references or files on the drives. It might take up to a month to know if there is an issue. -- Russell Mosemann

Bug#908216: btrfs blocked for more than 120 seconds

I used btrfs-progs (4.17-1~bpo9+1) from the backports repository, which does have zstd support. btrfs-check does need zstd support. Otherwise, it will error out with unsupported feature (10). -- Russell Mosemann -Original Message- From: "Nicholas D Steeves" Sent: Saturda

Bug#908216: btrfs blocked for more than 120 seconds

with the same file results in the same hang. -- Russell Mosemann

Bug#908216: btrfs blocked for more than 120 seconds

aste bytes: 695281951 file data blocks allocated: 3067911655424 referenced 6563527507968 -- Russell Mosemann

Bug#908216: btrfs blocked for more than 120 seconds

after a reboot sometimes triggers the same bug, and sometimes it works fine. -- Russell Mosemann

Bug#908216: btrfs blocked for more than 120 seconds

t; > BTW, you're not using SMR and/or USB disks, right? No SMR or USB disks are being used. It is either a single-partition, dedicated hard drive or a partition on hardware RAID. > On Mon, Feb 25, 2019 at 12:33:51PM -0600, Russell Mosemann wrote: > > Steps to reproduce > > &

Bug#908216: btrfs blocked for more than 120 seconds

Steps to reproduce Simply copying a file into the file system can cause things to lock up. In this case, the files will usually be thin-provisioned qcow2 disks for kvm vm's. There is no detailed formula to force the lockup to occur, but it happens regularly, sometimes multiple times in one

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.16-1~bpo9+1 Severity: important If the btrfs fixes will not be backported to 4.19, then this is not an appropriate base kernel for the next version of Debian. Feb 24 19:09:21 vhost182 kernel: INFO: task btrfs-transacti:604 blocked for more than 120

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.16-1~bpo9+1 Severity: important Feb 24 17:19:32 vhost002 kernel: INFO: task btrfs-transacti:643 blocked for more than 120 seconds. Feb 24 17:19:32 vhost002 kernel: Not tainted 4.19.0-0.bpo.2-amd64 #1 Debian 4.19.16-1~bpo9+1 Feb 24 17:19:32 vhost002

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.16-1~bpo9+1 Severity: important Feb 24 10:47:24 lxc008 kernel: INFO: task btrfs:4752 blocked for more than 120 seconds. Feb 24 10:47:25 lxc008 kernel: Tainted: G I 4.19.0-0.bpo.2-amd64 #1 Debian 4.19.16-1~bpo9+1 Feb 24 10:47:25 lxc008

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.16-1~bpo9+1 Severity: important Feb 23 00:36:42 vhost002 kernel: INFO: task btrfs-transacti:638 blocked for more than 120 seconds. Feb 23 00:36:42 vhost002 kernel: Not tainted 4.19.0-0.bpo.2-amd64 #1 Debian 4.19.16-1~bpo9+1 Feb 23 00:36:42 vhost002

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.16-1~bpo9+1 Severity: important Feb 22 19:09:23 vhost182 kernel: INFO: task btrfs-transacti:612 blocked for more than 120 seconds. Feb 22 19:09:23 vhost182 kernel: Not tainted 4.19.0-0.bpo.2-amd64 #1 Debian 4.19.16-1~bpo9+1 Feb 22 19:09:23 vhost182

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.16-1~bpo9+1 Severity: important This is a frequent bug that occurs nearly daily for many months, now. Feb 21 19:02:38 vhost182 kernel: INFO: task btrfs-transacti:617 blocked for more than 120 seconds. Feb 21 19:02:38 vhost182 kernel: Not tainted

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.16-1~bpo9+1 Severity: important Feb 21 17:19:15 vhost002 kernel: INFO: task btrfs-transacti:636 blocked for more than 120 seconds. Feb 21 17:19:15 vhost002 kernel: Not tainted 4.19.0-0.bpo.2-amd64 #1 Debian 4.19.16-1~bpo9+1 Feb 21 17:19:15 vhost002

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.16-1~bpo9+1 Severity: important Feb 20 18:34:42 lxc008 kernel: INFO: task fbackup main:27837 blocked for more than 120 seconds. Feb 20 18:34:58 lxc008 kernel: Tainted: G I 4.19.0-0.bpo.2-amd64 #1 Debian 4.19.16-1~bpo9+1 Feb 20

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.12-1~bpo9+1 Severity: important Feb 19 19:01:04 vhost182 kernel: INFO: task btrfs-transacti:613 blocked for more than 120 seconds. Feb 19 19:01:04 vhost182 kernel: Tainted: GE 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1 Feb 19

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.16-1~bpo9+1 Severity: important Feb 15 14:21:09 lxc009 kernel: INFO: task rsync:1762 blocked for more than 120 seconds. Feb 15 14:21:09 lxc009 kernel: Not tainted 4.19.0-0.bpo.2-amd64 #1 Debian 4.19.16-1~bpo9+1 Feb 15 14:21:09 lxc009 kernel: "echo 0 >

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.16-1~bpo9+1 Severity: important Feb 15 08:08:50 lxc008 kernel: INFO: task fbackup main:2330 blocked for more than 120 seconds. Feb 15 08:08:50 lxc008 kernel: Tainted: G I 4.19.0-0.bpo.2-amd64 #1 Debian 4.19.16-1~bpo9+1 Feb 15

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.12-1~bpo9+1 Severity: important With the debilitating btrfs bugs in 4.19, it probably wasn't prudent to remove 4.17 and 4.18 from the repository, until 4.20 is released. Jan 25 17:17:50 vhost002 kernel: INFO: task btrfs-transacti:661 blocked for more than

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.12-1~bpo9+1 Severity: important Jan 23 17:16:23 vhost002 kernel: INFO: task btrfs-transacti:638 blocked for more than 120 seconds. Jan 23 17:16:23 vhost002 kernel: Tainted: GE 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1 Jan 23

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.12-1~bpo9+1 Severity: important Jan 22 09:35:31 vhost002 kernel: INFO: task btrfs-transacti:4031 blocked for more than 120 seconds. Jan 22 09:35:31 vhost002 kernel: Tainted: GE 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1 Jan 22

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.12-1~bpo9+1 Severity: important The only solution is to revert to 4.17. Jan 19 18:14:35 vhost004 kernel: INFO: task btrfs-transacti:691 blocked for more than 120 seconds. Jan 19 18:14:35 vhost004 kernel: Tainted: G I E 4.19.0-0.bpo.1-amd64

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.19.12-1~bpo9+1 Severity: important Yes, the btrfs hung task problem still exists in the latest kernel. Jan 19 18:40:41 vhost003 kernel: INFO: task btrfs-transacti:666 blocked for more than 120 seconds. Jan 19 18:40:41 vhost003 kernel: Tainted: G I E

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.18.20-2~bpo9+1 Severity: important This problem was so bad with 4.18.6-1~bpo9+1 that I had to revert to 4.17.0. When saw that 4.18.20 was out, I wanted to give it a try. Big mistake. Please fix this problem, already. Dec 22 18:14:11 vhost004 kernel: INFO: task

Bug#909475: task jbd2 blocked for more than 120seconds

Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Dec 03 06:04:09 vhost032 kernel: INFO: task jbd2/sdc1-8:644 blocked for more than 120 seconds. Dec 03 06:04:09 vhost032 kernel: Not tainted 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1 Dec 03 06:04:09 vhost032 kernel:

Bug#914196: jbd2 blocked for 120 seconds

Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Dear Maintainer, * What led up to the situation? The system was performing normal duties. The kernel reported that jbd2 was blocked for more than 120 seconds. See log file details below. There was no apparent problem with

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Nov 01 03:43:58 lxc009 kernel: INFO: task rsync:39988 blocked for more than 120 seconds. Nov 01 03:43:58 lxc009 kernel: Not tainted 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1 Nov 01 03:43:58 lxc009 kernel: "echo 0 >

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Oct 19 02:38:41 lxc009 kernel: INFO: task rsync:18730 blocked for more than 120 seconds. Oct 19 02:38:41 lxc009 kernel: Not tainted 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1 Oct 19 02:38:41 lxc009 kernel: "echo 0

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Oct 18 01:40:34 lxc009 kernel: INFO: task kworker/u130:2:40876 blocked for more than 120 seconds. Oct 18 01:40:34 lxc009 kernel: Not tainted 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1 Oct 18 01:40:34 lxc009

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Oct 17 01:07:25 lxc008 kernel: INFO: task fbackup main:23119 blocked for more than 120 seconds. Oct 17 01:07:25 lxc008 kernel: Tainted: G I 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1 Oct 17

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important This problem is happening on a daily basis on more than one machine. Oct 16 01:12:41 lxc008 kernel: INFO: task rsync:14731 blocked for more than 120 seconds. Oct 16 01:12:41 lxc008 kernel: Tainted: G I

Bug#908216: btrfs blocked for more than 120 seconds

Package: linux-image-4.18.0-0.bpo.1-amd64 Severity: important Sep 27 01:25:47 lxc008 kernel: INFO: task rsync:24406 blocked for more than 120 seconds. Sep 27 01:25:47 lxc008 kernel: Tainted: G I 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1 Sep 27 01:25:47 lxc008

Bug#908216: btrfs blocked for more than 120 seconds

Package: linux-image-4.18.0-0.bpo.1-amd64 Severity: important Sep 25 22:10:29 lxc008 kernel: INFO: task fbackup main:6251 blocked for more than 120 seconds. Sep 25 22:10:30 lxc008 kernel: Tainted: G I 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1 Sep 25 22:10:30 lxc008

Bug#909475: task jbd2 blocked for more than 120 seconds

Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Dear Maintainer, * What led up to the situation? See below for log extract. * What exactly did you do (or not do) that was effective (or ineffective)? A reboot was required. * What are the associated lines from

Bug#908216: btrfs blocked for more than 120 seconds

Package: linux-image-4.18.0-0.bpo.1-amd64 Severity: important Sep 22 17:15:44 lxc008 kernel: INFO: task backup cleanup:2165 blocked for more t han 120 seconds. Sep 22 17:15:44 lxc008 kernel: Tainted: G I 4.18.0-0.bpo.1- amd64 #1 Debian 4.18.6-1~bpo9+1 Sep 22 17:15:44 lxc008

Bug#908216: btrfs blocked for more than 120 seconds

Package: linux-image-4.17.0-0.bpo.3-amd6 Severity: important Sep 09 00:39:52 lxc008 kernel: INFO: task rsync:20113 blocked for more than 120 seconds. Sep 09 00:39:52 lxc008 kernel: Tainted: G I 4.17.0-0.bpo.3-amd64 #1 Debian 4.17.17-1~bpo9+1 Sep 09 00:39:52 lxc008

Bug#908216: task btrfs-transacti:663 blocked for more than 120 seconds

Package: linux-image-4.17.0-0.bpo.3-amd6 Severity: important Sep 07 22:14:51 lxc008 kernel: INFO: task fbackup main:7247 blocked for more than 120 seconds. Sep 07 22:14:51 lxc008 kernel: Tainted: G I 4.17.0-0.bpo.3-amd64 #1 Debian 4.17.17-1~bpo9+1 Sep 07 22:14:51

Bug#907859: task btrfs-transacti:663 blocked for more than 120 seconds

Package: linux-image-4.17.0-0.bpo.3-amd6 Severity: important Sep 03 08:18:04 vhost004 kernel: INFO: task btrfs-transacti:692 blocked for more than 120 seconds. Sep 03 08:18:06 vhost004 kernel: Tainted: G I 4.17.0-0.bpo.3-amd64 #1 Debian 4.17.17-1~bpo9+1 Sep 03 08:18:07

Bug#907859: task btrfs-transacti:663 blocked for more than 120 seconds

Package: linux-image-4.17.0-0.bpo.3-amd6 Severity: important Dear Maintainer, * What led up to the situation? Normal system operation, as far as I am aware, and then btrfs hung. The file system became inaccessible. See log lines below. * What exactly did you do (or not do) that was

Bug#906225: btrfs_run_delayed_refs No space left

Package: src:linux Version: 4.17.8-1~bpo9+1 Severity: important Sep 01 22:45:31 lxc008 kernel: [ cut here ] Sep 01 22:45:31 lxc008 kernel: BTRFS: Transaction aborted (error -28) Sep 01 22:45:31 lxc008 kernel: WARNING: CPU: 3 PID: 708 at

Bug#896666: qemu-system-x86: page allocation failure

Package: src:linux Version: 4.17.0-0.bpo.1 Severity: important Aug 24 19:10:20 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO) , nodemask=(null) Aug 24 19:10:20 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#906225: btrfs_run_delayed_refs No space left

Package: src:linux Version: 4.17.8-1~bpo9+1 Severity: important Dear Maintainer, * What led up to the situation? Normal copying of files to the btrfs file system. There is tons of free space on the disk. The "no space left" error occurred, and the file system was forced readonly. We are

Bug#896666: qemu-system-x86: page allocation failure: 4.16.12-1~bpo9+1

Package: src:linux Version: 4.16.12-1~bpo9+1 Severity: important Jul 02 19:09:31 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) Jul 02 19:09:31 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.12-1~bpo9+1

Package: src:linux Version: 4.16.12-1~bpo9+1 Severity: important Jun 23 00:40:08 vhost003 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) Jun 23 00:40:08 vhost003 kernel: qemu-system-x86 cpuset=emulator

Bug#898336: hpwdt NMI kernel crash on shutdown/reboot

Package: src:linux Version: 4.16.12-1~bpo9+1 Severity: important [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ 1125.048758] hpwdt: Unexpected close, not stopping watchdog! [ 1129.467546] Kernel panic - not syncing: An NMI occurred. Depending on your

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 31 18:31:39 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 31 18:31:39 vhost004 kernel: qemu-system-x86 cpuset=/

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 28 18:32:33 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 28 18:32:33 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 27 23:35:31 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO) , nodemask=(null) May 27 23:35:31 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 26 23:27:39 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO) , nodemask=(null) May 26 23:27:39 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 27 00:48:35 vhost003 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 27 00:48:35 vhost003 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 24 23:28:49 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 24 23:28:49 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 24 21:31:33 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 24 21:31:33 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 24 21:28:14 vhost003 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO) , nodemask=(null) May 24 21:28:14 vhost003 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 24 00:46:15 vhost003 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 24 00:46:15 vhost003 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 23 05:32:54 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 23 05:32:54 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 22 21:31:28 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 22 21:31:28 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 21 23:24:51 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 21 23:24:51 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 20 18:32:12 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO) , nodemask=(null) May 20 18:32:12 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 16 21:23:53 vhost003 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 16 21:23:53 vhost003 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 16 04:37:09 vhost003 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 16 04:37:09 vhost003 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 16 00:47:48 vhost003 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 16 00:47:48 vhost003 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 12 21:23:50 vhost003 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 12 21:23:50 vhost003 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.15.0-0.bpo.2-amd64

Package: src:linux Version: 4.15.11-1~bpo9+1 Severity: important May 05 18:29:18 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO) , nodemask=(null) May 05 18:29:18 vhost004 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.15.0-0.bpo.2-amd64

Package: src:linux Version: 4.15.11-1~bpo9+1 Severity: important Apr 24 00:38:33 vhost003 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) Apr 24 00:38:33 vhost003 kernel: qemu-system-x86 cpuset=emulator

Bug#896666: qemu-system-x86: page allocation failure: 4.15.0-0.bpo.2-amd64

Package: src:linux Version: 4.15.11-1~bpo9+1 Severity: important Dear Maintainer, * What led up to the situation? A vm was shut down by a script for a nightly backup (virsh shutdown ). When the script started the vm (virsh define , virsh start , virsh undefine ), the process failed,

Bug#886784: linux-image-4.14.0-0.bpo.2-amd64: apparmor blocks libvirtd

Package: src:linux Version: 4.14.7-1~bpo9+1 Severity: important Dear Maintainer, * What led up to the situation? New install of Debian 9.3.0 and linux-image-4.14.0-0.bpo.2-amd64. * What exactly did you do (or not do) that was effective (or ineffective)? Starting and stopping a

Bug#864714: task crm_node:15263 blocked for more than 120 seconds.

Package: src:linux Version: 4.9.30-2+deb9u2~bpo8+1 Severity: important Aug 08 23:14:25 vhost032 kernel: INFO: task crm_node:15263 blocked for more than 120 seconds. Aug 08 23:14:25 vhost032 kernel: Not tainted 4.9.0-0.bpo.3-amd64 #1 Debian 4.9.30-2+deb9u2~bpo8+1 Aug 08 23:14:25 vhost032

Bug#864714: task crm_node:16894 blocked for more than 120 seconds.

Package: src:linux Version: 4.9.30-2+deb9u2~bpo8+1 Severity: important Aug 09 03:39:08 vhost082 kernel: INFO: task crm_node:16894 blocked for more than 120 seconds. Aug 09 03:39:08 vhost082 kernel: Not tainted 4.9.0-0.bpo.3-amd64 #1 Debian 4.9.30-2+deb9u2~bpo8+1 Aug 09 03:39:08 vhost082

Bug#864714: task crm_node:12797 blocked for more than 120 seconds

Package: src:linux Version: 4.9.30-2+deb9u2~bpo8+1 Severity: important Dear Maintainer, Aug 04 09:46:19 vhost171 kernel: INFO: task crm_node:12797 blocked for more than 120 seconds. Aug 04 09:46:19 vhost171 kernel: Not tainted 4.9.0-0.bpo.3-amd64 #1 Debian 4.9.30-2+deb9u2~bpo8+1 Aug 04

Bug#864714: task systemd-machine:1262 blocked for more than 120 seconds.

Package: src:linux Version: 4.9.30-2+deb9u2~bpo8+1 Severity: important Dear Maintainer, Aug 02 21:25:14 vhost001 crmd[1359]: notice: State transition S_TRANSITION_ENGINE -> S_IDLE Aug 02 21:26:14 vhost001 systemd[1]: systemd-machined.service stop-sigterm timed out. Killing. Aug 02 21:27:13

Bug#864714: task crm_node:13269 blocked for more than 120 seconds.

Package: src:linux Version: 4.9.30-2+deb9u2~bpo8+1 Severity: important Dear Maintainer, Aug 03 03:35:05 vhost082 lrmd[1336]: warning: p-vs1-2_stop_0 process (PID 13403) timed out Aug 03 03:35:05 vhost082 lrmd[1336]: warning: p-vs1-2_stop_0:13403 - timed out after 6ms Aug 03 03:35:05

Bug#860808: ocfs2 blocks jbd2

Package: src:linux Version: 4.9.30-2~bpo8+1 Severity: important Jul 24 11:14:11 vhost032 kernel: WARNING: CPU: 5 PID: 16652 at /build/linux-PrKZyy/linux-4.9.30/fs/jbd2/transaction.c:297 start_this_handle+0x3fb/0x400 [jbd2] Jul 24 11:14:11 vhost032 kernel: Modules linked in: vhost_net vhost

Bug#841144: kernel BUG at /build/linux-PrKZyy/linux-4.9.30/fs/ocfs2/alloc.c:1514!

Package: src:linux Version: 4.9.30-2~bpo8+1 Severity: important Jul 20 08:02:45 vhost002 kernel: [ cut here ] Jul 20 08:02:45 vhost002 kernel: kernel BUG at /build/linux-PrKZyy/linux-4.9.30/fs/ocfs2/alloc.c:1514! Jul 20 08:02:45 vhost002 kernel: invalid opcode:

Bug#841144: kernel BUG at /build/linux-PrKZyy/linux-4.9.30/fs/ocfs2/alloc.c:1514!

Package: src:linux Version: 4.9.30-2~bpo8+1 Severity: important Jul 20 07:18:48 vhost002 kernel: [ cut here ] Jul 20 07:18:48 vhost002 kernel: kernel BUG at /build/linux-PrKZyy/linux-4.9.30/fs/ocfs2/alloc.c:1514! Jul 20 07:18:48 vhost002 kernel: invalid opcode:

Bug#841144: kernel BUG at /build/linux-PrKZyy/linux-4.9.30/fs/ocfs2/alloc.c:1514!

Package: src:linux Version: 4.9.30-2~bpo8+1 Severity: important Jul 20 06:50:09 vhost002 kernel: [ cut here ] Jul 20 06:50:09 vhost002 kernel: kernel BUG at /build/linux-PrKZyy/linux-4.9.30/fs/ocfs2/alloc.c:1514! Jul 20 06:50:09 vhost002 kernel: invalid opcode:

Bug#866385: ocfs2 dlm null pointer dereference

Package: src:linux Version: 4.9.25-1~bpo8+1 Severity: important Dear Maintainer, * What led up to the situation? Jun 29 04:15:42 vhost031 kernel: (kswapd0,97,0):ocfs2_unlock_ast:1135 ERROR: Dlm passes error -22 for lock N0011, unlock _action 2 Jun 29 04:15:42 vhost031 kernel:

Bug#860808: ocfs2 blocks jbd2

Package: src:linux Version: 4.9.30-2~bpo8+1 Severity: important Jun 29 01:00:07 vhost001 kernel: [ cut here ] Jun 29 01:00:07 vhost001 kernel: WARNING: CPU: 5 PID: 25562 at /build/linux-PrKZyy/linux-4.9.30/fs/jbd2/transaction.c:297 start_this_handle+0x3fb/0x400 [jbd2]

Bug#865524: task crm_attribute blocked for more than 120 seconds

Package: src:linux Version: 4.9.25-1~bpo8+1 Severity: important Jun 22 03:36:33 vhost082 kernel: INFO: task crm_attribute:32644 blocked for more than 120 seconds. Jun 22 03:36:33 vhost082 kernel: Not tainted 4.9.0-0.bpo.3-amd64 #1 Jun 22 03:36:33 vhost082 kernel: "echo 0 >

Bug#860808: ocfs2 blocks jbd2

Package: src:linux Version: 4.9.18-1~bpo8+1 Severity: important Jun 14 11:00:08 vhost242 kernel: [ cut here ] Jun 14 11:00:08 vhost242 kernel: WARNING: CPU: 5 PID: 6409 at /home/zumbi/linux-4.9.18/fs/jbd2/transaction.c:297 start_this_handle+0x3fb/0x400 [jbd2] Jun 14

Bug#860808: ocfs2 blocks jbd2

Package: src:linux Version: 4.9.25-1~bpo8+1 Severity: important Jun 13 10:30:13 vhost082 kernel: [ cut here ] Jun 13 10:30:13 vhost082 kernel: WARNING: CPU: 0 PID: 10866 at /home/zumbi/linux-4.9.25/fs/jbd2/transaction.c:297 start_this_handle+0x3fb/0x400 [jbd2] Jun 13

Bug#841144: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514!

Package: src:linux Version: 4.9.18-1~bpo8+1 Severity: important Jun 13 21:04:43 vhost242 kernel: [ cut here ] Jun 13 21:04:43 vhost242 kernel: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514! Jun 13 21:04:43 vhost242 kernel: invalid opcode: [#1] SMP

Bug#864714: task crm_node blocked for more than120 seconds.

Package: src:linux Version: 4.9.25-1~bpo8+1 Severity: important Jun 13 03:45:08 vhost012 kernel: INFO: task crm_node:26960 blocked for more than 120 seconds. Jun 13 03:45:08 vhost012 kernel: Not tainted 4.9.0-0.bpo.3-amd64 #1 Jun 13 03:45:08 vhost012 kernel: "echo 0 >

Bug#864714: task crm_node blocked for more than 120 seconds.

Package: src:linux Version: 4.9.25-1~bpo8+1 Severity: important Jun 13 03:37:10 vhost082 kernel: INFO: task crm_node:20251 blocked for more than 120 seconds. Jun 13 03:37:10 vhost082 kernel: Not tainted 4.9.0-0.bpo.3-amd64 #1 Jun 13 03:37:10 vhost082 kernel: "echo 0 >

Bug#860808: ocfs2 blocks jbd2

It has been reported several times. There doesn't seem to be any movement on it. All that remains is to document the situation. -- Russell Mosemann -Original Message- From: "Ben Hutchings" <b...@decadent.org.uk> Sent: Saturday, June 10, 2017 1:46pm To: "Russ

Bug#860808: ocfs2 blocks jbd2

Package: src:linux Version: 4.9.25-1~bpo8+1 Severity: important Jun 10 12:15:22 vhost012 kernel: [ cut here ] Jun 10 12:15:22 vhost012 kernel: WARNING: CPU: 0 PID: 10013 at /home/zumbi/linux-4.9.25/fs/jbd2/transaction.c:297 start_this_handle+0x3fb/0x400 [jbd2] Jun 10

Bug#860808: ocfs2 blocks jbd2

Package: src:linux Version: 4.9.25-1~bpo8+1 Severity: important Jun 10 12:09:36 vhost011 kernel: [ cut here ] Jun 10 12:09:36 vhost011 kernel: WARNING: CPU: 5 PID: 4311 at /home/zumbi/linux-4.9.25/fs/jbd2/transaction.c:297 start_this_handle+0x3fb/0x400 [jbd2] Jun 10

Bug#841144: kernel BUG at /home/zumbi/linux-4.9.25/fs/ocfs2/alloc.c:1514!

Jun 09 18:04:32 vhost012 kernel: [ cut here ] Jun 09 18:04:32 vhost012 kernel: kernel BUG at /home/zumbi/linux-4.9.25/fs/ocfs2/alloc.c:1514! Jun 09 18:04:32 vhost012 kernel: invalid opcode: [#1] SMP Jun 09 18:04:32 vhost012 kernel: Modules linked in: vhost_net vhost

Bug#841144: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514!

Package: src:linux Version: 4.9.18-1~bpo8+1 Severity: important May 21 18:48:42 vhost022 kernel: [ cut here ] May 21 18:48:42 vhost022 kernel: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514! May 21 18:48:42 vhost022 kernel: invalid opcode: [#1] SMP

Bug#841144: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514!

Package: src:linux Version: 4.9.18-1~bpo8+1 Severity: important May 17 18:56:17 vhost032 kernel: [ cut here ] May 17 18:56:17 vhost032 kernel: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514! May 17 18:56:17 vhost032 kernel: invalid opcode: [#1] SMP

Bug#841144: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514!

Package: src:linux Version: 4.9.18-1~bpo8+1 Severity: important May 17 14:02:13 vhost032 kernel: [ cut here ] May 17 14:02:13 vhost032 kernel: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514! May 17 14:02:13 vhost032 kernel: invalid opcode: [#1] SMP

Bug#841144: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514!

Package: src:linux Version: 4.9.18-1~bpo8+1 Severity: important May 17 14:30:45 vhost032 kernel: [ cut here ] May 17 14:30:45 vhost032 kernel: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514! May 17 14:30:45 vhost032 kernel: invalid opcode: [#1] SMP

Bug#841144: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514!

Package: src:linux Version: 4.9.18-1~bpo8+1 Severity: important May 17 12:43:27 vhost032 kernel: [ cut here ] May 17 12:43:27 vhost032 kernel: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514! May 17 12:43:27 vhost032 kernel: invalid opcode: [#1] SMP

Bug#841144: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514!

Package: src:linux Version: 4.9.18-1~bpo8+1 Severity: important May 17 10:39:30 vhost032 kernel: [ cut here ] May 17 10:39:30 vhost032 kernel: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514! May 17 10:39:30 vhost032 kernel: invalid opcode: [#1] SMP

Bug#841144: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514!

Package: src:linuxVersion: 4.9.18-1~bpo8+1Severity: important May 16 21:54:00 vhost032 kernel: [ cut here ] May 16 21:54:00 vhost032 kernel: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514! May 16 21:54:00 vhost032 kernel: invalid opcode: [#1] SMP May

Bug#862790: kernel: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/dlm/dlmast.c:306!

Package: src:linux Version: 4.9.18-1~bpo8+1 Severity: important Dear Maintainer, * What led up to the situation? May 16 19:20:49 vhost032 kernel: [ cut here ] May 16 19:20:49 vhost032 kernel: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/dlm/dlmast.c:306! May 16

Bug#841144: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514!

Package: src:linux Version: 4.9.18-1~bpo8+1 Severity: important Dear Maintainer, * What led up to the situation? May 16 17:26:31 vhost032 kernel: [ cut here ] May 16 17:26:31 vhost032 kernel: kernel BUG at /home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514! May 16

  1   2   >