[Kernel-packages] [Bug 2049352] Re: Package BlueZ 5.72 for Noble
and it migrated! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: Triaged Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2049352] Re: Package BlueZ 5.72 for Noble
Bluez should migrate next run, and then you can do the update if you want, is it ok for you? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: Triaged Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2047780] Re: BlueZ release 5.71
next time we should make sure the changelog lists all the delta from Debian :) But with the same tarball it will be easier to find it out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
two patches are now with Debian bugs Opened #1060393 in bluez 5.67-1 by Gianfranco Costamagna (locutusofborg) «please update patch work-around-Logitech-diNovo-Edge-keyboard-firmware-i.patch». https://bugs.debian.org/1060393 Opened #1060395 in bluez by Gianfranco Costamagna (locutusofborg) «please add simple testsuite from Ubuntu». https://bugs.debian.org/1060395 ** Bug watch added: Debian Bug tracker #1060393 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060393 ** Bug watch added: Debian Bug tracker #1060395 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060395 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
and ell-dev needs a i386 whitelist, not sure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
Hello, I did the merge from Debian, now the packaging is really simpler, please have a look and upload if possible. ** Attachment added: "bluez_5.71-1ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5738106/+files/bluez_5.71-1ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
Hello Daniel! >Thank you for working over the weekend on this. I would have resolved it myself on the Monday if someone >answered the question in comment #11. This is what a team does, help other people. In this case I started answering to comment #11, I did fix->fix->fix DH_VERBOSE, fix something more, read manpage to check if compat level was the culprit, and found nothing on manual... So I just started looking at incorporating some dh fixes from debian packaging, and after 6 uploads on my ppa, the variables started being correctly parsed. I still don't have an answer for that question, this is why I came up with a frustrated answer :) Thanks for your work, and I hope with our suggestions in the future the maintenance of the package will become easier, with help of MoM. For example your Debian bug #1060242 is already acked and confirmed, so I would say there is an extremely good cooperation with Debian, and I'm pretty sure with some Debian bugs, the maintenance for Ubuntu will become less and less painful. For example all this kind of issues would have been not a problem if the package would have been merged from Debian years ago. This is why the best way to move forward is to me to just do a merge, and then use MoM in the future to grab new fixes and new releases. If we need a new upstream version, we can still help Debian package it, and then merge. This will make the current packaging a lot easier for the benefit of the community and sponsors (including fixing some bugs in Debian too) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
I don't understand why bluez packaging can't be merged with the debian fixes and continues to follow some logic of "never update to newer dh or compat". Also patches from Debian are never received, as well as new binaries not installed. I did some really little cleanup and the package now builds sanely, the variables are used and looks "better". But as sponsor I would refuse to continue to upload this useless and old packaging, and force somebody to really cleanup this maintenance burden that increased over time. Also, why is the tarball different from the Debian one? I'm attaching a debian directory that builds fine, not tested at all. ** Attachment added: "bluez_5.71-0ubuntu6.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5736981/+files/bluez_5.71-0ubuntu6.debian.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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
sponsored again. ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Lunar) Status: Incomplete => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Mantic) Status: Incomplete => In Progress -- 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 Released Status in alsa-ucm-conf source package in Jammy: In Progress Status in alsa-ucm-conf source package in Lunar: In Progress Status in alsa-ucm-conf source package in Mantic: In Progress Status in alsa-ucm-conf source package in Noble: Fix Released 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
sponsored after removing one newline in jammy debdiff. There was an
extra space in the patch, causing a different md5sum, and I prefer them
to be bit bit identical across releases when possible.
find . -name 0001-ucm2-soundwire-add-rt713-SDCA-device.patch -exec md5sum {} \;
af9963b8a1d20d1b6c57ffdb690aefc0
./jammy/debian/patches/0001-ucm2-soundwire-add-rt713-SDCA-device.patch
af9963b8a1d20d1b6c57ffdb690aefc0
./lunar/debian/patches/0001-ucm2-soundwire-add-rt713-SDCA-device.patch
af9963b8a1d20d1b6c57ffdb690aefc0
./mantic/debian/patches/0001-ucm2-soundwire-add-rt713-SDCA-device.patch
** Changed in: alsa-ucm-conf (Ubuntu Jammy)
Status: New => In Progress
** Changed in: alsa-ucm-conf (Ubuntu Lunar)
Status: New => In Progress
** Changed in: alsa-ucm-conf (Ubuntu Mantic)
Status: New => In Progress
--
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 Released
Status in alsa-ucm-conf source package in Jammy:
In Progress
Status in alsa-ucm-conf source package in Lunar:
In Progress
Status in alsa-ucm-conf source package in Mantic:
In Progress
Status in alsa-ucm-conf source package in Noble:
Fix Released
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 2009355] Re: linux-libc-dev is no longer multi-arch safe
** 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/2009355 Title: linux-libc-dev is no longer multi-arch safe Status in linux package in Ubuntu: Confirmed Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/i386/b/binutils/20230305_112702_eba45@/log.gz dpkg: error processing archive /tmp/apt-dpkg-install-9IkDRS/098-linux-libc-dev_6.1.0-16.16_i386.deb (--unpack): trying to overwrite shared '/arch/x86/include/generated/asm/.syscalls_32.h.cmd', which is different from other instances of package linux-libc-dev:i386 I'm not sure why linux-libc-dev_6.1.0-16.16 has files in /arch /install /scripts. But these files are different on different arch (or different build, since it embeds build path) ==> amd64/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-1t584m/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-1t584m/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h ==> i386/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-f194dh/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-f194dh/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009355/+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 2009355] Re: linux-libc-dev is no longer multi-arch safe
** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- 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/2009355 Title: linux-libc-dev is no longer multi-arch safe Status in linux package in Ubuntu: Confirmed Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/i386/b/binutils/20230305_112702_eba45@/log.gz dpkg: error processing archive /tmp/apt-dpkg-install-9IkDRS/098-linux-libc-dev_6.1.0-16.16_i386.deb (--unpack): trying to overwrite shared '/arch/x86/include/generated/asm/.syscalls_32.h.cmd', which is different from other instances of package linux-libc-dev:i386 I'm not sure why linux-libc-dev_6.1.0-16.16 has files in /arch /install /scripts. But these files are different on different arch (or different build, since it embeds build path) ==> amd64/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-1t584m/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-1t584m/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h ==> i386/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-f194dh/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-f194dh/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009355/+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 1991725] Re: fails to sign kernel modules
@sil2100, since this bug is already 13 days old (when the package was really accepted), and its verified as working, can't we just promote it to proposed pocket? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Kinetic: Fix Committed Bug description: [Impact] With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules. This fix for this is in the -proposed pocket at the moment, and has been tested to work. [Test plan] 1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.) 2. Install Ubuntu on the system, but do not enable the installation of third-party drivers. 3. When installation finishes, reboot. 4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system. 5. Enable -proposed. 6. Update *just* the DKMS package with "sudo apt install dkms". 7. Disable -proposed. 8. Run "sudo apt install bcmwl-kernel-source". 9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should begin working once Ubuntu boots. [Where problems could occur] Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease. --- Original bug reports: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+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 1991725] Re: fails to sign kernel modules
Ubuntu-SRU please release this one if possible, it is tested and working, and preventing people from building kernel modules. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Committed Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+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 1964825] [NEW] linux-firmware can't be upgraded in jammy breaking autopkgtests
Public bug reported: steps to reproduce: jammy chroot: dpkg -i linux-firmware_20220302.gitee0667aa-0ubuntu1_all.deb dpkg -i linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory example of failing autopkgtests: autopkgtest for pystemd/unknown: arm64: Regression ♻ autopkgtest for samba/unknown: arm64: Regression ♻ autopkgtest for shibboleth-sp/unknown: arm64: Regression ♻ autopkgtest for snapd/unknown: arm64: Regression ♻ autopkgtest for spice-vdagent/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for squid/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for sssd/unknown: arm64: Regression ♻ autopkgtest for strongswan/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for stunnel4/unknown: arm64: Regression ♻ autopkgtest for swupdate/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for systemd/unknown: arm64: Regression ♻ autopkgtest for systemd-bootchart/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for tang/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for tgt/unknown: arm64: Regression ♻ autopkgtest for tinyssh/20220311-1: amd64: Regression ♻ , armhf: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻ autopkgtest for tinyssh/unknown: arm64: Regression ♻ autopkgtest for tpm2-abrmd/unknown: arm64: Regression ♻ autopkgtest for tpm2-pkcs11/unknown: arm64: Regression ♻ autopkgtest for ubuntu-drivers-common/1:0.9.5.1: amd64: Pass, ppc64el: Pass, s390x: Not a regression autopkgtest for ubuntu-drivers-common/unknown: arm64: Regression ♻ autopkgtest for udisks2/unknown: arm64: Regression ♻ autopkgtest for umockdev/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for upower/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for usbauth/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for util-linux/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for vlc/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for vte2.91/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for webhook/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for wireshark/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for wlroots/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for yder/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for zfs-linux/unknown: arm64: Regression ♻ I'm attaching the full strace ** Affects: linux-firmware (Ubuntu) Importance: Critical Assignee: Julian Andres Klode (juliank) Status: Confirmed ** Attachment added: "linux-firmware.tar.gz" https://bugs.launchpad.net/bugs/1964825/+attachment/5568774/+files/linux-firmware.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964825 Title: linux-firmware can't be upgraded in jammy breaking autopkgtests Status in linux-firmware package in Ubuntu: Confirmed Bug description: steps to reproduce: jammy chroot: dpkg -i linux-firmware_20220302.gitee0667aa-0ubuntu1_all.deb dpkg -i linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory example of failing autopkgtests: autopkgtest for pystemd/unknown: arm64: Regression ♻ autopkgtest for samba/unknown: arm64: Regression ♻ autopkgtest for shibboleth-sp/unknown: arm64: Regression ♻ autopkgtest for snapd/unknown: arm64: Regression ♻ autopkgtest for spice-vdagent/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for squid/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for sssd/unknown: arm64: Regression ♻ autopkgtest for strongswan/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for stunnel4/unknown: arm64: Regression ♻ autopkgtest for swupdate/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for systemd/unknown: arm64: Regression ♻ autopkgtest for systemd-bootchart/unknown: arm64: Reference test in progress, but real test failed
[Kernel-packages] [Bug 1964278] Re: package firmware-sof-signed 1.7-1 failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201
This should be released in 1.9-1ubuntu1 and later releases ** Changed in: firmware-sof (Ubuntu) Status: New => Fix Released -- 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/1964278 Title: package firmware-sof-signed 1.7-1 failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201.4 Status in firmware-sof package in Ubuntu: Fix Released Bug description: running script "apl-sof-setup-audio" to setup SOF audio on laptop. During the script, received an error "dpkg-deb: error: paste subprocess was killed by signal." and the bug report dialog appeared immediately after. ProblemType: Package DistroRelease: Ubuntu 21.10 Package: firmware-sof-signed 1.7-1 Uname: Linux 5.10.102-g142ef9297957-dirty x86_64 ApportVersion: 2.20.11-0ubuntu71 AptOrdering: firmware-sof-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 8 17:44:45 2022 Dependencies: DpkgTerminalLog: Preparing to unpack .../firmware-sof-signed_1.7-1_all.deb ... Unpacking firmware-sof-signed (1.7-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.7-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201.4 DuplicateSignature: package:firmware-sof-signed:1.7-1 Unpacking firmware-sof-signed (1.7-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.7-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201.4 ErrorMessage: trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201.4 PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: firmware-sof Title: package firmware-sof-signed 1.7-1 failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1964278/+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 1780680] Re: Older version in bionic than in xenial
** Changed in: fuse-umfuse-ext2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1780680 Title: Older version in bionic than in xenial Status in fuse-umfuse-ext2 package in Ubuntu: Fix Released Status in libclc package in Ubuntu: Won't Fix Status in libdrm package in Ubuntu: Won't Fix Status in linux-meta-azure package in Ubuntu: Fix Released Status in linux-meta-gcp package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Won't Fix Status in patch package in Ubuntu: Invalid Status in python-pyvmomi package in Ubuntu: Invalid Status in snapcraft package in Ubuntu: Fix Released Status in wireless-regdb package in Ubuntu: Fix Released Bug description: These packages have an older version in artful than in xenial. fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1 libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1 libdrm 2.4.83-1 < 2.4.91-2~16.04.1 mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1 patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1 python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1 snapcraft 2.42+17.10 < 2.42.1 wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1 Some of these are older in bionic than in xenial too. Shouldn’t there be an automated check for this? (See also: bug 1780679, bug 1780681.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+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 1935778] Re: Request LLVM 12.0.1 backport to focal/updates
** Also affects: llvm-toolchain-12 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: llvm-toolchain-12 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: llvm-toolchain-12 (Ubuntu Focal) Status: New => In Progress ** Changed in: llvm-toolchain-12 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: llvm-toolchain-12 (Ubuntu) Status: New => Fix Released ** Description changed: + [ Impact ] + * People using llvm backend with other compilers + [ Description ] + * There is a fixed bug in 12.0.1 for this issue, the backend is unusable with some external compilers + [ Regression potential ] + * Low, this is part of upstream since 12.0.1 to 14 + [Other info] Hi, Focal Fossa currently carries LLVM 12.0.0, which has a bug in its C API that renders it unusable as a backend for some compilers. The upstream commit that fixes the bug is https://github.com/llvm/llvm- project/commit/07234c7d6bc246925710b88a1f9552f678587165 and was included in their 12.0.1 release. Would you be so kind as to backport 12.0.1 to Ubuntu 20.04 LTS, please? Thanks in advance for your reply. ** Summary changed: - Request LLVM 12.0.1 backport to focal/updates + [SRU] Request LLVM 12.0.1 backport to focal/updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-12 in Ubuntu. https://bugs.launchpad.net/bugs/1935778 Title: [SRU] Request LLVM 12.0.1 backport to focal/updates Status in llvm-toolchain-12 package in Ubuntu: Fix Released Status in llvm-toolchain-12 source package in Focal: In Progress Status in llvm-toolchain-12 source package in Hirsute: In Progress Bug description: [ Impact ] * People using llvm backend with other compilers [ Description ] * There is a fixed bug in 12.0.1 for this issue, the backend is unusable with some external compilers [ Regression potential ] * Low, this is part of upstream since 12.0.1 to 14 [Other info] Hi, Focal Fossa currently carries LLVM 12.0.0, which has a bug in its C API that renders it unusable as a backend for some compilers. The upstream commit that fixes the bug is https://github.com/llvm/llvm- project/commit/07234c7d6bc246925710b88a1f9552f678587165 and was included in their 12.0.1 release. Would you be so kind as to backport 12.0.1 to Ubuntu 20.04 LTS, please? Thanks in advance for your reply. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/1935778/+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 1874309] Re: package linux-image-5.4.0-25-generic 5.4.0-25.29 failed to install/upgrade: installed linux-image-5.4.0-25-generic package pre-removal script subprocess returned er
Should be fixed in impish #1933248 please drop virtualbox-guest-dkms virtualbox-guest-source ** Changed in: virtualbox-hwe (Ubuntu) Status: Confirmed => Fix Released ** 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/1874309 Title: package linux-image-5.4.0-25-generic 5.4.0-25.29 failed to install/upgrade: installed linux-image-5.4.0-25-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Bug description: Steps to reproduce: (In virtualbox) terminal-> sudo apt install virtualbox-guest-utils-hwe virtualbox-guest-dkms-hwe virtualbox-guest-x11-hwe during installation, all kernels and modules are erased, and error screen stating that user will not be able to log in if every kernel is erased is presented. After selecting yes, process is aborted. After that, deleted packages are reinstalled with sudo apt install linux-generic linux-modules-extra-5.4.0-21-generic linux-image-5.4.0-21-generic linux-image-generic linux-modules-extra-5.4.0-25-generic linux-image-5.4.0-25-generic Upon every consequent reboot, error pops up on screen, and asks user to send information. Ubuntu 5.4.0-25.29-generic 5.4.30 Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-25-generic 5.4.0-25.29 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pixxel 1620 F pulseaudio CasperMD5CheckResult: skip Date: Mon Apr 20 15:04:22 2020 ErrorMessage: installed linux-image-5.4.0-25-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-04-20 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-25-generic root=UUID=1e4016f9-5151-41ca-8098-999f643fdf2a ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 RfKill: SourcePackage: linux Title: package linux-image-5.4.0-25-generic 5.4.0-25.29 failed to install/upgrade: installed linux-image-5.4.0-25-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874309/+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 1929194] Re: virtualbox-hwe/6.1.22-dfsg-1ubuntu1.21.10.1 ADT test failure with linux-unstable/5.13.0-3.3
Should be already fixed in impish ** Changed in: virtualbox-hwe (Ubuntu) Status: New => Fix Released ** Changed in: linux-unstable (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-unstable in Ubuntu. https://bugs.launchpad.net/bugs/1929194 Title: virtualbox-hwe/6.1.22-dfsg-1ubuntu1.21.10.1 ADT test failure with linux-unstable/5.13.0-3.3 Status in linux-unstable package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Bug description: This is a scripted bug report about ADT failures while running virtualbox-hwe tests for linux-unstable/5.13.0-3.3 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/arm64/v/virtualbox-hwe/20210518_211710_937e6@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/armhf/v/virtualbox-hwe/20210518_174332_8c208@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/ppc64el/v/virtualbox-hwe/20210518_160609_96694@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/s390x/v/virtualbox-hwe/20210518_144648_96694@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-unstable/+bug/1929194/+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 1932171] Re: virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Can't mark as duplicate of 1926937 ** No longer affects: linux-hwe-5.11 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932171 Title: virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 Status in virtualbox-hwe package in Ubuntu: Confirmed Status in linux-hwe-5.11 source package in Focal: Confirmed Status in virtualbox-hwe source package in Focal: Confirmed Bug description: This is a scripted bug report about ADT failures while running virtualbox-hwe tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/v/virtualbox-hwe/20210611_210612_79a80@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-hwe/+bug/1932171/+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 1929193] Re: virtualbox/6.1.22-dfsg-1 ADT test failure with linux-unstable/5.13.0-3.3
** Changed in: linux-unstable (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-unstable in Ubuntu. https://bugs.launchpad.net/bugs/1929193 Title: virtualbox/6.1.22-dfsg-1 ADT test failure with linux- unstable/5.13.0-3.3 Status in linux-unstable package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Bug description: This is a scripted bug report about ADT failures while running virtualbox tests for linux-unstable/5.13.0-3.3 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/amd64/v/virtualbox/20210518_200239_7ad7e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-unstable/+bug/1929193/+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 1915051] Re: dkms-autopkgtest: Also select binary packages that depends on dkms for testing
The fix/hints should come from hirsute, because the package never migrated there to release pocket. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1915051 Title: dkms-autopkgtest: Also select binary packages that depends on dkms for testing Status in dkms package in Ubuntu: Fix Committed Status in dkms source package in Focal: Fix Committed Status in dkms source package in Groovy: Fix Committed Status in dkms source package in Hirsute: Fix Committed Bug description: [Impact] The current version of dkms-autopkgtest in 20.04 and later only selects binary packages with names ending with "-dkms" for its automatic DKMS test. With that packages suchs bcml-kernel-source and nvidia drivers are not being tested automatically by autopkgtest. [Test Case] Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom- 0ubuntu5) and the 5.8 kernel and even with this version of the driver failing to build with the 5.8 kernel, the test succeeds. The expected behavior, is that that dkms-autopkgtest should fail in this case. [Where problems could occur] The main issue that we can have here is selecting additional packages for the DKMS test that are not DKMS packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1915051/+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 1904590] Re: Virtualbox does not work on 20.04-edge kernel due to DKMS build failure
*** This bug is a duplicate of bug 1901904 ***
https://bugs.launchpad.net/bugs/1901904
** This bug is no longer a duplicate of bug 1891916
virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1 fails to build with kernel 5.8
** This bug has been marked a duplicate of bug 1901904
[SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with
linux-hwe-5.8 5.8.0-25.26~20.04.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1904590
Title:
Virtualbox does not work on 20.04-edge kernel due to DKMS build
failure
Status in dkms package in Ubuntu:
Confirmed
Status in virtualbox package in Ubuntu:
Confirmed
Bug description:
Building DKMS kernel modules for Virtualbox for kernel 5.8 (Ubuntu
kernel linux-image-generic-hwe-20.04-edge) fails and subsequently
Virtualbox does not work.
Ubuntu release:
~$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Relevant Virtualbox packages/versions:
virtualbox6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-guest-additions-iso6.1.10-1~ubuntu1.20.04.1
virtualbox-qt 6.1.10-dfsg-1~ubuntu1.20.04.1
Kernel packages:
~$ dpkg-query -f '${Package} ${Status}\n' -W "linux-image*" | awk '$NF ==
"installed"{print $1}'
linux-image-5.4.0-54-generic
linux-image-5.8.0-28-generic
linux-image-5.8.0-29-generic
linux-image-generic
linux-image-generic-hwe-20.04-edge
Kernel:
~$ uname -r
5.8.0-29-generic
I get an error when building DKMS for Virtualbox for kernel 5.8:
~$ sudo /usr/lib/dkms/dkms_autoinstaller start 5.8.0-29-generic
* dkms: running auto installation service for kernel 5.8.0-29-generic
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.8.0-29-generic -C
/lib/modules/5.8.0-29-generic/build
M=/var/lib/dkms/virtualbox/6.1.10/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.0-29-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information.
Build log file:
~$ cat /var/lib/dkms/virtualbox/6.1.10/build/make.log
DKMS make.log for virtualbox-6.1.10 for kernel 5.8.0-29-generic (x86_64)
di 17 nov 2020 16:30:39 CET
make: Entering directory '/usr/src/linux-headers-5.8.0-29-generic'
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvGip.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvTracer.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPLibAll.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/alloc-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/initterm-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/memobj-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/mpnotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/powernotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
In file included from ./include/asm-generic/percpu.h:7,
from ./arch/x86/include/asm/percpu.h:556,
from ./arch/x86/include/asm/preempt.h:6,
from ./include/linux/preempt.h:78,
from ./include/linux/spinlock.h:51,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/../SUPDrvInternal.h:79,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c: In
function ‘supdrvOSChangeCR4’:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
error: ‘cpu_tlbstate’ undeclared (first use in this function); did you mean
‘cpuhp_state’?
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
| ^~~~
./include/linux/percpu-defs.h:318:9: note: in definition of macro
‘__pcpu_size_call_return’
318 | typeof(variable) pscr_ret__; \
| ^~~~
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:24:
note: in expansion of macro ‘this_cpu_read’
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
|^
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
note: each undeclared identifier is reported only once for each function it
appears in
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
| ^~~~
[Kernel-packages] [Bug 1849642] Re: please provide a libbpf-dev library as debian does
** 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/1849642 Title: please provide a libbpf-dev library as debian does Status in linux package in Ubuntu: Fix Released Bug description: Hello, looks like Debian kernel is now providing a libbpf for user space applications and suricata is using it if available. Right now I patched suricata to stop using it, but a long term plan might be to start providing such features in Ubuntu kernel too. libbpf-dev and libbpf0 should be enough to fulfill suricata needs! thanks Gianfranco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849642/+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 1852435] Re: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22
** Tags added: regression-update ** Tags added: regression-proposed -- 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/1852435 Title: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22 Status in linux package in Ubuntu: Confirmed Bug description: System doesn't boot anymore with new kernel update linux- image-5.3.0-22-generic. Here is the screenshot where the boot process stops: https://photos.app.goo.gl/6b7D2SsGBpgKWLd1A I installed old kernel packages out of local deb cache (linux- image-5.3.0-19-generic), initramfs regenerated, same boot options and was able to boot fine. I assume something went wrong with new security patches, ucode for intel CPU seems not to be an issue, because old kernel booted with newly generated initrd image. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-22-generic 5.3.0-22.24 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrej 3321 F pulseaudio /dev/snd/controlC0: andrej 3321 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 14:37:01 2019 InstallationDate: Installed on 2019-11-04 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q500E2GE ProcFB: 0 i915drmfb ProcKernelCmdLine: initrd=\initrd.img-5.3.0-19-generic BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET35W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q500E2GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET35W(1.13):bd10/11/2019:svnLENOVO:pn20Q500E2GE:pvrThinkPadL490:rvnLENOVO:rn20Q500E2GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L490 dmi.product.name: 20Q500E2GE dmi.product.sku: LENOVO_MT_20Q5_BU_SMB_FM_ThinkPad L490 dmi.product.version: ThinkPad L490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852435/+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 1852435] Re: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22
I can confirm the fix worked on another ThinkPad device with BIOS/TPM enabled. -- 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/1852435 Title: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22 Status in linux package in Ubuntu: Confirmed Bug description: System doesn't boot anymore with new kernel update linux- image-5.3.0-22-generic. Here is the screenshot where the boot process stops: https://photos.app.goo.gl/6b7D2SsGBpgKWLd1A I installed old kernel packages out of local deb cache (linux- image-5.3.0-19-generic), initramfs regenerated, same boot options and was able to boot fine. I assume something went wrong with new security patches, ucode for intel CPU seems not to be an issue, because old kernel booted with newly generated initrd image. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-22-generic 5.3.0-22.24 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrej 3321 F pulseaudio /dev/snd/controlC0: andrej 3321 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 14:37:01 2019 InstallationDate: Installed on 2019-11-04 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q500E2GE ProcFB: 0 i915drmfb ProcKernelCmdLine: initrd=\initrd.img-5.3.0-19-generic BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET35W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q500E2GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET35W(1.13):bd10/11/2019:svnLENOVO:pn20Q500E2GE:pvrThinkPadL490:rvnLENOVO:rn20Q500E2GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L490 dmi.product.name: 20Q500E2GE dmi.product.sku: LENOVO_MT_20Q5_BU_SMB_FM_ThinkPad L490 dmi.product.version: ThinkPad L490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852435/+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 1852435] Re: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22
My blame list contains: - tpm_tis_core: Turn on the TPM before probing IRQ's - tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for interrupts - tpm: Wrap the buffer from the caller to tpm_buf in tpm_send() -- 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/1852435 Title: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22 Status in linux package in Ubuntu: Confirmed Bug description: System doesn't boot anymore with new kernel update linux- image-5.3.0-22-generic. Here is the screenshot where the boot process stops: https://photos.app.goo.gl/6b7D2SsGBpgKWLd1A I installed old kernel packages out of local deb cache (linux- image-5.3.0-19-generic), initramfs regenerated, same boot options and was able to boot fine. I assume something went wrong with new security patches, ucode for intel CPU seems not to be an issue, because old kernel booted with newly generated initrd image. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-22-generic 5.3.0-22.24 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrej 3321 F pulseaudio /dev/snd/controlC0: andrej 3321 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 14:37:01 2019 InstallationDate: Installed on 2019-11-04 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q500E2GE ProcFB: 0 i915drmfb ProcKernelCmdLine: initrd=\initrd.img-5.3.0-19-generic BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET35W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q500E2GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET35W(1.13):bd10/11/2019:svnLENOVO:pn20Q500E2GE:pvrThinkPadL490:rvnLENOVO:rn20Q500E2GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L490 dmi.product.name: 20Q500E2GE dmi.product.sku: LENOVO_MT_20Q5_BU_SMB_FM_ThinkPad L490 dmi.product.version: ThinkPad L490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852435/+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 1852435] Re: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22
Also, I can say: Disabling TPM in bios works as workaround kernel 5.3.0-19 was fine 5.3.0-20 was not, and nothing works up to 5.3.0-24 -- 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/1852435 Title: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22 Status in linux package in Ubuntu: Confirmed Bug description: System doesn't boot anymore with new kernel update linux- image-5.3.0-22-generic. Here is the screenshot where the boot process stops: https://photos.app.goo.gl/6b7D2SsGBpgKWLd1A I installed old kernel packages out of local deb cache (linux- image-5.3.0-19-generic), initramfs regenerated, same boot options and was able to boot fine. I assume something went wrong with new security patches, ucode for intel CPU seems not to be an issue, because old kernel booted with newly generated initrd image. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-22-generic 5.3.0-22.24 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrej 3321 F pulseaudio /dev/snd/controlC0: andrej 3321 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 14:37:01 2019 InstallationDate: Installed on 2019-11-04 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q500E2GE ProcFB: 0 i915drmfb ProcKernelCmdLine: initrd=\initrd.img-5.3.0-19-generic BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET35W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q500E2GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET35W(1.13):bd10/11/2019:svnLENOVO:pn20Q500E2GE:pvrThinkPadL490:rvnLENOVO:rn20Q500E2GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L490 dmi.product.name: 20Q500E2GE dmi.product.sku: LENOVO_MT_20Q5_BU_SMB_FM_ThinkPad L490 dmi.product.version: ThinkPad L490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852435/+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 1852435] Re: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22
Related bugs: https://bugzilla.kernel.org/show_bug.cgi?id=204121 https://bugzilla.redhat.com/show_bug.cgi?id=1770021 ** Bug watch added: Linux Kernel Bug Tracker #204121 https://bugzilla.kernel.org/show_bug.cgi?id=204121 ** Bug watch added: Red Hat Bugzilla #1770021 https://bugzilla.redhat.com/show_bug.cgi?id=1770021 -- 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/1852435 Title: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22 Status in linux package in Ubuntu: Confirmed Bug description: System doesn't boot anymore with new kernel update linux- image-5.3.0-22-generic. Here is the screenshot where the boot process stops: https://photos.app.goo.gl/6b7D2SsGBpgKWLd1A I installed old kernel packages out of local deb cache (linux- image-5.3.0-19-generic), initramfs regenerated, same boot options and was able to boot fine. I assume something went wrong with new security patches, ucode for intel CPU seems not to be an issue, because old kernel booted with newly generated initrd image. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-22-generic 5.3.0-22.24 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrej 3321 F pulseaudio /dev/snd/controlC0: andrej 3321 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 14:37:01 2019 InstallationDate: Installed on 2019-11-04 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q500E2GE ProcFB: 0 i915drmfb ProcKernelCmdLine: initrd=\initrd.img-5.3.0-19-generic BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET35W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q500E2GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET35W(1.13):bd10/11/2019:svnLENOVO:pn20Q500E2GE:pvrThinkPadL490:rvnLENOVO:rn20Q500E2GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L490 dmi.product.name: 20Q500E2GE dmi.product.sku: LENOVO_MT_20Q5_BU_SMB_FM_ThinkPad L490 dmi.product.version: ThinkPad L490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852435/+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 1849642] Re: please provide a libbpf-dev library as debian does
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** 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/1849642 Title: please provide a libbpf-dev library as debian does Status in linux package in Ubuntu: Confirmed Bug description: Hello, looks like Debian kernel is now providing a libbpf for user space applications and suricata is using it if available. Right now I patched suricata to stop using it, but a long term plan might be to start providing such features in Ubuntu kernel too. libbpf-dev and libbpf0 should be enough to fulfill suricata needs! thanks Gianfranco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849642/+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 1729051] Re: dkms mkdeb fails: Can't find package
** Changed in: dkms (Ubuntu Artful)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1729051
Title:
dkms mkdeb fails: Can't find package
Status in dkms package in Ubuntu:
Fix Released
Status in dkms source package in Artful:
Invalid
Status in dkms package in Debian:
Fix Released
Bug description:
For some reason, the Debian version of dkms mkdeb tries to generate a
.deb package with the current arch as a suffix in its name, instead of
'all'. However, since the control file wasn't properly set up, the
.deb file will have the 'all' suffix and dkms mkdeb will fail.
This bug is also present in Ubuntu. I added a patch to the original
Debian bug report, here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558
but since the original bug report was made about a year ago and nobody
cared, I'm hoping that someone will at least fix this for Ubuntu.
The patch looks like this:
--- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31
14:40:41.690069116 -0300
+++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31
14:41:12.137973994 -0300
@@ -6,6 +6,6 @@
Standards-Version: 3.8.1
Package: DEBIAN_PACKAGE-dkms
-Architecture: all
+Architecture: DEBIAN_BUILD_ARCH
Depends: dkms (>= 1.95), ${misc:Depends}
Description: DEBIAN_PACKAGE driver in DKMS format.
I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1729051/+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 1849642] [NEW] please provide a libbpf-dev library as debian does
Public bug reported: Hello, looks like Debian kernel is now providing a libbpf for user space applications and suricata is using it if available. Right now I patched suricata to stop using it, but a long term plan might be to start providing such features in Ubuntu kernel too. libbpf-dev and libbpf0 should be enough to fulfill suricata needs! thanks Gianfranco ** 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/1849642 Title: please provide a libbpf-dev library as debian does Status in linux package in Ubuntu: New Bug description: Hello, looks like Debian kernel is now providing a libbpf for user space applications and suricata is using it if available. Right now I patched suricata to stop using it, but a long term plan might be to start providing such features in Ubuntu kernel too. libbpf-dev and libbpf0 should be enough to fulfill suricata needs! thanks Gianfranco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849642/+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 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
sforshee now your fix has migrated but the dkms is still failing... -- 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/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in ddcci-driver-linux package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1837073/+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 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
sponsored! -- 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/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clickhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). FOR THE KERNEL TEAM: Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+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 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
and opened a merge request in Debian -- 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/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clickhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). FOR THE KERNEL TEAM: Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+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 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
Shouldn't this change be forwarded in Debian? can you please open a bug report? -- 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/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clickhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). FOR THE KERNEL TEAM: Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+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 1839154] [NEW] please backport upstream patch to kernel 5.2
Public bug reported: Hello, there is a serious regression in the 5.2 kernel, already fixed in 5.3-rc2 with an ongoing request of a stable backport: https://www.spinics.net/lists/netdev/msg590128.html bug: https://github.com/torvalds/linux/commit/5142967ab524eb8e5c1f6122e46e2df81bae178b fix: https://github.com/torvalds/linux/commit/f41828ee10b36644bb2b2bfa9dd1d02f55aa0516 please apply asap, this is regressing firewalld testsuite, but the bug is clearly in the kernel itself! ** Affects: linux (Ubuntu) Importance: Critical Status: 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/1839154 Title: please backport upstream patch to kernel 5.2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, there is a serious regression in the 5.2 kernel, already fixed in 5.3-rc2 with an ongoing request of a stable backport: https://www.spinics.net/lists/netdev/msg590128.html bug: https://github.com/torvalds/linux/commit/5142967ab524eb8e5c1f6122e46e2df81bae178b fix: https://github.com/torvalds/linux/commit/f41828ee10b36644bb2b2bfa9dd1d02f55aa0516 please apply asap, this is regressing firewalld testsuite, but the bug is clearly in the kernel itself! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839154/+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 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
ok lets followup in the other bug ** Changed in: dkms (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Released Status in dkms source package in Disco: Fix Released Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+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 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
Disco is fine, because the fund_module function is implemented already in 2.6.1 ** Changed in: dkms (Ubuntu Disco) Status: New => Fix Committed ** Changed in: dkms (Ubuntu Disco) Status: Fix Committed => Fix Released ** Changed in: dkms (Ubuntu Bionic) Status: New => In Progress ** Changed in: dkms (Ubuntu Bionic) Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco) ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: In Progress Status in dkms source package in Disco: Fix Released Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+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 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
This patch relies on a function that has been implemented later. I'm reopening the bug and uploading a fix for this one. vboxpci.ko: Running module version sanity check. /usr/sbin/dkms: line 784: find_module: command not found modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation ** Changed in: dkms (Ubuntu Bionic) Status: Fix Released => New ** Changed in: dkms (Ubuntu Disco) Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: In Progress Status in dkms source package in Disco: Fix Released Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+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 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
it is still failing... -- 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/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in ddcci-driver-linux package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1837073/+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 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
@Paolo Pisati, the fix didn't work... ** Changed in: ddcci-driver-linux (Ubuntu) Status: Confirmed => 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/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in ddcci-driver-linux package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1837073/+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 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in ddcci-driver-linux package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1837073/+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 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
We should 1) re-enable that on s390x 2) make the ddcci-driver-linux package stop providing binaries on s390x or hint the testsuite in case the user wants to dkms on previous kernels. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- 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/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837073/+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 1837073] [NEW] linux 5.2.0-8.9 disabled backlight on s390x.
Public bug reported: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 ** Affects: linux (Ubuntu) Importance: High Assignee: Seth Forshee (sforshee) Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) 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/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837073/+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 1783267] Re: linux-modules-extra breaks virtualbox guest modules
This looks like a regression in the kernel builtin module, nothing I can fix in virtualbox side. There have been breaking changes in newer 5.2+ virtualbox kernel modules, I suggest to avoid having them in 16.04, and to move to 18.04 if you want a newer codebase ** Changed in: virtualbox-hwe (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783267 Title: linux-modules-extra breaks virtualbox guest modules Status in linux package in Ubuntu: Confirmed Status in virtualbox-hwe package in Ubuntu: Invalid Bug description: linux-modules-extra-4.15.0-29-generic installs virtualbox guest modules that are newer than what virtualbox-guest-dkms-hwe provides (5.2.8 vs 5.1.34): $ modinfo /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko filename: /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko license:GPL and additional rights description:Oracle VM VirtualBox Graphics Card author: Oracle Corporation srcversion: 689EDF1E50DE15779B4F930 alias: pci:v80EEdBEEFsv*sd*bc*sc*i* depends:drm,drm_kms_helper,ttm staging:Y retpoline: Y intree: Y name: vboxvideo vermagic: 4.15.0-29-generic SMP mod_unload parm: modeset:Disable/Enable modesetting (int) $ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko version:5.2.8_KernelUbuntu r120774 alias: fs-vboxsf license:GPL author: Oracle Corporation description:Oracle VM VirtualBox VFS Module for Host File System Access srcversion: AF89497125574B5225F9B6A depends:vboxguest retpoline: Y intree: Y name: vboxsf vermagic: 4.15.0-29-generic SMP mod_unload parm: follow_symlinks:Let host resolve symlinks rather than showing them (int) $ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko version:5.2.8_KernelUbuntu r120774 license:GPL description:Oracle VM VirtualBox Guest Additions for Linux Module author: Oracle Corporation srcversion: F2E5886E3B0544500D404A1 alias: pci:v80EEdCAFEsvsdbc*sc*i* depends: retpoline: Y intree: Y name: vboxguest vermagic: 4.15.0-29-generic SMP mod_unload Thus installation with dkms fails (while attempting `apt-get install --reinstall virtualbox-guest-dkms-hwe`): Building initial module for 4.15.0-29-generic Done. vboxguest: Running module version sanity check. Error! Module version 5.1.34_Ubuntu for vboxguest.ko is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu). You may override by specifying --force. vboxsf.ko: Running module version sanity check. Error! Module version 5.1.34_Ubuntu for vboxsf.ko is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu). You may override by specifying --force. vboxvideo.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.15.0-29-generic/updates/dkms/ depmod DKMS: install completed. My system does not start correctly with kernel 4.15 and I had to fall back to 4.13 which has working virtualbox guest modules. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 24 08:33:57 2018 InstallationDate: Installed on 2015-02-04 (1265 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-08-02 (720 days ago) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dyslimet 3006 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c045d946-13ab-48d3-afa0-2496f98eb0a4 InstallationDate: Installed on 2015-02-04 (1266 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001
[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
This is fixed in the -proposed kernel, so I don't plan to hack virtualbox sources to drop such flag. ** Changed in: virtualbox (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xtables-addons package in Ubuntu: Confirmed Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+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 1619446] Re: mismatching headers between powerpc/ppc64el and other archs
Yes it does exist in eoan. (see gambas3 failures
https://launchpad.net/ubuntu/+source/gambas3/3.13.0-1~exp1~build1/+build/16742807
)
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Changed in: linux (Ubuntu)
Importance: Medium => 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/1619446
Title:
mismatching headers between powerpc/ppc64el and other archs
Status in linux package in Ubuntu:
Confirmed
Bug description:
the header files from linux-libc-dev are causing repsnapper on
-proposed to FTBFS on powerpc/ppc64el
I tracked it to 2 include clauses:
#include
#include
causing the following error on powerpc/ppc64el builds:
following errors:
src/printer/custom_baud.cpp: In function 'bool set_custom_baudrate(int,
int)':
src/printer/custom_baud.cpp:15:19: error: aggregate
'set_custom_baudrate(int, int)::termios2 options' has incomplete type and
cannot be defined
struct termios2 options;
^
src/printer/custom_baud.cpp:17:26: error: 'TCGETS2' was not declared in
this scope
if ( ioctl( device_fd, TCGETS2, ) < 0 ) {
^
src/printer/custom_baud.cpp:27:26: error: 'TCSETS2' was not declared in
this scope
if ( ioctl( device_fd, TCSETS2, ) < 0 ) {
Please see bug #1619100 for more info.
Comparing the powerpc/ppc64el headers to amd64 I found that they seem
to be missing includes to other headers under asm-generic/
If I try to add the missing asm-generic headers:
#include
#include
#include
#include
Then the build again fails on both powerpc/ppc64el and succeeds on all
other archs, this time the error is:
In file included from src/printer/custom_baud.cpp:11:0:
/usr/include/asm-generic/termbits.h:11:8: error: redefinition of ‘struct
termios’
struct termios {
^~~
In file included from src/printer/custom_baud.cpp:9:0:
/usr/include/powerpc-linux-gnu/asm/termbits.h:22:8: error: previous
definition of ‘struct termios’
struct termios {
^~~
In file included from src/printer/custom_baud.cpp:11:0:
/usr/include/asm-generic/termbits.h:31:8: error: redefinition of ‘struct
ktermios’
struct ktermios {
^~~~
In file included from src/printer/custom_baud.cpp:9:0:
/usr/include/powerpc-linux-gnu/asm/termbits.h:35:8: error: previous
definition of ‘struct ktermios’
struct ktermios {
^~~~
Finally, modifying the original includes to remove the asm/termbits.h:
#include
#include
#include
Allows for the repsnapper build to succeed on all arches, including
powerpc/ppc64el. Question is: why is this even needed?
linux-libc-dev packages:
Get:10 http://ftpmaster.internal/ubuntu yakkety/main powerpc linux-libc-dev
powerpc 4.4.0-9136.55 [818 kB]
Get:10 http://ftpmaster.internal/ubuntu yakkety/main ppc64el linux-libc-dev
ppc64el 4.4.0-9136.55 [818 kB]
Get:10 http://ftpmaster.internal/ubuntu yakkety/main amd64 linux-libc-dev
amd64 4.4.0-9136.55 [828 kB]
Checking the headers is seems that powerpc/ppc64el are missing
includes for asm-generics:
$ grep -r TCGETS2 linux-libc-dev_4.4.0-9136.55_*/
linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/ioctls.h:#define
TCGETS2 _IOR('T', 0x2A, struct termios2)
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/ioctls.h:#define
TCGETS2 _IOR('T', 0x2A, struct termios2)
$ grep -r ioctls.h linux-libc-dev_4.4.0-9136.55_*/
linux-libc-dev_4.4.0-9136.55_amd64/usr/include/x86_64-linux-gnu/asm/ioctls.h:#include
linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/termios.h:#include
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/termios.h:#include
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/powerpc64le-linux-gnu/asm/termios.h:#include
$ grep -r "termios2 {" linux-libc-dev_4.4.0-9136.55_*/
linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/termbits.h:struct
termios2 {
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/termbits.h:struct
termios2 {
$ grep -r termbits.h linux-libc-dev_4.4.0-9136.55_*/
linux-libc-dev_4.4.0-9136.55_amd64/usr/include/x86_64-linux-gnu/asm/termbits.h:#include
linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/termios.h:#include
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/termios.h:#include
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/powerpc64le-linux-gnu/asm/termios.h:#include
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619446/+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 1825210] Re: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update
The bionic package contains the change! (its linux-hwe-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/1825210 Title: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Bug description: [SRU Justification] Impact: The virtualbox package was updated in disco just prior to release, with numerous bug fixes. It is standard practice during development to sync our in-kernel source with the latest version of the virtualbox-guest-dkms package, however this upload was done so late in the release that there was not time to update the source in our kernel tree. Fix: Re-sync the vbox guest dkms drivers from virtualbox 6.0.6-dfsg-1. Regression Potential: This is a sync from the dkms package in the disco-release pocket, thus the code has presumably been tested against the Ubuntu Disco kernel. However, this is a very large pile of changes, and contains more than just bug fixes, so regressions are possible. Test Case: Boot a kernel with the updated driver in virtualbox and confirm that the guest drier functionality works as expected. --- * the changes are already in disco (vbox-guest-dkms), and they are fixes for the kernel 5.0. They might seem a lot of changes, but they are needed, and probably some of them are even CVE fixes... As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825210/+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 1825210] Re: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1825210 Title: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Bug description: [SRU Justification] Impact: The virtualbox package was updated in disco just prior to release, with numerous bug fixes. It is standard practice during development to sync our in-kernel source with the latest version of the virtualbox-guest-dkms package, however this upload was done so late in the release that there was not time to update the source in our kernel tree. Fix: Re-sync the vbox guest dkms drivers from virtualbox 6.0.6-dfsg-1. Regression Potential: This is a sync from the dkms package in the disco-release pocket, thus the code has presumably been tested against the Ubuntu Disco kernel. However, this is a very large pile of changes, and contains more than just bug fixes, so regressions are possible. Test Case: Boot a kernel with the updated driver in virtualbox and confirm that the guest drier functionality works as expected. --- * the changes are already in disco (vbox-guest-dkms), and they are fixes for the kernel 5.0. They might seem a lot of changes, but they are needed, and probably some of them are even CVE fixes... As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825210/+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 1825210] Re: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update
yes, the kernel contains the new kernel modules for vbox, thanks! ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825210 Title: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Bug description: [SRU Justification] Impact: The virtualbox package was updated in disco just prior to release, with numerous bug fixes. It is standard practice during development to sync our in-kernel source with the latest version of the virtualbox-guest-dkms package, however this upload was done so late in the release that there was not time to update the source in our kernel tree. Fix: Re-sync the vbox guest dkms drivers from virtualbox 6.0.6-dfsg-1. Regression Potential: This is a sync from the dkms package in the disco-release pocket, thus the code has presumably been tested against the Ubuntu Disco kernel. However, this is a very large pile of changes, and contains more than just bug fixes, so regressions are possible. Test Case: Boot a kernel with the updated driver in virtualbox and confirm that the guest drier functionality works as expected. --- * the changes are already in disco (vbox-guest-dkms), and they are fixes for the kernel 5.0. They might seem a lot of changes, but they are needed, and probably some of them are even CVE fixes... As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825210/+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 1825210] Re: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update
** Summary changed: - Please sync vbox modules from virtualbox 6.0.6 on next kernel update + [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update ** Description changed: + [SRU Justification] + * the changes are already in disco (vbox-guest-dkms), and they are fixes for the kernel 5.0. + They might seem a lot of changes, but they are needed, and probably some of them are even CVE fixes... + As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825210 Title: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update Status in linux package in Ubuntu: Confirmed Bug description: [SRU Justification] * the changes are already in disco (vbox-guest-dkms), and they are fixes for the kernel 5.0. They might seem a lot of changes, but they are needed, and probably some of them are even CVE fixes... As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825210/+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 1825210] Re: Please sync vbox modules from virtualbox 6.0.6 on next kernel update
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** 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/1825210 Title: Please sync vbox modules from virtualbox 6.0.6 on next kernel update Status in linux package in Ubuntu: Confirmed Bug description: As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825210/+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 1825210] [NEW] Please sync vbox modules from virtualbox 6.0.6 on next kernel update
Public bug reported: As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. thanks ** Affects: linux (Ubuntu) Importance: High Assignee: Seth Forshee (sforshee) Status: Confirmed ** Tags: bot-stop-nagging ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu) 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/1825210 Title: Please sync vbox modules from virtualbox 6.0.6 on next kernel update Status in linux package in Ubuntu: Confirmed Bug description: As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825210/+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 1798921] Re: sky2 ethernet card don't work after returning from suspension
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+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 1818148] Re: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed)
*** This bug is a duplicate of bug 1818049 *** https://bugs.launchpad.net/bugs/1818049 ** This bug has been marked a duplicate of bug 1818049 virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] -- 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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1
[Kernel-packages] [Bug 1818148] Re: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed)
Am I correct in saying that this is probably due to the kernel module not being built correctly? I'm marking as duplicate -- 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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias:
[Kernel-packages] [Bug 1783267] Re: linux-modules-extra breaks virtualbox guest modules
can you please try a systemctl cat virtualbox-guest-utils-hwe when the system is not starting? -- 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/1783267 Title: linux-modules-extra breaks virtualbox guest modules Status in linux package in Ubuntu: Confirmed Status in virtualbox-hwe package in Ubuntu: New Bug description: linux-modules-extra-4.15.0-29-generic installs virtualbox guest modules that are newer than what virtualbox-guest-dkms-hwe provides (5.2.8 vs 5.1.34): $ modinfo /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko filename: /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko license:GPL and additional rights description:Oracle VM VirtualBox Graphics Card author: Oracle Corporation srcversion: 689EDF1E50DE15779B4F930 alias: pci:v80EEdBEEFsv*sd*bc*sc*i* depends:drm,drm_kms_helper,ttm staging:Y retpoline: Y intree: Y name: vboxvideo vermagic: 4.15.0-29-generic SMP mod_unload parm: modeset:Disable/Enable modesetting (int) $ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko version:5.2.8_KernelUbuntu r120774 alias: fs-vboxsf license:GPL author: Oracle Corporation description:Oracle VM VirtualBox VFS Module for Host File System Access srcversion: AF89497125574B5225F9B6A depends:vboxguest retpoline: Y intree: Y name: vboxsf vermagic: 4.15.0-29-generic SMP mod_unload parm: follow_symlinks:Let host resolve symlinks rather than showing them (int) $ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko version:5.2.8_KernelUbuntu r120774 license:GPL description:Oracle VM VirtualBox Guest Additions for Linux Module author: Oracle Corporation srcversion: F2E5886E3B0544500D404A1 alias: pci:v80EEdCAFEsvsdbc*sc*i* depends: retpoline: Y intree: Y name: vboxguest vermagic: 4.15.0-29-generic SMP mod_unload Thus installation with dkms fails (while attempting `apt-get install --reinstall virtualbox-guest-dkms-hwe`): Building initial module for 4.15.0-29-generic Done. vboxguest: Running module version sanity check. Error! Module version 5.1.34_Ubuntu for vboxguest.ko is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu). You may override by specifying --force. vboxsf.ko: Running module version sanity check. Error! Module version 5.1.34_Ubuntu for vboxsf.ko is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu). You may override by specifying --force. vboxvideo.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.15.0-29-generic/updates/dkms/ depmod DKMS: install completed. My system does not start correctly with kernel 4.15 and I had to fall back to 4.13 which has working virtualbox guest modules. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 24 08:33:57 2018 InstallationDate: Installed on 2015-02-04 (1265 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-08-02 (720 days ago) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dyslimet 3006 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c045d946-13ab-48d3-afa0-2496f98eb0a4 InstallationDate: Installed on 2015-02-04 (1266 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 80ee:0022 VirtualBox Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox-hwe ProcFB: 0 vboxdrmfb
