ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: serge 1046 F pulseaudio
/dev/snd/pcmC1D0p: serge 1046 F...m pulseaudio
/dev/snd/controlC0: serge 1046 F pulseaudio
CasperMD5CheckResult
/dev/snd/controlC1: serge 1046 F pulseaudio
/dev/snd/pcmC1D0p: serge 1046 F...m pulseaudio
/dev/snd/controlC0: serge 1046 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Fri Nov 10 13:23:37 2023
InstallationDate: Installed on 2020-12-06
Package: linux-image-5.15.0-86-generic 5.15.0-86.96
ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
Uname: Linux 5.15.0-84-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: serge 1046 F
/controlC1: serge 1046 F pulseaudio
/dev/snd/pcmC1D0p: serge 1046 F...m pulseaudio
/dev/snd/controlC0: serge 1046 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Fri Nov 10 13:23:37 2023
InstallationDate: Installed on 2020-12-06 (1068 days
:
USERPID ACCESS COMMAND
/dev/snd/controlC2: serge 2070 F pulseaudio
/dev/snd/controlC0: serge 2070 F pulseaudio
/dev/snd/controlC1: serge 2070 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Nov 26 11:41:24 2023
DpkgTerminalLog:
Preparing
-image-5.15.0-86-generic 5.15.0-86.96
ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
Uname: Linux 5.15.0-84-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: serge 1046 F pulseaudio
: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: serge 1046 F pulseaudio
/dev/snd/pcmC1D0p: serge 1046 F...m pulseaudio
/dev/snd/controlC0: serge 1046 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Fri Nov 10 13:23:37 2023
Wtf? Why status "Fix Released"? How it works?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2034477
Title:
Keyboard and Touchpad Not Working in New Lenovo V15 Gen4
Lenovo V15 G4 AMN (82YU00UCRA) - AMD Ryzen 3 7320U - same problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2034477
Title:
Keyboard and Touchpad Not Working in New
I would like to report that with -32 kernel sound works fine and -35
does not in a more complex configuration. AMD RX 560 is bypassed into a
virtual machine using IOMMU. A display port connection is used.
I'm attaching 'sudo lspci -nvvv' for -32 and -35 kernels invoked from
the virtual machine.
ctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
Installation
e 'systemctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
Instal
ctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
InstallationDate:
ctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
InstallationDate:
ctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
Installat
e 'systemctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
Instal
e 'systemctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
assume the 'systemctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ub
e 'systemctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
Instal
ctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
InstallationDate:
ctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
Installation
ctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
InstallationDate:
ctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
Installation
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:
ctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
Installation
ctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
InstallationDate:
e 'systemctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
assume the 'systemctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ub
ctl disable
dnsmasq is doing), but that did not work for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 3929 F pulseaudio
DistroRelease: Ubuntu 22.04
InstallationDate:
for me.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.2
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: serge 3929 F pulseaudio
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-02-25 (283 days ago)
+ In
> Fwiw, I think you need index=on enabled for origin xattrs to be set.
Did try that, no difference. Anyway I probably just need to take a
closer look at what exact operations are done under /etc/rc*.d when
disabling a service... I'm sure I'm missing something obvious.
--
You received this bug
Public bug reported:
This was reported (and worked around) in https://github.com/project-
stacker/stacker/pull/333.
The kernel does not allow user.* xattrs on a symlink. However, on
5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu mainline
build (6.1.0-060100rc5-generic), an
*** This bug is a duplicate of bug 1772985 ***
https://bugs.launchpad.net/bugs/1772985
Forgot to add. This does not appear to affect my ability to connect to
my wifi.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in
*** This bug is a duplicate of bug 1772985 ***
https://bugs.launchpad.net/bugs/1772985
Any update on this? I did a messy upgrade of 18.04 LTS from 16.04 LTS.
I have one package left to upgrade and consistently get this error:
serge@serge-X551MA:~$ sudo apt upgrade
[sudo] password for serge
Using dkms manually:
sudo dkms install -m nvidia -v 390.116 -k 5.3.0-26-generic
DKMS make.log for nvidia-390.116 for kernel 5.3.0-26-generic (x86_64)
lundi 20 janvier 2020, 22:05:02 (UTC+0100)
make[1] : on entre dans le répertoire « /usr/src/linux-headers-5.3.0-26-generic
»
test -e
I confirm: /lib/modules/5.3.0-26-generic/updates is missing
--
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/1860306
Title:
Linux kernel 5.3.0-26 breaks nvidia driver
Status in linux
My syslog:
Jan 20 21:20:26 pollux gpu-manager[997]: Error: can't open
/lib/modules/5.3.0-26-generic/updates/dkms
Jan 20 21:20:27 pollux gpu-manager[997]: Error: can't open
/lib/modules/5.3.0-26-generic/updates/dkms
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You
It is notable to see so much Fujitsu Siemens hardware affected.
I have the same issue with the onboard USB 2.0 of a Fujitsu Siemens P710 E90+
Intel i5 3470 desktop computer.
The problem occurs with any of my Varmilo VA88M keyboards, but not with
a Cherry Cymotion G-224. The Varmilo keyboards
The fixing commit 0f90603c33bdf6575cfdc81edd53f3f13ba166fb
is included into 4.16.4 according to
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.16.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have tested with latest 4.17.3-generic (since do not like to boot the
box with rc). I cannot reproduce the bug with 4.17.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member
apport information
** Tags added: apport-collected bionic
** Description changed:
Kernel: linux-image-4.15.0-23-generic
Ubuntu: 18.04
Hardware: Lenovo ThinkPad X1 Yoga 2nd,
model 20JD0026RT
Basically the bug is
https://bugs.freedesktop.org/show_bug.cgi?id=100378
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1779199/+attachment/5157529/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Kernel: linux-image-4.15.0-23-generic
Ubuntu: 18.04
Hardware: Lenovo ThinkPad X1 Yoga 2nd,
model 20JD0026RT
Basically the bug is
https://bugs.freedesktop.org/show_bug.cgi?id=100378
https://bugs.freedesktop.org/show_bug.cgi?id=105196
Downgrade to the latest mainline kernel
Can anyone confirm that only laptops with Insyde BIOS are affected?
I have Lenovo Yoga X1 2nd gen with Phoenix BIOS and booted it into
17.10. Fortunately, I do not observe the symptoms.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I have same problem with my ElementaryOS 0.4.1 based on Ubuntu 16.04.
Kernel - 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC 2017
CPU - i5-3210M
I upgaded bluetoothctl from 5.37 to 5.46, but problem still exists.
$ dmesg | grep -i blue
[3.113911] usb 1-1.2: Product: Bluetooth USB
orld
echo "unmounting,"
umount /mnt
echo "disconnecting,"
cleanup
echo "Done"
failed=0
echo PASS
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F
echo "Done"
failed=0
echo PASS
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate:
ot;
+ umount /mnt
+ echo "disconnecting,"
+
+ cleanup
+
+ echo "Done"
+ failed=0
+
+ echo PASS
+
+
+ ---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: serge 1399 F pulseaudio
+ US
dmremove the devices)
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
Instal
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
Installation
pportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
InstallationMedia:
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
Installation
pportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
InstallationMedia:
dmremove the devices)
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
dmremove the devices)
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
dmremove the devices)
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
Instal
dmremove the devices)
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
Instal
pportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
InstallationMedia:
dmremove the devices)
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
Instal
dmremove the devices)
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
Instal
pportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: serge 1399 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-15 (41 days ago)
InstallationMedia: Xubunt
/dev/snd/controlC0: serge 1399 F pulseaudio
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 17.04
+ InstallationDate: Installed on 2017-09-15 (41 days ago)
+ InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ IwConfig:
+ lxcbr0no wireless exte
Public bug reported:
I've been trying this on several platforms -
16.04 physical host
16.04 VMware
17.04 vmware
The script pasted below creates a virtual disk, writes a partition
table, creates an fs and some thin pools, then verifies that writes
happened as expected.
On 16.04 physical host it
I've seen reports that this is fixed in 4.10?
--
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/882147
Title:
overlayfs does not implement inotify interfaces correctly
Status in coreutils
Nope, tail -f is still broken at least in 4.12.
--
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/882147
Title:
overlayfs does not implement inotify interfaces correctly
Status in
I observe the same problem with
Ubuntu 16.04.02, Kernel 4.8.0.49 and Network card Intel X520-DA2 (10GbE)
I don't see that problem with Ubuntu 16.04.02 Kernel 4.8.0.36
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
-63 works for me as well, thank you!
--
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/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
Status in linux package in Ubuntu:
Just re-tested. The z kernel builds fine. the yakkety-proposed kernel
still fails to build:
cc1: fatal error:
/home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h:
No such file or directory
compilation terminated.
--
You received this bug notification because you
** Tags added: bot-stop-nagging
** 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/1641168
Title:
packaging error in
Public bug reported:
When I try to build the kernel source from yakkety-updates locally, I
get failure like:
cc1: fatal error:
/home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h:
No such file or directory
** Affects: linux (Ubuntu)
Importance: Undecided
net.ifnames=0 biosdevname=0 works for me on xenial/amd64
4.4.0-36-generic
--
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/1545441
Title:
Xenial/4.4 kernel does not honor biosdevname=0
Please open a new bug - thanks.
--
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/1448269
Title:
qemu guest hangs on nested kvm startup with host kernel oops
Status in linux package in
Thanks for the info.
If updating kernels fixes it, then it's possible, but unlikely, that it
can be fixed in userspace. Marking this as affecting the kernel.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** 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/1602443
Title:
Bad page state in qemu-system-x86 process
How do you figure verification needed? See comment #3.
** Tags removed: verification-needed-xenial
--
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/1584163
Title:
cgroup namespace
I recommend opening new bugs against libvirt and docker. Libvirt moves
VMS into a cpuset by default. I assume docker does the same. (My
xenial laptop runs upstart, so this is not systemd's doing)
--
You received this bug notification because you are a member of Kernel
Packages, which is
"LXC cases, like docker and KVM" - did you mean non-lxc cases?
xenial by default should now be using libpam-cgfs, should not be using
cgmanager, and should not be creating cpusets.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
With xenial kernel:
132 125 0:57 /lxc/x1 /sys/fs/cgroup/blkio
rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,blkio,nsroot=/lxc/x1
with xenial-proposed kernel:
134 125 0:59 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime -
cgroup cgroup rw,blkio
** Tags removed:
Public bug reported:
During xenial cycle we applied a patch (and a followon fix for criu)
to fix a usability problem with cgroup namespaces and /proc/self/mountinfo.
Since then, the approach to fix it upstream has changed. Please revert
the two nsroot patches currently in xenial and yakkety,
** Changed in: lxc (Ubuntu Xenial)
Status: Confirmed => Invalid
** No longer affects: lxc (Ubuntu Vivid)
** No longer affects: lxc (Ubuntu Wily)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for reporting this bug. The 'kvm' package shouldn't really
exist. The bug you're referring to is in the kernel kvm code, so I'm
marking it as affecting the kernel. (If it were in the userspace qemu
package, then the 'qemu' package would be the right bug target).
** Package changed: kvm
Thanks for reporting this bug. The 'kvm' package shouldn't really exist.
The bug you're referring to is in the kernel kvm code, so I'm marking it
as affecting the kernel. (If it were in the userspace qemu package, then
the 'qemu' package would be the right bug target).
** Package changed: kvm
@leftyfb - what exactly is IBM asking to verify? Whether kvm works
under powervm? Did smoser's info help?
--
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/1563887
Title:
Ok so if I'm following this right there are two issues:
1. the bug reporter is using a powervm partition. KVM cannot be used
there. This is not a KVM bug.
2. the xenial cloud images have an outdated 4.2 kernel which doesn't
boot in kvm on powernv. A workaround is to use the isos which do
If you can reproduce this with the ppc64 xenial iso or a rootfs
installed from that, using 4.4 kernel, please let us know. Otherwise,
I think the fix will be for cloud images to be updated with a 4.4 kernel.
--
You received this bug notification because you are a member of Kernel
Packages,
4.4.0-16 also works.
** Also affects: livecd-rootfs (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/1563887
Title:
qemu-system-ppc64
Actually the clou dimages have a 4.2 kernel. When I use a xenial beta2
iso which has 4.4.0-15-generic #31, it boots fine. I can install, and I
can boot the installed image (with same kernel) just fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Result of doing qemu-system-ppc64 -m 1024 -vnc :1 -net nic -net
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries
-drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive
file=my-seed.img,if=virtio
** Attachment added: "crash.png"
Hm - I can boot a wily cloud image, just not a xenial one.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
I see the same problem with 2 different m/b:
Asus X99-A and Asus Z97-A
I can see the problem with Kernels 3.16 and 3.19.
Does anyone have a work-around, such as changing USB parameters in the
BIOS?
I also see that a complete power down temporarily fixes the issue.
Also woth noting: my Z97-A
** 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/1558897
Title:
guest vm hangs
Status in linux package in
Sorry, I had forgotten my own workaround for this.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu)
Status: Won't Fix => Invalid
--
You received this bug notification
Ok, this is happening because lxc, for privileged containers, bind-
mounts /proc/sys and /proc/sys/net onto themselves. This prevents later
unprivileged mounting of /proc.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sorry, testcase in #8 is invalid, bc lxc-usernsexec doesn't create a new
pid namespace, so mount is denied because we do not own our
pidns->userns.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Simplest way to reproduce:
sudo systemctl stop proc-sys-fs-binfmt_misc.automount # (just to be sure)
unshare -mpf
mount --make-rslave /
mount -t proc proc /proc
lxc-usernsexec
# mount -t proc proc /proc # permission denied, regardless what -o options may
pass.
--
You received this bug
Current wily kernel is giving me the same behavior.
--
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/1543367
Title:
nested unprileged container fails to start at mounting /proc
Status in
Upstream kernel still fails:
lxc-start 20160304193125.498 ERRORlxc_conf -
conf.c:lxc_mount_auto_mounts:742 - Operation not permitted - error mounting
proc on /usr/lib/x86_64-linux-gnu/lxc/proc flags 14
lxc-start: conf.c: lxc_mount_auto_mounts: 742 Operation not permitted - error
Note - I am not actively looking at this bug as I've not managed to
reproduce it. Hopefully the kernel team has it under control, please
shout if I'm needed.
If using juju first is a prerequisite to reproducing this, I can try
that, but my impression from previous reports has been that this is
@sforshee,
Because in the past mountall would fail if we didn't.
--
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/1551854
Title:
LXD bootstrap issues on xenial
Status in linux package
@sforshee - are you saying that removing the debugfs line from
/usr/share/lxc/config/ubuntu-common.conf fixes this for you?
--
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/1551854
Title:
1 - 100 of 327 matches
Mail list logo
