Package: src:linux
Version: 4.9.2-2~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
The server had unexpectedly rebooted. Upon reboot, several DRBD drives were
resynching when the bug was exposed. The system was forced to reboot, again.
Feb 15 07:53:47 vhost172
Package: src:linux
Version: 4.8.11-1~bpo8+1
Severity: critical
Dear Maintainer,
* What led up to the situation?
Jan 15 17:31:03 vhost032 kernel: [ cut here ]
Jan 15 17:31:03 vhost032 kernel: kernel BUG at
/build/linux-Wgpe2M/linux-4.8.11/fs/ocfs2/alloc.c:1514!
Jan 15
Package: src:linux
Version: 4.9.13-1~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
Mar 25 06:14:44 vhost082 kernel: [ cut here ]
Mar 25 06:14:44 vhost082 kernel: kernel BUG at
/home/zumbi/linux-4.9.13/fs/ocfs2/reservations.c:507!
Mar
Package: src:linux
Version: 4.9.13-1~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
Mar 19 10:00:16 vhost242 kernel: [ cut here ]
Mar 19 10:00:16 vhost242 kernel: kernel BUG at
/home/zumbi/linux-4.9.13/fs/ocfs2/alloc.c:1514!
Mar 19
Package: src:linux
Version: 4.9.13-1~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
Apr 01 16:00:08 vhost342 kernel: [ cut here ]
Apr 01 16:00:08 vhost342 kernel: kernel BUG at
/home/zumbi/linux-4.9.13/fs/ocfs2/alloc.c:1514!
Apr 01
Package: src:linux
Version: 4.9.13-1~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
Apr 20 12:03:24 vhost002 kernel: [ cut here ]
Apr 20 12:03:24 vhost002 kernel: WARNING: CPU: 1 PID: 19193 at
Package: src:linux
Version: 4.9.2-2~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
Mar 02 08:00:13 vhost172 kernel: [ cut here ]
Mar 02 08:00:13 vhost172 kernel: kernel BUG at
/home/zumbi/linux-4.9.2/fs/ocfs2/alloc.c:1514!
Mar 02
Package: src:linux
Version: 4.9.2-2~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
Mar 07 13:43:35 vhost172 kernel: JBD2: qemu-system-x86 wants too many credits
credits:175114 rsv_credits:0 max:16384
Mar 07 13:43:35 vhost172 kernel: [ cut here
Package: src:linux
Version: 4.9.13-1~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
Mar 14 10:00:55 vhost032 kernel: [ cut here ]
Mar 14 10:00:55 vhost032 kernel: kernel BUG at
/home/zumbi/linux-4.9.13/fs/ocfs2/alloc.c:1514!
Mar 14
Package: src:linux
Version: 4.9.13-1~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
Mar 14 10:58:55 vhost012 kernel: [ cut here ]
Mar 14 10:58:55 vhost012 kernel: kernel BUG at
/home/zumbi/linux-4.9.13/fs/ocfs2/alloc.c:1514!
Mar 14
Package: src:linux
Version: 4.9.2-2~bpo8+1
Severity: important
Dear Maintainer,
Please fix this bug. It exists in multiple kernel versions. It locks the file
system until hard reboot.
* What led up to the situation?
Mar 07 09:00:24 vhost012 kernel: [ cut here ]
Package: src:linux
Version: 4.9.2-2~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
Mar 02 14:30:10 vhost172 kernel: [ cut here ]
Mar 02 14:30:10 vhost172 kernel: kernel BUG at
/home/zumbi/linux-4.9.2/fs/ocfs2/alloc.c:1514!
Mar 02
Package: src:linux
Version: 4.9.2-2~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
Mar 02 11:30:09 vhost172 kernel: [ cut here ]
Mar 02 11:30:09 vhost172 kernel: kernel BUG at
/home/zumbi/linux-4.9.2/fs/ocfs2/alloc.c:1514!
Mar 02 11:30:09
Package: src:linux
Version: 4.9.2-2~bpo8+1
Severity: important
Dear Maintainer,
This is utterly ridiculous.
* What led up to the situation?
Mar 02 17:30:09 vhost172 kernel: [ cut here ]
Mar 02 17:30:09 vhost172 kernel: kernel BUG at
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:
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:
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:
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
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]
Package: src:linux
Version: 4.9.18-1~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
Apr 29 00:10:08 vhost192 kernel: [ cut here ]
Apr 29 00:10:08 vhost192 kernel: WARNING: CPU: 7 PID: 18835 at
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
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
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
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
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
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
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
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
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
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
Package: src:linux
Version: 4.9.18-1~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
May 13 08:00:06 vhost012 kernel: [ cut here ]
May 13 08:00:06 vhost012 kernel: WARNING: CPU: 5 PID: 1853 at
package: src:linux
Version: 4.9.18-1~bpo8+1
Severity: important
Is anyone from ocfs2 addressing these bugs?
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
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 >
Package: src:linux
Version: 4.9.18-1~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
May 16 14:26:06 vhost032 kernel: [ cut here ]
May 16 14:26:06 vhost032 kernel: kernel BUG at
/home/zumbi/linux-4.9.18/fs/ocfs2/alloc.c:1514!
May 16
Package: src:linux
Version: 4.9.18-1~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
May 16 14:57:46 vhost032 kernel: [ cut here ]
May 16 14:57:46 vhost032 kernel: WARNING: CPU: 5 PID: 10628 at
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
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 >
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 >
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
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
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
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
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
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
Package: src:linux
Version: 4.9.18-1~bpo8+1
Severity: important
Dear Maintainer,
* What led up to the situation?
May 01 23:16:23 vhost032 kernel: [ cut here ]
May 01 23:16:23 vhost032 kernel: WARNING: CPU: 10 PID: 6435 at
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
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,
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
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
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
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
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
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
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
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:
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
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
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
aste bytes: 695281951
file data blocks allocated: 3067911655424
referenced 6563527507968
--
Russell Mosemann
after a reboot sometimes triggers the
same bug, and sometimes it works fine.
--
Russell Mosemann
with the same file results in the same
hang.
--
Russell Mosemann
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
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
. 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
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
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
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
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
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
> >
&
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
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
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
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
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
75 matches
Mail list logo
