Thx a log Heitor! With no mention of some new package fixing this I did not
correlate that to any patch to the kernel.
Will the be fixed in the HWE kernel as well then?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Robert thanks for keeping this bug alive and updated!
1) More debug info required?
@Robert, reading your post
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/50 again,
I am wondering if you asked me to provided more debug info with NVM 4.4 on my
E810 NICs? Would this
Same here during boot, running 6.5.0-15-generic on Ubuntu 23.10:
$ dmesg | grep -C3 evict
[ 10.769204] EXT4-fs (xvda1): mounted filesystem
446b2699-dd26-4b84-9ada-d0cb48d21c93 r/w with ordered data mode. Quota mode:
none.
[ 11.061845] SGI XFS with ACLs, security attributes, realtime,
We see the same issue with lots of references to arrays within
mpt3sas_scsih.c:
```
UBSAN: array-index-out-of-bounds in
/build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12
UBSAN: array-index-out-of-bounds in
Public bug reported:
Similar to the bug https://bugs.launchpad.net/ubuntu/+source/linux-
hwe-6.5/+bug/2051123 where traces were shown, we observed a "BUG" being
reported on yet another machine of the same make / model (Asus
RS720A-E11-RS24U using dual socket AMD EPYC Milan CPUs):
```
[...]
Jan
** Attachment added: "lspci output of the machine type showing the traces"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051123/+attachment/5742209/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
We just observed this issue on another machine of the same make and model.
Kernel log of the boot up to the crash is attached.
This machine had NO virtual machines running though. We saw side effects
such as hanging processes but were able to log in and reboot the
machine.
** Summary changed:
@Stefan Could you kindly elaborate on the "Fix Commmited"? Was there any
change to the kernel that would fix this issue? Is this fixed with 4.40
NVM from Intel?
Reading Roberts post
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/50)
again, it seems that he is only guessing
Public bug reported:
A few hours after upgrading a machine serving as VM hypervisor running
OpenStack Nova + libvirt from linux kernel 6.2.0-37-generic to
6.5.0-14-generic we observed kernel traces and quick disintegration of
the system and its various processes.
While the TCP connection itself
Public bug reported:
We observed a kernel trace on a KVM hypervisor servers during live
migrating an instance:
```
[...]
Jan 23 10:58:53 fra-az1-comp-22 kernel: [ cut here ]
Jan 23 10:58:53 fra-az1-comp-22 kernel: WARNING: CPU: 75 PID: 1082578 at
@Robert,
first thanks a lot for pursuing this issue!
1) I certainly can provide the debugging info. May I ask if ...
a) the system in question would need to have an active LAG (LACP) for
this to be helpful? We did switch to active-backup on all our machines
due to this very issue.
b) this
The seeding [1] of it is also quite clear on why it is still there.
"""
# This stack is no more very relevant, but was in the early days of internet
# dialin. This stack is a candidate for demotion, but OTOH received no
# bugs/CVEs over the last years and therefore can stay as-is for now.
# ppp
FWIW, we updated our NICs to 4.30 as they were individually purchased
and not part of pre-built servers and also have this issue.
So in essence the issue also exists with the latest firmware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
1) Andre, after I switched to active-backup the issue is gone (so far).
But yeah, we are looking for a reproducer as well. It's hard to narrow
down some random issue - also likely for Intel.
2) But I just received an email from an Intel developer with a suggested
change to the driver to narrow
I hope the links and explanations added will help you in future uploads.
Even better, next time be available on IRC after the ping, but I understand
it might be rather late for you - so this isn't a complaint but a
recommendation.
The upload to noble should unblock you there, once you verified
For now https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.10-1ubuntu1 looks just as good as in my tests.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2042902
Title:
I've created the merge of 1.2.10 by following [1], then re-added the patch
of Ethan and that of you Artur.
I hope I didn't add too many issues :-)
At least I'm sure I got this whole topic much forward.
The merge including all I mentioned can be seen here (As training material
for how this upload
I contacted Ethan who created the one patch I could not track down.
He had all the information that I needed:
- This is actually from
- https://github.com/alsa-project/alsa-ucm-conf/pull/321
- https://github.com/alsa-project/alsa-ucm-conf/pull/322
- related to private LP bug 2037058
- Not yet
Analyze for merge readiness:
The current delta is:
* d/p/0001-ucm2-Qualcomm-sc8280xp-fix-device-numbers.patch
* d/p/0001-acp63-add-initial-support-for-AMD-Pink-Sardine-ACP63.patch
* d/p/0002-acp63.conf-use-symbolic-link.patch
* d/p/0003-acp62-add-initial-support-for-AMD-ACP-v6.2-RPL.patch
=>
I got a ping on patch pilot duty, sadly on my ping back if they would be
available for questions if I find more that needs to be sorted out was
unanswered. So I need to carry all into this bug.
This is kind of a log of my own understanding process, feel free to ignore it:
Proposed change:
- It
I ran into this issue on 22.04 LTS (using HWE kernel 6.2) on a 100G dual-port
E810 NIC.
Also with LACP only, active-backup works without issues.
To bring this more to the attention of the driver devs, I posted to the
intel-wired-lan ML: https://lists.osuosl.org/pipermail/intel-wired-
@phil
As I said above for me it mostly was "I'm sure some change was expected, but so
much?".
It has various benefits as gladly outlined by Dimitri, fixing many
issues, but coming at a price tag.
Seeing how big the price tag is for small size, high density cases I
consider it potentially too
> it only gets activated when you install ksmtuned (which is not
installed by default).
No, installing qemu-system-... will also enable it.
So Seth gladly filed bug 2033565 to discuss and change this now or at least
towards 24.04.
--
You received this bug notification because you are a member
> @paelzer Are you happy to adjust your regression testing/metrics gathering to
> increase the
> memory required knowing that it was a conscious decision to switch kernel and
> incur the
> performance hit for the benefit of using a kernel with more support and less
> reported bugs?
I am.
In
IMHO: If it turns out unfixable, this at least needs to be a release
notes entry
--
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/2032933
Title:
Mantic (23.10) minimal images increase in
One thing that came up when discussing with SMB as an obvious "uses mem
more in a kernel" are the structures needed per POSSIBLE cpu.
Comparing the system that I downgraded I found from [1]:
With the -kvm kernel before:
kernel: setup_percpu: NR_CPUS:64 nr_cpumask_bits:1 nr_cpu_ids:1
Checking kernels:
1. This already uses linux-image-virtual, it is not the even bigger
linux-image-generic.
2. The change of the image build sadly combined it all
a) new image build/seeding by CPC
b) different kernel type -kvm -> -virtual that uses generic
c) switch of kernel versions
We
>From the daily runs on images I can see that 6.2.0-1008 seems to be fixed in
>that regard.
It loses just as much as it formerly gained.
Since this arrived in lunar-updates/security should we close this bug?
--
You received this bug notification because you are a member of Kernel
Packages,
Mauricio is right in all he asks for, except most of them are "style"
which I'd recommend but not insist on.
$ dquilt rename -P 0001-arm64-support-more-than-one-crash-kernel-
regions.patch lp2024479-arm64-support-more-than-one-crash-kernel-
regions.patch
I thought it would be only refreshed, but
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683998/+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/2025984/+attachment/5683997/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683999/+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: "acpidump.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5684000/+files/acpidump.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/2025984/+attachment/5683995/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683996/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683994/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683993/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Hi,
we haven't even been able to strip off all the weight we gained with bug
2015867 and now I've found another change eating another ~13mb.
This time it might again be all intentional, and maybe even unchangeable.
But I'd like to file it so that you can consciously think
there is a
problem with nouveau:
Jul 04 08:08:50 christian-homeoffice kernel: pci_bus :05: Allocating
resources
Jul 04 08:08:50 christian-homeoffice kernel: pci :04:00.0: bridge window
[mem 0x0010-0x000f 64bit pref] to [bus 05] add_size 20 add_align
10
Jul 04 08:08:50 christian
buntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: christian 2130 F pulseaudio
/dev/snd/controlC1: christian 2130 F pulseaudio
/dev/snd/controlC0: christian 2130 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Ju
Seen the first lunar test with the fix.
Overall we now have:
- 859 mb (before) -> 984 mb (bug) -> 899 mb (fixed)
So there would be more to get back to the old sizes, but I've understood
that this seemed to be what can be done for now.
I'll update again to confirm once I see the change land in
Hi,
I was rechecking the numbers after a while as you called this fix released and
confirmed for some more cleanup in mantic. AFAIC even Lunar didn't improve.
To better see it I'll attach an image of daily metrics, it didn't
recover since my report on early April and Lunar as well as Mantic 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/2019040
Title:
linux-*: please enable dm-verity kconfigs to
No boot again probably due to the fact that I haven't removed my Nvidia
Drivers at the moment and left them while I upgraded to 23.04. Unable to
do the apport-collect 2017802
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you
Public bug reported:
I have tried installing different Ubuntu distros ranging from the GNOME,
Unity and Cinnamon versions. But I am constantly unable to boot to the
desktop after installing 23.04 or updating from one version to another.
I tried to restart a few times to see if it will proceed to
For those using the lowlatency kernel, the last kernel that works with
HDMI audio is "5.19.0-1017-lowlatency".
--
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/2009136
Title:
No HDMI
Thank you for your response Konrad.
I followed the docs for replacing pulseaudio with pipewire which worked well.
Now the bluetooth app offers more codecs to use.
I figured out "mSBC" offers the best quality.
Compared to A2DP it still sucks and sounds horrible.
You dont want to accept this if you
Hi,
now it's 2023 and I still have this problem.
Using Mint 21.1 and Teams for Linux.
When I switch to A2DP I cannot use the headset mic.
When I switch to HFP the sound in conversations is horrible.
Would appreciate a fix here.
--
You received this bug notification because you are a member of
Just picking on linux-headers for now it is more or less what I
expected.
It went 26 -> 107 mb and I see new directories for rust of:
81M
linux-headers-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb.extract/usr/src/linux-headers-6.2.0-1003-kvm/rust
228K
This isn't about the deb size, but about the size as extracted on the system.
Especially headers will most likely compress really well into the deb.
Comparing the latest 5.19 with the recent 6.2 [1][2] that got through propose
migration we can see the increase just fine. debsizes as downloaded
This is ran on daily images, the kernel versions are already listed above.
Hence no need to ran apport-collect for this issue.
Setting to "Confirmed"
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Public bug reported:
Hi,
in the regular monitoring of metrics there was a bump in disk size last week.
The default image once installed consumes now 994 (formerly 859) megabytes.
Looking at the consumers there was much noise, but the biggest change
was
linux-headers-5.19.0-1008-kvm 25197 ->
we have the same issue with this kernel, but also with NFSv4
thanks,
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/2009882
Title:
Linux 5.4.0-144-generic x86_64 multithread
** Changed in: cloud-initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs/1967593
Title:
kernel
** 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/2009449
Title:
linux-libc-dev creates top level directories /arch
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2009449/+attachment/5652114/+files/acpidump.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/2009449/+attachment/5652113/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2009449/+attachment/5652112/+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/2009449/+attachment/5652111/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2009449/+attachment/5652110/+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: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2009449/+attachment/5652107/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2009449/+attachment/5652108/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2009449/+attachment/5652109/+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: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2009449/+attachment/5652106/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/2009449/+attachment/5652103/+files/CRDA.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/2009449
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2009449/+attachment/5652105/+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/2009449
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2009449/+attachment/5652104/+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
** Tags added: apport-collected
** Description changed:
In what package did you find this bug?
linux-libc-dev:amd64 (unfortunately the bug system does not let me enter the
package name in the editbox, i.e. it says "linux-libc-dev" does not exist in
Ubuntu. Please choose
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1985956
Title:
linux-libc-dev and libc6-dev do not agree who owns fsconfig_command
Status in glibc
Thanks for the ping Markus, let us know if you run into it again on another
system
e1000 as fallback is fine, but also slow IMHO.
So I hope you we can one day find what it was.
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you
> I had thought I should be able to reproduce it by mounting (in an
unprivileged user+mountns) an overlayfs where the underlay has, say,
"/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.
Fwiw, I think you need index=on
Bionic was already reset for other reasons at the end of march this year.
Jammy was already reset for other reasons in January this year.
Kinetic was already reset for other reasons in May this year (and Lunar is
based on that).
Only Focal was left open and is now queued.
--
You received this
I was lost in old habits when providing MRs for hints, sorry.
This doesn't need hints to land, since it is broken in release due to external
changes a set of baseline runs with migration-reference/0 will work just as
much and be less effort.
Scheduling those now ...
P.S. That will unblock the
I prepared and linked a set of changes to hint the current version as badtest.
Please consider merging them as this version will be broken permanently until a
new upload will fix this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Patch added: "suggested fix to apply in -dev and SRU so that tests will work
again"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+attachment/5633150/+files/0001-Fix-tests-to-be-compatible-to-jammy.patch
** Also affects: ubuntu-fan (Ubuntu Lunar)
Importance:
Public bug reported:
This breaks all ubuntu-fan autopkgtest since Jammy was released in April
2022.
Miriam found it while checking an autopkgtest regression in bug 1995260
Summary:
- the tests in test_local_lxd hardcode to "lts"
local series='lts'
- due to that we always test the latest
Same problem here with a X260. Additionally, power off does not work. If
I power of from gnome, I have to press the power button for 5 seconds
and than again to turn the system on again. I tried all other hints
(TPM, all suggested kernel versions) - nothing worked. That's really a
serious issue!
Some insight of the check on the history of this out of the many updates
on the upstream bug:
On master branch this was introduced via:
commit 159d8c274fd92438ca6d7068d7a5eeda157227f4
Author: Mika Westerberg
Date: Wed Jun 9 13:25:33 2021 +0300
ACPI: Pass the same capabilities to the _OSC
Hey,
the error message inside libvirt is from parsing PCI VPD Data.
If you say removing that card removes the message it seems to indicate that the
VPD of that device is either
a) broken as coming from the device and needs a FW Update (or report to Intel
to create one)
or
b) valid VPD data but
FYI: Adding libvirt here and marking it as update-excuse, so that the
to-be-expected FTBFS can be understood.
Once fixed in either package I can hit rebuild and move on through migration.
It built fine on a PPA overriding this problem in an ugly way and otherwise
than this build issue here works
Since this happens on build and not on a target system, I'll mark it
confirmed without providing the data that the Kernel bot asks for.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Tags
You can usually replicate that behavior by starting a few guests and
instead of shutdown stopping the libvirt-guests service.
If that works in your case as well it will easen having a look, so let
me ask does that work for you?
--
You received this bug notification because you are a member of
And something on arm64 already forces this, despite only being in -proposed.
For example if someone tries
linux-libc-dev (<5.19.0-1),
to avoid this FTBFS for now that works on all other architectures (right now),
but on arm64 gives me:
Missing build dependencies: linux-libc-dev (<= 5.19.0-1)
Public bug reported:
Right now in kinetic-proposed builds are failing due to both sets of
headers defining fsconfig_command.
(kinetic-amd64)root@Keschdeichel:/build/libvirt-LTnG76/libvirt-8.6.0/debian/build#
apt-cache policy libc6-dev linux-libc-dev
libc6-dev:
Installed: 2.36-0ubuntu1
My VM has been running solid for 8h today. So it seems my issue got
resolved
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1981669
Title:
After updated from
Looking at the changelog (https://www.virtualbox.org/wiki/Changelog) I
have no clue what could have fixed the issue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1981669
Hi,
I have a system that recently shows (same kernel upgrade) the same issue.
I've also found [1] which I think the kernel team might want to participate and
track.
They seem to have identified a patch that potentially needs to be
reverted - at least to confirm it is what now causes this.
There
Today I installed the latest Virtualbox: 3.1.36r152435. So I figured I give it
a try and the Windows VM is running stable since 1,5 h on 5.14.0-1045-oem.
If it keeps running for the rest of today, I'll give it a full day test
tomorrow and report back.
--
You received this bug notification
to
5.11.0.40 which works correctly.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1890 F pulseaudio
/dev/snd/controlC0: christian 1890 F pulseaudio
:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-05-06 (609 days ago
FYI
There was a request on IRC to also promote firmware-sof
Moving that here to have an auditable trail why things were changed - also I
guess we'd want to have an explicit ack by the kernel team that this is the
very same case.
>From #ubuntu-release
[11:53] ubuntu-archive: Please move the
Public bug reported:
With kernel linux-image-5.14.0-1042-oem VirtualBox VM runs stable
With kernel linux-image-5.14.0-1044-oem VirtualBox VM crashed constantly
Wiht kernel linux-image-5.14.0-1045-oem VirtualBox VM crash multiple times a day
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Just stating (for my future self any anyone else) that for the other way
around (removing features that were never enabled before) there is code
that could handle that [1][2]. In a similar fashion libvirt could try to
consider older sources before this change as "ok I accept to not insist
on this
These were also backported into Focals kernel in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893115
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895174
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895879
Therefore also fixed in Focal.
(and also fixes of those fixes
The identified fixes got merged in 5.9 and later.
So Impish and later are good.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi,
I'm coming by cleaning old open bugs to ensure nothing gets forgotten for too
long and or clutters the view to the remaining issues.
This case here - as Paride outlined almost two years ago - is already
covered and discussed in bug 1833586 . We won't/can't SRU it and there
was no further
Arr, this is a bad case :-/
First of all - yes Sven it is a regression. Somewhat relieved by having
a workaround, but not making it not a regression.
First of all I have to beg all your pardon for not seeing this earlier,
due to the bug tasks being closed most of the review passed that we have
I tried the fix with GFXMODE=800x600 -> it did nothing. I had bigger
letters but the same error.
I tried the fix with editing mkinitramfs and replacing 1 by 19 on line
196 to restore the high compression level. Then regenerated the image ->
it worked.
For readers, this is not so easy, because
@guiverc this is not related to Ubuntu 19.10 or 19.04.
It was initially reported at that time, but it is still open.
I just stumbled on it, ugrading from 21 to 22.04.
Same behavior:
"error: out of memory.
Press any key to continue..."
Then kernel panic message.
I created a bootable USB image
For easier debugging this can be reproduced on any affected system
(Tried KVM and EC2) by just running:
$ sudo systemctl start hv-kvp-daemon.service
^^ This will stall while one would assume it should quick-exit due to
the ConditionVirtualization not being met.
A full cycle (90 second stall)
1 - 100 of 1329 matches
Mail list logo
