Hello Debian Kernel Team,
I write direct to you, because people on the Freenode Chat seems to
ignore my request as its regarding to the kernel of the upcoming Release
"Buster"
I am running an Homeserver, with an ASUS KGPE-D16 Board with coreboot (
as many FOSS Groups use this platform for their S
Processing control commands:
> affects -1 libreswan
Bug #929938 [linux] linux: please enable CONFIG_XFRM_STATISTICS=y
Added indication that 929938 affects libreswan
--
929938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with p
X-Debbugs-Cc: Paul Wouters
Package: linux
Version: 4.19.37-3
Control: affects -1 libreswan
0 dkg@alice:~$ grep CONFIG_XFRM_STATISTICS /boot/config-4.19.0-5-amd64
# CONFIG_XFRM_STATISTICS is not set
0 dkg@alice:~$
Paul Wouters, Libreswan upstream developer says:
> Still this kernel option is t
Hi Mo and Theodore,
On Sun, Jun 2, 2019 at 4:04 AM Theodore Ts'o wrote:
> Also, it's not accurate that "linux developers didn't accept". Ryan
> sent a query to Linus, and Linus didn't respond. I don't know if he
> sent a single message, or whether he retried a couple of times. A
> failure to
Hi.
Thanks for bringing up this issue originally.
I think it has started some good discussion with the Debian zfs
maintainers.
However, I think this particular subthread about zfs has served its
purpose.
I cannot find anything in your message that is on topic for the
debian-devel mailing list.
Package: src:linux
Version: 4.19.37-3
Severity: normal
Sequence of events:
1. Notebook is rebooted properly, used for work for some hours
2. Notebook lid was closed, STR works as usual
3. Notebook opened; some work; lid close, STR works
4. Notebook was opened; NFS4 from remote machine mounted
#
# bts-link upstream status pull for source package src:linux
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #906180 (http://bugs.debian.org/906180
Processing control commands:
> severity -1 grave
Bug #929557 [src:linux] linux: restore __kernel_fpu needed for zfs for
AES-NI/AVX support [mainline not in debian yet]
Severity set to 'grave' from 'wishlist'
--
929557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929557
Debian Bug Tracking
control: severity -1 grave
Dear kernel maintainers,
Buster will be released with 4.19.37 kernel. That's fine
and it doesn't break ZFS. However, the changes introduced
in 4.19.38 and linux 5.0 break ZFS. That means the current
0.7.12-2 will fail to build everywhere after the first
Buster point rel
Control: severity -1 wishlist
On Mon, Jun 03, 2019 at 06:39:39PM -0700, Mo Zhou wrote:
> I believe this is a kernel bug. Instead of submitting
> a grave RC for the 10.1 release, we'd better sort it out
> right now before the Buster release.
We already stated that we wont change it by marking this
Processing control commands:
> severity -1 wishlist
Bug #929557 [src:linux] linux: restore __kernel_fpu needed for zfs for
AES-NI/AVX support [mainline not in debian yet]
Severity set to 'wishlist' from 'grave'
--
929557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929557
Debian Bug Track
An additional point of view. Prespective is Linux Kernel developer.
OOT means Out of Tree.
And the tree is the Linux source code directory tree.
- Forwarded message from "Enrico Weigelt, metux IT consult"
-
Date: Wed, 29 May 2019 13:01:09 +0200
From: "Enrico Weigelt, metux IT consult
Hi,
> linux (4.19.37-1) unstable; urgency=medium
(snip)
> * Import patches to enable loading keys from UEFI db and MOK from
> http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git to
> allow kernel modules built by users (eg: by dkms) to be verified, and
> to load dbx and
13 matches
Mail list logo
