If not going for marking the subtest flaky as in groovy, I have prepared
force-reset-test as alternatives in:
-
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390005
-
To match the open packages blocked on this in active releases I added
linux-meta for BIonic (thanks Kleber for the hint) and Focal (Thanks
Kelsey for the hint).
I think all of those had enough of retry-until-success and I'd ask again
for how we should proceed there. Masking/Resetting the test via
Hi Tim,
good to have this sorted out.
In this case please follow the guidance and questions I have put into comment
#2 and let us know the results.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--- B - Host changed, Guest stayed ---
In this case I think the biggest moving pieces are:
1. Host Kernel
2. Host qemu
3. Host libvirt (to a much smaller extend)
We can do some A/B tests to sort things out.
#1 install linux-generic-hwe-18.04 which will bring a 5.4 kernel to Bionic
#2,#3 install
--- A - Host stayed, Guest changed ---
If that is the case then we can mostly ignore the Host.
Never the less knowing the details what is used in the host is helpful.
As mentioned per your uname I assume you have `linux-kvm` used in the guest.
That is meant as a reduced kernel for virtual
Hi Neil,
thanks for the report.
I haven't seen/heard about this particular issue yet, maybe it is related to
the specific intel model and/or firmware version - so if you could derive that
from the host and let us know that might be helpful (if someone can find a
similar model to cross verify
Present on Debian, but not Ubuntu:
$ rma libcpupower-dev
libcpupower-dev | 4.9.228-1 | oldstable | amd64, arm64,
armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libcpupower-dev | 4.19.118-2+deb10u1~bpo9+1 | stretch-backports | amd64, arm64,
armel, armhf, i386,
Public bug reported:
I don't know how important that is as gkrellm2-cpufreq itself is scheduled for
removal.
But I wanted to make sure that it is known that the Debian kernel produces
"libcpupower-dev" which isn't available in Ubuntu and thereby blocking various
things in proposed.
The new update to "cpufreqd" now also build-depends on libcpupower-dev.
This is more common to be used, so the prio slightly increases IMHO.
OTOH cpufreqd already has delta, and we might as well try to build differently.
The package seems community/foundations maintained, but not in main.
Adding
Hi Rafael,
on the qemu side I think we are ready,
we have
CONFIG_VHOST_USER=y CONFIG_VHOST_KERNEL=y
already and also virtio-scsi already enabled.
vhost-net support yes
vhost-crypto support yes
On Qemu I'm waiting on:
a) Kernel Teams statement on backporting the commit mentioned
b) some testing (by the reporter if possible) of the referred PPA builds of
Qemu.
Setting to incomplete until we have that.
** Changed in: qemu (Ubuntu Focal)
Status: Triaged => Incomplete
--
You
# Kernel
It lists a bunch of depending kernel changes
40bc47b08b6e ("kvm: x86: Enumerate support for CLZERO instruction")
504ce1954fba ("KVM: x86: Expose XSAVEERPTR to the guest")
6d61e3c32248 ("kvm: x86: Expose RDPID in KVM_GET_SUPPORTED_CPUID")
52297436199d ("kvm: svm: Update
# Libvirt
Depending on the case sometimes libvirt also needs changes - Focal
already has /usr/share/libvirt/cpu_map/x86_EPYC.xml which contains the
base version and v3 will plug in there. But for "Epic-Rome" there isn't
anything upstream in libvirt.
I think this will therefore be non-selectable
-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: christian 1277 F pulseaudio
/dev/snd/pcmC0D0c: christian 1277 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop
: christian 1277 F pulseaudio
/dev/snd/pcmC0D0c: christian 1277 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 4 07:58:06 2020
InstallationDate: Installed on 2020-06-28 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa"
it is clear as mud.
Thanks for any advice or any working fix! And thank God for my wlan-
dongle!!!
Kind regards,
Christian.
--
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/1886247
Title
COMMAND
/dev/snd/controlC0: christian 1277 F pulseaudio
/dev/snd/pcmC0D0c: christian 1277 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 4 07:58:06 2020
InstallationDate: Installed on 2020-06-28 (5 days ago)
InstallationMedia: Ubuntu
mentioned, is there, I hope I will
recognize the fix. Kudos for everyone who's busy fixing the Lenovo / Realtek
issue!!
Kind regards,
Christian.
On Jul 5 2020, at 7:04 am, Daniel Letzeisen <1886...@bugs.launchpad.net> wrote:
> You may need to build your own rtw88 module from:
> https:
: christian 1277 F pulseaudio
/dev/snd/pcmC0D0c: christian 1277 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 4 07:58:06 2020
InstallationDate: Installed on 2020-06-28 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Rel
in linux package in Ubuntu:
In Progress
Status in linux source package in Eoan:
Fix Committed
Bug description:
SRU Justification
Impact: The patch
commit cfaa482afb97e3c05d020af80b897b061109d51f
Author: Christian Brauner
Date: Tue Apr 14 22:26:53 2020 +0200
UBUNTU: SAUCE
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
You received this bug notification because you are
** 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/1884635
Title:
lxc 1:4.0.2-0ubuntu1 ADT test failure with
Public bug reported:
SRU Justification
Impact: The patch
commit cfaa482afb97e3c05d020af80b897b061109d51f
Author: Christian Brauner
Date: Tue Apr 14 22:26:53 2020 +0200
UBUNTU: SAUCE: shiftfs: fix dentry revalidation
BugLink: https://bugs.launchpad.net/bugs/1872757
to fix https
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
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/1879688
Title:
shiftfs: fix btrfs snapshot deletion
Confirmed this is fixed:
brauner@wittgenstein|~
> lxc shell f1-vm
root@f1-vm:~# lxc shell f1
root@f1:~# btrfs subvolume create my-subvol
root@f1:~# chown 1000:1000 my-subvol
root@f1:~# btrfs subvolume delete my-subvol
Delete subvolume (no-commit): '/root/my-subvol'
** Tags removed:
In the meantime the Debian packaging was split and now comes from src:libbpf.
That in turn went into groovy and works well.
Thanks @fginther for making me aware.
This is done, I have closed the remaining tasks appropriately.
** Also affects: libbpf (Ubuntu)
Importance: Undecided
Hi You-Cheng,
thanks for your support.
I have removed pci=nocrs, but the touchpad did not work after reboot.
--
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/1881322
Title:
Touchpad not
Just to let you know, I got the touchpad on my Lenovo V15-IIL to work
with these boot parameters: i8042.nopnp=1 pci=nocrs
(Latest Bios dkcn29ww, Ubuntu Kernel 5.4.)
Hope this helps others, until the touchpad model gets recognized with
the default parameters. I got this info from
I am still affected by this bug on focal with intel gpu/hda on kernel
5.4.0-26
Adding the value to /etc/modprobe.d/alsa-base.conf does not help me
Linux Ashen-One 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
➜ ~ lspci -v
00:00.0 Host bridge: Intel
I'm experiencing the same behaviour under Ubuntu 18.04 with kernel
5.3.0-51-generic.
My mouse is the Logitech Performance MX and my keyboard is the Logitech
K800 (both connected to the Logitech USB unifying receiver)...
--
You received this bug notification because you are a member of Kernel
of subvolumes and only by userns root.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Christian Brauner (cbrauner)
Status: Confirmed
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Christian B
FYI - I'm facing a bug where it would have been really helpful to have
this fixed for better reporting. Therefore giving this nudge by pinging
here ...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
James, can you try this kernel, please: https://drive.google.com/open?id
=19iTwaFSYNS95_I-gD_rvFoV9cMAfy6io
--
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/1879196
Title:
'shifted'
So I've gone through codesearch on Debian and there are no users apart
from a bunch of defines for __NR_uselib when it isn't defined.
--
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/1879454
Public bug reported:
We're currently planning to be more proactive in deprecating the
uselib() syscall similar to how we deprecated the sysctl() syscall. This
will be a long process of course but the starting point is to set
CONFIG_USELIB=n in all new Ubuntu versions. I spoke to Eric and
I have a fix for this note, that this is a regression we introduced by
another fix. I also want to put this cautious note here so people better
understand why shiftfs has such bugs and why they are not simple idiot
regressions but rather intricate to fix:
Note, in general it's not advisable
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We assigned Andy back in last summer as he was working/talking about it.
But I have the assumption here it might be the case that everyone else thinks
"sure, this is on Andy I'll do nothing" and therefore overall nothing happens
on this.
Also I have checked the org-chart again and since this is
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1872094
Title:
shiftfs: broken shiftfs nesting
Status in linux
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1824719
Title:
shiftfs: Allow stacking overlayfs on top
Status
tus in linux package in Ubuntu:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact: Christian Kellner reported that creating temporary files via
O_TMPFILE shiftfs reports EST
** Tags removed: verification-needed-eoan verification-needed-focal
** Tags added: verification-done-eoan verification-done-focal
--
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/1872094
in linux package in Ubuntu:
In Progress
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact: Christian Kellner reported that creating temporary files via
O_TMPFILE shiftfs reports ESTALE
We are working on dpdk 19.11.3 and it would finally be nice to get this
delta resolved and XDP support in which required the libbpf I requested
here (well actually in 1826410 you all know the story).
... ping ... :-)
--
You received this bug notification because you are a member of Kernel
and the stable trees and can be
cherry-picked to bionic/linux.
commit 467d12f5c7842896d2de3ced74e4147ee29e97c8
Author: Christian Borntraeger
Date: Thu Feb 20 20:04:03 2020 -0800
include/uapi/linux/swab.h: fix userspace breakage, use
__BITS_PER_LONG for swap
[Testcase]
Install linux
As it seems the issue is neither triggered nor resolvable by qemu -
marking the bug task invalid.
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
.
commit 467d12f5c7842896d2de3ced74e4147ee29e97c8
Author: Christian Borntraeger
Date: Thu Feb 20 20:04:03 2020 -0800
include/uapi/linux/swab.h: fix userspace breakage, use
__BITS_PER_LONG for swap
[Testcase]
Install linux-libc-dev and build qemu.
[Regression Potential
Both fixes are in v4.19.0 and later
** Also affects: iproute2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: iproute2 (Ubuntu)
Status: New => Fix Released
** Changed in: iproute2 (Ubuntu Bionic)
Status: New => Triaged
** Changed in: iproute2 (Ubuntu
Yeah Dan, thanks for chiming in.
In particular that would be at least (but not lmited to) the changes:
8.04
Rework DTLS MTU detection. (#10)
7.08
Support automatic DTLS MTU detection with OpenSSL.
7.07
Automatic DTLS MTU detection.
Ubuntu has these newer versions.
Bionic 18.04 is on 7.08 and the
This is reported against 5.4.0-30.34 (in the guest I assume).
Per [1] that date window is the change from
2020-05-08 12:58:43 Published Focal proposedmaindevel
5.4.0-31.35
2020-05-08 13:00:19 Superseded Focal proposedmaindevel
5.4.0-30.34
2020-05-05 12:18:15
from ubuntu kernel,
upstream d5767057c9a)
Author: Yury Norov
Date: Thu Jan 30 22:16:40 2020 -0800
uapi: rename ext2_swab() to swab() and share globally in swab.h
Fixed by [2] (but missing in our proposed kernel)
commit 467d12f5c7842896d2de3ced74e4147ee29e97c8
Author: Christian
467d12f5c7842896d2de3ced74e4147ee29e97c8
Author: Christian Borntraeger
Date: Thu Feb 20 20:04:03 2020 -0800
include/uapi/linux/swab.h: fix userspace breakage, use
__BITS_PER_LONG for swap
This fix also is in 4.14 stable kernel as
ffd115f2dca955ce0782e801d488ecfaccde421f.
That should be the closest for our
467d12f5c7842896d2de3ced74e4147ee29e97c8
Author: Christian Borntraeger
Date: Thu Feb 20 20:04:03 2020 -0800
include/uapi/linux/swab.h: fix userspace breakage, use
__BITS_PER_LONG for swap
This fix also is in 4.14 stable kernel as
ffd115f2dca955ce0782e801d488ecfaccde421f.
That should
On Wed, May 06, 2020 at 10:32:19AM -, Kleber Sacilotto de Souza wrote:
> With the fixup patch applied, I could not reproduce the issue anymore on
> both Eoan and Focal running ubuntu_fan_smoke_test and
> ubuntu_docker_smoke_test.
Sweet, thank you and sorry for the rebase mess-up with Andrei's
Fix here:
https://lists.ubuntu.com/archives/kernel-team/2020-May/109617.html
--
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/1857257
Title:
linux-image-5.0.0-35-generic breaks
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Chris
Fix here:
https://lists.ubuntu.com/archives/kernel-team/2020-May/109617.html
--
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/1876645
Title:
Unable to handle kernel pointer dereference in
Yeah, that patch is buggy and I think this might've been my fault
actually. The fix should be:
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index 9d16fff5342a..fbec523a67c9 100644
--- a/fs/overlayfs/file.c
+++ b/fs/overlayfs/file.c
@@ -42,6 +42,7 @@ static struct file
Apologies, this only occurs from me when I don't have the POWER plugged
in. If I am on just battery it will just boot to a black screen, but
when plugged in to the charger it boots up just fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is
in linux package in Ubuntu:
In Progress
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact: Christian Kellner reported that creating temporary files via
O_TMPFILE shiftfs reports ESTALE
I am also experiencing this same issue on an Acer Aspire Slim 5. I
installed Ubuntu 20.04 server edition and then Mate-desktop on top of
that. It seems that I only experience this issue when I do not have
ethernet plugged in. With ethernet plugged in the system boots just fine
into the window
I get the same propblem on Ubuntu 20.04
uname -a
Linux christian-vie-ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
sudo lspci -vvnk -s 01:00.0
01:00.0 0280: 8086:2723 (rev 1a)
Subsystem: 8086:0084
Control: I/O- Mem+ BusMaster
The case with the module parameter in SEV needs a fix similar to
https://libvirt.org/git/?p=libvirt.git;a=commit;h=b183a75319b90d0af5512be513743e1eab950612
as it can be re-loaded at any time.
Essentially the checks in virQEMUCapsLoadCache check qemu/kernel version and
many other things.
They
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
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/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of
FYI:
19.04:
ii dmidecode 3.2-2amd64SMBIOS/DMI table decoder
$ sudo cat /sys/class/dmi/id/product_serial
VMware-42 18 59 50 7a fe ee b9-86 41 a6 c8 5a 5a 23 a6
$ sudo dmidecode | grep -i serial | grep VM
Serial Number: VMware-42 18 59 50 7a fe ee b9-86 41 a6 c8 5a 5a
Since ages qemu is locking the image files (I think since 18.04) and
that seems to block the command here.
IIRC Read-only readers can flag their open calls to skip that (e.g.
qemu-img has an option --force-share). Not sure what virt-clone uses
here, but whatever it is needs the similar treatment.
Agreed @cborntra, if that is your use case then those two ways are not
equivalent.
Then for now I only know of the "workaround to specify kernel/initramfs
directly" that you are aware of as well.
Let's see what feedback Andrew gets when asking to change the path back.
--
You received this bug
Actually the following works pretty well for getting to the old-style installer
on s390x.
Instead of a location to the install-dir, just hand it an ISO (can also be a
local file).
virt-install --name ubuntu20-guest1 --memory 4096 --vcpus 4 --disk
"size=4" --cdrom
in the function _set_url_paths it makes up the defaults:
# generic
url_prefix = "current/images"
...
# s390x specific as it can't find "normal" kernel/initrd there
hvmroot = "%s/generic/" % url_prefix
kernel_basename = "kernel.%s" % self._debname
That will construct
** Description changed:
SRU Justification
Impact: Christian Kellner reported that creating temporary files via
O_TMPFILE shiftfs reports ESTALE. This can be reproduced via:
import tempfile
import os
-
def test():
- with tempfile.TemporaryFile() as fd:
- fd.write
Public bug reported:
SRU Justification
Impact: Christian Kellner reported that creating temporary files via
O_TMPFILE shiftfs reports ESTALE. This can be reproduced via:
import tempfile
import os
def test():
with tempfile.TemporaryFile() as fd:
fd.write("data".enc
This should preferably be backported to all LTS kernels that support
shiftfs.
--
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/1872094
Title:
shiftfs: broken shiftfs nesting
Status in
to the lowers mount to get around vfs layering restrictions.
Regression Potential: Limited to shiftfs.
Test Case: Built a kernel with the mentioned fix and ran the reproducer.
The issue was not reproducible.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Christian Brauner
See
https://github.com/brauner/ubuntu-unstable/commits/2020-04-10/shiftfs_nesting
for fix.
--
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/1872094
Title:
shiftfs: broken shiftfs nesting
Same here, 20.04 beta, AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile
(Thinkpad t495s), upgraded from 19.10.
I have the same list of 24 missing amdgpu modules as the previous
poster.
This bug really needs re-working and yet it's status is set to "Fix
Released" (which I can't seem to be able to
Thanks David, so it might be issues with special HW types.
I'm glad you identified quirks to loas uas with to mitigate the issue - this
might help others being affected.
But until I have a local reproducer to debug in-depth I'm not sure I can
do more on the libvirt side (and even then no
On March 27, 2020 10:57:17 PM GMT+01:00, Seth Forshee
wrote:
>Applied the patches from linux-next, plus one additional fix I saw,
>"sysfs: fix static inline declaration of sysfs_groups_change_owner()".
>@Christian, please let me know if there are any other fixes we need to
&
There is no power box free this week, but indeed I'm +1 as well.
Test results look good as well (I've re-run them just to be extra sure) btw:
prep (x86_64): Pass 20 F/S/N 0/0/0 - RC 0 (15 min 55036 lin)
migrate (x86_64) : Pass 288 F/S/N 0/0/0 - RC 0 (60 min 214809 lin)
cross (x86_64)
Chances are high that this -fixed was brought in via a bug/discussion,
lets check the changelog to find it.
9 gcc-9 (9.3.0-1) unstable; urgency=medium
...
16 * Stop shipping the include-fixed directory.
...
Hmm, there is a very suspicious dir showing up:
echo "#include " | gcc -E -Wp,-v -
ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu"
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/include"
#include "..." search starts here:
this still had one indirection
this is even better:
$ cat > test.c << EOF
> /*
> * Test FTBFS 1867316
> */
>
> #include
> EOF
ubuntu@focal-ftbfs:~/chrony-3.5$ gcc -c test.c
In file included from test.c:5:
/usr/include/limits.h:124:26: error: no include path in which to search for
limits.h
** Changed in: alsa-topology-conf (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: alsa-ucm-conf (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
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/1860041
Title:
shiftfs: prevent lower dentries from going
That's an old version, sorry. It's already in Dave's tree. The merge commit is
here:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=ebb4a4bf76f164457184a3f43ebc1552416bc823
--
You received this bug notification because you are a member of Kernel
Packages, which
The patch series has been acked upstream and is sitting in Dave Miller's
tree. We should backport it to 5.4!
--
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/1865359
Title:
sysfs:
Public bug reported:
SRU Justification
Impact:
patchsets.)
We have been struggling with a bug surrounding the ownership of network
device sysfs files when moving network devices between network
namespaces owned by different user namespaces reported by multiple
users.
Currently, when moving
Ping for FF closing in and this holding back some DPDK functionality.
Any updates on getting this in time into 20.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/1836708
Title:
I have a brand new ThinkPad t495s (Ryzen 7 Pro 3700U) with a fresh Eoan
deployment, which exhibits exactly the behaviour described in this
ticket. AFAIK everything is up-to-date. Am I doing smth wrong or is
there an issue with this fix? Please let me know if I can provide
further evidence or
The mentioned commit 6ab79a20af3a7b3bf610ba9aebb446a9f0b05930 is in qemu 4.1
and later.
Since we will have qemu 4.2 in 20.04 please retry with that once available.
I'll set a bug tak reference in the changelog of the update.
** Tags removed: qemu-19.10
** Tags added: qemu-20.04
--
You received
ng vfs_unlink() on it and dput() it afterwards.
Regression Potential: Limited to shiftfs.
Test Case: Compiled a kernel with the fix and used the reproducer above
to verify that the kernel cannot be crashed anymore.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Christian B
OK, let's try with the Broadcom first -- I've sent email and copied you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1859223
Title:
Firmware missing for Thinkpad X-series
** Summary changed:
- Firmware missing for Thinkpad X-series Bluetooth adapters, heads to headset
HSP/HFP profiles not working
+ Firmware missing for Thinkpad X-series Bluetooth adapters, leads to headset
HSP/HFP profiles not working
--
You received this bug notification because you are a
Note that I've found dozens of posts on the web that describe the same
symptom, and a subset of those arrive at the same conclusion of this
bug. I do agree that the license that the github repo holds indicates
that the files are made available for personal use, but perhaps we can
address that.
For my laptop, which is an x230 model 2325KZ5, I have:
Bus 001 Device 004: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0
[ThinkPad]
The file which I needed to use was brcm/BCM20702A1-0a5c-21e6.hcd as
noted above. That is the only file needed to fix my issue.
The post I linked to is for
Public bug reported:
Hello there, it's my third or fourth session spending hours trying to
debug why a Bluetooth headset would not work in HSP/HFP mode on my x230.
The failure more is super obscure because at the time of error the only
thing you notice is that no audio comes through in either
to_cpu(udev->descriptor.idProduct) == 0x3082) ||
(le16_to_cpu(udev->descriptor.idProduct) == 0xa387)))
set_bit(LENOVO_MACPASSTHRU, >flags);
works for me.
Regards,
Christian
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
On Tue, Jan 07, 2020 at 07:07:36PM -, Andrew Vagin wrote:
> The root cause of this fail is a wrong mount ID which is reported for
> file mappings:
If you have cycles to come up with a patch to fix this that would be
appreciated. Otherwise this will end up lower in my priority queue since
my
Thank you for your report.
This looks like a valid warning to me, rather than a bug in Ubuntu.
Also the bug lacks some details to go any further on it.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug tracker to track
Yep, agreeing tho You-Sheng.
People are seeing this when e.g. using lm-sensores as it will trigger the hwmon
interfaces which have plenty of these old calls.
Here an example list:
Documentation/hwmon/hwmon-kernel-api.rst:27:
hwmon_device_register_with_groups(struct device *dev, const char
Same issue on my laptop:
[8.498382] [ cut here ]
[8.498387] Could not determine valid watermarks for inherited state
[8.498448] WARNING: CPU: 2 PID: 185 at
/build/linux-dWhjJj/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537
401 - 500 of 1329 matches
Mail list logo
