[07:34] <LocutusOfBorg> hello apw sforshee which vbox driver are you using nowadays? 5.2.8 is out, should I ping you or you will take the one mainline?
[07:34]  * LocutusOfBorg hopes for the latter
[12:01] <LocutusOfBorg> apw, ping :)
[12:01] <LocutusOfBorg> BTW virtualbox is "regressed" because some new tests see that the built kernel and the one in Ubuntu differ... obviously
[12:08] <apw> yep, dkms is a pile of crap, it has no idea how to compare versions if there is not a manual version
[12:18] <LocutusOfBorg> apw, second question, are you using vbox mainline kernel drivers? 
[12:20] <apw> we are still at .26 i think, and i believe not using those, because the only one which existed at the time was blowin up
[12:20] <apw> but i would have to defer to sforshee for accurate memory on that 
[12:22] <LocutusOfBorg> please delete it, and switch to the mainline version :)
[12:25] <apw> mainline only provides one of them at 4.15 level right ?
[12:35] <LocutusOfBorg> no, even 4.14 IIRC
[12:58] <ricotz> hi, is bionic getting 4.16 after all?
[13:04] <sforshee> LocutusOfBorg: bionic currently has version 5.2.6-dfsg-5, we are using the in-tree vboxvideo driver which I believe is the only one that exists in 4.15
[13:06] <sforshee> once the 5.2.8 package promotes I can update to that
[13:50] <LocutusOfBorg> sforshee, sorry, I mean, don't use the vboxvideo from vbox, but use the one inside the kernel source tree
[13:50] <LocutusOfBorg> it is now fixed
[13:51] <LocutusOfBorg> git tag --contains ce10d7b4e8e3574b9616e54a09d64521b9aeb8b6
[13:51] <LocutusOfBorg> v4.15
[13:51] <LocutusOfBorg> since 4.15~rc1
[13:51] <sforshee> LocutusOfBorg: yes, that's what I meant by "using the in-tree" driver. We've been using that in-kernel one rather than the one we import from vbox-guest-dkms for a while now
[13:52] <LocutusOfBorg> I don't get this: [14:06:00] <sforshee> once the 5.2.8 package promotes I can update to that
[13:52] <LocutusOfBorg> I mean: please continue to use the in-tree one then
[13:52] <sforshee> LocutusOfBorg: we still import the vbox-guest-dkms drivers but disable the vboxvideo one from there
[13:53] <LocutusOfBorg> oh... ok, I don't see the need, but fine
[13:53] <sforshee> it provides other functions than the video doesn't it?
[13:53] <sforshee> otherwise maybe we don't need to do that anymore
[13:54] <LocutusOfBorg> vboxsf and so on...
[13:54] <LocutusOfBorg> ok
[13:54] <LocutusOfBorg> just disable vboxvideo from there then
[13:54] <sforshee> yeah, our import script does that automatically now
[13:54] <LocutusOfBorg> ack
[13:54] <LocutusOfBorg> unfortunately such drivers might have a bug
[13:54] <LocutusOfBorg> KERNEL=="vboxguest", NAME="vboxguest", OWNER="root", MODE="0660"
[13:54] <LocutusOfBorg> KERNEL=="vboxuser", NAME="vboxuser", OWNER="root", MODE="0666"
[13:55] <apw> (see truth you need sforshee :)
[13:55] <LocutusOfBorg> this is the content of: debian/virtualbox-guest-dkms.udev
[13:57] <LocutusOfBorg> anyhow, it is fine to grab even 5.2.8 right now, but I don't think there are updates there
[13:59] <sforshee> LocutusOfBorg: hmm, so you're saying without those udev rules having those drivers in the kernel may not provide any benefit?
[14:00] <sforshee> I mean, if you think there's no benefit in having them shipped with the kernel now we should talk about removing them
[14:00] <sforshee> would save me some effort at minimum ;-)
[14:00] <sforshee> I'm unfamiliar with the history of why we started shipping them in the kernel packages anyhow
[14:00] <LocutusOfBorg> I didn't receive any complain about them, so maybe they are fixed now, and I should remove the udev rule too
[14:01] <LocutusOfBorg> unfortunately it has been added too many years ago
[14:01] <LocutusOfBorg> so, I prefer to "don't touch if it isn't broken"
[14:01] <LocutusOfBorg> BTW please grab 5.2.8, the difference with 5.2.6 is *only* kernel 4.15 fixes, so, before trying to fix, update the tarball :)
[14:02] <sforshee> ack, will update
[14:02] <LocutusOfBorg> (I'm about to send a diff)
[14:03] <LocutusOfBorg> https://paste.ubuntu.com/p/WnZgVw7h5C/
[14:03] <LocutusOfBorg> there is a new timer function, probably some fixes in timer syncronization host/guest
[14:03] <LocutusOfBorg> and the most important thing is a new structure
[14:03] <LocutusOfBorg> + * Intel PCID invalidation types.
[14:04] <LocutusOfBorg> (I presume, because upstream refuses to release CVE patches), it has something to do with spectre/meltdown
[14:04] <LocutusOfBorg> +    /* Clear bits which we don't pass through for security reasons. */
[14:04] <LocutusOfBorg> +    pDst->Attr.fMode       &= ~(RTFS_UNIX_ISUID | RTFS_UNIX_ISGID | RTFS_UNIX_ISTXT);
[14:05] <LocutusOfBorg> apw, can you please update the vbox hint, I don't want to loose days to fix dkms, better have a vbox versionless hint for now
[14:06] <apw> not gong to make it versionless
[14:06] <LocutusOfBorg> it is clearly a bad test, and I don't need autopkgtests because in case of dkms failure I get reports from debian and Ubuntu *minutes* after dinstall, really
[14:06] <apw> i read the logs before updating the hints normally
[14:39] <amitk> apw: do you guys provide linux-tools-common for the mainline builds at http://kernel.ubuntu.com/~kernel-ppa/mainline/ ?
[14:39] <amitk> I'm looking for perf
[14:39] <apw> nope we don't make tools mostly, because they don't work in a cross environment
[14:39] <apw> likely we don't do them at all, when we could for x86 at least
[14:39]  * amitk nods
[15:15] <Misha_R> Hello! A friend is looking for a HWE kernel DEB for Ubuntu LTS from December. He wants a version before the Meltdown/Spectre patches.
[15:15] <Misha_R> Where can he find such a DEB?
[15:21] <apw> Misha_R, in the launchpad librarian ...
[15:22] <apw> https://launchpad.net/ubuntu/+source/linux/+publishinghistory
[15:22] <apw> Misha_R, ^ that has the complete publishing history for the kernel; oh you wanted linux-hwe
[15:22] <apw> https://launchpad.net/ubuntu/+source/linux-hwe/+publishinghistory
[15:22] <apw> Misha_R, ^ so that one
[15:23] <apw> iirc -26 was the first one with those changes, but you should check
[15:27] <Misha_R> apw thanks
[15:44] <Misha_R> apw: we can't seem to find the way to download the actual debs. For example we try this one https://launchpad.net/ubuntu/+source/linux-hwe/4.10.0-41.45~16.04.1 . There is a list of binary files but there does ot seem to be a way to download them
[15:45] <Misha_R> Is rebuilding from source the only option?
[15:53] <TJ-> Misha_R: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/13771372
[15:54] <TJ-> Misha_R: That's the link from the page you referenced, under "Builds > amd64"
[16:00] <Misha_R> Thanks!
[16:01] <Misha_R> TJ-: thanks!
[17:21] <raidghost> TJ had a question about modify dvb amount. Possible to turn the limit of 8 up to 16 ?
[17:22] <raidghost> TJ-: Did you get any answer for that dvb question?
[17:22] <TJ-> raidghost: no I didn't... create a bug report so we can log/follow it
[17:23] <raidghost> TJ-: Where to make that kind of report? not that into this things :p
[17:23] <TJ-> !bug ~ raidghost 
[17:23] <TJ-> grrr
[17:23] <TJ-> !bug | raidghost 
[17:23] <ubot5`> raidghost: If you find a bug in Ubuntu or any of its derivatives, please report it using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs.
[17:23] <TJ-> raidghost: report it against the package "linux"
[17:24] <raidghost> Have to figure out how to explain the thingy. not good with words
[17:26] <raidghost>  thought that it was the driver i had to rebuild. but if its the kernel. Its a bit more not easy.
[17:28] <TJ-> raidghost: "Increase DVB_MAX_ADAPTERS from 8 to 16 in kernel config" and then explain why (because there are 4 cards each with 4 devices on)
[17:28] <TJ-> raidghost: tell me the bug once you're created it and I'll add some commentary
[17:35] <raidghost> TJ-: okey ;)
[18:49] <raidghost> TJ-: Just a quick question. Since the host that i want to type the ubuntu-bug thingy on doesnt have graphical. is that needed to get that box that selects all the hardware information?
[19:22] <raidghost> TJ-: Just created it. link is in PM
[19:36] <Misha_R> Excuse me, another question again
[19:37] <Misha_R> With Xenial (LTS) and the HEW kernel, how should one decide whether to install linux-image or linux-image-extras ?
[19:37] <Misha_R> I could not find any explanations later than 14.04
[21:12] <apw> you always need linux-image add linux-image-extra if you are on hardware
[21:13] <thresh> I always install -extra, because I've been burned too many times upgrading my OS and being unable to boot or no network card up.
[21:34] <mozmck> What is in the -extra package, and should a mainline build create one?
[21:47] <apw> -extra has modules you don't need on a virtual machine, mainline builds do not make one because they do no split at all, linux-image is "fat"
[22:28] <mozmck> apw: thanks.  I'm running preempt-rt and no virtual machines.