** 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/1999229
Title:
mlx5 VF LAG flapping
Status in linux package in
Public bug reported:
Getting a call trace below with the 5.17.0-1003-oem OEM kernel.
HW: Lenovo 21D4000HUS
WNIC: 04:00.0 Network controller: Qualcomm QCNFA765 Wireless Network
Adapter (rev 01)
~$ uname -r
5.17.0-1003-oem
ноя 03 10:22:47 dz16 kernel: wlp4s0: send auth to aa:46:8d:38:07:9d
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628252/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628250/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628253/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628248/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628251/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628249/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628247/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628246/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628245/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628244/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628243/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628241/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628239/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628238/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628242/+files/Lsusb.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/1995207
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628240/+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/1995207
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5628237/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Description changed:
Gnome shell crashed while I was doing web browsing.
A crash report was also submitted via apport. This is a fresh install of
Ubuntu 22.10.
~$ uname -r
5.19.0-23-generic
HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H
As far as looking at the practice of using stateless offload for
tunneled traffic:
I can see that there were tests performed on Intel HW in upstream OpenStack
with TX & TSO features enabled (albeit with VXLAN tunnels):
Marked this bug as invalid for charm-octavia and added Linux since this
is either a driver problem with bnxt and BCM57414 or a firmware issue.
The card in question: https://buy.hpe.com/us/en/options/adapters/host-
adapters/proliant-host-adapters/hpe-ethernet-10-25gb-2-port-
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: charm-octavia
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
753-mlx5e/H/
I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
passed with positive feedback.
[Where problems could occur]
If this pa
lin/kernel/lp-1957753-mlx5e/H/
I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
passed with positive feedback.
[Where problems could oc
tps://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
passed with positive feedback.
[Wh
And, finally, the Jammy kernel:
$ uname -r
5.15.0-17-generic
$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0
$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
**
Impish kernel looks good:
$ uname -r
5.13.0-28-generic
$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2
$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0
--
You received this bug notification because you are a member of Kernel
Packages,
Hirsute kernel looks good as well:
$ uname -r
5.11.0-50-generic
$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2
$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0
--
You received this bug notification because you are a member of Kernel
Focal:
$ uname -r
5.4.0-97-generic
$ sudo ip link set enp130s0f0 vf 2 vlan 1
RTNETLINK answers: Operation not permitted
$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0
Looks good - vlan 0 programming doesn't result in EPERM as expected
contrary to non-zero vlans.
Will try others as
Public bug reported:
There is an issue with hypervisor host side mlx5 driver operation on
Bluefield devices in kernels <=5.16 that was recently fixed in master
with a one-liner:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
** 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/1918583
Title:
Switch to libgpiod and disable CONFIG_GPIO_SYSFS
Public bug reported:
Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153
debian.master/config/config.common.ubuntu: CONFIG_GPIO_SYSFS=y
However, this interface got deprecated for removal:
Recently hit that on Focal due to the fact that quotas were enabled by
LXD.
This renders the system completely unresponsive if you use btrfs as a
rootfs with btrfs-transaction or btrfs-cleaner kernel threads hogging a
100% of 1 CPU core.
Booting using a live USB, disabling quotas and temporarily
** Tags added: champagne
--
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/1838151
Title:
Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing
wide band speech support.
Sandor,
Not on the VRF usage side but there is a feature in MAAS 2.6 to have a
better way to work in multi-homed environments (for bionic+ machines):
https://docs.maas.io/2.6/en/intro-new
"Networking - Multiple default gateways"
It relies on "routing policy database" (RPDB) functionality
Setting to 'Confirmed' as the issue was fixed upstream and this is a
backport request.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- bcache device is accessible even if a backing device is not (writeback mode)
+ [4.15] bcache device is accessible
Public bug reported:
This is a request for a backport of the following upstream patch from
4.18:
"bcache: stop bcache device when backing device is offline"
https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee
Field engineering uses bcache quite extensively and it
Tried using direct kernel boot with QEMU and couldn't reproduce it:
sha256sum
/mnt/libvirt-images/boot-resources-20190419-115735/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-initrd
69ca457a119fe309d315972ca2756a17bd9bc55bc98f2bea5542566a7f41b08f
The bionic/ga files from #63 need to be placed into both dirs:
1) /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-18.04/bionic/daily
2) /var/lib/maas/boot-resources/current/ubuntu/amd64/generic/bionic/daily
The sha256 of the *initrd file* that triggers the issue is
tar -czvf boot-resources-20190419-115735-amd64-generic-bionic.tar.gz
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/
** Changed in: qemu (Ubuntu)
Status: Confirmed => 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/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes
Tested bionic-hwe - the issue does not occur with 2048 MiB.
The closest issue filed upstream I found is this:
https://bugzilla.kernel.org/show_bug.cgi?id=199845
** Bug watch added: Linux Kernel Bug Tracker #199845
https://bugzilla.kernel.org/show_bug.cgi?id=199845
--
You received this bug
Found something interesting.
Bionic + 2048 MiB of RAM (bad):
[1.520243] Unpacking initramfs...
[ 14.712821] Initramfs unpacking failed: broken padding
[ 14.723088] Freeing initrd memory: 56636K
Bionic + 2049 MiB of RAM (good):
[0.752624] Unpacking initramfs...
[5.572407]
I cannot reproduce the same with a xenial (GA kernel) image with 2048
MiB of RAM allocated to a VM.
So it seems to me that this is a kernel issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The kernel code path mentioned in #55 is only executed if there is no
"early userspace init" - in other words, if there is no /init on initrd:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/init/main.c?id=Ubuntu-4.15.0-47.50#n1087
/*
* check if
echo -n
'BOOT_IMAGE=http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/boot-kernel
nomodeset ro
root=squash:http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/squashfs
ip=maas-vhost6:BOOTIF ip6=off overlayroot=tmpfs
overlayroot_cfgdisk=disabled
Just reproduced it on my env (where things used to work) after updating
from MAAS 2.5.0~rc2 to 2.5.2.
https://paste.ubuntu.com/p/CY834ZGnvS/
[ 15.458594] VFS: Cannot open root device
"squash:http://10.10.101.2:5248/images/ubuntu/amd64/generic/bion; or
unknown-block(0,0): error -6
tree
Had this with nvidia graphics drivers after installing and then removing
proprietary drivers downloaded from nvidia website. I could not log in
at all at first boot.
If you see nvidia modules loaded, make sure that you select an xorg
session on the login screen (not wayland) if you this control
nvidia-xconfig -generated xorg.conf looked like this
https://paste.ubuntu.com/p/4hRVzHmbJV/
--
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/1785964
Title:
Unable to unlock the desktop
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219760/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219756/+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/1807140
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219755/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219762/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219761/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219758/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The information above is from a VM with a reproducer.
** 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/1807140
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219757/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219763/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219759/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected uec-images
** Description changed:
I ran into a problem with the console argument handling on a physical
system with a BMC (Dell R610) and also reproduced the same behavior on a
QEMU/KVM VM with multiple serial ports.
The kernel
** Description changed:
I ran into a problem with the console argument handling on a physical
system with a BMC (Dell R610) and also reproduced the same behavior on a
QEMU/KVM VM with multiple serial ports.
- The kernel documentation notes that the last entry will
+ The kernel
Public bug reported:
I ran into a problem with the console argument handling on a physical
system with a BMC (Dell R610) and also reproduced the same behavior on a
QEMU/KVM VM with multiple serial ports.
The kernel documentation notes that the last entry will
Got similar behavior with windows server 2012r2 VMs.
Environment:
uname -a
Linux ubuntu-q87 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ii linux-image-4.13.0-36-generic
4.13.0-36.40~16.04.1
Dup:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728256
https://bugs.launchpad.net/qemu/+bug/1728256/comments/11
This affects other guests like W2k12r2 and Windows 10 as well.
** Tags added: cpe-onsite
--
You received this bug notification because you are a member of Kernel
** 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/1728256
Title:
Memory corruption in Windows 10 guest / amd64
John,
Interfaces of a host carry enough information to be used to make routing
decisions - that's the core idea of host and router-side VRF
implementations. Network spaces as of now do not help you to solve
routing problems in any way unless you have one big L2 network and
"routing" is done
One additional detail. Even on 4.15 "Unhandled alg" can be reproduced
occasionally after disconnecting and reconnecting the adapter to an STA:
дек 22 22:12:45 blade kernel: iwlwifi :3b:00.0: Unhandled alg: 0x707
дек 22 22:12:45 blade kernel: iwlwifi :3b:00.0: Unhandled alg: 0x707
дек 22
Tested 9260NGW with different kernels (-33 for 4.13, -34 for 4.14 and
4.15):
1) 4.13.0-21.24 + iwlwifi-9260-th-b0-jf-b0-33.ucode: could not connect
to any network, "Unhandled alg: 0x707"
wlp59s0: associated
and then immediately
deauthenticating from ...
see https://paste.ubuntu.com/26234416/
I can confirm this behavior on 4.13 -> 4.15rc4 with Intel 9260NGW.
3b:00.0 Network controller: Intel Corporation Device 2526 (rev 29)
Subsystem: Intel Corporation Device 0014
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at dd20 (64-bit, non-prefetchable)
Andres,
I'm not going to be at the sprint but the problems described need a
proper solution in MAAS and Juju at least from the end host perspective.
Similar to how VLANs are supported natively in MAAS & Juju, L3
virtualization technologies like VRF should be as well. I hope the
information I will
*** This bug is a duplicate of bug 1737640 ***
https://bugs.launchpad.net/bugs/1737640
** This bug has been marked a duplicate of bug 1737640
/usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured
interfaces cause ifup failures
--
You received this bug notification
Tested that on a "broken" environment (after a reboot with a broken
package):
root@maas-xenial3:~# apt install ubuntu-fan
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
ubuntu-fan
1 upgraded, 0 newly
This is reproducible on a machine with a single NIC:
https://paste.ubuntu.com/26170595/
** Summary changed:
- bridge activaction error: bridge activation failed | unconfigured interfaces
cause ifup failures
+ /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured
interfaces
Before and after ifdown -> ifup with fan:
http://paste.ubuntu.com/26169937/
After purging:
http://paste.ubuntu.com/26169950/
--
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
ubuntu-fan clearly triggers the problem.
Clean machine, no bridges after Juju installs ubuntu-fan and networking
still works as bridges were not created yet => no ifup/down executions:
root@maas-xenial3:/home/ubuntu# ifdown -a ; ifup -a
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic
** Description changed:
Problem description:
* a host is multi-homed if it has multiple network interfaces with L3
addresses configured (physical or virtual interfaces, natural to
OpenStack regardless of IPv4/IPv6 and IPv6 in general);
+
+ (see 3.3.4 Local Multihoming
+
** Description changed:
Problem description:
* a host is multi-homed if it has multiple network interfaces with L3
addresses configured (physical or virtual interfaces, natural to
OpenStack regardless of IPv4/IPv6 and IPv6 in general);
* if all hosts that need to participate in L3
For Ubuntu kernel this is a backport request.
--
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/1737428
Title:
VRF support to solve routing problems associated with multi-homing
Status in
Public bug reported:
Problem description:
* a host is multi-homed if it has multiple network interfaces with L3
addresses configured (physical or virtual interfaces, natural to
OpenStack regardless of IPv4/IPv6 and IPv6 in general);
* if all hosts that need to participate in L3 communication
Looks like masking systemd-udevd removes this behavior. Need to figure
out where it actually clears everything out.
ubuntu@maas-xenial4:~$ sudo systemctl mask systemd-udevd
11:32 PM Created symlink from /etc/systemd/system/systemd-udevd.service to
/dev/null.
# reboot
ubuntu@maas-xenial4:~$ ls
Ryan,
As discussed in IRC, I tweaked locations for testing in #11 and added
all paths in #14.
Looks like after `mount -n -o move /dev ${rootmnt}/dev` ${rootmnt}/dev
has the proper content (see the bcache rule as well)
https://paste.ubuntu.com/26082611/
== before ==
lrwxrwxrwx113
Just in case also checked with this rule that creates links at /dev
/dev/disk/by-uuid /dev/bcache/by-uuid https://paste.ubuntu.com/26081756/
They are all there originally (see the screenshot).
But not there afterwards. So it's not just a problem with a different
path.
After booting with break=bottom kernel parameter I can see that symlinks
are in fact present at the initramfs stage.
They are gone afterwards post pivot_root & systemd start (the bcache dir
isn't even present while it was there)
ubuntu@maas-xenial4:~$ ls /dev/disk/
by-dname by-id by-label
We do run udevd at the initramfs stage in init-top and stop it in init-
bottom:
➜ scripts git:(ubuntu/xenial-updates) ✗ grep -RiP udev
init-bottom/udev:# Stop udevd, we'll miss a few events while we run init, but
we catch up
init-bottom/udev:udevadm control --exit
So, the kernel fix could look like this:
* instead of just failing with "device already registered"
* the kernel would emit another uevent with CACHED_UUID which would be
processed another time to set up a symlink
It seems like this approach with "synthetic uevents" may be used for
other
I reviewed this once again:
1. persistent /dev/bcache - not possible or needed due to how kernel
enumeration works
2. our userspace handles /dev/by-dname/ properly so we just need
CACHED_UUID given to us during coldplug in some way to properly create
/dev/bcache/by-uuid/ symlinks and
Marcos,
#68
Regardless of fastboot on/off I get the same behavior without
pcie_aspm=off
➜ ~ uname -r
4.13.0-16-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/1521173
Title:
** Tags added: cpe-onsite
--
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/1729145
Title:
/dev/bcache/by-uuid links not created after reboot
Status in linux package in Ubuntu:
Triaged
So, going back to question in #60, the Dell link just says to get the
latest stuff from kvalo's firmware repo.
If you are on 17.10 like myself then you already have it and it doesn't
help with the original problem:
➜ ~ apt policy linux-firmware
linux-firmware:
Installed: 1.169
Candidate:
There's also Intel 9260 coming up (wave 2):
https://wikidevi.com/wiki/Intel_Dual_Band_Wireless-AC_9260_(9260NGW)
Judging by this https://communities.intel.com/message/506847#506847 it's
only available for OEMs as of now so maybe those will go into
circulation soon for regular folks.
Meanwhile,
There is a scenario where a real rootfs is located on a bcache device,
however, for that we need to register a bcache device at the initrd
stage which already happens now. Then we'd locate a file system on it
and do pivot_root and so on.
The bcache naming, I believe, is not guaranteed at this
Just to clarify on UUIDs - there are 3 types of UUIDs in question:
1. cache set UUIDs (upstream docs mention that multiple cache devices per cache
set are not supported but a configuration with M:N as in
: has been taken into account)
2. cache device superblock UUIDs;
3. backing device
Public bug reported:
I wanted to test a snap application called clementine and opened up
preferences after it was launched and playing music. After clicking on
something my whole system hanged.
Regardless of the app, I decided to lookup how something like that could
manage to "kill" the whole
Haven't noticed that issue on previous kernels although I was mostly
using NVIDIA GPU not integrated intel GPU as in this case.
I will try to reproduce this on 4.14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Haven't noticed that issue on previous kernels although I was mostly
using NVIDIA GPU not integrated intel GPU as in this case.
I will try to reproduce this on 4.14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
окт 06 13:49:20 blade kernel: asynchronous wait on fence
i915:gnome-shell[2505]/1:42b timed out
окт 06 13:49:21 blade kernel: [drm] GPU HANG: ecode 9:0:0x96dbccee, in
qtdemux0:sink [5106], reason: Hang on rcs0, action: reset
окт 06 13:49:21 blade kernel: [drm] GPU hangs can
Gathering more evidence in support of a faulty motherboard theory.
At some point I got this (system wasn't under heavy load - just a
browser opened + remote video playback):
https://gist.github.com/dshcherb/06f4e4a0260b6d5313df1594d959849a#file-
nvme-failure-razer-dmesg-log-L2073
сен 10
Sorry, I should have mentioned that before: in the original test I also
had a device plugged in via usb type-c (thunderbolt 3) - that device had
an ethernet interface which you can see in the logs. It's another
problem that I need to debug because type-c hot-plug of that device
worked once but
I will try 2 things:
1. re-seat the card
2. get a card from a different manufacturer and test.
It might be a buggy slot in the motherboard and if the problem persists
with a new card I will know for sure that the slot is defective.
--
You received this bug notification because you are a
1 - 100 of 143 matches
Mail list logo
