@Khaled after giving it a little more thought, I think these changes
might be needed in bionic in the situation that an artful user is
upgrading to bionic or when a xenial hwe user is upgrading to bionic. I
think that if the lttng-modules-dkms binary package is upgraded to the
bionic package bionic while there are still kernels installed from the
old release, the user will see this bug. Could you test these situations
or just get out a bigger hammer and prepare a bionic debdiff that I can
sponsor?
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: Khaled El Mously (kmously)
Status: In Progress
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => Khaled El Mously (kmously)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Khaled El Mously (kmously)
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Artful)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => 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/1756240
Title:
Unable to build lttng-module with Artful kernel
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
In Progress
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
New
Bug description:
[Impact]
* The 4.13.0-38 artful kernel included a change (backported from
4.15) that modifies the definition of kvm_mmio(). This breaks the
lttng-modules-dkms package because it is using the old (<4.15)
definition.
* lttng-modules-dkms already has a list of kernel version
"exceptions" with which it uses the >=4.15 definition. Proposed
solution is to add the Ubuntu kernel range 4.13.0-38 up to
4.14.255-255 to that list of exceptions.
[Test Case]
* Tested by first successfully building lttng-modules-dkms on
4.13.0-37, then reproducing the problem described here on 4.13.0-38,
then applying the code-change and confirming that I can successfully
build on both 4.13.0-37 and 4.13.0-38 after that.
[Regression Potential]
* Low-regression potential. Could prevent lttng-modules-dkms from
being built for specific kernel versions, but this is unlikely as the
change was tested to confirm that it works as expected on 4.13.0-37
and 4.13.0-38 - and should work fine for other Ubuntu kernels as well.
The lttng module failed to build with the proposed Artful kernel
(4.13.0-38), it works with 4.13.0-37
Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-38-generic 4.13.0-38.43
ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Mar 16 04:13 seq
crw-rw---- 1 root audio 116, 33 Mar 16 04:13 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Fri Mar 16 04:17:14 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Intel Corporation S1200RP
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB:
0 mgadrmfb
1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
RelatedPackageVersions:
linux-restricted-modules-4.13.0-38-generic N/A
linux-backports-modules-4.13.0-38-generic N/A
linux-firmware 1.169.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
dmi.board.asset.tag: ....................
dmi.board.name: S1200RP
dmi.board.vendor: Intel Corporation
dmi.board.version: G62254-407
dmi.chassis.asset.tag: ....................
dmi.chassis.type: 17
dmi.chassis.vendor: ..............................
dmi.chassis.version: ..................
dmi.modalias:
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr....................:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..............................:ct17:cvr..................:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: S1200RP
dmi.product.version: ....................
dmi.sys.vendor: Intel Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+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
