Public bug reported:
== SRU Justification ==
* Impact:
RTL8153-BD is used in Dell DA300 type-C dongle and should be added to the
whitelist of devices to activate MAC address passthrough.
* Fix:
Two commits in upstream need to be applied in order to support this feature.
Both of them are in
Public bug reported:
This issue was spotted with a KVM node running Xenial KVM kernel, it
works well with generic / lowlatency kernel and B/C/D KVM kernels. (I
guess maybe this is because of some missing configs?)
It was not spotted before as we don't install the nfs-kernel-server for
SRU
Are we still going to change the section of the metapackages? Those
tasks are still open.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1787460
Title:
Unattended upgrades removed
** Changed in: linux (Ubuntu)
Status: Fix Committed => 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/1780066
Title:
[Bionic] Disk IO hangs when using BFQ as io
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bluez (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => In Progress
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
@sthou...@in.ibm.com: Thanks for that test. Unfortunately I'm not quite sure
why the patch isn't fixing the problem. This was the patch that IBM submitted
upstream and reported that it fixes the problem. The patch applied cleanly to
bionic. I'm still investigating this further and may require
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
02:00.0 Network controller [0280]: Intel Corporation Device [8086:2526] (rev 29)
Subsystem: Intel Corporation Device [8086:4018]
** Tags added: originate-from-1820564 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
[Impact]
New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not
correctly probed without the corresponding id entry in kernel.
[Fix]
Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series".
[Test Case]
Verified on Intel 9260D2WL.
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Tags removed: originate-from-1820564 somerville
** Changed in: linux (Ubuntu)
Assignee: You-Sheng Yang (vicamo) => (unassigned)
** Summary changed:
- iwlwifi not working with Intel AC 9260
+ iwlwifi not working with Intel AC 9260 on kernel 4.15
--
You received this bug notification
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
70:00.0 Network controller [0280]: Intel Corporation Device [8086:2526] (rev 29)
Subsystem: Intel Corporation Device [8086:0014]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr-
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => In Progress
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: hwe-next
Status: New => Fix Released
--
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/1817817
Title:
To add power setting bin file for SAR support (QCA6174)
If you can still ssh in while the screen is frozen then please do so and
run:
dmesg > frozendmesg.txt
and send us the file 'frozendmesg.txt'
** Summary changed:
- Screen frozen after switch to other tty and do login & logout
+ [nvidia] Screen frozen after switch to other tty and do login &
Browsing the Xorg modesetting source code it appears that might be to
blame too, since it seems to try to use atomic mode setting.
--
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/1813423
*** This bug is a duplicate of bug 1813423 ***
https://bugs.launchpad.net/bugs/1813423
Yes, the differences in hardware model and software don't matter here.
What's common is that it's an Intel GPU using the Xorg modesetting
driver, which uses the i915 kernel driver.
Your Nvidia GPU doesn't
You have been subscribed to a public bug:
To simplify reproduce steps, one only has to:
1. install (tested so far) Ubuntu Bionic
2. switch to other tty by pressing Ctrl+Alt+Fn
3. login and logout
Then it should try to switch back to GDM (no matter you have logged in GUI or
not), triggers
** Bug watch added: freedesktop.org Bugzilla #109206
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--
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/1690085
Title:
Ryzen 1800X
Launchpad has imported 21 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=194521.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
@Borislav has the fix for erratum 1033 "A Lock Operation May Cause the
System to Hang" been applied so far? The suggested workaround was
"Program MSRC001_1020[4] to 1b", but I couldn't find anything about it
in master branch. According to the document, 1033 only affects B1.
--
You received this
There's a patch in comment #526 for people to test before we include it
so that there's at least *some* fix in the kernel, going forward...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I am running Fedora on AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
with Gnome.
I use kernel parameters idle=nomwait iommu=pt processor.max_cstate=1 set
via grubby.
I am not getting any hangs unless I suspend with lid close or suspend on
power button. It would probably be better to not execute
(In reply to alfie from comment #566)
> But I really want C6/P6 and ignoring the BIOS seems to get me there...
Why do you think the patch I pointed to won't give you C6?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
(In reply to Another User from comment #564)
> Can your system reach turbo frequencies with this patch?
> Maybe I understand something wrongly...
Yes, I have a ryzen 1600 and I can see 1/2 cores running at ~3.6 GHz
under some peculiar stress case.
(In reply to Borislav Petkov from comment #565)
(In reply to Borislav Petkov from comment #569)
> (In reply to Tolga Cakir from comment #568)
> Such a "fix" does not exist. Possibly because it is unlikely this is causing
> it and BIOS might be applying the fix already. People with B1s (model 1,
> stepping 1) could test though by doing as root:
(In reply to Tolga Cakir from comment #568)
> @Borislav has the fix for erratum 1033 "A Lock Operation May Cause the
> System to Hang" been applied so far? The suggested workaround was "Program
> MSRC001_1020[4] to 1b", but I couldn't find anything about it in master
> branch. According to the
(In reply to alfie from comment #561)
> This is pretty strange, could someone explain it to me? Wasn't mwait bugged
> in ryzen?
Looks like this patch makes kernel to ignore BIOS messages about unsupported
C-state.
this function used in "acpi_processor_ffh_cstate_probe" which further used in
[X][PATCH 0/4] LP#1821259 Fix for deadlock in cpu_stopper
https://lists.ubuntu.com/archives/kernel-team/2019-March/099427.html
[B][PATCH 0/2] Fix for LP#1821259 (pending patches for) Fix for deadlock in
cpu_stopper
https://lists.ubuntu.com/archives/kernel-team/2019-March/099432.html
** Also
Since Bionic already has the fix commit applied,
the original kernel version doesn't hit the problem.
--
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/1821259
Title:
Hard lockup in 2 CPUs
Both xenial and bionic original/patched kernels
were tested with stress-ng scheduler class, and
no regressions were observed.
$ stress-ng --version
stress-ng, version 0.09.56 (gcc 8.3, x86_64 Linux 4.15.0-47-generic)
$ sudo stress-ng --class scheduler --sequential 0
$ uname -rv
Test-case on Xenial;
$ ls -1d /sys/devices/system/cpu/cpu[0-9]*
/sys/devices/system/cpu/cpu0
/sys/devices/system/cpu/cpu1
Original
$ uname -rv
4.4.0-144-generic #170-Ubuntu SMP Thu Mar 14 11:56:20 UTC 2019
$ sudo insmod kmod-stopper/kmod-stopper.ko
[ 74.198379] mod_init() :: this
--
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/1821259
Title:
Hard lockup in 2 CPUs due to deadlock in cpu_stoppers
Status in linux package in Ubuntu:
Incomplete
Bug description:
Test-case (kmod-stopper.c)
-
$ sudo apt-get -y install gcc make libelf-dev linux-headers-$(uname -r)
$ touch Makefile # fake it, and use this make line:
$ make -C /lib/modules/$(uname -r)/build M=$(pwd) obj-m=kmod-stopper.o modules
$ echo 9 | sudo tee /proc/sys/kernel/printk
$ sudo
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1821259
and then change the status of the bug to 'Confirmed'.
If, due to the
Analysis
The 1st hard lockup is harder to get the interesting data out of, as apparently
the registers with variables
related to the cpu number have been clobbered by more recent calls in the
spinlock path.
Looking at the 2nd hard lockup:
addr2line + code shows us that
Public bug reported:
[Impact]
* This problem hard locks up 2 CPUs in a deadlock, and this
soft locks up other CPUs as an effect; the system becomes
unusable.
* This is relatively rare / difficult to hit because it's a
corner case in scheduling/load balancing that needs timing
with
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-disco
** Tags removed: block-proposed
** Description changed:
This bug is for
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xrdp (Ubuntu)
Status: New => 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/1817225
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ness are you using secure boot?
--
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/1776563
Title:
Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
load,
your fan runs at 100% because you use pci=noacpi
--
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/1776563
Title:
Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs,
--- Comment From grom...@br.ibm.com 2019-03-21 16:33 EDT---
Hi Cascardo,
(In reply to comment #36)
> I would like to ask if using the same location as the real perf binary
> itself would be fine for your needs.
>
> That is, a symlink at /usr/lib/linux-tools/`uname -r`/libperf_jvmti.so
>
Hello Talat - You said that this test passes on the 18.04 LTS kernel so
it is worth nothing that the commit you identified is also present in
that kernel. It was released in 4.15.0-32.34:
https://git.launchpad.net/~ubuntu-
Hi Talat,
Something else occurs to me, could you list which kernels are affected?
Is this correct so far:
4.15: Not affected
4.18: Affected
How about 5.0 and perhaps 4.4 (not sure if 4.4 includes support for this
though, so that may be not worth investigating.)
And for failing kernels, could
Err... nevermind 4.4 anyway. just 5.0 would be interesting to see if
this persisted into Disco.
--
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/1801574
Title:
[cosmic] ipoib ping with
just tried the firmware after updating, unfortunately doesn't work
--
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/1819028
Title:
Intel 9260 WiFi adapter doesn't work on B450 motherboard
** Changed in: linux-firmware (Ubuntu Bionic)
Status: Incomplete => Fix Committed
** Changed in: linux-firmware (Ubuntu Cosmic)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-firmware (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
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/1751266
Title:
Missing firmware in
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
Yes, tried a few back now. 4.15.0-43-generic is the last good one.
-44 has the weird things, Youtube video goes slower (or stops for while) and
then speeds too much and audio gets out of sync with that.
In VLC audio stutter starts at about after first 10 to 12 seconds.
--
You received this
I've found that I can make the system stable with the following
settings:
System Settings:
Privacy>Screen Lock:On
Power>Dim screen when inactive: Off
Power>Blank screen: 10m
Power>Automatic
Bugs still persist with bios 1.13 and 5.0+ kernels. Advanced touchpad
doesn't work out the box like 4.19 and 4.20 did, new dmesg errors about
pcie powersaving [use pcie_aspm=off to fix], complaints about not
locating smbus and iommu too late in the boot (sometimes causing
softlocks [fix with Ives
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1821068
Title:
Touchpad not detected on Dell XPS 13 model 9370
Status
The linux kernel apport hook is provided by apport directly, so needs to
be fixed there:
$ grep -i Wifi /usr/share/apport/package-hooks/source_linux.py
apport.hookutils.attach_wifi(report)
$ dpkg -S /usr/share/apport/package-hooks/source_linux.py
apport:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
When I wrote the workaround, I didn't observe this:
[ 60.486464] xhci_hcd :05:00.3: Refused to change power state, currently
in D3
[ 60.486471] xhci_hcd :05:00.4: Refused to change power state, currently
in D3
So please file a new bug report.
--
You received this bug notification
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
I'm going to update the Linux kernel to the latest option (4.15.0-46.49)
This will probably stop the Intel wifi from working, this should be a great
way to test the new firmware you sent
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
Replaced motherboard and trackpad. The problem is fixed. Seems to have been a
hardware issue.
You can mark the issue as "closed" or "not (our) bug".
On Thursday, March 21, 2019, 11:06:24 AM CDT, Michael Nahas
wrote:
No, "sudo modprobe hid-multitouch" did nothing.
FYI, my laptop
--
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/1820371
Title:
PCI/internal sound card not detected
Status in linux package in Ubuntu:
Confirmed
Bug description:
no sound in dell
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1819695
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you
So can we close this bug report now or not?
--
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/1776563
Title:
Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
Created attachment 281951
attachment-3442-0.html
I'll compile a 5 series kernel and get back sometime this week week.
On Thu, Mar 21, 2019, 10:49 wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=200087
>
> --- Comment #121 from Vladislav Kamenev (mazahakafore...@ya.ru) ---
> I think we
Running a 2200U with Bios 1.13 and Kernel 5.0.3, and I still soft lock
without pci=noacpi in grub before boot. Fan definitely is running at
100% after booting as well. With pci=noacpi, I can boot, but the
touchpad does not work, although I haven't attempted to work on that
problem yet.
--
You
I think we should wait till more people try 1.13 bios with 5.0 kernel
and confirm that laptop is now usable
--
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/1776563
Title:
Acer
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
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
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1819691
Title:
linux-raspi2:
I fail to see how it is not the same issue; I am receiving the same
error that the commit (621faf4f) claims to fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1756700
Title:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1819695
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1819612
Title:
linux-raspi2:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1819616
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1819693
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1819713
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-disco
** Tags removed: block-proposed
** Description changed:
This bug is for
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1819711
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1821205
Title:
"couldn't find IFLA_VF_INFO
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1819658
Follow up of my previous comment:
Compiled and installed RHEL 8 kernel. RHEL 8 aacraid driver does not
seem to have the bug.
System Rescue CD v5.2.2 (http://www.system-rescue-cd.org) aacraid module
does not encounter the bug.
However Debian did not boot "out of the box" if I installed either
Ok, thanks Jason.
That is great info, but about as much as we had so far :-/
Can you set your deployment up in a way that if that happens again you
can collect these binaries?
If it right now still triggers if you (re)deploy a 2G guest use the
chance to finally give us the bits that we will need
Public bug reported:
Hi,
I have a Chelsio T62100-LP-CR and I'm trying to create a libvirt VM that
gets a VF from the NIC.
The following XML is used :
When starting the VM, libvirt fails with the following :
ubuntu@lubbock:~$ sudo virsh start
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 193 matches
Mail list logo
