** Attachment added: "journalctl-full.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018448/+attachment/5671132/+files/journalctl-full.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Public bug reported:
Hi,
in lunar (haven't tried others yet), the laptop screen flickers every few
minutes, and I get these errors in dmesg when that happens:
[qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on
pipe A: 0x0080
[qui mai 4 22:07:56 2023] i915 :00:0
@koba, thanks for your kinetic testing. The [test plan] however also has
this bit:
"""
The thermald log should indicate version 2 is being used with the message:
"ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64
values that are parsed and ignored.
"""
Did you observe that
More info:
https://lore.kernel.org/lkml/1bb01e6c-3829-6af4-b2c5-5dc82bd75...@lenovo.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2008188
Title:
blacklist: Problem blackli
There is no need for logs for this issue, so setting the bug back to
"confirmed".
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Public bug reported:
The qxl kernel module is present in linux-modules-extra, which is not
installed by default using cloud images.
The scenario that breaks is if you want to have an ubuntu desktop in a
VM. Since we don't have a desktop image, you start by deploying the
normal image, and then ins
Public bug reported:
I upgraded my kinetic raspiberry pi4 to lunar, and to my surprise the
zfs module is missing:
root@pi4:~# apt-file find zfs.ko
linux-modules-6.2.0-1002-aws: /lib/modules/6.2.0-1002-aws/kernel/zfs/zfs.ko
linux-modules-6.2.0-1002-azure: /lib/modules/6.2.0-1002-azure/kernel/zfs/z
Public bug reported:
I don't know what's wrong with this package, or with the kernel package:
ubuntu@l-crash:~$ sudo crash -st /usr/lib/debug/boot/vmlinux-6.1.0-16-generic
WARNING: /usr/lib/debug/boot/vmlinux-6.1.0-16-generic
and /proc/version do not match!
WARNING: /proc/version indi
On jammy, it works on btrfs:
root@nsn7:/mnt# rm -f foo.img; touch foo.img; fallocate -z -l 10M foo.img; ls
-lah foo.img
-rw-r--r-- 1 root root 10M abr 19 10:46 foo.img
root@nsn7:/mnt# mount -t btrfs
/btrfs.img on /mnt type btrfs
(rw,relatime,ssd,space_cache=v2,subvolid=5,subvol=/)
--
You rece
I applied zfs_fallocate_reserve_percent=0 to the kernel module,
confirmed it was set, but I still see the same incorrect behavior with
fallocate:
root@nsn7:/tank/test# rm -f foo.img; touch foo.img; fallocate -z -l 10M
foo.img; ls -lah foo.img
-rw-r--r-- 1 root root 0 abr 19 10:35 foo.img
root@ns
Impish kernel on zfs:
andreas@nsnx:~$ rm foo.img
andreas@nsnx:~$ touch foo.img
andreas@nsnx:~$ fallocate -z -l 10M foo.img
fallocate: fallocate failed: Operation not supported
Jammy kernel on zfs:
root@j1:~# touch foo.img
root@j1:~# fallocate -z -l 10M foo.img
root@j1:~# ll foo.img
-rw-r--r--
The impish kernel returns "not supported" when fallocate is used in the
way mysql does it. That makes mysql aware of the problem, and switch
strategies, and it works.
The jammy kernel is saying all is fine with the call and its results,
but it isn't. Mysql, or any userspace, shouldn't be second gu
I see you are running the kvm kernel flavor, and indeed I don't see the
nfsd.ko module, nor a package named like linux-modules-extra-kvm, which,
in the case of the other cloud kernels, does have nfsd.ko.
I'm changing this bug to be about the linux kernel, as they can answer
best why nfsd.ko is not
I just switched to an analog headset, and the periodic loud chirping
noise I had on my usb headset (impish kernel) is gone.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1966432
Title:
> This disabled NFS3 support seems only to affect the client part of
the kernel-module.
NFSv3 is fine, it's udp that is disabled in the kernel (I think you
understood that, and above is just a typo, but clarifying nonetheless).
Clients running a kernel with CONFIG_NFS_DISABLE_UDP_SUPPORT=y shoul
Are you sure it's using udp? Did you confirm with /proc/mounts or mount
output? I didn't get it to work, not even with a focal server, and the
kernel option disabling UDP sounds very adamant.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I added this to the Jammy 22.04 release notes at
https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668
If it's decided to flip this option before release, please remove that
release notes remark.
--
You received this bug notification because you are a member of Kernel
Packages, whic
This was first disabled on groovy, the first ubuntu release after focal:
root@g1:~# grep NFS /boot/config-5.8.0-59-generic |grep UDP
CONFIG_NFS_DISABLE_UDP_SUPPORT=y
The upstream help text next to that kernel option says:
"""
Choose Y here to disable the use of NFS over UDP. NFS over UDP
on moder
Found this in /boot/config-$(uname -r):
CONFIG_NFS_DISABLE_UDP_SUPPORT=y
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964093
Title:
nfsver=3,udp not working anymore
Status in linux
I restored nfs-utils 1.x in the jammy client, and tried to mount again.
It still fails. I don't think this is an nfs-utils problem:
ubuntu@j-nfs-dep8:~$ dpkg -l|grep nfs
ii libnfsidmap2:amd64 0.25-6build1 amd64
NFS idmapping library
ii nfs-common
Kernel team, is it safe to revert the order today for jammy?
I.e., can we apply this to the wireguard-tools package:
--- a/debian/control
+++ b/debian/control
@@ -18,7 +18,7 @@ Rules-Requires-Root: no
Package: wireguard
Architecture: all
Depends:
- wireguard-dkms (>= 0.0.20200121-2) | wireguard
In my pi4 case, I reverted to a previous kernel and didn't see the
problem anymore. I was seeing it during snapshot send, though, I didn't
to a full `find /storage` and touch every single file to confirm the
problem was gone.
--
You received this bug notification because you are a member of Kerne
I reproduced it in bionic with hwe kernel, and a privileged docker
container with iptables 1.8.3, with host networking. Didn't try other
versions yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu.
https://bu
I know it's been a long time, but can you still get to the version of
iptables that's running inside the k8s pod that is inserting these
rules? I assume it was kube-router?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-5.4
I'm on a PI4, where the latest impish kernel is linux-
image-5.13.0-1009-raspi 5.13.0-1009.10 and I saw the bug
there. I reverted to kernel linux-image-5.11.0-1021-raspi
5.11.0-1021.22 and was able to mount my encrypted datasets again.
The kernel versioning seems to be different in the p
This change regressed my apparmor profile for a script I'm working on,
which walks over processes using python3-psutil, in bionic.
I have this config in the apparmor profile:
capability sys_ptrace,
ptrace trace,
With kernel 4.15.0-154-generic #161 it works.
With kernel 4.15.0-158-generic #1
postgresql-common amd64 and i386: passed after a retry
ubuntu-fan: see previous comment, known flaky test, and analysis of the test
output shows that the test actually passed. I retried both amd64 and s390x, but
I ask the SRU team to consider those runs green if they failed again (update:
amd64
This was fixed in 0.12.11 by adding allow-stderr to the dep8
restrictions. Last affected ubuntu release is bionic and earlier.
Closing the bug.
** Changed in: ubuntu-fan (Ubuntu)
Status: New => Fix Released
** Changed in: ubuntu-fan (Ubuntu)
Status: Fix Released => Confirmed
--
Yo
ubuntu-fan dep8 failures are due to
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1830180. It
was fixed in focal+, but in bionic it remains flaky. Explanation is in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-
fan/+bug/1830180/comments/1
I'll retry it once or twice, but we can see
Actuall, the bug was specifically about bionic, so let's adjust the
tasks.
** Also affects: ubuntu-fan (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: ubuntu-fan (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: ubuntu-fan (Ubuntu)
Status: Confirmed
This happens because systemd-resolve --status $nic can be called in this loop
before it's ready to answer:
while [ $timeout -gt 0 ]; do
dns2=$(systemd-resolve --status $nic1| \
awk '/DNS Serv
*** This bug is a duplicate of bug 1884110 ***
https://bugs.launchpad.net/bugs/1884110
This is fixed already:
linux-meta-raspi (5.4.0.1014.15) focal; urgency=medium
* linux-image-raspi provides zfs modules only for arm64 (LP: #1886682)
- [Packaging] Only provide zfs for arm64
-- Juer
When this happens, do you see "arc prune" or "z_upgrade" processes in
top, using a lot of cpu?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1889110
Title:
zfs pool locks and see "I
I marked it incomplete so it will expire on its own if there is no new
information, but feel free to actually close it if you prefer ("invalid"
is fine).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
+1, this is not like sarnold's crash-with-every-snapshot-send
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1870559
Ti
Sorry, I mistook this for a comment on another zfs bug that I was
watching.
I haven't seen that crash again since the day I reported it. Since it's so rare
(happened just once), do you think it's worth it to try the kernel from the
ppa? I'd rather not stay away from the official focal kernel fo
Adding zfs to the pi kernel was discussed and rejected in the past:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852119
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/18
For what is worth, I also have the arc_prune eating cpu problem. I
thought it was because my "machine" has just 3Gb of RAM, but this report
makes me think there is something wrong in that area with zfs 0.8.x,
since you have what, 64Gb of RAM?
The same 3Gb machine didn't have any such problems with
zfs-dkms was not being used, I had no need for it on this machine. I
only have zfs-dkms in my pi4, since the ubuntu kernel there doesn't
include the zfs module.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Sorry, I've since reinstalled the server. The same pool is there, and
it's still focal, but the OS disk was reinstalled. I used it to test the
subiquity server installer.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Public bug reported:
I was transferring my zfs snapshots to the backup server, when suddenly
it stalled. I checked dmesg on the server and found a "kernel bug"
entry.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-21-generic 5.4.0-21.25
ProcVersionSignature: Ubuntu 5.4.0-
Good to know, thanks. Maybe something in the reboot process is exporting
these extra pools, causing them to be removed from the cache.
Have you guys also tried editing /etc/default/zfs and listing your extra
pool(s) there? Specifically:
# List of pools that SHOULD be imported at boot by the initr
Did you run "zpool export " before rebooting? IIRC that
removes it from the cache file.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850130
Title:
zpools fail to import after rebo
In other words, boot, import the pool, and reboot without exporting it.
Sorry if you did that already, I just skimmed the bug and jumped to the
last comment.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs
Public bug reported:
While updating my focal server this morning, I got a dpkg prompt about
/etc/default/zfs. Inspecting the diff showed some paths changed from
/etc to /usr/local/etc:
...
Setting up zfsutils-linux (0.8.3-1ubuntu2) ...
** Tags added: update-excuse
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852122
Title:
ocfs2-tools is causing kernel panics in Ubuntu Focal
(Ubuntu-5.4.0-9.12)
Status in OCFS2 Too
Just got this update in focal:
https://launchpad.net/ubuntu/+source/zfs-linux/0.8.2-3ubuntu5
* Add support for for hardware-accelerated encryption (LP: #1857040)
and include faster KABI checks and restructuring backports to
ease the backporting effort.
Backport of upstream ZFS commits:
This bug is requesting that the pi kernel be shipped with zfs, so zfs-
dkms is not needed:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852119
The pi4 can have up to 4Gb of RAM, that's a good start for zfs. I'm
using the dkms package for now, but hoping that this request is
addres
It's just the release notes task of this bug that is marked as fixed,
meaning the release notes got an entry about this known problem.
On Wed, Jan 1, 2020, 15:34 Gerald Hopf wrote:
> Why is this tagged as fixed when obviously it was never fixed?
>
> --
> You received this bug notification becau
*** This bug is a duplicate of bug 1851858 ***
https://bugs.launchpad.net/bugs/1851858
** This bug has been marked a duplicate of bug 1851858
adds ESM to sources.list.d unconditionally, despite it being x86-only
--
You received this bug notification because you are a member of Kernel
Pack
Hm, at first glance this didn't work with the new kernel and zfsutils-
linux package:
root@nsn7:/zfs-test# zfs diff tank/d1@s1 tank/d1
Unable to determine path or stats for object 3 in tank/d1@s1: File exists
root@nsn7:/zfs-test# uname -a
Linux nsn7 5.3.0-21-generic #22-Ubuntu SMP Tue Oct 29 22:55
Eoan verification
First, reproducing the bug:
root@nsn7:~# mkdir /zfs-test
root@nsn7:~# cd /zfs-test/
root@nsn7:/zfs-test# truncate -s 10G file.img
root@nsn7:/zfs-test# zpool create -o ashift=12 -O acltype=posixacl -O
compression=lz4 -O xattr=sa -O normalization=formD -O dnodesize=auto tank
$(
This is the PR to backport the master fix into 0.8.2:
https://github.com/zfsonlinux/zfs/pull/9515
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845018
Title:
SIMD broken in 0.8.1
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849665
Title:
zfs diff: Unable to determine path or stats for object
Status in zfs-linux package in Ubuntu:
In Progress
Bu
Public bug reported:
Eoan 19.10
zfsutils-linux 0.8.1-1ubuntu14
kernel 5.3.0-19-generic #20-Ubuntu
When using zfs diff on an encrypted dataset, I frequently encounter this
error:
# zfs diff nsnx/trusty-2a@snap1 nsnx/trusty-2a
+ /nsnx/trusty-2a/bin
Unable to determine path or stats for objec
Yeah, on eoan I get:
$ cat /proc/spl/kstat/zfs/fletcher_4_bench
0 0 0x01 -1 0 4250112835 2191051355493
implementation native byteswap
scalar 7121128976 5682673600
superscalar 9132158207 6984205638
superscalar4 8279361738 6770847284
fast
comment #4 suggested that the panic only happened because
kernel.softlockup_panic was set to 1, was that verified?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1846237
Title:
Kernel Pa
Setting linux task to triaged, as there are commits to pick up. Xen I'm
still unsure.
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
iproute2 is handled by the kernel team nowadays, due to its close ties
with the kernel itself. Unsubscribing ubuntu-server for that reason.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute
I installed linux-source in disco, applied those two patches to the
source tree, copied the config file from /boot and rebuilt the kernel,
rebooted, and can confirm the bug is fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
These two patches applied in that order fix the issue:
https://lore.kernel.org/linux-cifs/20190321045902.14326-1-lsahl...@redhat.com/t/#u
https://lore.kernel.org/linux-cifs/cah2r5ms_md9uosm5x0acamtz2zhiu0+hvvzzjf2pgzqyxny...@mail.gmail.com/
--
You received this bug notification because you are a
Extra patch to be applied on top:
https://lore.kernel.org/linux-
cifs/cah2r5ms_md9uosm5x0acamtz2zhiu0+hvvzzjf2pgzqyxny...@mail.gmail.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/182
Thanks for the build. Unfortunately, that patch didn't work. I followed
up in the mailing list.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821053
Title:
[disco] [5.0.0-7.8] can't mo
A patch was provided:
https://lore.kernel.org/linux-
cifs/20190321045902.14326-1-lsahl...@redhat.com/t/#u
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821053
Title:
[disco] [5.0.0-7.
It didn't work :/
same error.
I enabled some cifs debugging
(https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting):
# modprobe cifs
# echo 'module cifs +p' > /sys/kernel/debug/dynamic_debug/control
# echo 'file fs/cifs/* +p' > /sys/kernel/debug/dynamic_debug/control
# echo 7 > /proc/fs/cif
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1821053/+attachment/5247955/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1821053/+attachment/5247956/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1821053/+attachment/5247954/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821053
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1821053/+attachment/5247957/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Tags added: apport-collected uec-images
** Description changed:
Hi,
with a simple smb.conf setup like this:
[pub]
path = /pub
guest ok = yes
The following mount command fails when the running kernel is 5.0.0-7:
root@ubuntu:~# dmesg -C
root@ubuntu:~# mo
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1821053/+attachment/5247959/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1821053/+attachment/5247958/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821053
If I force the SMB1 protocol (vers=1.0), then the mount works:
root@ubuntu:~# mount //localhost/pub /mnt -o guest,vers=1.0
root@ubuntu:~# mount -t cifs
//localhost/pub on /mnt type cifs
(rw,relatime,vers=1.0,sec=none,cache=strict,uid=0,noforceuid,gid=0,noforcegid,addr=127.0.0.1,soft,unix,posixpat
Public bug reported:
Hi,
with a simple smb.conf setup like this:
[pub]
path = /pub
guest ok = yes
The following mount command fails when the running kernel is 5.0.0-7:
root@ubuntu:~# dmesg -C
root@ubuntu:~# mount //localhost/pub /mnt -o guest
mount error(13): Permission denied
Refer to the mount
Another alternative would be to have vesa specify a working bpp value,
if that is the only problem there.
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Adding a test for xorg for their consideration.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1818879
Title:
pull cirrus.ko into main kernel package
Status in linux package in Ubuntu:
Public bug reported:
In disco, xorg stopped shipping a cirrus module/driver, instead relying
on the kernel one. But the kernel one is in the linux-modules-
extra--generic package, which is not installed by default in
vms.
That breaks some assumptions: uvtool, for example, doesn't specify a
video
** Bug watch added: github.com/pmem/ndctl/issues #78
https://github.com/pmem/ndctl/issues/78
** Also affects: ndctl via
https://github.com/pmem/ndctl/issues/78
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, w
** Changed in: linux-kvm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1788336
Title:
Failed to install nfs-kernel-server package on KVM ker
So, in Cosmic (18.10) it's fixed, but remains in Xenial (16.04) and
Bionic (18.04)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1767857
Title:
Kernel 4.4.0-122 Breaks qemu-system-x86
Aug 22 04:15:58 zeppo mount[3580]: mount: unknown filesystem type 'nfsd'
Can you check these please:
root@xenial-nfs:~# find /lib/modules -name 'nfsd.ko'
/lib/modules/4.4.0-138-generic/kernel/fs/nfsd/nfsd.ko
root@xenial-nfs:~# dpkg -S /lib/modules/4.4.0-138-generic/kernel/fs/nfsd/nfsd.ko
linux-i
Is there something to be done in the user space pmdk component for this
bug, or is it purely a kernel issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799237
Title:
mprotect fails
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubunt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1780872
Title:
wake on lan is not working
Status in linux package in
** Package changed: ethtool (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1780872
Title:
wake
Adding a linux task for the kernel team to consider dropping that empty
line, that was perhaps added by mistake.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
The kernel aspect of this is being tracked in another bug: #1772671
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1773383
Title:
iotop crashes on l
** Changed in: ethtool (Ubuntu)
Importance: Undecided => Low
** Changed in: ethtool (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
T
Do you get a notice in dmesg when you don't specify the version at mount
time?
On Fri, Apr 27, 2018, 03:05 Walter Cheuk wrote:
> Same problem happened to Ubuntu 16.04.5. I have to specify "vers=1.0" to
> mount a NAS drive successfully. The help said the default version is
> 1.0, so I spent a lot
I'm seeing files (ok, one file) disappear from a share when it's mounted
with vers=3.0. But it's not a top-level share, it's just
"c:\Shares\jsmith" on a windows 2016 server:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1764778/comments/15
--
You received this bug notification because you
clamav explicitly mentions ifupdown in a debconf question regarding how
the user would like freshclam (updating the virus signatures db) to
work. One of the options is a ifupdown hook attached to what the user
calls "the internet interface". That option should be removed, or better
yet, migrated to
bind9 in bionic at least detects nic changes and does not need to be
reloaded.
Interface being removed:
Mar 28 13:59:04 bionic-bind9 named[7098]: no longer listening on
192.168.122.138#53
Interface being added:
Mar 28 13:59:04 bionic-bind9 named[7098]: listening on IPv4 interface ens7,
192.168.
Confirmed that qemu in bionic does not have that commit yet. Subscribing
ubuntu-server for consideration.
** Changed in: qemu (Ubuntu Bionic)
Status: New => Triaged
** Changed in: qemu (Ubuntu Bionic)
Importance: Undecided => Wishlist
** Tags added: server-next
--
You received this b
This feature is being developed in https://github.com/panlinux/ubuntu-
advantage-script/tree/livepatch-motd
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1710976
Title:
Livepatch motd e
** Changed in: update-notifier (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Zesty will be EOL before we can push this fix out, marking it as "won't
fix"
** Changed in: ubuntu-fan (Ubuntu Zesty)
Status: Confirmed => Won't Fix
** Changed in: ubuntu-fan (Ubuntu Bionic)
Importance: Critical => Undecided
** Changed in: ubuntu-fan (Ubuntu Artful)
Status: Inco
The bug exists in artful and bionic, it's probably just not as critical
as it was ifupdown systems like xenial and zesty.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
I mean, I can see the error in netplan systems like artful, but maybe
the impact there is different and local to ubuntu-fan only:
root@04-57:~# fanctl up -a
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting
primary: " (32-)/4 "
--
You received this bug notification becaus
I can see that ubuntu-fan in zesty, artful and bionic needs this patch,
but I can't determine if it's actually hit by this bug.
artful, for example, will use netplan in a fresh install, not e-n-i. Are
these releases really affected by this bug?
--
You received this bug notification because you a
I installed the updated package on an existing maas server on
xenial/amd64, and deployed a new node (also xenial/amd64) where I also
installed the updated package plus some server software. No visible side
effects.
--
You received this bug notification because you are a member of Kernel
Packages,
101 - 200 of 221 matches
Mail list logo
