[Kernel-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
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 itself is still recommended by network-manager and thereby has quite # an install base. """ Removing is maybe too hard as Steve outlined, but what about at least demoting to universe (to encourage it a bit less)? The seed change to the section linked above would be trivial, but it would need coordination with the Desktop variants as a dependency to network-manager-pptp is in most of the meta packages. reverse-depends --release=noble src:network-manager-pptp Reverse-Recommends == * network-manager (for network-manager-pptp) * ubuntu-budgie-desktop [amd64 arm64 armhf ppc64el] * ubuntu-budgie-desktop-minimal [amd64 arm64 armhf ppc64el] * ubuntu-budgie-desktop-raspi [arm64 armhf] * ubuntu-desktop [amd64 arm64 armhf ppc64el] * ubuntu-desktop-minimal [amd64 arm64 armhf ppc64el] * ubuntu-mate-core (for network-manager-pptp-gnome) * ubuntu-mate-desktop (for network-manager-pptp-gnome) * ubuntu-unity-desktop [amd64 arm64 armhf ppc64el] * ubuntukylin-desktop (for network-manager-pptp-gnome) * vanilla-gnome-desktop [amd64 arm64 armhf ppc64el] * xubuntu-desktop (for network-manager-pptp-gnome) * xubuntu-desktop (for network-manager-pptp) Reverse-Depends === * lomiri-indicator-network (for network-manager-pptp) It comes at a comfort loss though, since this is depended on by all those meta packages to work right away in a fresh install, which would be a behavior that will be lost. Also if there is a CVE, then only people using ubuntu pro would get a fix. Which is free for personal use, but those forced to use pptp are likely people with non-personal use of outdated infrastructure. So we'd make the world a bit less secure as likely not all would get the fixes then. Still I'd want to know from Steve and Seth which discussed so far - what would you think about that as a compromise? [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/supported-misc-servers#n190 -- 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/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Incomplete Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. IPSec OpenVPN Strongswan are much better alternatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
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 all is indeed fine there you can update the SRU uploads accordingly (patch headers). If you want to overachieve (=this is optional and depends how sure or not you are), pre-build in PPAs and demonstrate you have tested it there successfully. Then you can ping sponsors again to sponsor the uploads to -unapproved for the SRU team to have a look. ** Changed in: alsa-ucm-conf (Ubuntu Noble) Status: New => Fix Committed -- 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: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
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: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
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 could have been for noble) => https://code.launchpad.net/~paelzer/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/456227 I tested the build in a PPA and while I couldn't test on much real HW (just a super old NUC and I didn't fully know what to check - it had sound at least) it is early enough in the noble cycle for you to have a look at that. I hope that also is easier for you as you might be closer to HW to test. And in general it seems 1.2.10 is the version for noble, as 1.2.11 would be expected in ~May 2024. So the merge should have been done at some point. [1]: https://github.com/canonical/ubuntu-maintainers- handbook/blob/main/PackageMerging.md -- 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: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
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 upstream accepted, but discussed with sil2100 and accepted as-is for now - Ethan plans to file a public LP and update it once upstream accepted a final form of it I'll put all of that into the patch headers to help the next person that comes by. -- 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: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
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 => Those are in 1.2.10 and can be dropped on a merge * d/p/0001-Add-initial-support-for-MediaTek-mt8390-evk-and-mt83.patch => This is not upstream AFAICS => It does not have the dep-3 patch headers for Forwarded or Origin and sadly such moments trying to find what happened is just why they should always be added. This is a sin of the past and not your fault Artur, but your patch also misses those, so let me teach you about that ... Learning links: - Standard for patch headers: https://dep-team.pages.debian.net/deps/dep3/ - If you want it a bit more consumable https://github.com/canonical/ubuntu-maintainers-handbook/blob/a5a386be1be1507fbd1dd8842699b0758042169c/DebianPatch.md#the-patchfile-header Also your git export is not of the hash that is in the final repository Instead it is from the PR which might go away and is therefore harder to find. And finally, no trace back from the patch to the bug that made it being added. So overall your patch should ideally be like: - use correct git hash - add Origin - add Applied-Upstream - Add last-update Which makes it start like: From b422a8e08cb3845053ece1fc832294adca21a684 Mon Sep 17 00:00:00 2001 From: Shuming Fan Date: Thu, 12 Oct 2023 10:07:36 +0800 Subject: [PATCH] ucm2: soundwire: add rt713 SDCA device Closes: https://github.com/alsa-project/alsa-ucm-conf/pull/363 Signed-off-by: Shuming Fan Signed-off-by: Jaroslav Kysela Origin: upstream, https://github.com/alsa-project/alsa-ucm-conf/commit/b422a8e08cb3845053ece1fc832294adca21a684 Bug: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902 Applied-Upstream: v1.2.11 Last-Update: 2023-11-24 --- ... I'll do that for you here for noble to make some progress, but you can still fix this up for the SRU uploads. It really would have helped if you'd have been available after you pinged me on IRC. At the end of the day we want to teach, not just correct uploads. -- 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: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
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 adds a few regex expressions to allow matching the new HW - and then configuration for those new matches - Accepted upstream - Other than fixup releases Upstream seems to tag two releases per year, one in Q2 one in Q4 - Due to that I'd this to be in a new revision v1.2.11 by May 2024 - that might be worth to mention for packages to know when they will be able to drop it Paride and Athos guided you to correctly obey the usual "fix -devel first" rule and due to noble being new that you need to start there. We are adding one particular device, but I see that due to having added Ubuntu delta in the past we have not yet picked up 1.2.10 which would have picked up plenty of other fixes and devices. => https://github.com/alsa-project/alsa-ucm-conf/releases/tag/v1.2.10 alsa-ucm-conf | 1.2.10-1 | unstable | source, all alsa-ucm-conf | 1.2.9-1ubuntu3 | noble | source, all The SRU fix is fine, those are meant to be surgical based on the need of our users, but for noble it feels we should aim for 1.2.10 + this. Checking who usually did that, ah Jürg and Ethan - fine we can ask them for opinions as they might know the subject matter. Great, so I'd propose we combine a merge of 1.2.10 with your fix on top. -- 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: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
@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 much for some. As I said in my report "This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected." so a way forward IMHO would be: 1. We leave mantic as is 2. We certainly need a release notes entry that explains the pros/cons that led to the decision 3. kernel can continue to optimize this case (see all the discussions/suggestions above already) 4. towards 24.04 4a) if this is received well, keep it 4b) if our decision was good, but not accounting for too many use-cases that we can't fix otherwise reconsider having a reduced kernel in 24.04 That would mostly an ask to the kernel team (but needs CPC to ensure it is correct e.g. in making it clear which images change due to that and which won't as they were already based on -generic). Phil/Xnox - what do you think about that approach? -- 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 memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) download/qcow2 images available @ https://cloud-images.ubuntu.com/minimal/ are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * This is during image build only and will not affect any subsequent package installs * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
> 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 of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032933 Title: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) download/qcow2 images available @ https://cloud-images.ubuntu.com/minimal/ are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * This is during image build only and will not affect any subsequent package installs * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
> @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 fact I already have. To be clear, I knew that the change from -kvm to -virtual was a conscious decision (I do not even know how long back I heard xnox talking about it, many years for sure) fixing the many issues xnox mentioned. I just never heard anyone saying or suggesting - and personally didn't expect it to be - that very intense on low-memory / density scenarios. I'd be happy if everyone here could continue the thought of checking if any further package/module could be omitted (or at least not auto- loaded) for the minimal images. Which should tune us back down a bit, even if that is not all the way to where we were before. -- 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 memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) images are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
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 memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) images are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
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 nr_node_ids:1 kernel: rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=1. With the -generic kernel: kernel: setup_percpu: NR_CPUS:8192 nr_cpumask_bits:1 nr_cpu_ids:1 nr_node_ids:1 kernel: rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=1. So let us try the new 6.3 generic kernel, but with kernel parameter maxcpus=1 possible_cpus=1 nr_cpus=1 ^^ this might be too hard, but ok for testing That gives me: kernel: setup_percpu: NR_CPUS:8192 nr_cpumask_bits:1 nr_cpu_ids:1 nr_node_ids:1 But sadly, the memory does not look much better: root@m-new:~# cat /proc/meminfo MemTotal: 956176 kB MemFree: 640960 kB MemAvailable: 664816 kB Was a good idea, but sadly that wasn't it. And the initial NR_CPUS is a compile time parameter which we can not tune down :-/ [1]: https://github.com/torvalds/linux/blob/master/arch/x86/kernel/setup_percpu.c#L122 -- 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 memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) images are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
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 did not yet think about 2c here afaics. This is not just -kvm -> -generic. But instead 6.2.0-1003-kvm -> 6.3.0-7-generic 6.3.0-7-kvm does not exist (not built anymore), so to check which of the changes broke this we might need to look at. The closest comparison I'd find is - https://launchpad.net/ubuntu/+source/linux/6.2.0-21.21 - https://launchpad.net/ubuntu/+source/linux-signed/6.2.0-21.21 Installing that on my system The new system with the high memory consumption has: linux-image-6.3.0-7-generic 6.3.0-7.7+1 linux-modules-6.3.0-7-generic 6.3.0-7.7 I'm comparing for: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/25980736/+files/linux-modules-6.2.0-21-generic_6.2.0-21.21_amd64.deb https://launchpad.net/~canonical-signing/+archive/ubuntu/primary-2022v1/+build/25984194/+files/linux-image-6.2.0-21-generic_6.2.0-21.21_amd64.deb root@m-old:~# cat /proc/meminfo MemTotal: 955692 kB MemFree: 630128 kB MemAvailable: 653536 kB So that lets us assume, that the move 6.2->6.3 was not what broke it (actually 6.3 is even a little bit better). The cause really seems to be more the move -kvm -> -generic. I'm sure some change was expected, but so much? Adding Linux bug tasks for them to chime in. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: cloud-images 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/2032933 Title: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) images are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025984] Re: Size in crease in modules in 6.2.0-1007
>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, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025984 Title: Size in crease in modules in 6.2.0-1007 Status in linux package in Ubuntu: New Bug description: 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 about it and we can be sure :-) Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS. I see root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6 total 368 drwxr-xr-x 3 root root 4096 Jun 21 20:18 ./ drwxr-xr-x 21 root root 4096 Jun 21 20:18 ../ -rw-r--r-- 1 root root 26305 May 31 09:04 ah6.ko -rw-r--r-- 1 root root 119073 May 31 09:04 esp6.ko -rw-r--r-- 1 root root 16889 May 31 09:04 esp6_offload.ko -rw-r--r-- 1 root root 74929 May 31 09:04 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 13409 May 31 09:04 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 21 20:18 netfilter/ -rw-r--r-- 1 root root 54617 May 31 09:04 sit.ko -rw-r--r-- 1 root root 16961 May 31 09:04 tunnel6.ko -rw-r--r-- 1 root root 19449 May 31 09:04 xfrm6_tunnel.ko root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6 total 752 drwxr-xr-x 3 root root 4096 Jun 28 20:17 ./ drwxr-xr-x 21 root root 4096 Jun 28 20:17 ../ -rw-r--r-- 1 root root 92705 Jun 21 12:50 ah6.ko -rw-r--r-- 1 root root 118881 Jun 21 12:50 esp6.ko -rw-r--r-- 1 root root 83465 Jun 21 12:50 esp6_offload.ko -rw-r--r-- 1 root root 74481 Jun 21 12:50 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 79129 Jun 21 12:50 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 28 20:17 netfilter/ -rw-r--r-- 1 root root 123361 Jun 21 12:50 sit.ko -rw-r--r-- 1 root root 81905 Jun 21 12:50 tunnel6.ko -rw-r--r-- 1 root root 84137 Jun 21 12:50 xfrm6_tunnel.ko That is just an example, modules have been growing all over the place. In sum the mentioned ~13mb. But neither did all modules change, nor was it by an equal amount. Here for example sit.ko more than doubled. https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious either, so I'd appreciate you having a look. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: minimal CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230628 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12 RelatedPackageVersions: linux-restricted-modules-6.2.0-1007-kvm N/A linux-backports-modules-6.2.0-1007-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-1007-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 2/2/2022 dmi.bios.release: 0.0 dmi.bios.vendor: EDK II dmi.bios.version: unknown dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-8.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-8.0 dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku: dmi.product.name: Standard PC
[Kernel-packages] [Bug 2024479] Re: kdump fails on arm64 when offset is not specified
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 the patch has an actual backport
change around the position of `fill_property' so it is a backport. But wait, is
it?
No, deeper inspection found this to be noise from the refresh - the function
was the same before and after patch. So we can take the content from upstream
as-is (will do) and keep the origin tag.
(It even pops the same content the old did add which confirms it is the same -
just with other diff context).
Bonus: updating the changelog to say the new filename.
With that in place, all is looking good.
I miss a PPA build here to be extra sure, but that issue (if any) would then be
on @joalif to resolve if breaking.
Uploaded to Mantic:
$ dput ubuntu ../kexec-tools_2.0.22-2ubuntu4_source.changes
Uploading kexec-tools using ftp to ubuntu (host: upload.ubuntu.com; directory:
/ubuntu)
running ppaforppaonly: Stop uploads to the archive with or to ppa without ~ppa
suffix.
running gitubuntu: Warn if uploading without git-ubuntu Vcs-* entries.
running gpg: check GnuPG signatures before the upload
running releasemismatch: Warn about mismatching suffixesg e.g. focal with a
XX.YY not being 20.04
running updatemaintainer: Stop if ubuntu changes are without ubuntu maintainer.
running suite-mismatch: check the target distribution for common errors
running badauthor: Stop if uploading with root@ or ubuntu@ email adresses.
running required-fields: check whether a field is present and non-empty in the
changes file
running checksum: verify checksums before uploading
running nobug: Stop if uploading without any bug reference.
running check-debs: makes sure the upload contains a binary package
running supported-distribution: check whether the target distribution is
currently supported (using distro-info)
{'allowed': ['release', 'proposed', 'backports', 'security'], 'known':
['release', 'proposed', 'updates', 'backports', 'security']}
running placeholderbug: Stop if using common placeholder numbers as bug
reference.
Uploading kexec-tools_2.0.22-2ubuntu4.dsc
Uploading kexec-tools_2.0.22-2ubuntu4.debian.tar.xz
Uploading kexec-tools_2.0.22-2ubuntu4_source.buildinfo
Uploading kexec-tools_2.0.22-2ubuntu4_source.changes
** Changed in: kexec-tools (Ubuntu Mantic)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2024479
Title:
kdump fails on arm64 when offset is not specified
Status in kexec-tools package in Ubuntu:
Fix Committed
Status in linux package in Ubuntu:
Incomplete
Status in kexec-tools source package in Focal:
In Progress
Status in linux source package in Focal:
Won't Fix
Status in kexec-tools source package in Jammy:
In Progress
Status in linux source package in Jammy:
Incomplete
Status in kexec-tools source package in Kinetic:
Won't Fix
Status in linux source package in Kinetic:
Won't Fix
Status in kexec-tools source package in Lunar:
In Progress
Status in kexec-tools source package in Mantic:
Fix Committed
Bug description:
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not
specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the
crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
[Fix]
To address this issue the following upstrem commits are needed:
- From the kernel side:
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region
above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not
specified
- From kexec-tools:
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the
regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM
[Kernel-packages] [Bug 2025984] UdevDb.txt
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. https://bugs.launchpad.net/bugs/2025984 Title: Size in crease in modules in 6.2.0-1007 Status in linux package in Ubuntu: New Bug description: 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 about it and we can be sure :-) Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS. I see root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6 total 368 drwxr-xr-x 3 root root 4096 Jun 21 20:18 ./ drwxr-xr-x 21 root root 4096 Jun 21 20:18 ../ -rw-r--r-- 1 root root 26305 May 31 09:04 ah6.ko -rw-r--r-- 1 root root 119073 May 31 09:04 esp6.ko -rw-r--r-- 1 root root 16889 May 31 09:04 esp6_offload.ko -rw-r--r-- 1 root root 74929 May 31 09:04 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 13409 May 31 09:04 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 21 20:18 netfilter/ -rw-r--r-- 1 root root 54617 May 31 09:04 sit.ko -rw-r--r-- 1 root root 16961 May 31 09:04 tunnel6.ko -rw-r--r-- 1 root root 19449 May 31 09:04 xfrm6_tunnel.ko root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6 total 752 drwxr-xr-x 3 root root 4096 Jun 28 20:17 ./ drwxr-xr-x 21 root root 4096 Jun 28 20:17 ../ -rw-r--r-- 1 root root 92705 Jun 21 12:50 ah6.ko -rw-r--r-- 1 root root 118881 Jun 21 12:50 esp6.ko -rw-r--r-- 1 root root 83465 Jun 21 12:50 esp6_offload.ko -rw-r--r-- 1 root root 74481 Jun 21 12:50 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 79129 Jun 21 12:50 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 28 20:17 netfilter/ -rw-r--r-- 1 root root 123361 Jun 21 12:50 sit.ko -rw-r--r-- 1 root root 81905 Jun 21 12:50 tunnel6.ko -rw-r--r-- 1 root root 84137 Jun 21 12:50 xfrm6_tunnel.ko That is just an example, modules have been growing all over the place. In sum the mentioned ~13mb. But neither did all modules change, nor was it by an equal amount. Here for example sit.ko more than doubled. https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious either, so I'd appreciate you having a look. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: minimal CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230628 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12 RelatedPackageVersions: linux-restricted-modules-6.2.0-1007-kvm N/A linux-backports-modules-6.2.0-1007-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-1007-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 2/2/2022 dmi.bios.release: 0.0 dmi.bios.vendor: EDK II dmi.bios.version: unknown dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-8.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-8.0 dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-8.0 dmi.sys.vendor: QEMU
[Kernel-packages] [Bug 2025984] ProcModules.txt
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. https://bugs.launchpad.net/bugs/2025984 Title: Size in crease in modules in 6.2.0-1007 Status in linux package in Ubuntu: New Bug description: 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 about it and we can be sure :-) Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS. I see root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6 total 368 drwxr-xr-x 3 root root 4096 Jun 21 20:18 ./ drwxr-xr-x 21 root root 4096 Jun 21 20:18 ../ -rw-r--r-- 1 root root 26305 May 31 09:04 ah6.ko -rw-r--r-- 1 root root 119073 May 31 09:04 esp6.ko -rw-r--r-- 1 root root 16889 May 31 09:04 esp6_offload.ko -rw-r--r-- 1 root root 74929 May 31 09:04 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 13409 May 31 09:04 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 21 20:18 netfilter/ -rw-r--r-- 1 root root 54617 May 31 09:04 sit.ko -rw-r--r-- 1 root root 16961 May 31 09:04 tunnel6.ko -rw-r--r-- 1 root root 19449 May 31 09:04 xfrm6_tunnel.ko root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6 total 752 drwxr-xr-x 3 root root 4096 Jun 28 20:17 ./ drwxr-xr-x 21 root root 4096 Jun 28 20:17 ../ -rw-r--r-- 1 root root 92705 Jun 21 12:50 ah6.ko -rw-r--r-- 1 root root 118881 Jun 21 12:50 esp6.ko -rw-r--r-- 1 root root 83465 Jun 21 12:50 esp6_offload.ko -rw-r--r-- 1 root root 74481 Jun 21 12:50 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 79129 Jun 21 12:50 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 28 20:17 netfilter/ -rw-r--r-- 1 root root 123361 Jun 21 12:50 sit.ko -rw-r--r-- 1 root root 81905 Jun 21 12:50 tunnel6.ko -rw-r--r-- 1 root root 84137 Jun 21 12:50 xfrm6_tunnel.ko That is just an example, modules have been growing all over the place. In sum the mentioned ~13mb. But neither did all modules change, nor was it by an equal amount. Here for example sit.ko more than doubled. https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious either, so I'd appreciate you having a look. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: minimal CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230628 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12 RelatedPackageVersions: linux-restricted-modules-6.2.0-1007-kvm N/A linux-backports-modules-6.2.0-1007-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-1007-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 2/2/2022 dmi.bios.release: 0.0 dmi.bios.vendor: EDK II dmi.bios.version: unknown dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-8.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-8.0 dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-8.0
[Kernel-packages] [Bug 2025984] WifiSyslog.txt
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. https://bugs.launchpad.net/bugs/2025984 Title: Size in crease in modules in 6.2.0-1007 Status in linux package in Ubuntu: New Bug description: 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 about it and we can be sure :-) Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS. I see root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6 total 368 drwxr-xr-x 3 root root 4096 Jun 21 20:18 ./ drwxr-xr-x 21 root root 4096 Jun 21 20:18 ../ -rw-r--r-- 1 root root 26305 May 31 09:04 ah6.ko -rw-r--r-- 1 root root 119073 May 31 09:04 esp6.ko -rw-r--r-- 1 root root 16889 May 31 09:04 esp6_offload.ko -rw-r--r-- 1 root root 74929 May 31 09:04 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 13409 May 31 09:04 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 21 20:18 netfilter/ -rw-r--r-- 1 root root 54617 May 31 09:04 sit.ko -rw-r--r-- 1 root root 16961 May 31 09:04 tunnel6.ko -rw-r--r-- 1 root root 19449 May 31 09:04 xfrm6_tunnel.ko root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6 total 752 drwxr-xr-x 3 root root 4096 Jun 28 20:17 ./ drwxr-xr-x 21 root root 4096 Jun 28 20:17 ../ -rw-r--r-- 1 root root 92705 Jun 21 12:50 ah6.ko -rw-r--r-- 1 root root 118881 Jun 21 12:50 esp6.ko -rw-r--r-- 1 root root 83465 Jun 21 12:50 esp6_offload.ko -rw-r--r-- 1 root root 74481 Jun 21 12:50 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 79129 Jun 21 12:50 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 28 20:17 netfilter/ -rw-r--r-- 1 root root 123361 Jun 21 12:50 sit.ko -rw-r--r-- 1 root root 81905 Jun 21 12:50 tunnel6.ko -rw-r--r-- 1 root root 84137 Jun 21 12:50 xfrm6_tunnel.ko That is just an example, modules have been growing all over the place. In sum the mentioned ~13mb. But neither did all modules change, nor was it by an equal amount. Here for example sit.ko more than doubled. https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious either, so I'd appreciate you having a look. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: minimal CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230628 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12 RelatedPackageVersions: linux-restricted-modules-6.2.0-1007-kvm N/A linux-backports-modules-6.2.0-1007-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-1007-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 2/2/2022 dmi.bios.release: 0.0 dmi.bios.vendor: EDK II dmi.bios.version: unknown dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-8.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-8.0 dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-8.0
[Kernel-packages] [Bug 2025984] acpidump.txt
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. https://bugs.launchpad.net/bugs/2025984 Title: Size in crease in modules in 6.2.0-1007 Status in linux package in Ubuntu: New Bug description: 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 about it and we can be sure :-) Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS. I see root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6 total 368 drwxr-xr-x 3 root root 4096 Jun 21 20:18 ./ drwxr-xr-x 21 root root 4096 Jun 21 20:18 ../ -rw-r--r-- 1 root root 26305 May 31 09:04 ah6.ko -rw-r--r-- 1 root root 119073 May 31 09:04 esp6.ko -rw-r--r-- 1 root root 16889 May 31 09:04 esp6_offload.ko -rw-r--r-- 1 root root 74929 May 31 09:04 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 13409 May 31 09:04 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 21 20:18 netfilter/ -rw-r--r-- 1 root root 54617 May 31 09:04 sit.ko -rw-r--r-- 1 root root 16961 May 31 09:04 tunnel6.ko -rw-r--r-- 1 root root 19449 May 31 09:04 xfrm6_tunnel.ko root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6 total 752 drwxr-xr-x 3 root root 4096 Jun 28 20:17 ./ drwxr-xr-x 21 root root 4096 Jun 28 20:17 ../ -rw-r--r-- 1 root root 92705 Jun 21 12:50 ah6.ko -rw-r--r-- 1 root root 118881 Jun 21 12:50 esp6.ko -rw-r--r-- 1 root root 83465 Jun 21 12:50 esp6_offload.ko -rw-r--r-- 1 root root 74481 Jun 21 12:50 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 79129 Jun 21 12:50 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 28 20:17 netfilter/ -rw-r--r-- 1 root root 123361 Jun 21 12:50 sit.ko -rw-r--r-- 1 root root 81905 Jun 21 12:50 tunnel6.ko -rw-r--r-- 1 root root 84137 Jun 21 12:50 xfrm6_tunnel.ko That is just an example, modules have been growing all over the place. In sum the mentioned ~13mb. But neither did all modules change, nor was it by an equal amount. Here for example sit.ko more than doubled. https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious either, so I'd appreciate you having a look. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: minimal CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230628 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12 RelatedPackageVersions: linux-restricted-modules-6.2.0-1007-kvm N/A linux-backports-modules-6.2.0-1007-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-1007-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 2/2/2022 dmi.bios.release: 0.0 dmi.bios.vendor: EDK II dmi.bios.version: unknown dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-8.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-8.0 dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-8.0 dmi.sys.vendor:
[Kernel-packages] [Bug 2025984] ProcCpuinfoMinimal.txt
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. https://bugs.launchpad.net/bugs/2025984 Title: Size in crease in modules in 6.2.0-1007 Status in linux package in Ubuntu: New Bug description: 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 about it and we can be sure :-) Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS. I see root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6 total 368 drwxr-xr-x 3 root root 4096 Jun 21 20:18 ./ drwxr-xr-x 21 root root 4096 Jun 21 20:18 ../ -rw-r--r-- 1 root root 26305 May 31 09:04 ah6.ko -rw-r--r-- 1 root root 119073 May 31 09:04 esp6.ko -rw-r--r-- 1 root root 16889 May 31 09:04 esp6_offload.ko -rw-r--r-- 1 root root 74929 May 31 09:04 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 13409 May 31 09:04 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 21 20:18 netfilter/ -rw-r--r-- 1 root root 54617 May 31 09:04 sit.ko -rw-r--r-- 1 root root 16961 May 31 09:04 tunnel6.ko -rw-r--r-- 1 root root 19449 May 31 09:04 xfrm6_tunnel.ko root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6 total 752 drwxr-xr-x 3 root root 4096 Jun 28 20:17 ./ drwxr-xr-x 21 root root 4096 Jun 28 20:17 ../ -rw-r--r-- 1 root root 92705 Jun 21 12:50 ah6.ko -rw-r--r-- 1 root root 118881 Jun 21 12:50 esp6.ko -rw-r--r-- 1 root root 83465 Jun 21 12:50 esp6_offload.ko -rw-r--r-- 1 root root 74481 Jun 21 12:50 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 79129 Jun 21 12:50 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 28 20:17 netfilter/ -rw-r--r-- 1 root root 123361 Jun 21 12:50 sit.ko -rw-r--r-- 1 root root 81905 Jun 21 12:50 tunnel6.ko -rw-r--r-- 1 root root 84137 Jun 21 12:50 xfrm6_tunnel.ko That is just an example, modules have been growing all over the place. In sum the mentioned ~13mb. But neither did all modules change, nor was it by an equal amount. Here for example sit.ko more than doubled. https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious either, so I'd appreciate you having a look. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: minimal CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230628 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12 RelatedPackageVersions: linux-restricted-modules-6.2.0-1007-kvm N/A linux-backports-modules-6.2.0-1007-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-1007-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 2/2/2022 dmi.bios.release: 0.0 dmi.bios.vendor: EDK II dmi.bios.version: unknown dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-8.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-8.0 dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-8.0
[Kernel-packages] [Bug 2025984] ProcInterrupts.txt
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. https://bugs.launchpad.net/bugs/2025984 Title: Size in crease in modules in 6.2.0-1007 Status in linux package in Ubuntu: New Bug description: 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 about it and we can be sure :-) Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS. I see root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6 total 368 drwxr-xr-x 3 root root 4096 Jun 21 20:18 ./ drwxr-xr-x 21 root root 4096 Jun 21 20:18 ../ -rw-r--r-- 1 root root 26305 May 31 09:04 ah6.ko -rw-r--r-- 1 root root 119073 May 31 09:04 esp6.ko -rw-r--r-- 1 root root 16889 May 31 09:04 esp6_offload.ko -rw-r--r-- 1 root root 74929 May 31 09:04 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 13409 May 31 09:04 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 21 20:18 netfilter/ -rw-r--r-- 1 root root 54617 May 31 09:04 sit.ko -rw-r--r-- 1 root root 16961 May 31 09:04 tunnel6.ko -rw-r--r-- 1 root root 19449 May 31 09:04 xfrm6_tunnel.ko root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6 total 752 drwxr-xr-x 3 root root 4096 Jun 28 20:17 ./ drwxr-xr-x 21 root root 4096 Jun 28 20:17 ../ -rw-r--r-- 1 root root 92705 Jun 21 12:50 ah6.ko -rw-r--r-- 1 root root 118881 Jun 21 12:50 esp6.ko -rw-r--r-- 1 root root 83465 Jun 21 12:50 esp6_offload.ko -rw-r--r-- 1 root root 74481 Jun 21 12:50 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 79129 Jun 21 12:50 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 28 20:17 netfilter/ -rw-r--r-- 1 root root 123361 Jun 21 12:50 sit.ko -rw-r--r-- 1 root root 81905 Jun 21 12:50 tunnel6.ko -rw-r--r-- 1 root root 84137 Jun 21 12:50 xfrm6_tunnel.ko That is just an example, modules have been growing all over the place. In sum the mentioned ~13mb. But neither did all modules change, nor was it by an equal amount. Here for example sit.ko more than doubled. https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious either, so I'd appreciate you having a look. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: minimal CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230628 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12 RelatedPackageVersions: linux-restricted-modules-6.2.0-1007-kvm N/A linux-backports-modules-6.2.0-1007-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-1007-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 2/2/2022 dmi.bios.release: 0.0 dmi.bios.vendor: EDK II dmi.bios.version: unknown dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-8.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-8.0 dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-8.0
[Kernel-packages] [Bug 2025984] ProcCpuinfo.txt
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. https://bugs.launchpad.net/bugs/2025984 Title: Size in crease in modules in 6.2.0-1007 Status in linux package in Ubuntu: New Bug description: 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 about it and we can be sure :-) Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS. I see root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6 total 368 drwxr-xr-x 3 root root 4096 Jun 21 20:18 ./ drwxr-xr-x 21 root root 4096 Jun 21 20:18 ../ -rw-r--r-- 1 root root 26305 May 31 09:04 ah6.ko -rw-r--r-- 1 root root 119073 May 31 09:04 esp6.ko -rw-r--r-- 1 root root 16889 May 31 09:04 esp6_offload.ko -rw-r--r-- 1 root root 74929 May 31 09:04 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 13409 May 31 09:04 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 21 20:18 netfilter/ -rw-r--r-- 1 root root 54617 May 31 09:04 sit.ko -rw-r--r-- 1 root root 16961 May 31 09:04 tunnel6.ko -rw-r--r-- 1 root root 19449 May 31 09:04 xfrm6_tunnel.ko root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6 total 752 drwxr-xr-x 3 root root 4096 Jun 28 20:17 ./ drwxr-xr-x 21 root root 4096 Jun 28 20:17 ../ -rw-r--r-- 1 root root 92705 Jun 21 12:50 ah6.ko -rw-r--r-- 1 root root 118881 Jun 21 12:50 esp6.ko -rw-r--r-- 1 root root 83465 Jun 21 12:50 esp6_offload.ko -rw-r--r-- 1 root root 74481 Jun 21 12:50 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 79129 Jun 21 12:50 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 28 20:17 netfilter/ -rw-r--r-- 1 root root 123361 Jun 21 12:50 sit.ko -rw-r--r-- 1 root root 81905 Jun 21 12:50 tunnel6.ko -rw-r--r-- 1 root root 84137 Jun 21 12:50 xfrm6_tunnel.ko That is just an example, modules have been growing all over the place. In sum the mentioned ~13mb. But neither did all modules change, nor was it by an equal amount. Here for example sit.ko more than doubled. https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious either, so I'd appreciate you having a look. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: minimal CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230628 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12 RelatedPackageVersions: linux-restricted-modules-6.2.0-1007-kvm N/A linux-backports-modules-6.2.0-1007-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-1007-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 2/2/2022 dmi.bios.release: 0.0 dmi.bios.vendor: EDK II dmi.bios.version: unknown dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-8.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-8.0 dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-8.0
[Kernel-packages] [Bug 2025984] CurrentDmesg.txt
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. https://bugs.launchpad.net/bugs/2025984 Title: Size in crease in modules in 6.2.0-1007 Status in linux package in Ubuntu: New Bug description: 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 about it and we can be sure :-) Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS. I see root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6 total 368 drwxr-xr-x 3 root root 4096 Jun 21 20:18 ./ drwxr-xr-x 21 root root 4096 Jun 21 20:18 ../ -rw-r--r-- 1 root root 26305 May 31 09:04 ah6.ko -rw-r--r-- 1 root root 119073 May 31 09:04 esp6.ko -rw-r--r-- 1 root root 16889 May 31 09:04 esp6_offload.ko -rw-r--r-- 1 root root 74929 May 31 09:04 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 13409 May 31 09:04 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 21 20:18 netfilter/ -rw-r--r-- 1 root root 54617 May 31 09:04 sit.ko -rw-r--r-- 1 root root 16961 May 31 09:04 tunnel6.ko -rw-r--r-- 1 root root 19449 May 31 09:04 xfrm6_tunnel.ko root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6 total 752 drwxr-xr-x 3 root root 4096 Jun 28 20:17 ./ drwxr-xr-x 21 root root 4096 Jun 28 20:17 ../ -rw-r--r-- 1 root root 92705 Jun 21 12:50 ah6.ko -rw-r--r-- 1 root root 118881 Jun 21 12:50 esp6.ko -rw-r--r-- 1 root root 83465 Jun 21 12:50 esp6_offload.ko -rw-r--r-- 1 root root 74481 Jun 21 12:50 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 79129 Jun 21 12:50 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 28 20:17 netfilter/ -rw-r--r-- 1 root root 123361 Jun 21 12:50 sit.ko -rw-r--r-- 1 root root 81905 Jun 21 12:50 tunnel6.ko -rw-r--r-- 1 root root 84137 Jun 21 12:50 xfrm6_tunnel.ko That is just an example, modules have been growing all over the place. In sum the mentioned ~13mb. But neither did all modules change, nor was it by an equal amount. Here for example sit.ko more than doubled. https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious either, so I'd appreciate you having a look. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: minimal CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230628 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12 RelatedPackageVersions: linux-restricted-modules-6.2.0-1007-kvm N/A linux-backports-modules-6.2.0-1007-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-1007-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 2/2/2022 dmi.bios.release: 0.0 dmi.bios.vendor: EDK II dmi.bios.version: unknown dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-8.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-8.0 dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-8.0
[Kernel-packages] [Bug 2025984] [NEW] Size in crease in modules in 6.2.0-1007
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 about it and we can be sure :-) Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS. I see root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6 total 368 drwxr-xr-x 3 root root 4096 Jun 21 20:18 ./ drwxr-xr-x 21 root root 4096 Jun 21 20:18 ../ -rw-r--r-- 1 root root 26305 May 31 09:04 ah6.ko -rw-r--r-- 1 root root 119073 May 31 09:04 esp6.ko -rw-r--r-- 1 root root 16889 May 31 09:04 esp6_offload.ko -rw-r--r-- 1 root root 74929 May 31 09:04 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 13409 May 31 09:04 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 21 20:18 netfilter/ -rw-r--r-- 1 root root 54617 May 31 09:04 sit.ko -rw-r--r-- 1 root root 16961 May 31 09:04 tunnel6.ko -rw-r--r-- 1 root root 19449 May 31 09:04 xfrm6_tunnel.ko root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6 total 752 drwxr-xr-x 3 root root 4096 Jun 28 20:17 ./ drwxr-xr-x 21 root root 4096 Jun 28 20:17 ../ -rw-r--r-- 1 root root 92705 Jun 21 12:50 ah6.ko -rw-r--r-- 1 root root 118881 Jun 21 12:50 esp6.ko -rw-r--r-- 1 root root 83465 Jun 21 12:50 esp6_offload.ko -rw-r--r-- 1 root root 74481 Jun 21 12:50 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 79129 Jun 21 12:50 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 28 20:17 netfilter/ -rw-r--r-- 1 root root 123361 Jun 21 12:50 sit.ko -rw-r--r-- 1 root root 81905 Jun 21 12:50 tunnel6.ko -rw-r--r-- 1 root root 84137 Jun 21 12:50 xfrm6_tunnel.ko That is just an example, modules have been growing all over the place. In sum the mentioned ~13mb. But neither did all modules change, nor was it by an equal amount. Here for example sit.ko more than doubled. https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious either, so I'd appreciate you having a look. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: minimal CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230628 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12 RelatedPackageVersions: linux-restricted-modules-6.2.0-1007-kvm N/A linux-backports-modules-6.2.0-1007-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-1007-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 2/2/2022 dmi.bios.release: 0.0 dmi.bios.vendor: EDK II dmi.bios.version: unknown dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-8.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-8.0 dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-8.0 dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bot-stop-nagging cloud-image lunar ** Tags added: bot-stop-nagging ** Tags added: apport-collected cloud-image lunar ** Description changed: 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 about it and we can be sure :-) Comparing
[Kernel-packages] [Bug 2015867] Re: Kernel 6.1 bumped the disk consumption on default images by 15%
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 Mantic. -- 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/2015867 Title: Kernel 6.1 bumped the disk consumption on default images by 15% Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] After enabling Rust support in the kernel we noticed an increased size in linux-headers, because all the Rust libraries required to build out-of-tree kernel modules are now included in linux-headers directly. The increased size goes from ~30MB to ~100MB. This extra size is not worth it, considering the small amount of users that are going to experiment Rust in the kernel at the moment. [Test case] Install linux-headers and check the size of /usr/src/linux- headers-`uname -r`. [Fix] Some work has already done to reduce the size of linux-headers by dropping some binary artifacts (*.o and *.cmd) that are not required to build out-of-tree kernel modules. Ideally it'd be nicer to provide a separate package (called for example linux-lib-rust-`uname -r`) to ship the Rust-specific dependencies (libraries / headers). In this way linux-headers would be restored back to the original size, those that want to experiment Rust in the kernel can simply install linux-lib-rust and we can prevent wasting space in the cloud images. [Regression potential] Introducing a new package in the kernel may break something in our kernel promotion workflow, so with this change applied we need to pay a little more attention when the kernel is going to be promoted to release/updates. [Original bug report] 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 -> linux-headers-6.2.0-1002-kvm 108072 linux-modules-5.19.0-1008-kvm 76090 -> linux-modules-6.2.0-1002-kvm 97221 I haven't looked deeper yet. Is that an accident and will be fixed soon, is that a change we can do nothing about, anything in between? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015867] Re: Kernel 6.1 bumped the disk consumption on default images by 15%
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 still quite high compared to former releases. I'll bump prio up to reflect that ** Attachment added: "Disk-consumption-spike.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015867/+attachment/5681406/+files/Disk-consumption-spike.png ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High -- 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/2015867 Title: Kernel 6.1 bumped the disk consumption on default images by 15% Status in linux package in Ubuntu: Confirmed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Confirmed Bug description: [Impact] After enabling Rust support in the kernel we noticed an increased size in linux-headers, because all the Rust libraries required to build out-of-tree kernel modules are now included in linux-headers directly. The increased size goes from ~30MB to ~100MB. This extra size is not worth it, considering the small amount of users that are going to experiment Rust in the kernel at the moment. [Test case] Install linux-headers and check the size of /usr/src/linux- headers-`uname -r`. [Fix] Some work has already done to reduce the size of linux-headers by dropping some binary artifacts (*.o and *.cmd) that are not required to build out-of-tree kernel modules. Ideally it'd be nicer to provide a separate package (called for example linux-lib-rust-`uname -r`) to ship the Rust-specific dependencies (libraries / headers). In this way linux-headers would be restored back to the original size, those that want to experiment Rust in the kernel can simply install linux-lib-rust and we can prevent wasting space in the cloud images. [Regression potential] Introducing a new package in the kernel may break something in our kernel promotion workflow, so with this change applied we need to pay a little more attention when the kernel is going to be promoted to release/updates. [Original bug report] 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 -> linux-headers-6.2.0-1002-kvm 108072 linux-modules-5.19.0-1008-kvm 76090 -> linux-modules-6.2.0-1002-kvm 97221 I haven't looked deeper yet. Is that an accident and will be fixed soon, is that a change we can do nothing about, anything in between? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
** 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 allow MoK/db verified root images Status in linux package in Ubuntu: New Status in linux-meta-azure package in Ubuntu: New Status in linux-meta-kvm package in Ubuntu: New Bug description: The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015867] Re: Kernel 6.1 bumped the disk consumption on default images by 15%
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 linux-headers-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb.extract/usr/src/linux-headers-6.2.0-1003-kvm/include/generated I know linux-headers are meant to be the full source, but this increases the size of a default installed (and therefore also often downloaded) package by x4. You see that even the compressed size increased, actually even more than extracted. I'm not sure we can, but could we think about separating that and not installing by default. I'm afraid that might break things but it juts feels rather "expensive" in terms of disk space, image size, regular download ... OTOH, looking at it maybe we can do something... I know rust is using static linking and it looks like here also a lot pre-generated content. /tmp/kernel-sizes/6.2/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: $ ll -S | head total 81876 -rw-r--r-- 1 paelzer paelzer 54727271 Apr 6 09:50 libcore.rmeta -rw-r--r-- 1 paelzer paelzer 18678432 Apr 6 09:50 libmacros.so -rw-r--r-- 1 paelzer paelzer 5380859 Apr 6 09:50 libbindings.rmeta -rw-r--r-- 1 paelzer paelzer 2835696 Apr 6 09:50 core.o -rw-r--r-- 1 paelzer paelzer 904778 Apr 6 09:50 liballoc.rmeta -rw-r--r-- 1 paelzer paelzer 589288 Apr 6 09:50 bindings.o -rw-r--r-- 1 paelzer paelzer 186221 Apr 6 09:50 libkernel.rmeta -rw-r--r-- 1 paelzer paelzer 106528 Apr 6 09:50 kernel.o -rw-r--r-- 1 paelzer paelzer99356 Apr 6 09:50 .bindings.o.cmd Since these are meant to be sources, could we provide them in a way to be regeneratable but not of the binary size and format in linux-headers? -- 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/2015867 Title: Kernel 6.1 bumped the disk consumption on default images by 15% Status in linux package in Ubuntu: Confirmed Bug description: 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 -> linux-headers-6.2.0-1002-kvm 108072 linux-modules-5.19.0-1008-kvm 76090 -> linux-modules-6.2.0-1002-kvm 97221 I haven't looked deeper yet. Is that an accident and will be fixed soon, is that a change we can do nothing about, anything in between? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015867] Re: Kernel 6.1 bumped the disk consumption on default images by 15%
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 and sizes as extracted on disk (just dpkg -x, you do not need a system to install): [I'm sure LP display will break this, looks reasonable in monospace) - [5] is a public gspread of the same content. 5.19-deb 6.2-debincrease 5.19-extract 6.2-extract increase name 163560 407486 149.14% 8058881188856 47.52% linux-buildinfo 290915416637576 471.90% 25134419 110300530338.84% linux-headers 734227251221.06%7341452 8890656 21.10% linux-image-unsigned 197923488 213022492 7.63% 11905670581294452144 8.73% linux-image-unsigned-dbgsym 12582164 13126606 4.33% 81571446 84147433 3.16% linux-kvm-headers 78908127575524-4.00%27081556 26699145 -1.41% linux-kvm-tools 15549556 17799166 14.47%78035966 89312382 14.45% linux-modules 1756 1758 0.11% 34409 34401-0.02%linux-tools Further [3][4] show that this isn't specific to the -kvm kernel. It is in the generic kernel as well. New code might have more modules, so while it is quite a lot and we need to ask ourself if anything could be done it might be a necessary step. But the sources, they have grown so much and are default installed. The bump to default image size is quite much IMHO - enough to discuss about it here at least. [1]: https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/devel/+build/24551183 [2]: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/25964206 [3]: https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/devel/+build/24547812 [4]: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/25964139 [5]: https://docs.google.com/spreadsheets/d/1hJ3cQpwDJ-NCcGTZfZD2zX7tpq8XRhIifYtnZL29sVU -- 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/2015867 Title: Kernel 6.1 bumped the disk consumption on default images by 15% Status in linux package in Ubuntu: Confirmed Bug description: 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 -> linux-headers-6.2.0-1002-kvm 108072 linux-modules-5.19.0-1008-kvm 76090 -> linux-modules-6.2.0-1002-kvm 97221 I haven't looked deeper yet. Is that an accident and will be fixed soon, is that a change we can do nothing about, anything in between? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015867] Re: Kernel 6.1 bumped the disk consumption on default images by 15%
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 Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015867 Title: Kernel 6.1 bumped the disk consumption on default images by 15% Status in linux package in Ubuntu: Confirmed Bug description: 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 -> linux-headers-6.2.0-1002-kvm 108072 linux-modules-5.19.0-1008-kvm 76090 -> linux-modules-6.2.0-1002-kvm 97221 I haven't looked deeper yet. Is that an accident and will be fixed soon, is that a change we can do nothing about, anything in between? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015867] [NEW] Kernel 6.1 bumped the disk consumption on default images by 15%
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 -> linux-headers-6.2.0-1002-kvm 108072 linux-modules-5.19.0-1008-kvm 76090 -> linux-modules-6.2.0-1002-kvm 97221 I haven't looked deeper yet. Is that an accident and will be fixed soon, is that a change we can do nothing about, anything in between? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-stop-nagging ** Tags added: bot-stop-nagging -- 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/2015867 Title: Kernel 6.1 bumped the disk consumption on default images by 15% Status in linux package in Ubuntu: Incomplete Bug description: 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 -> linux-headers-6.2.0-1002-kvm 108072 linux-modules-5.19.0-1008-kvm 76090 -> linux-modules-6.2.0-1002-kvm 97221 I haven't looked deeper yet. Is that an accident and will be fixed soon, is that a change we can do nothing about, anything in between? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967593] Re: kernel modules going missing after reboot
** 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 modules going missing after reboot Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. EDIT2: it turns out this is caused by the cloud-initramfs-copymods package mounting over modules locations. Removed it and reinstalled kernel modules package (extras didnt seem necessary, but probably prudent too). This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub,
[Kernel-packages] [Bug 1985956] Re: linux-libc-dev and libc6-dev do not agree who owns fsconfig_command
** 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 package in Ubuntu:
Fix Released
Status in libvirt package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
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
Candidate: 2.36-0ubuntu1
Version table:
*** 2.36-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.35-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
linux-libc-dev:
Installed: 5.19.0-15.15
Candidate: 5.19.0-15.15
Version table:
*** 5.19.0-15.15 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
5.15.0-27.28 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
Actually also with "just the kernel" from proposed this happens as in the
past only:
linux-libc-dev:amd64: /usr/include/linux/mount.h
included that struct.
File ownership
$ dpkg -S /usr/include/x86_64-linux-gnu/sys/mount.h /usr/include/linux/mount.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/sys/mount.h
linux-libc-dev:amd64: /usr/include/linux/mount.h
Example error from building libvirt:
In file included from /usr/include/linux/fs.h:19,
from ../../src/util/virfile.c:74:
/usr/include/linux/mount.h:95:6: error: redeclaration of 'enum
fsconfig_command'
95 | enum fsconfig_command {
| ^~~~
In file included from ../../src/util/virfile.c:46:
/usr/include/x86_64-linux-gnu/sys/mount.h:189:6: note: originally defined here
189 | enum fsconfig_command
| ^~~~
Repro-test:
$ cat test.c
# include
# include
#include
int main() {
printf("Hello %d", FSCONFIG_SET_FLAG);
return 0;
}
gcc test.c -o /dev/null
In file included from /usr/include/linux/fs.h:19,
from test.c:2:
/usr/include/linux/mount.h:95:6: error: redeclaration of 'enum
fsconfig_command'
95 | enum fsconfig_command {
| ^~~~
In file included from test.c:1:
/usr/include/x86_64-linux-gnu/sys/mount.h:189:6: note: originally defined here
189 | enum fsconfig_command
| ^~~~
/usr/include/linux/mount.h:96:9: error: redeclaration of enumerator
'FSCONFIG_SET_FLAG'
96 | FSCONFIG_SET_FLAG = 0,/* Set parameter, supplying
no value */
| ^
/usr/include/x86_64-linux-gnu/sys/mount.h:191:3: note: previous definition of
'FSCONFIG_SET_FLAG' with type 'enum fsconfig_command'
191 | FSCONFIG_SET_FLAG = 0,/* Set parameter, supplying no
value */
| ^
/usr/include/linux/mount.h:97:9: error: redeclaration of enumerator
'FSCONFIG_SET_STRING'
97 | FSCONFIG_SET_STRING = 1,/* Set parameter, supplying a
string value */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:193:3: note: previous definition of
'FSCONFIG_SET_STRING' with type 'enum fsconfig_command'
193 | FSCONFIG_SET_STRING = 1,/* Set parameter, supplying a
string value */
| ^~~
/usr/include/linux/mount.h:98:9: error: redeclaration of enumerator
'FSCONFIG_SET_BINARY'
98 | FSCONFIG_SET_BINARY = 2,/* Set parameter, supplying a
binary blob value */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:195:3: note: previous definition of
'FSCONFIG_SET_BINARY' with type 'enum fsconfig_command'
195 | FSCONFIG_SET_BINARY = 2,/* Set parameter, supplying a
binary blob value */
| ^~~
/usr/include/linux/mount.h:99:9: error: redeclaration of enumerator
'FSCONFIG_SET_PATH'
99 | FSCONFIG_SET_PATH = 3,/* Set parameter, supplying
an object by path */
| ^
/usr/include/x86_64-linux-gnu/sys/mount.h:197:3: note: previous definition of
'FSCONFIG_SET_PATH' with type 'enum fsconfig_command'
197 | FSCONFIG_SET_PATH = 3,/* Set parameter, supplying an
object by path */
| ^
/usr/include/linux/mount.h:100:9: error: redeclaration of enumerator
'FSCONFIG_SET_PATH_EMPTY'
100 | FSCONFIG_SET_PATH_EMPTY = 4,/* Set parameter, supplying
an object by (empty) path */
|
[Kernel-packages] [Bug 1945868] Re: focal kvm virtio_net set_features failed (-22)
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 are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945868 Title: focal kvm virtio_net set_features failed (-22) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Invalid Bug description: Setup linux-modules-5.4.0-88-generic within focal guest on a (equal) ubuntu 20.04 kvm bare metal machine. When using virtio as network driver it is failing with: net eth0: Fail to set guest offload. virtio_net virtio1 eth0: set_features() failed (-22); wanted 0x008000174a29, left 0x0 0800017ca29 followed by further kern log entries: [ cut here ] netdevice: br0: failed to disable 0x8000 on eth0! WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 __netdev_update_features+0x4d1/0x9f0 Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover failover pata_acpi floppy CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic #99-Ubuntu Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 RIP: 0010:__netdev_update_features+0x4d1/0x9f0 Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d b8 4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 8b 45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7 RSP: 0018:bf1840e0ba98 EFLAGS: 00010282 RAX: RBX: 000f RCX: 0006 RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0 RBP: bf1840e0bb10 R08: 02d1 R09: 0004 R10: R11: 0001 R12: 9c2c0b258000 R13: 9c2c0b2580c0 R14: 9c2c0615a000 R15: 000f FS: 7f98be558580() GS:9c2c13a0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fffc24a1080 CR3: 00030b3e4000 CR4: 06f0 Call Trace: netdev_update_features+0x25/0x60 br_device_event+0x20f/0x300 [bridge] notifier_call_chain+0x55/0x80 raw_notifier_call_chain+0x16/0x20 call_netdevice_notifiers_info+0x2e/0x60 netdev_update_features+0x59/0x60 dev_disable_lro+0x21/0xf0 br_add_if+0x301/0x650 [bridge] add_del_if+0x67/0x80 [bridge] br_dev_ioctl+0x54/0x80 [bridge] dev_ifsioc+0xe5/0x3e0 ? _cond_resched+0x19/0x30 dev_ioctl+0x2dd/0x470 sock_do_ioctl+0xa8/0x140 ? evict+0x14c/0x1b0 sock_ioctl+0x24f/0x3c0 ? _cond_resched+0x19/0x30 ? get_max_files+0x20/0x20 do_vfs_ioctl+0x407/0x670 ksys_ioctl+0x67/0x90 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f98be47c50b Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 RSP: 002b:7ffd783321e8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 0002 RCX: 7f98be47c50b RDX: 7ffd78332210 RSI: 89a2 RDI: 0003 RBP: 7ffd78332210 R08: 0020 R09: fefefeff77686d74 R10: 7ffd78333e80 R11: 0246 R12: 7ffd78333e7e R13: 7ffd78333e7e R14: R15: ---[ end trace 240d361752e8f3f0 ]--- [ cut here ] Temporary solution is to return to the old rtl8139 driver and slow network down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998184] Re: fanatic tests spawn latest LTS but isn't compatible with it
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 bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1998184 Title: fanatic tests spawn latest LTS but isn't compatible with it Status in ubuntu-fan package in Ubuntu: New Status in ubuntu-fan source package in Bionic: New Status in ubuntu-fan source package in Focal: New Status in ubuntu-fan source package in Jammy: New Status in ubuntu-fan source package in Kinetic: New Status in ubuntu-fan source package in Lunar: New Bug description: 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 (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998184] Re: fanatic tests spawn latest LTS but isn't compatible with it
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 test flaws, but the problem itself is still present and needs to be fixed in ubuntu-fan - until then there will be no test coverage. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1998184 Title: fanatic tests spawn latest LTS but isn't compatible with it Status in ubuntu-fan package in Ubuntu: New Status in ubuntu-fan source package in Bionic: New Status in ubuntu-fan source package in Focal: New Status in ubuntu-fan source package in Jammy: New Status in ubuntu-fan source package in Kinetic: New Status in ubuntu-fan source package in Lunar: New Bug description: 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 (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998184] Re: fanatic tests spawn latest LTS but isn't compatible with it
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 to the bug report. https://bugs.launchpad.net/bugs/1998184 Title: fanatic tests spawn latest LTS but isn't compatible with it Status in ubuntu-fan package in Ubuntu: New Status in ubuntu-fan source package in Bionic: New Status in ubuntu-fan source package in Focal: New Status in ubuntu-fan source package in Jammy: New Status in ubuntu-fan source package in Kinetic: New Status in ubuntu-fan source package in Lunar: New Bug description: 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 (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998184] Re: fanatic tests spawn latest LTS but isn't compatible with it
** 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: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1998184 Title: fanatic tests spawn latest LTS but isn't compatible with it Status in ubuntu-fan package in Ubuntu: New Status in ubuntu-fan source package in Bionic: New Status in ubuntu-fan source package in Focal: New Status in ubuntu-fan source package in Jammy: New Status in ubuntu-fan source package in Kinetic: New Status in ubuntu-fan source package in Lunar: New Bug description: 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 (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998184] [NEW] fanatic tests spawn latest LTS but isn't compatible with it
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 (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. ** Affects: ubuntu-fan (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-fan (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: ubuntu-fan (Ubuntu Focal) Importance: Undecided Status: New ** Affects: ubuntu-fan (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: ubuntu-fan (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: ubuntu-fan (Ubuntu Lunar) Importance: Undecided Status: New -- 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/1998184 Title: fanatic tests spawn latest LTS but isn't compatible with it Status in ubuntu-fan package in Ubuntu: New Status in ubuntu-fan source package in Bionic: New Status in ubuntu-fan source package in Focal: New Status in ubuntu-fan source package in Jammy: New Status in ubuntu-fan source package in Kinetic: New Status in ubuntu-fan source package in Lunar: New Bug description: 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 (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981783] Re: there is an ACPI error message every time it booting
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 regardless of the query flag And then reverted in: commit 2ca8e6285250c07a2e5a22ecbfd59b5a4ef73484 Author: Rafael J. Wysocki Date: Wed Mar 16 13:37:44 2022 +0100 Revert "ACPI: Pass the same capabilities to the _OSC regardless of the query flag" In Ubuntu the revert landed in 5.15.33 upstream and 5.15.0-34 in Ubuntu. I'm not entirely sure yet (no access to the system atm) if the introduction or the revert caused it. But since it still happens to people I assume the latter. AFAICS no further new commit happened since then to resolve the problem for both cases ... -- 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/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS
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 uncommon and breaking the parser in libvirt #1. libvirt You could gather some info and then decide if it is more (a) or (b) to then report it directly to intel or to upstream libvirt [1] to have a look. I think to check what libvirt can (or can not read) you could run $ virsh nodedev-list # now select the i350 OCP $ virsh nodedev-dumpxml That should cause libvirt to try to read and report you the VPD data of the device. I'd expect this triggers the issue, maybe you find anything odd in there already ... 1b. debug If 1 recerates the issue you might want to run the same with livbirt debug info enabled [3] and report that here and/or upstream depending what you see. #2. kernel This is rather kernel dependent, it might be worth trying a few older/newer mainline kernels [2] to see if any might already behave different #3. data It might be great to report the actual VPD data exposed. That would be $ sudo cat /sys/devices/pci...///vpd Until we (or intel or upstreams) have that data there is not much we can do, hence setting the bug to incomplete for now. [1]: https://gitlab.com/libvirt/libvirt/-/issues [2]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ [3]: https://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Debug.html ** Changed in: libvirt (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (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/1986520 Title: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hardware Configuration: Server MTM: Bona POR SE450 OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) BMC Version: 1.40 (Build ID: USX311E) UEFI Version: 1.03 (Build ID: CME105C) LXPM Version: 3.19 (Build ID: CML103A) CPU: Xeon Silver 4314 16C 135W 2.4GHz DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; HMA84GR7CJR4N-XNT4 DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2 IO Config: RAID: Intel VROC (VMD NVMe RAID) Premium SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 Ethernet Adapter SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter Storage: DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD PSU1: CFFv4 AC 1100W (Delta) 110V PSU2: CFFv4 AC 1100W (Delta) 110V M/B build version: PASS5 MB Steps: 1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk. 2. Install KVM features and desktop GUI. 3. Run "apt upgrade" to update packages. 4. Create a namespace on BPS DIMM App Direct Not Interleaved mode. 5. Run "virt-manager" then install Windows Server 2022 on the namespace. 6. Reboot Guest OS and Host OS to check if there is any unexpected error in system logs. (=> failed, there are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] ) Expected behaviors: There are no any unexpected errors in system logs. Current behaviors: There are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-18 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220816) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894 Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root
[Kernel-packages] [Bug 1985956] Re: linux-libc-dev and libc6-dev do not agree who owns fsconfig_command
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 fine through all tests.
--
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 package in Ubuntu:
New
Status in libvirt package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
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
Candidate: 2.36-0ubuntu1
Version table:
*** 2.36-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.35-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
linux-libc-dev:
Installed: 5.19.0-15.15
Candidate: 5.19.0-15.15
Version table:
*** 5.19.0-15.15 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
5.15.0-27.28 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
Actually also with "just the kernel" from proposed this happens as in the
past only:
linux-libc-dev:amd64: /usr/include/linux/mount.h
included that struct.
File ownership
$ dpkg -S /usr/include/x86_64-linux-gnu/sys/mount.h /usr/include/linux/mount.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/sys/mount.h
linux-libc-dev:amd64: /usr/include/linux/mount.h
Example error from building libvirt:
In file included from /usr/include/linux/fs.h:19,
from ../../src/util/virfile.c:74:
/usr/include/linux/mount.h:95:6: error: redeclaration of 'enum
fsconfig_command'
95 | enum fsconfig_command {
| ^~~~
In file included from ../../src/util/virfile.c:46:
/usr/include/x86_64-linux-gnu/sys/mount.h:189:6: note: originally defined here
189 | enum fsconfig_command
| ^~~~
Repro-test:
$ cat test.c
# include
# include
#include
int main() {
printf("Hello %d", FSCONFIG_SET_FLAG);
return 0;
}
gcc test.c -o /dev/null
In file included from /usr/include/linux/fs.h:19,
from test.c:2:
/usr/include/linux/mount.h:95:6: error: redeclaration of 'enum
fsconfig_command'
95 | enum fsconfig_command {
| ^~~~
In file included from test.c:1:
/usr/include/x86_64-linux-gnu/sys/mount.h:189:6: note: originally defined here
189 | enum fsconfig_command
| ^~~~
/usr/include/linux/mount.h:96:9: error: redeclaration of enumerator
'FSCONFIG_SET_FLAG'
96 | FSCONFIG_SET_FLAG = 0,/* Set parameter, supplying
no value */
| ^
/usr/include/x86_64-linux-gnu/sys/mount.h:191:3: note: previous definition of
'FSCONFIG_SET_FLAG' with type 'enum fsconfig_command'
191 | FSCONFIG_SET_FLAG = 0,/* Set parameter, supplying no
value */
| ^
/usr/include/linux/mount.h:97:9: error: redeclaration of enumerator
'FSCONFIG_SET_STRING'
97 | FSCONFIG_SET_STRING = 1,/* Set parameter, supplying a
string value */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:193:3: note: previous definition of
'FSCONFIG_SET_STRING' with type 'enum fsconfig_command'
193 | FSCONFIG_SET_STRING = 1,/* Set parameter, supplying a
string value */
| ^~~
/usr/include/linux/mount.h:98:9: error: redeclaration of enumerator
'FSCONFIG_SET_BINARY'
98 | FSCONFIG_SET_BINARY = 2,/* Set parameter, supplying a
binary blob value */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:195:3: note: previous definition of
'FSCONFIG_SET_BINARY' with type 'enum fsconfig_command'
195 | FSCONFIG_SET_BINARY = 2,/* Set parameter, supplying a
binary blob value */
| ^~~
/usr/include/linux/mount.h:99:9: error: redeclaration of enumerator
'FSCONFIG_SET_PATH'
99 | FSCONFIG_SET_PATH = 3,/* Set parameter, supplying
an object by path */
| ^
/usr/include/x86_64-linux-gnu/sys/mount.h:197:3: note: previous definition of
'FSCONFIG_SET_PATH' with type 'enum fsconfig_command'
197 | FSCONFIG_SET_PATH = 3,/* Set parameter, supplying
[Kernel-packages] [Bug 1985956] Re: linux-libc-dev and libc6-dev do not agree who owns fsconfig_command
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 added: 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 package in Ubuntu:
New
Status in libvirt package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
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
Candidate: 2.36-0ubuntu1
Version table:
*** 2.36-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.35-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
linux-libc-dev:
Installed: 5.19.0-15.15
Candidate: 5.19.0-15.15
Version table:
*** 5.19.0-15.15 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
5.15.0-27.28 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
Actually also with "just the kernel" from proposed this happens as in the
past only:
linux-libc-dev:amd64: /usr/include/linux/mount.h
included that struct.
File ownership
$ dpkg -S /usr/include/x86_64-linux-gnu/sys/mount.h /usr/include/linux/mount.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/sys/mount.h
linux-libc-dev:amd64: /usr/include/linux/mount.h
Example error from building libvirt:
In file included from /usr/include/linux/fs.h:19,
from ../../src/util/virfile.c:74:
/usr/include/linux/mount.h:95:6: error: redeclaration of 'enum
fsconfig_command'
95 | enum fsconfig_command {
| ^~~~
In file included from ../../src/util/virfile.c:46:
/usr/include/x86_64-linux-gnu/sys/mount.h:189:6: note: originally defined here
189 | enum fsconfig_command
| ^~~~
Repro-test:
$ cat test.c
# include
# include
#include
int main() {
printf("Hello %d", FSCONFIG_SET_FLAG);
return 0;
}
gcc test.c -o /dev/null
In file included from /usr/include/linux/fs.h:19,
from test.c:2:
/usr/include/linux/mount.h:95:6: error: redeclaration of 'enum
fsconfig_command'
95 | enum fsconfig_command {
| ^~~~
In file included from test.c:1:
/usr/include/x86_64-linux-gnu/sys/mount.h:189:6: note: originally defined here
189 | enum fsconfig_command
| ^~~~
/usr/include/linux/mount.h:96:9: error: redeclaration of enumerator
'FSCONFIG_SET_FLAG'
96 | FSCONFIG_SET_FLAG = 0,/* Set parameter, supplying
no value */
| ^
/usr/include/x86_64-linux-gnu/sys/mount.h:191:3: note: previous definition of
'FSCONFIG_SET_FLAG' with type 'enum fsconfig_command'
191 | FSCONFIG_SET_FLAG = 0,/* Set parameter, supplying no
value */
| ^
/usr/include/linux/mount.h:97:9: error: redeclaration of enumerator
'FSCONFIG_SET_STRING'
97 | FSCONFIG_SET_STRING = 1,/* Set parameter, supplying a
string value */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:193:3: note: previous definition of
'FSCONFIG_SET_STRING' with type 'enum fsconfig_command'
193 | FSCONFIG_SET_STRING = 1,/* Set parameter, supplying a
string value */
| ^~~
/usr/include/linux/mount.h:98:9: error: redeclaration of enumerator
'FSCONFIG_SET_BINARY'
98 | FSCONFIG_SET_BINARY = 2,/* Set parameter, supplying a
binary blob value */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:195:3: note: previous definition of
'FSCONFIG_SET_BINARY' with type 'enum fsconfig_command'
195 | FSCONFIG_SET_BINARY = 2,/* Set parameter, supplying a
binary blob value */
| ^~~
/usr/include/linux/mount.h:99:9: error: redeclaration of enumerator
'FSCONFIG_SET_PATH'
99 | FSCONFIG_SET_PATH = 3,/* Set parameter, supplying
an object by path */
| ^
/usr/include/x86_64-linux-gnu/sys/mount.h:197:3: note: previous definition of
'FSCONFIG_SET_PATH' with type 'enum fsconfig_command'
197 | FSCONFIG_SET_PATH = 3,/* Set parameter, supplying an
Re: [Kernel-packages] [Bug 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS
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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986520 Title: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hardware Configuration: Server MTM: Bona POR SE450 OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) BMC Version: 1.40 (Build ID: USX311E) UEFI Version: 1.03 (Build ID: CME105C) LXPM Version: 3.19 (Build ID: CML103A) CPU: Xeon Silver 4314 16C 135W 2.4GHz DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; HMA84GR7CJR4N-XNT4 DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2 IO Config: RAID: Intel VROC (VMD NVMe RAID) Premium SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 Ethernet Adapter SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter Storage: DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD PSU1: CFFv4 AC 1100W (Delta) 110V PSU2: CFFv4 AC 1100W (Delta) 110V M/B build version: PASS5 MB Steps: 1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk. 2. Install KVM features and desktop GUI. 3. Run "apt upgrade" to update packages. 4. Create a namespace on BPS DIMM App Direct Not Interleaved mode. 5. Run "virt-manager" then install Windows Server 2022 on the namespace. 6. Reboot Guest OS and Host OS to check if there is any unexpected error in system logs. (=> failed, there are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] ) Expected behaviors: There are no any unexpected errors in system logs. Current behaviors: There are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1986520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985956] Re: linux-libc-dev and libc6-dev do not agree who owns fsconfig_command
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)
So while both still exist:
linux-libc-dev | 5.15.0-27.28 | kinetic | amd64, arm64, armhf,
i386, ppc64el, riscv64, s390x
linux-libc-dev | 5.19.0-15.15 | kinetic-proposed | amd64, arm64, armhf,
i386, ppc64el, riscv64, s390x
Probably some other dependency makes this non-avoidable for now.
--
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 package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Bug description:
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
Candidate: 2.36-0ubuntu1
Version table:
*** 2.36-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.35-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
linux-libc-dev:
Installed: 5.19.0-15.15
Candidate: 5.19.0-15.15
Version table:
*** 5.19.0-15.15 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
5.15.0-27.28 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
Actually also with "just the kernel" from proposed this happens as in the
past only:
linux-libc-dev:amd64: /usr/include/linux/mount.h
included that struct.
File ownership
$ dpkg -S /usr/include/x86_64-linux-gnu/sys/mount.h /usr/include/linux/mount.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/sys/mount.h
linux-libc-dev:amd64: /usr/include/linux/mount.h
Example error from building libvirt:
In file included from /usr/include/linux/fs.h:19,
from ../../src/util/virfile.c:74:
/usr/include/linux/mount.h:95:6: error: redeclaration of 'enum
fsconfig_command'
95 | enum fsconfig_command {
| ^~~~
In file included from ../../src/util/virfile.c:46:
/usr/include/x86_64-linux-gnu/sys/mount.h:189:6: note: originally defined here
189 | enum fsconfig_command
| ^~~~
Repro-test:
$ cat test.c
# include
# include
#include
int main() {
printf("Hello %d", FSCONFIG_SET_FLAG);
return 0;
}
gcc test.c -o /dev/null
In file included from /usr/include/linux/fs.h:19,
from test.c:2:
/usr/include/linux/mount.h:95:6: error: redeclaration of 'enum
fsconfig_command'
95 | enum fsconfig_command {
| ^~~~
In file included from test.c:1:
/usr/include/x86_64-linux-gnu/sys/mount.h:189:6: note: originally defined here
189 | enum fsconfig_command
| ^~~~
/usr/include/linux/mount.h:96:9: error: redeclaration of enumerator
'FSCONFIG_SET_FLAG'
96 | FSCONFIG_SET_FLAG = 0,/* Set parameter, supplying
no value */
| ^
/usr/include/x86_64-linux-gnu/sys/mount.h:191:3: note: previous definition of
'FSCONFIG_SET_FLAG' with type 'enum fsconfig_command'
191 | FSCONFIG_SET_FLAG = 0,/* Set parameter, supplying no
value */
| ^
/usr/include/linux/mount.h:97:9: error: redeclaration of enumerator
'FSCONFIG_SET_STRING'
97 | FSCONFIG_SET_STRING = 1,/* Set parameter, supplying a
string value */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:193:3: note: previous definition of
'FSCONFIG_SET_STRING' with type 'enum fsconfig_command'
193 | FSCONFIG_SET_STRING = 1,/* Set parameter, supplying a
string value */
| ^~~
/usr/include/linux/mount.h:98:9: error: redeclaration of enumerator
'FSCONFIG_SET_BINARY'
98 | FSCONFIG_SET_BINARY = 2,/* Set parameter, supplying a
binary blob value */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:195:3: note: previous definition of
'FSCONFIG_SET_BINARY' with type 'enum fsconfig_command'
195 | FSCONFIG_SET_BINARY = 2,/* Set parameter, supplying a
binary blob value */
| ^~~
/usr/include/linux/mount.h:99:9: error: redeclaration of enumerator
'FSCONFIG_SET_PATH'
99 | FSCONFIG_SET_PATH = 3,/* Set parameter, supplying
an object by path */
|
[Kernel-packages] [Bug 1985956] [NEW] linux-libc-dev and libc6-dev do not agree who owns fsconfig_command
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
Candidate: 2.36-0ubuntu1
Version table:
*** 2.36-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.35-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
linux-libc-dev:
Installed: 5.19.0-15.15
Candidate: 5.19.0-15.15
Version table:
*** 5.19.0-15.15 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
5.15.0-27.28 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
Actually also with "just the kernel" from proposed this happens as in the past
only:
linux-libc-dev:amd64: /usr/include/linux/mount.h
included that struct.
File ownership
$ dpkg -S /usr/include/x86_64-linux-gnu/sys/mount.h /usr/include/linux/mount.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/sys/mount.h
linux-libc-dev:amd64: /usr/include/linux/mount.h
Example error from building libvirt:
In file included from /usr/include/linux/fs.h:19,
from ../../src/util/virfile.c:74:
/usr/include/linux/mount.h:95:6: error: redeclaration of 'enum fsconfig_command'
95 | enum fsconfig_command {
| ^~~~
In file included from ../../src/util/virfile.c:46:
/usr/include/x86_64-linux-gnu/sys/mount.h:189:6: note: originally defined here
189 | enum fsconfig_command
| ^~~~
Repro-test:
$ cat test.c
# include
# include
#include
int main() {
printf("Hello %d", FSCONFIG_SET_FLAG);
return 0;
}
gcc test.c -o /dev/null
In file included from /usr/include/linux/fs.h:19,
from test.c:2:
/usr/include/linux/mount.h:95:6: error: redeclaration of 'enum fsconfig_command'
95 | enum fsconfig_command {
| ^~~~
In file included from test.c:1:
/usr/include/x86_64-linux-gnu/sys/mount.h:189:6: note: originally defined here
189 | enum fsconfig_command
| ^~~~
/usr/include/linux/mount.h:96:9: error: redeclaration of enumerator
'FSCONFIG_SET_FLAG'
96 | FSCONFIG_SET_FLAG = 0,/* Set parameter, supplying no
value */
| ^
/usr/include/x86_64-linux-gnu/sys/mount.h:191:3: note: previous definition of
'FSCONFIG_SET_FLAG' with type 'enum fsconfig_command'
191 | FSCONFIG_SET_FLAG = 0,/* Set parameter, supplying no value
*/
| ^
/usr/include/linux/mount.h:97:9: error: redeclaration of enumerator
'FSCONFIG_SET_STRING'
97 | FSCONFIG_SET_STRING = 1,/* Set parameter, supplying a
string value */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:193:3: note: previous definition of
'FSCONFIG_SET_STRING' with type 'enum fsconfig_command'
193 | FSCONFIG_SET_STRING = 1,/* Set parameter, supplying a string
value */
| ^~~
/usr/include/linux/mount.h:98:9: error: redeclaration of enumerator
'FSCONFIG_SET_BINARY'
98 | FSCONFIG_SET_BINARY = 2,/* Set parameter, supplying a
binary blob value */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:195:3: note: previous definition of
'FSCONFIG_SET_BINARY' with type 'enum fsconfig_command'
195 | FSCONFIG_SET_BINARY = 2,/* Set parameter, supplying a binary
blob value */
| ^~~
/usr/include/linux/mount.h:99:9: error: redeclaration of enumerator
'FSCONFIG_SET_PATH'
99 | FSCONFIG_SET_PATH = 3,/* Set parameter, supplying an
object by path */
| ^
/usr/include/x86_64-linux-gnu/sys/mount.h:197:3: note: previous definition of
'FSCONFIG_SET_PATH' with type 'enum fsconfig_command'
197 | FSCONFIG_SET_PATH = 3,/* Set parameter, supplying an object
by path */
| ^
/usr/include/linux/mount.h:100:9: error: redeclaration of enumerator
'FSCONFIG_SET_PATH_EMPTY'
100 | FSCONFIG_SET_PATH_EMPTY = 4,/* Set parameter, supplying an
object by (empty) path */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:199:3: note: previous definition of
'FSCONFIG_SET_PATH_EMPTY' with type 'enum fsconfig_command'
199 | FSCONFIG_SET_PATH_EMPTY = 4,/* Set parameter, supplying an object
by (empty) path */
| ^~~
/usr/include/linux/mount.h:101:9: error: redeclaration of enumerator
'FSCONFIG_SET_FD'
101 | FSCONFIG_SET_FD = 5,/* Set parameter, supplying an
object by fd */
| ^~~
/usr/include/x86_64-linux-gnu/sys/mount.h:201:3: note: previous definition of
[Kernel-packages] [Bug 1981783] Re: there is an ACPI error message every time it booting
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 are also more people on there saying that it triggers with 5.15.0-41. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=213023 ** Bug watch added: Linux Kernel Bug Tracker #213023 https://bugzilla.kernel.org/show_bug.cgi?id=213023 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=213023 Importance: Unknown Status: Unknown -- 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/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738272] Re: microcode packages, like firmware packages, should be in main
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 firmware-sof source package to main to be consistent with linux-firmware. See bug [11:53] See bug 1738272 Even if all other special firmware cases apply this still would need an owning team. http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html lists kernel-packages as the owner, so that aspect should be fine indeed. @Kernel Team - or most likely @apw - do you agree and want this promoted as maintained by the kernel team? @Luis: This isn't listed in https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html so there would need to be a dependency or seed change to hold it in main. Do you know (if not coordinate with the kernel team please) where this will be done before being promoted? [Without that it would again fall out of main in the next few hours after promotion] ** Also affects: firmware-sof (Ubuntu) Importance: Undecided Status: New ** Changed in: firmware-sof (Ubuntu) Status: New => Incomplete ** Changed in: firmware-sof (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1738272 Title: microcode packages, like firmware packages, should be in main Status in firmware-sof package in Ubuntu: Incomplete Status in intel-microcode package in Ubuntu: Fix Released Status in iucode-tool package in Ubuntu: Fix Released Bug description: The MIR for intel-microcode and iucode-tool in LP: #139 requested that these packages be shipped in restricted. The iucode-tool package is free software, and is shipped in restricted only because of the circular recommends with intel-microcode. The intel-microcode package contains non-free software (free redistribution, but no source code). However, this code is not part of the OS; it runs /under/ the OS on the CPU, and is analogous to linux-firmware, which we do include in main. The question of suitability for restricted vs. main in Ubuntu was not examined as part of the previous MIR, and the security team signed off on it for "restricted or main as appropriate"; so I think the decision to put it in restricted was not based on a thorough examination of the facts by an archive admin, and does not represent a precedent that needs to be examined further. I believe that these two packages should be promoted to main for consistency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1738272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
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 feature and spawn a guest without", but then you'd end up on the new system with guests that appear to have the very same definition but behaving different - that would (other than not being implemented yet) still sound like asking for even more trouble. [1]: https://gitlab.com/libvirt/libvirt/-/commit/52cbfb2186364b1ab64f56e1360dcbc7d8ab85c1 [2]: https://gitlab.com/libvirt/libvirt/-/commit/7e0a3104982c5ba273316d6e39184d28c9f2fc9a -- 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/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $
[Kernel-packages] [Bug 1886364] Re: initiator causes kernel crash when login lun/disk on Focal
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 btw) ** Changed in: linux (Ubuntu Focal) Status: Confirmed => 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/1886364 Title: initiator causes kernel crash when login lun/disk on Focal Status in ceph-iscsi package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Released Bug description: Software version linaro@j13-r120-t32-09:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal linaro@j13-r120-t32-09:~$ uname -a Linux j13-r120-t32-09 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 17:57:16 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux linaro@j13-r120-t32-09:~$ stack@j13-r120-t32-09:~/devstack-plugin-ceph$ apt search ceph-iscsi Sorting... Done Full Text Search... Done ceph-iscsi/focal,now 3.4-0ubuntu2 all [installed] common logic and CLI tools for creating and managing LIO gateways for Ceph stack@j13-r120-t32-09:~/devstack-plugin-ceph$ apt search tcmu-runner Sorting... Done Full Text Search... Done libtcmu2/focal,now 1.5.2-5build1 arm64 [installed,automatic] Library that handles the userspace side of the LIO TCM-User backstore tcmu-runner/focal,now 1.5.2-5build1 arm64 [installed] Daemon that handles the userspace side of the LIO TCM-User backstore Hardware cavium thx1 root@j13-r120-t32-09:/home/linaro# lshw -c cpu *-cpu description: CPU product: ARM (CN88xx) vendor: CN8890-2000BG2601-CP-Y-G physical id: 2e bus info: cpu@0 version: 2.1 serial: CPU Serial# slot: Socket size: 2GHz capacity: 2GHz clock: 156MHz capabilities: lm configuration: cores=48 enabledcores=48 root@j13-r120-t32-09:/home/linaro# lshw -c system j13-r120-t32-09 description: System product: R120-T32-00 (01234567890123456789AB) vendor: GIGABYTE version: 0100 serial: GHG2N2912A0009 width: 64 bits capabilities: smbios-3.0.0 dmi-3.0.0 smp cp15_barrier setend swp tagged_addr_disabled configuration: chassis=server family=Server sku=01234567890123456789AB uuid=--4000-8000-1C1B0D94A9DE Reproduce Setup ceph iscsi gate way and initiator in the same ubuntu focal all-in-one. iSCSI targets setup 1, $ apt install ceph-iscsi targetcli-fb 2, ceph iscsi config stack@j13-r120-t32-09:~/devstack-plugin-ceph$ sudo cat /etc/ceph/iscsi-gateway.cfg [config] api_port = 5002 api_password = openstack api_user = openstack api_secure = false prometheus_host = 10.101.96.110 gateway_keyring = ceph.client.admin.keyring cluster_name = ceph trusted_ip_list = 10.101.96.110,localhost minimum_gateways = 1 pool = volumes 3, target iqn, client iqn, disk/lun creation https://docs.ceph.com/docs/master//rbd/iscsi-target-cli/ iSCSI initiator setup 1, $ apt install open-iscsi https://www.server-world.info/en/note?os=Ubuntu_18.04=iscsi=3 2, $ iscsiadm -m discovery -t sendtargets -p 10.101.96.110 $ sudo iscsiadm -m node -T iqn.1993-08.org.opendev:01:a9aa4032d2c1 -l Login lun cause crash ceph iscsi gw node [ 122.112611] xfs filesystem being mounted at /var/lib/ceph supports timestamps until 2038 (0x7fff) linaro@j13-r120-t32-09:~$ [ 1512.796815] Unable to handle kernel read from unreadable memory at virtual address 01dc0040 [ 1512.805865] Mem abort info: [ 1512.808647] ESR = 0x9604 [ 1512.811702] EC = 0x25: DABT (current EL), IL = 32 bits [ 1512.817023] SET = 0, FnV = 0 [ 1512.820089] EA = 0, S1PTW = 0 [ 1512.823238] Data abort info: [ 1512.826128] ISV = 0, ISS = 0x0004 [ 1512.829972] CM = 0, WnR = 0 [ 1512.832933] user pgtable: 4k pages, 48-bit VAs, pgdp=000cd14a [ 1512.839410] [01dc0040] pgd= [ 1512.844300] Internal error: Oops: 9604 [#1] SMP [ 1512.849169] Modules linked in: target_core_pscsi target_core_file target_core_iblock iscsi_target_mod xfs xt_REDIRECT xt_comment xt_nat xt_mark xt_connmark ip6table_raw iptable_raw xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc target_core_user uio target_core_mod nf_conntrack_netlink binfmt_misc nls_iso8859_1 nfnetlink_cttimeout nfnetlink ipmi_ssif
[Kernel-packages] [Bug 1886364] Re: initiator causes kernel crash when login lun/disk on Focal
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. https://bugs.launchpad.net/bugs/1886364 Title: initiator causes kernel crash when login lun/disk on Focal Status in ceph-iscsi package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Released Bug description: Software version linaro@j13-r120-t32-09:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal linaro@j13-r120-t32-09:~$ uname -a Linux j13-r120-t32-09 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 17:57:16 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux linaro@j13-r120-t32-09:~$ stack@j13-r120-t32-09:~/devstack-plugin-ceph$ apt search ceph-iscsi Sorting... Done Full Text Search... Done ceph-iscsi/focal,now 3.4-0ubuntu2 all [installed] common logic and CLI tools for creating and managing LIO gateways for Ceph stack@j13-r120-t32-09:~/devstack-plugin-ceph$ apt search tcmu-runner Sorting... Done Full Text Search... Done libtcmu2/focal,now 1.5.2-5build1 arm64 [installed,automatic] Library that handles the userspace side of the LIO TCM-User backstore tcmu-runner/focal,now 1.5.2-5build1 arm64 [installed] Daemon that handles the userspace side of the LIO TCM-User backstore Hardware cavium thx1 root@j13-r120-t32-09:/home/linaro# lshw -c cpu *-cpu description: CPU product: ARM (CN88xx) vendor: CN8890-2000BG2601-CP-Y-G physical id: 2e bus info: cpu@0 version: 2.1 serial: CPU Serial# slot: Socket size: 2GHz capacity: 2GHz clock: 156MHz capabilities: lm configuration: cores=48 enabledcores=48 root@j13-r120-t32-09:/home/linaro# lshw -c system j13-r120-t32-09 description: System product: R120-T32-00 (01234567890123456789AB) vendor: GIGABYTE version: 0100 serial: GHG2N2912A0009 width: 64 bits capabilities: smbios-3.0.0 dmi-3.0.0 smp cp15_barrier setend swp tagged_addr_disabled configuration: chassis=server family=Server sku=01234567890123456789AB uuid=--4000-8000-1C1B0D94A9DE Reproduce Setup ceph iscsi gate way and initiator in the same ubuntu focal all-in-one. iSCSI targets setup 1, $ apt install ceph-iscsi targetcli-fb 2, ceph iscsi config stack@j13-r120-t32-09:~/devstack-plugin-ceph$ sudo cat /etc/ceph/iscsi-gateway.cfg [config] api_port = 5002 api_password = openstack api_user = openstack api_secure = false prometheus_host = 10.101.96.110 gateway_keyring = ceph.client.admin.keyring cluster_name = ceph trusted_ip_list = 10.101.96.110,localhost minimum_gateways = 1 pool = volumes 3, target iqn, client iqn, disk/lun creation https://docs.ceph.com/docs/master//rbd/iscsi-target-cli/ iSCSI initiator setup 1, $ apt install open-iscsi https://www.server-world.info/en/note?os=Ubuntu_18.04=iscsi=3 2, $ iscsiadm -m discovery -t sendtargets -p 10.101.96.110 $ sudo iscsiadm -m node -T iqn.1993-08.org.opendev:01:a9aa4032d2c1 -l Login lun cause crash ceph iscsi gw node [ 122.112611] xfs filesystem being mounted at /var/lib/ceph supports timestamps until 2038 (0x7fff) linaro@j13-r120-t32-09:~$ [ 1512.796815] Unable to handle kernel read from unreadable memory at virtual address 01dc0040 [ 1512.805865] Mem abort info: [ 1512.808647] ESR = 0x9604 [ 1512.811702] EC = 0x25: DABT (current EL), IL = 32 bits [ 1512.817023] SET = 0, FnV = 0 [ 1512.820089] EA = 0, S1PTW = 0 [ 1512.823238] Data abort info: [ 1512.826128] ISV = 0, ISS = 0x0004 [ 1512.829972] CM = 0, WnR = 0 [ 1512.832933] user pgtable: 4k pages, 48-bit VAs, pgdp=000cd14a [ 1512.839410] [01dc0040] pgd= [ 1512.844300] Internal error: Oops: 9604 [#1] SMP [ 1512.849169] Modules linked in: target_core_pscsi target_core_file target_core_iblock iscsi_target_mod xfs xt_REDIRECT xt_comment xt_nat xt_mark xt_connmark ip6table_raw iptable_raw xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc target_core_user uio target_core_mod nf_conntrack_netlink binfmt_misc nls_iso8859_1 nfnetlink_cttimeout nfnetlink ipmi_ssif ipmi_devintf cavium_rng_vf joydev input_leds ipmi_msghandler cavium_rng thunderx_edac openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel ip_tables x_tables autofs4 crct10dif_ce
[Kernel-packages] [Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module
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 input/discussion here. Setting Bionic to Won't Fix - and from latter releases it is already fine. ** Changed in: open-iscsi (Ubuntu Bionic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module Status in linux package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Won't Fix Status in linux source package in Bionic: New Status in open-iscsi source package in Bionic: Won't Fix Bug description: Overview --- It appears the Bionic and Xenial minimal images have always shipped with a failing systemd unit: "systemd-modules-load.service" with the error "Failed to find module 'ib_iser'" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables # cloud-config.service may show up failing to setup the timezone... From the journal: Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 'ib_iser' Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Steps to reproduce --- $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img --name=bionic-minimal $ multipass exec bionic-minimal -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1069-kvm root=PARTUUID=ffb7214d-c783-45ed-b736-278d4ee0cac0 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 4.15.0-1069.70-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1069-kvm N/A linux-backports-modules-4.15.0-1069-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-1069-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
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 on recent and/or dormant bugs filter them out. And now sadly it feels "too late" to make it much better. The underlying problem in this case is that the resolution seems to make it only worse. Let me explain that... If we'd take away the new features in the package itself, then anything started with 6.0.0-0ubuntu8.5 and later would conflict with the new update. And that means we are comparing two sets of guests - those started in the first 11 months vs those started (or restarted) in the last 14 months. Even purely on numbers that quite likely means the latter group would win. Furthermore - unless I'm mistaken - all future versions Groovy, Hirsute, Impish, Jammy, ... match upstream which has the features added on those types. Due to that reverting this we'd also make Focals types incompatible with future releases and inhibit migration and similar to those. In the meantime (between now and the introduction of this change to the type) there were also two qemu security updates [1][2] which usually imply to restart or migrate the guests. So quite likely the majority of those left started before 03/2021 have been re-cycled since then. I do not think that versioned types would help here (but haven't spent days to experiment with it), at least not for those guests already running from the past - and those are the only ones left affected. So what else than shrugging and feeling bad could we do ...? I think we could as lessons learned harden the regression tests a bit better. We could: 1. ensure that no cpu-model is lost only new, but no lost entries in $ virsh cpu-models $(uname -m) 2. ensure that we only got adds, but no removals in /usr/share/libvirt/cpu_map/ Those will be helpful, but were not the problem here (we only got Rome added, no change to EPYC named types), the problem is that there are now "known features" which before was just noise in the cpuid data. Now that it is detected properly 3. (Src) check if tests/cputestdata or tests/domaincapsdata got extended for existing types. Each of those will be another candidate for a regression of this type and at least should be detected and decided consciously (if we want/need it) or if we reject the request that caused it. I've added that to the list of known "should be tested better on regression checks" so that it can be implemented to catch those cases earlier next time. [1]: https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu6.17 [2]: https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu6.21 Ref: SD-670 -- 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/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will
[Kernel-packages] [Bug 1968013] Re: Boot and package install/update stalled due to linux-cloud-tools-common (hv-kvp-daemon.service)
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) of this start-try in the journal will look like: Apr 06 09:17:01 ip-172-31-16-15 sudo[2290]: ubuntu : TTY=pts/1 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/systemctl start hv-kvp-daemon.service Apr 06 09:17:01 ip-172-31-16-15 sudo[2290]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) Apr 06 09:17:01 ip-172-31-16-15 CRON[2294]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Apr 06 09:17:01 ip-172-31-16-15 CRON[2295]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 06 09:17:01 ip-172-31-16-15 CRON[2294]: pam_unix(cron:session): session closed for user root Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 09:18:31 ip-172-31-16-15 sudo[2290]: pam_unix(sudo:session): session closed for user root Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. -- 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/1968013 Title: Boot and package install/update stalled due to linux-cloud-tools- common (hv-kvp-daemon.service) Status in linux package in Ubuntu: Confirmed Bug description: I see a boot stall on a normal qemu/libvirt based KVM guest using an almost fresh cloud image a stall on boot: While live on the console I see: [ OK ] Reached target System Time Set. [ OK ] Finished Load AppArmor pro…s managed internally by snapd. [* ] A start job is running for /sys/dev…misc/vmbus!hv_kvp (41s / 1min 30s) Afterwards in the console I see: [ TIME ] Timed out waiting for device es/virtual/misc/vmbus!hv_kvp. [DEPEND] Dependency failed for Hyper-V KVP Protocol Daemon. Note: Found after wondering why my system isn't available for ssh after start In the journal this bonus minute can be seen for example here: Apr 06 05:48:42 login-jammy systemd[1]: systemd-fsckd.service: Deactivated successfully. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 05:49:41 login-jammy systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 05:49:41 login-jammy systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 05:49:41 login-jammy systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. Apr 06 05:49:41 login-jammy systemd[1]: Starting Initial cloud-init job (pre-networking)... This behavior is from: /usr/lib/systemd/system/hv-kvp-daemon.service $ dpkg -S hv-kvp-daemon.service linux-cloud-tools-common: /lib/systemd/system/hv-kvp-daemon.service It has the expected "should not matter elsewhere": ConditionVirtualization=microsoft ConditionKernelCommandLine=!snapd_recovery_mode But it also has: BindsTo=sys-devices-virtual-misc-vmbus\x21hv_kvp.device Right now it seems the latter overrules the former (in an obvious non microsoft environment it does run and wait) and thereby makes it stall boot until it gives up on it. This is on my system since I wanted to do performance checks for something completely else and is part of linux-cloud-tools-common which I had installed for perf. Repro: 1. get jammy system 2. install linux-cloud-tools-common 3. reboot and see the delay I'd expect this stalls boot everywhere except when on azure, but I still need to try that to confirm it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-cloud-tools-common 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 6 05:48 seq crw-rw 1 root audio 116, 33 Apr 6 05:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion:
[Kernel-packages] [Bug 1968013] Re: Boot stall on non-azure systems due to linux-cloud-tools-common
On a fresh AWS instance I already see it stalling on package install, I do not even need to reboot :-/ ubuntu@ip-172-31-16-15:~$ sudo apt install linux-cloud-tools-common Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-cloud-tools-common 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 72.4 kB of archives. After this operation, 342 kB of additional disk space will be used. Get:1 http://eu-south-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 linux-cloud-tools-common all 5.15.0-25.25 [72.4 kB] Fetched 72.4 kB in 0s (632 kB/s) Selecting previously unselected package linux-cloud-tools-common. (Reading database ... 63666 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_5.15.0-25.25_all.deb ... Unpacking linux-cloud-tools-common (5.15.0-25.25) ... Setting up linux-cloud-tools-common (5.15.0-25.25) ... Created symlink /etc/systemd/system/multi-user.target.wants/hv-fcopy-daemon.service → /lib/systemd/system/hv-fcopy-daemon.service. Created symlink /etc/systemd/system/multi-user.target.wants/hv-kvp-daemon.service → /lib/systemd/system/hv-kvp-daemon.service. Created symlink /etc/systemd/system/multi-user.target.wants/hv-vss-daemon.service → /lib/systemd/system/hv-vss-daemon.service. Progress: [ 60%] [###..] < here it is hanging ~1 minute > Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. Processing triggers for man-db (2.10.2-1) ... Scanning processes... Scanning linux images... It is interesting that it even hits: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. That is the try to start it from: /var/lib/dpkg/info/linux-cloud-tools-common.postinst :63 Which has: deb-systemd-invoke $_dh_action 'hv-fcopy-daemon.service' 'hv-kvp-daemon.service' 'hv-vss-daemon.service' >/dev/null || true In Journal we can see the exact same time-out Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. ** Summary changed: - Boot stall on non-azure systems due to linux-cloud-tools-common + Boot and package install/update stalled due to linux-cloud-tools-common (hv-kvp-daemon.service) -- 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/1968013 Title: Boot and package install/update stalled due to linux-cloud-tools- common (hv-kvp-daemon.service) Status in linux package in Ubuntu: Confirmed Bug description: I see a boot stall on a normal qemu/libvirt based KVM guest using an almost fresh cloud image a stall on boot: While live on the console I see: [ OK ] Reached target System Time Set. [ OK ] Finished Load AppArmor pro…s managed internally by snapd. [* ] A start job is running for /sys/dev…misc/vmbus!hv_kvp (41s / 1min 30s) Afterwards in the console I see: [ TIME ] Timed out waiting for device es/virtual/misc/vmbus!hv_kvp. [DEPEND] Dependency failed for Hyper-V KVP Protocol Daemon. Note: Found after wondering why my system isn't available for ssh after start In the journal this bonus minute can be seen for example here: Apr 06 05:48:42 login-jammy systemd[1]: systemd-fsckd.service: Deactivated successfully. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 05:49:41 login-jammy systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 05:49:41 login-jammy systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 05:49:41 login-jammy systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. Apr 06
[Kernel-packages] [Bug 1968013] [NEW] Boot stall on non-azure systems due to linux-cloud-tools-common
Public bug reported: I see a boot stall on a normal qemu/libvirt based KVM guest using an almost fresh cloud image a stall on boot: While live on the console I see: [ OK ] Reached target System Time Set. [ OK ] Finished Load AppArmor pro…s managed internally by snapd. [* ] A start job is running for /sys/dev…misc/vmbus!hv_kvp (41s / 1min 30s) Afterwards in the console I see: [ TIME ] Timed out waiting for device es/virtual/misc/vmbus!hv_kvp. [DEPEND] Dependency failed for Hyper-V KVP Protocol Daemon. Note: Found after wondering why my system isn't available for ssh after start In the journal this bonus minute can be seen for example here: Apr 06 05:48:42 login-jammy systemd[1]: systemd-fsckd.service: Deactivated successfully. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 05:49:41 login-jammy systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 05:49:41 login-jammy systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 05:49:41 login-jammy systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. Apr 06 05:49:41 login-jammy systemd[1]: Starting Initial cloud-init job (pre-networking)... This behavior is from: /usr/lib/systemd/system/hv-kvp-daemon.service $ dpkg -S hv-kvp-daemon.service linux-cloud-tools-common: /lib/systemd/system/hv-kvp-daemon.service It has the expected "should not matter elsewhere": ConditionVirtualization=microsoft ConditionKernelCommandLine=!snapd_recovery_mode But it also has: BindsTo=sys-devices-virtual-misc-vmbus\x21hv_kvp.device Right now it seems the latter overrules the former (in an obvious non microsoft environment it does run and wait) and thereby makes it stall boot until it gives up on it. This is on my system since I wanted to do performance checks for something completely else and is part of linux-cloud-tools-common which I had installed for perf. Repro: 1. get jammy system 2. install linux-cloud-tools-common 3. reboot and see the delay I'd expect this stalls boot everywhere except when on azure, but I still need to try that to confirm it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-cloud-tools-common 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 6 05:48 seq crw-rw 1 root audio 116, 33 Apr 6 05:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Apr 6 09:04:02 2022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) PackageArchitecture: all PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=16484d8a-587c-4c41-9201-e6079b9c6938 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.14.0-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-impish dmi.modalias: dmi:bvnSeaBIOS:bvr1.14.0-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-impish:cvnQEMU:ct1:cvrpc-q35-impish:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-impish dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy uec-images ** 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/1968013 Title: Boot stall on non-azure systems due to linux-cloud-tools-common Status in linux package in Ubuntu: Confirmed Bug description: I see a boot stall on a normal qemu/libvirt based
[Kernel-packages] [Bug 1967894] Re: KVM IPI Virtualization support for SPR
** Package changed: kvm (Ubuntu) => linux (Ubuntu) -- 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/1967894 Title: KVM IPI Virtualization support for SPR Status in linux package in Ubuntu: New Bug description: IPI virtualization targets to make the processor emulate the write to APIC registers that would send IPIs in virtualized system. VMX provide new VM-execution control and VMCS field to support IPI virtualization which can eliminate APIC-Write VM-exit. The processor sets the bit corresponding to the vector in target vCPU's PIR and may send a notification (IPI) specified by NDST and NV fields in target vCPU's PID. It is similar to what IOMMU engine does when dealing with posted interrupt from devices. IPI Virtualization is approved in SPR/EGS CCB and it is supposed to be enabled in C-step or later (perhaps D-step). Subject: Re: [PATCH v7 8/8] KVM: VMX: enable IPI virtualization https://lore.kernel.org/kvm/54df6da8-ad68-cc75-48db-d18fc8743...@intel.com/ Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966870] Re: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs
This is actually fixed already in 5.13.0.39.44 as shown above, but the root cause that I'm facing is that edge-Kernel is behind non -egde: $ rmadison -a amd64 -u ubuntu linux-image-generic-hwe-20.04-edge | grep focal linux-image-generic-hwe-20.04-edge | 5.13.0.27.29~20.04.13 | focal-security | amd64 linux-image-generic-hwe-20.04-edge | 5.13.0.27.29~20.04.13 | focal-updates | amd64 linux-image-generic-hwe-20.04-edge | 5.15.0.23.23~20.04.5 | focal-proposed | amd64 $ rmadison -a amd64 -u ubuntu linux-image-generic-hwe-20.04 | grep focal linux-image-generic-hwe-20.04 | 5.4.0.26.32 | focal | amd64 linux-image-generic-hwe-20.04 | 5.13.0.39.44~20.04.24 | focal-security | amd64 linux-image-generic-hwe-20.04 | 5.13.0.39.44~20.04.24 | focal-updates | amd64 And I see that this is not updated https://launchpad.net/ubuntu/+source/linux-meta-hwe-5.13 While this is stuck in proposed https://launchpad.net/ubuntu/+source/linux-meta-hwe-5.15 And never anyone levft proposed https://launchpad.net/ubuntu/+source/linux-meta-hwe-5.15/+publishinghistory Stuck in proposed, but as long as 5.15 is stuck 5.13 should continue. I do not have a perfect solution, but somehow edge should not fall behind non-edge. -- 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/1966870 Title: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs Status in linux package in Ubuntu: Confirmed Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O)
[Kernel-packages] [Bug 1966870] Re: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs
FYI for a different test I upgraded the system to Impish and on the 5.13.0-39-generic there neither of the two kernel bugs happens. -- 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/1966870 Title: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs Status in linux package in Ubuntu: Confirmed Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs
[Kernel-packages] [Bug 1966870] Re: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs
I tried things once more, this time OVS wasn't active at all (in the former try it was active after boot and then disabled) - still failing. Next I tried to use a different kernel(5.4.0-105-generic) I don't know when in >5.4 this started to fail, it surely worked a few months ago already using the an HWE kernel back then and running the same tests that now stumbled over this. I usually run with: linux-image-generic-hwe-20.04-edge 5.13.0.27.29~20.04.13 => the one that initially failed And now I cross tested: linux-generic 5.4.0.105.109 => working fine Would it be helpful to you to also get (it is somewhat suspicious that egde is behind non-edge): linux-image-generic-hwe-20.04 5.13.0.39.44~20.04.24 Would there be any other build that I should try helping you to pinpoint 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/1966870 Title: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs Status in linux package in Ubuntu: Confirmed Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4
[Kernel-packages] [Bug 1966870] Re: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs
As the last stage in the crash is in ? blk_mq_exit_hctx+0x160/0x160 I was looking if there was anything else with block devices going on. I found another crash right at boot/init time (this one is also in the attached currentDmesg.txt). [ 537.566942] [ cut here ] [ 537.566946] WARNING: CPU: 7 PID: 2421 at block/blk-mq.c:3087 blk_mq_release+0x45/0xe0 [ 537.566958] Modules linked in: nbd(+) xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 rpcrdma sunrpc rdma_ucm ib_iser libiscsi scsi_transport_iscsi ib_umad rdma_cm ib_ipoib iw_cm ib_cm dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm rapl intel_cstate efi_pstore ioatdma hpilo acpi_ipmi ipmi_si acpi_tad mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr ip_tables x_tables autofs4 btrfs [ 537.567073] blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core ses enclosure mgag200 i2c_algo_bit crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyarea sysfillrect aesni_intel sysimgblt mlx5_core fb_sys_fops pci_hyperv_intf crypto_simd ixgbe cec psample cryptd xfrm_algo nvme i2c_i801 rc_core mlxfw hpsa xhci_pci dca drm lpc_ich i2c_smbus tg3 xhci_pci_renesas nvme_core tls mdio scsi_transport_sas wmi [ 537.567146] CPU: 7 PID: 2421 Comm: modprobe Tainted: P O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 537.567151] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 537.567154] RIP: 0010:blk_mq_release+0x45/0xe0 [ 537.567159] Code: 48 31 d2 eb 07 83 c2 01 39 f2 74 27 48 63 c2 48 8b 04 c7 48 85 c0 74 ed 48 8b 88 30 02 00 00 48 05 30 02 00 00 48 39 c1 75 db <0f> 0b 83 c2 01 39 f2 75 d9 49 8b 84 24 90 05 00 00 49 8d 9c 24 90 [ 537.567163] RSP: 0018:c287c17f3a58 EFLAGS: 00010246 [ 537.567167] RAX: 9f2611f50230 RBX: 9f2609bfefa0 RCX: 9f2611f50230 [ 537.567170] RDX: RSI: 0001 RDI: 9f261e60ef38 [ 537.567173] RBP: c287c17f3a70 R08: 0004 R09: 002c [ 537.567175] R10: 9f2601c07800 R11: 01b6 R12: 9f2609bfef20 [ 537.567178] R13: 9f2609bfef20 R14: 9f2609bfefa0 R15: [ 537.567181] FS: 7f1728b36680() GS:9f2d5fbc() knlGS: [ 537.567185] CS: 0010 DS: ES: CR0: 80050033 [ 537.567188] CR2: 7f814132242d CR3: 000119bf4003 CR4: 001706e0 [ 537.567191] Call Trace: [ 537.567197] blk_release_queue+0xbc/0x140 [ 537.567203] kobject_release+0x4b/0x160 [ 537.567211] kobject_put+0x49/0x60 [ 537.567215] blk_put_queue+0x12/0x20 [ 537.567224] disk_release+0x68/0x90 [ 537.567231] device_release+0x3b/0xa0 [ 537.567239] kobject_release+0x4b/0x160 [ 537.567243] kobject_put+0x49/0x60 [ 537.567247] put_device+0x13/0x20 [ 537.567252] put_disk+0x1b/0x20 [ 537.567258] nbd_dev_add+0x259/0x2b0 [nbd] [ 537.567275] nbd_init+0x11a/0x1000 [nbd] [ 537.567284] ? 0xc0ffd000 [ 537.567287] do_one_initcall+0x48/0x1d0 [ 537.567298] ? __cond_resched+0x19/0x30 [ 537.567308] ? kmem_cache_alloc_trace+0x37c/0x440 [ 537.567319] do_init_module+0x62/0x260 [ 537.567325] load_module+0x125d/0x1440 [ 537.567332] __do_sys_finit_module+0xc2/0x120 [ 537.567337] ? __do_sys_finit_module+0xc2/0x120 [ 537.567343] __x64_sys_finit_module+0x1a/0x20 [ 537.567347] do_syscall_64+0x61/0xb0 [ 537.567354] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 537.567362] ? syscall_exit_to_user_mode+0x27/0x50 [ 537.567367] ? __x64_sys_newfstat+0x16/0x20 [ 537.567373] ? do_syscall_64+0x6e/0xb0 [ 537.567379] ? asm_exc_page_fault+0x8/0x30 [ 537.567385] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 537.567390] RIP: 0033:0x7f1728c7876d [ 537.567394] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d f3 36 0d 00 f7 d8 64 89 01 48 [ 537.567398] RSP: 002b:7ffcfaa186a8 EFLAGS: 0246 ORIG_RAX: 0139 [ 537.567402] RAX: ffda RBX: 559308b38000 RCX: 7f1728c7876d [ 537.567405] RDX: RSI: 559307d34358 RDI: 0003 [ 537.567407] RBP: 0006 R08: R09: [
[Kernel-packages] [Bug 1966870] Re: Focal 20.04.4 crashing when using openvswitch and disabling CPUs
I have tried the same again, this time with openvswitch unconfigured (but still running). ubuntu@node-horsea:~$ sudo ovs-vsctl del-br ovsbr0 ubuntu@node-horsea:~$ sudo ovs-vsctl show 8dfc2067-7b9b-48d7-a50a-df17bbd3cb6c ovs_version: "2.13.5" chcpu disabling/enabling still crashes. ubuntu@node-horsea:~$ sudo chcpu -d 5-11 Killed [ +3.357665] IRQ 56: no longer affine to CPU5 [ +0.21] IRQ 72: no longer affine to CPU5 [ +0.09] IRQ 82: no longer affine to CPU5 [ +0.11] IRQ 96: no longer affine to CPU5 [ +0.19] IRQ 121: no longer affine to CPU5 [ +0.12] IRQ 136: no longer affine to CPU5 [ +0.002380] smpboot: CPU 5 is now offline [ +0.000468] BUG: kernel NULL pointer dereference, address: 0008 [ +0.031357] #PF: supervisor write access in kernel mode [ +0.023816] #PF: error_code(0x0002) - not-present page [ +0.023147] PGD 0 P4D 0 [ +0.011391] Oops: 0002 [#1] SMP PTI [ +0.015688] CPU: 11 PID: 5967 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ +0.043614] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ +0.037462] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ +0.023926] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ +0.084916] RSP: 0018:acf3ccddbbb0 EFLAGS: 00010286 [ +0.023534] RAX: ccf3bfb7a580 RBX: RCX: acf3ccddbbb0 [ +0.033000] RDX: ccf3bfb7a588 RSI: RDI: [ +0.032118] RBP: acf3ccddbbe8 R08: R09: acf3ccddbaa8 [ +0.032456] R10: 0001 R11: 0001 R12: 8da022a5 [ +0.032331] R13: ccf3bfb7a580 R14: acf3ccddbbb0 R15: 0005 [ +0.032137] FS: 7f1a4aff9580() GS:8da29fcc() knlGS: [ +0.036480] CS: 0010 DS: ES: CR0: 80050033 [ +0.025981] CR2: 0008 CR3: 0005b29d6006 CR4: 001706e0 [ +0.032158] Call Trace: [ +0.010991] ? blk_mq_exit_hctx+0x160/0x160 [ +0.018782] cpuhp_invoke_callback+0x179/0x430 [ +0.020112] cpuhp_invoke_callback_range+0x44/0x80 [ +0.021557] _cpu_down+0x109/0x310 [ +0.015284] cpu_down+0x36/0x60 [ +0.014475] cpu_device_down+0x16/0x20 [ +0.016905] cpu_subsys_offline+0xe/0x10 [ +0.017652] device_offline+0x8e/0xc0 [ +0.016520] online_store+0x4c/0x90 [ +0.015662] dev_attr_store+0x17/0x30 [ +0.016581] sysfs_kf_write+0x3e/0x50 [ +0.016546] kernfs_fop_write_iter+0x138/0x1c0 [ +0.020381] new_sync_write+0x117/0x1b0 [ +0.017389] vfs_write+0x185/0x250 [ +0.015407] ksys_write+0x67/0xe0 [ +0.014961] __x64_sys_write+0x1a/0x20 [ +0.016879] do_syscall_64+0x61/0xb0 [ +0.016095] ? syscall_exit_to_user_mode+0x27/0x50 [ +0.021544] ? __x64_sys_faccessat+0x1c/0x20 [ +0.019347] ? do_syscall_64+0x6e/0xb0 [ +0.016881] entry_SYSCALL_64_after_hwframe+0x44/0xae [ +0.022785] RIP: 0033:0x7f1a4af140a7 [ +0.016084] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ +0.086348] RSP: 002b:7ffd8b2963d8 EFLAGS: 0246 ORIG_RAX: 0001 [ +0.034055] RAX: ffda RBX: 0040 RCX: 7f1a4af140a7 [ +0.032183] RDX: 0001 RSI: 55feb3b47869 RDI: 0004 [ +0.032139] RBP: 7f1a4aff9500 R08: R09: 7ffd8b296380 [ +0.032232] R10: R11: 0246 R12: 0004 [ +0.032338] R13: 7ffd8b2963e0 R14: 55feb3b47869 R15: 0001 [ +0.032799] Modules linked in: ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel rpcrdma kvm sunrpc rdma_ucm rapl intel_cstate ib_iser libiscsi scsi_transport_iscsi efi_pstore rdma_cm ib_umad ib_ipoib iw_cm ib_cm hpilo ioatdma acpi_ipmi ipmi_si acpi_power_meter acpi_tad mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr ip_tables x_tables autofs4 btrfs [ +0.48] blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core ses enclosure mgag200
[Kernel-packages] [Bug 1966870] Re: Focal 20.04.4 crashing when using openvswitch/hugepages
Ok, I have manually retried this - we do not need the KVM guest, it is the chcpu that kills it. Simplifying description ... ** Summary changed: - Focal 20.04.4 crashing when using openvswitch/hugepages + Focal 20.04.4 crashing when using openvswitch and disabling CPUs ** Description changed: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page - [ 1444.478052] PGD 0 P4D 0 + [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core ses enclosure mgag200 i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul
[Kernel-packages] [Bug 1966870] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574134/+files/Lspci-vt.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs
[Kernel-packages] [Bug 1966870] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574141/+files/ProcInterrupts.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear
[Kernel-packages] [Bug 1966870] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574136/+files/Lsusb-t.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs
[Kernel-packages] [Bug 1966870] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574145/+files/acpidump.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs
[Kernel-packages] [Bug 1966870] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574138/+files/ProcCpuinfo.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib
[Kernel-packages] [Bug 1966870] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574143/+files/UdevDb.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs
[Kernel-packages] [Bug 1966870] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574144/+files/WifiSyslog.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib
[Kernel-packages] [Bug 1966870] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574137/+files/Lsusb-v.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs
[Kernel-packages] [Bug 1966870] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574142/+files/ProcModules.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib
[Kernel-packages] [Bug 1966870] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574139/+files/ProcCpuinfoMinimal.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath
[Kernel-packages] [Bug 1966870] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574140/+files/ProcEnviron.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib
[Kernel-packages] [Bug 1966870] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574133/+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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs
[Kernel-packages] [Bug 1966870] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574135/+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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs
[Kernel-packages] [Bug 1966870] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574132/+files/CurrentDmesg.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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib
[Kernel-packages] [Bug 1966870] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1966870/+attachment/5574131/+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/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages Status in linux package in Ubuntu: New Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core
[Kernel-packages] [Bug 1966870] [NEW] Focal 20.04.4 crashing when using openvswitch/hugepages
Public bug reported: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core ses enclosure mgag200 i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel sysimgblt fb_sys_fops aesni_intel mlx5_core cec ixgbe pci_hyperv_intf crypto_simd xfrm_algo psample nvme cryptd rc_core hpsa mlxfw i2c_i801 dca xhci_pci drm i2c_smbus lpc_ich tg3 tls xhci_pci_renesas nvme_core mdio scsi_transport_sas wmi [ 1446.267521] CR2: 0008 [ 1446.282506] ---[ end trace 99f81ab62ed1f929 ]--- [ 1446.308857] RIP:
[Kernel-packages] [Bug 1964093] Re: nfsver=3, udp not working anymore
** Tags removed: server-todo -- 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/1964093 Title: nfsver=3,udp not working anymore Status in linux package in Ubuntu: Confirmed Bug description: Package: nfs-kernel-server Architecture: amd64 Version: 1:2.6.1-1~exp1ubuntu1 nfsversion 3 with proto udp seems not to be supported by the nfs- kernel-server anymore. In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still possible. I could mount with either tcp or udp: 1. tcp mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt mount|grep mnt: 192.168.0.1:/srv/nfs/testshare on /mnt type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1) 2. udp mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt mount|grep mnt: 192.168.0.1:/srv/nfs/testshare on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1) Now in Ubuntu 22.04 I get the message: mount.nfs: an incorrect mount option was specified I tried to enable upd in /etc/nfs.conf in section [nfsd]: [nfsd] # debug=0 # threads=8 # host= # port=0 # grace-time=90 # lease-time=90 # udp=n udp=y # tcp=y # vers2=n # vers3=y But there was no effect. nfs3 with udp is needed by several busybox mount binaries in initrds of Knoppix and other live distributions used via PXE boot. Best regards Jörg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930921] Re: Apache 2.4.41 corrupts files from samba share
** Bug watch added: Debian Bug tracker #900821 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 ** Also affects: debian via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 Importance: Unknown Status: Unknown -- 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/1930921 Title: Apache 2.4.41 corrupts files from samba share Status in apache2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in Debian: Unknown Bug description: Wenn I serve a samba share with apache 2.4.41 on Ubuntu 20.04 then some files have a corrupt header during transmission. It seems that the first few bytes of the headers are truncated and sometimes other bytes of the download are not belonging to the file. A workaround I found that works is to set "EnableMMAP Off" in the apache config. See other bug reports like this: https://serverfault.com/questions/1044724/apache2-sends-corrupt-responses-when-using-a-cifs-share https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 This is most probably not a bug in Ubuntu itself but I am reporting it here since I assume that a data corruption bug is seen as critical. I am also marking it as a security vulnerability since it seems that wrong parts of memory get exposed during file download. I don't know how random the exposed memory is and if it potentially could expose e.g. secrets. Please feel free to remove the security vulnerability flag if your assessment leads to a different conclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1930921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959984] Re: [22.04 FEAT] KVM: Allow long kernel command lines for QEMU
FYI: If you want/need a test - builds of the qemu that have that are in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4753 -- 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/1959984 Title: [22.04 FEAT] KVM: Allow long kernel command lines for QEMU Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Fix Committed Bug description: KVM: Allow long kernel command lines for QEMU Description: Originally, the kernel command line length was limited to 896 bytes, due to its fixed size in the kernel image. Recent kernels can support larger command lines by checking out the position and length using new fields in the kernel image. This feature allows QEMU direct kernel boot to use larger command lines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954473] Re: KVM Shared Virtual Memory (SVM)
** Tags added: intel-bug-december-2021 -- 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/1954473 Title: KVM Shared Virtual Memory (SVM) Status in linux package in Ubuntu: Incomplete Bug description: SVM is short for shared virtual memory. This task is aiming at enabling SVM support for assigned devices on KVM. Example: assign a GPU from host to guest, the application program running in guest could share its virtual memory address to the assigned device. Latest update: extend the vIOMMU in QEMU to support SVM feature. 1. Description of the Technology. SVM is shorted for Shared Virtual Memory, it is a VT-d feature that allows sharing application virtual address space with the I/O device. The feature works with the PCI sig Process Address Space ID (PASID). SVM has the following benefits: • Programmer gets a consistent view of memory across host application and device • Efficient access to data, avoiding pining or copying overheads 2. Use cases that is important for this technology (aka, why is this technology needed). Intel has multiple IPs that would support SVM, and the usage in guest is also a demand. e.g. QAT, it is usual to assign a QAT to guest and requires SVM to benefit from its advantages. 3. General design description (components modified: kvm, qemu-kvm, driver, libvirt (and other userland libraries)) Modified components would include: qemu-kvm, vfio driver, iommu driver Target Linux 5.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954469] Re: KVM Bus Lock Debug Exception
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. You opened a range of bugs in the same pass, other than most others - this one seems to refer to older qemu/kernel versions. Here you really need to specify what you'd need where - otherwise all we can do is consider that already fixed. TL;DR: linux 5.13 is in Ubuntu 21.10 [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Tags added: intel-bug-december-2021 -- 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/1954469 Title: KVM Bus Lock Debug Exception Status in linux package in Ubuntu: Fix Released Bug description: A bus lock is acquired either through split locked access to writeback (WB) memory or by using locks to uncacheable (UC) memory. This is typically > 1000 cycles slower than atomic operation within a cache line. It also disrupts performance on other cores (which must wait for the bus lock to be released before their memory operations). Bus lock debug exception is a sub-feature of bus lock detection. It is an ability to notify the kernel by an #DB trap after the instruction acquires a bus lock when CPL>0. This allows the kernel to enforce user application throttling or mitigations. A logical processor can be configured to generate a debug exception (#DB) following acquisition of a bus lock. Software enables those debug exceptions by setting bit 2 of the IA32_DEBUGCTL MSR. The CPU enumerates this feature using CPUID.(EAX=7, ECX=0).ECX[24]. A debug exception due to acquistion of a bus lock is reported as a trap following execution of the instruction acquiring the bus lock. The processor identifies such debug exceptions using bit 11 of DR6: delivery of a bus-lock #DB clears DR6[11]. Linux 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954465] Re: KVM AIA User IPI
** Tags added: intel-bug-december-2021 -- 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/1954465 Title: KVM AIA User IPI Status in linux package in Ubuntu: Incomplete Bug description: SENDUIPI is a new ring-3 instruction that sending IPI notification between ring 3 software. It uses a data structure (table) owned and managed by ring 0 OS. Ring 3 software can choose which table entry to invoke. Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954468] Re: KVM Architectural LBRs
** Tags added: intel-bug-december-2021 -- 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/1954468 Title: KVM Architectural LBRs Status in linux package in Ubuntu: Incomplete Bug description: Architectural LBRs (Last Branch Records) Architectural LBRs (Last Branch Records) enable recording of software path history by logging taken branches and other control flow transfers within model-specific registers, and is inherited from legacy LBR. If CPUID.(EAX=07H, ECX=0):EDX[19] is set to 1, the processor supports Architectural LBRs. With VMCS support and XSAVE support, the KVM guests could also use ARCH LBR as well. Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954463] Re: KVM ROP Control-Flow Enforcement Tech (CET)
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. You opened a range of bugs in the same pass, other than most others - this one also contains a reference to qemu changes. Therefore I'll add a src:qemu bug task. I have not found an upstream commit for "expose CET related CPUID and xsaves/xrstors support to guest" - the same as with the kernel changes, please refer to an upstream commit including the hash. There are a few xsaves changes in qemu 6.1 but none with your title, did you mean those? [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Incomplete ** Tags added: intel-bug-december-2021 -- 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/1954463 Title: KVM ROP Control-Flow Enforcement Tech (CET) Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: Control-Flow Enforcement Tech (CET) What is Intel CET: Control-flow Enforcement Technology (CET) provides protection against return/jump-oriented programming (ROP) attacks. It can be implemented to protect both the kernel and applications. In the first phase, only the user-mode protection is implemented on the 64-bit kernel. However, 32-bit applications are supported under the compatibility mode. CET includes shadow stack (SHSTK) and indirect branch tracking (IBT). The SHSTK is a secondary stack allocated from memory. The processor automatically pushes/pops a secure copy to the SHSTK every return address and, by comparing the secure copy to the program stack copy, verifies function returns are as intended. The IBT verifies all indirect CALL/JMP targets are intended and marked by the compiler with 'ENDBR' op codes. Why need this technology(CET VMX): CET also can provide ROP attack in guest OS with VMX HW support. This will enhance platform security in Cloud computing, it's meaningful for Cloud service providers. Key change in kvm: To enable KVM based CET feature for guest OS, we need to : 1) Expose the features(CET SHSTK/IBT) to guest OS via CPUID report. 2) Enable xsaves/xrstors support for guest OS. 3) Fix xsaves/xrstors issue in existing KVM code. 4) Enabled CET states loading in guest entry/exit. 5) Add CET VMX related definitions. Key change in Qemu-kvm: expose CET related CPUID and xsaves/xrstors support to guest. Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954464] Re: kvm SPR support for AMX
** Tags added: intel-bug-december-2021 -- 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/1954464 Title: kvm SPR support for AMX Status in linux package in Ubuntu: Incomplete Bug description: AMX (including XFD): AMX (Advance Matrix eXtensions) is a new programming paradigm for direct matrix operations. TMUL (TILE Matrix mULtiply unit) is the multiply accelerator. XFD (Extended Feature Disable) is an XSAVE extension mechanism for those features with large XSAVE storage context, that enables the OS not pre-allocate the space initially. AMX is the first one using XFD feature. Use cases: Deep learning inference and training (CNN, DNN), other data analytics and machine learning apps, HPC SGEMM Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954471] Re: KVM AIA Work Dispatch Instructions
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. You opened a range of bugs in the same pass, other than most others - this one seems to refer to older qemu/kernel versions. Here you really need to specify what you'd need where - otherwise all we can do is consider that already fixed. TL;DR: qemu 4.2 is in Ubuntu 20.04 linux 5.4 is in Ubuntu 20.04 [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Fix Released ** Tags added: intel-bug-december-2021 -- 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/1954471 Title: KVM AIA Work Dispatch Instructions Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Bug description: AIA has 3 sub features: AIA User Interrupts AIA User Wait Instructions AIA Work Dispatch Instructions AIA User Wait Instructions was merged for SNR in Kernel 5.4/Qemu4.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954472] Re: KVM Scalable I/O Virtualization
** Tags added: intel-bug-december-2021 -- 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/1954472 Title: KVM Scalable I/O Virtualization Status in linux package in Ubuntu: Incomplete Bug description: Core OS/ VMM device virtualization framework extended to support Scalable IOV; OS/ VMM support for Scalable IOV IOMMU extensions; PASID translation support; existing device frameworks extended to support Scalable IOV; converged SW arch as prescribed by spec Improved performance and lower complexity for software utilizing PCIe devices in virtualized environments Software Benefits: Broad range of usages, e.g. security, comms, server graphics Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954466] Re: KVM Protection Keys for Supervisor Pages (PKS)
** Tags added: intel-bug-december-2021 -- 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/1954466 Title: KVM Protection Keys for Supervisor Pages (PKS) Status in linux package in Ubuntu: Incomplete Bug description: SKX introduced the Protection Key for User Pages (PKU) feature enabling fast, thread-specific manipulation of permission restrictions on user pages. SPR introduced Protection Key for Supervisor Pages(PKS), a new feature that extends the Protection Key architecture to support thread-specific permission restrictions on supervisor pages. This important feature enables enhanced access control on memory, and brings more valid usage model. Generally PKS enables protections on 'domains' of supervisor pages to limit supervisor mode access to pages beyond the normal paging protections(U/S, R/W, P). PKS works in a similar fashion to user space pkeys, PKU. As with PKU, supervisor pkeys are checked in addition to normal paging protections and Access or Writes can be disabled via a MSR update without TLB flushes when permissions change. PKS virtualization enabling should base on existing PKU code. Major works: CPUID exposure New CR4 bit exposure New VMCS fields enabling IA32_PKRS saving/restoring #GP handling Target Linux 5.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954474] Re: KVM notify VM Exit
** Tags added: intel-bug-december-2021 -- 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/1954474 Title: KVM notify VM Exit Status in linux package in Ubuntu: Incomplete Bug description: A VMM can enable notification VM exits to occur if no interrupt windows occur in VMX non-root operation for a specified amount of time (notify window). KVM Enabling: enable bit 31 of secondary processor-based excution control. enable notification VM exit (exit reason 75) handler. expose a module param to configure notify window and disable/enable VM notify. Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954468] Re: KVM Architectural LBRs
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) -- 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/1954468 Title: KVM Architectural LBRs Status in linux package in Ubuntu: Incomplete Bug description: Architectural LBRs (Last Branch Records) Architectural LBRs (Last Branch Records) enable recording of software path history by logging taken branches and other control flow transfers within model-specific registers, and is inherited from legacy LBR. If CPUID.(EAX=07H, ECX=0):EDX[19] is set to 1, the processor supports Architectural LBRs. With VMCS support and XSAVE support, the KVM guests could also use ARCH LBR as well. Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954472] Re: KVM Scalable I/O Virtualization
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) -- 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/1954472 Title: KVM Scalable I/O Virtualization Status in linux package in Ubuntu: Incomplete Bug description: Core OS/ VMM device virtualization framework extended to support Scalable IOV; OS/ VMM support for Scalable IOV IOMMU extensions; PASID translation support; existing device frameworks extended to support Scalable IOV; converged SW arch as prescribed by spec Improved performance and lower complexity for software utilizing PCIe devices in virtualized environments Software Benefits: Broad range of usages, e.g. security, comms, server graphics Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954464] Re: kvm SPR support for AMX
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) -- 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/1954464 Title: kvm SPR support for AMX Status in linux package in Ubuntu: Incomplete Bug description: AMX (including XFD): AMX (Advance Matrix eXtensions) is a new programming paradigm for direct matrix operations. TMUL (TILE Matrix mULtiply unit) is the multiply accelerator. XFD (Extended Feature Disable) is an XSAVE extension mechanism for those features with large XSAVE storage context, that enables the OS not pre-allocate the space initially. AMX is the first one using XFD feature. Use cases: Deep learning inference and training (CNN, DNN), other data analytics and machine learning apps, HPC SGEMM Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954474] Re: KVM notify VM Exit
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) -- 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/1954474 Title: KVM notify VM Exit Status in linux package in Ubuntu: New Bug description: A VMM can enable notification VM exits to occur if no interrupt windows occur in VMX non-root operation for a specified amount of time (notify window). KVM Enabling: enable bit 31 of secondary processor-based excution control. enable notification VM exit (exit reason 75) handler. expose a module param to configure notify window and disable/enable VM notify. Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954466] Re: KVM Protection Keys for Supervisor Pages (PKS)
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) -- 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/1954466 Title: KVM Protection Keys for Supervisor Pages (PKS) Status in linux package in Ubuntu: Incomplete Bug description: SKX introduced the Protection Key for User Pages (PKU) feature enabling fast, thread-specific manipulation of permission restrictions on user pages. SPR introduced Protection Key for Supervisor Pages(PKS), a new feature that extends the Protection Key architecture to support thread-specific permission restrictions on supervisor pages. This important feature enables enhanced access control on memory, and brings more valid usage model. Generally PKS enables protections on 'domains' of supervisor pages to limit supervisor mode access to pages beyond the normal paging protections(U/S, R/W, P). PKS works in a similar fashion to user space pkeys, PKU. As with PKU, supervisor pkeys are checked in addition to normal paging protections and Access or Writes can be disabled via a MSR update without TLB flushes when permissions change. PKS virtualization enabling should base on existing PKU code. Major works: CPUID exposure New CR4 bit exposure New VMCS fields enabling IA32_PKRS saving/restoring #GP handling Target Linux 5.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954465] Re: KVM AIA User IPI
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) -- 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/1954465 Title: KVM AIA User IPI Status in linux package in Ubuntu: Incomplete Bug description: SENDUIPI is a new ring-3 instruction that sending IPI notification between ring 3 software. It uses a data structure (table) owned and managed by ring 0 OS. Ring 3 software can choose which table entry to invoke. Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954473] Re: KVM Shared Virtual Memory (SVM)
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) -- 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/1954473 Title: KVM Shared Virtual Memory (SVM) Status in linux package in Ubuntu: Incomplete Bug description: SVM is short for shared virtual memory. This task is aiming at enabling SVM support for assigned devices on KVM. Example: assign a GPU from host to guest, the application program running in guest could share its virtual memory address to the assigned device. Latest update: extend the vIOMMU in QEMU to support SVM feature. 1. Description of the Technology. SVM is shorted for Shared Virtual Memory, it is a VT-d feature that allows sharing application virtual address space with the I/O device. The feature works with the PCI sig Process Address Space ID (PASID). SVM has the following benefits: • Programmer gets a consistent view of memory across host application and device • Efficient access to data, avoiding pining or copying overheads 2. Use cases that is important for this technology (aka, why is this technology needed). Intel has multiple IPs that would support SVM, and the usage in guest is also a demand. e.g. QAT, it is usual to assign a QAT to guest and requires SVM to benefit from its advantages. 3. General design description (components modified: kvm, qemu-kvm, driver, libvirt (and other userland libraries)) Modified components would include: qemu-kvm, vfio driver, iommu driver Target Linux 5.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944104] Re: nested vm on vm not running
*** This bug is a duplicate of bug 1952246 *** https://bugs.launchpad.net/bugs/1952246 Hi Masato, I think I have re-discovered that with more detail in bug 1952246 Still waiting for the kernel team to look at. ** This bug has been marked a duplicate of bug 1952246 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1944104 Title: nested vm on vm not running Status in linux-oem-5.13 package in Ubuntu: Invalid Status in qemu package in Ubuntu: Incomplete Status in linux-oem-5.13 source package in Focal: New Status in qemu source package in Focal: Incomplete Bug description: The host machine ubuntu 20.04 kernel is 5.13.0-1012-oem, When the kernel of the guest machine is ubuntu 20.04 kernel 5.4.0-84-generic, vm cannot be started on the guest machine. - KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=000a0671 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=90 90 90 90 eb c3 90 90 90 90 90 90 00 00 00 00 56 54 46 00 <90> 90 eb ac 90 90 90 90 90 90 90 90 90 90 90 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - host kernel 5.4.0-84-generic gust kernel 5.4.0-84-generic: OK gust kernel 5.13.0-1012-oem : OK host kernel 5.13.0-1012-oem gust kernel 5.4.0-84-generic: NG gust kernel 5.13.0-1012-oem : OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu-system-x86 1:4.2-3ubuntu6.17 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 20 14:05:09 2021 ExecutablePath: /usr/bin/qemu-system-x86_64 InstallationDate: Installed on 2021-09-20 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-84-generic root=/dev/mapper/vg-lv_root ro intel_iommu=on amd_iommu=on SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1944104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
