[06:39] <tjaalton> is it possible to have linux-generic removed by some upgrade?
[06:41] <tjaalton> or autoremove
[08:38] <zzarr> hello! I tried this question in the #ubuntu channel and got the response "yes", but not how... is there a way to turn on/off power of a USB-port (physical) from command line?
[10:44] <jtaylor> hi, I have tried the xenial lts-yakkety kernel from the kernel because I like breaking stuff ;)  fyi lvm raid doesn't seem to work
[10:44] <jtaylor> *from the ppa
[10:44] <jtaylor> some error about cannot assemble array, unknown compatibility flags
[10:49] <apw> jtaylor, which version was the lts-yakkety in the PPA ?
[10:52] <apw> tjaalton, yes it is entirely possible if you have -proposed enabled, in theory much harder otherwise as we copy packages out in groups in the same publisher run
[10:52] <jtaylor> apw: hm the one yesterday
[10:52] <jtaylor> it updated today but the changelog was just abi
[10:53] <apw> so -19 ?
[10:53] <tjaalton> apw: maybe a mirror not in sync?
[10:53] <tjaalton> a friend complained about this
[10:53] <jtaylor> apw: yes
[10:54] <apw> tjaalton, maybe its all a little tricky after the fact, but it should tell you and make you acknoledge the removal
[10:56] <tjaalton> yeah it had gone at some point and then after do-release-upgrade it was still on the old hwe kernel
[10:57] <apw> well if they had linux-generic-lts-foo installed it would be quite common to remove linux-generic then
[10:57] <apw> though the former should be a transitional package in later releases
[10:58] <tjaalton> hmm if it was installed via .2 installer, linux-generic would not be installed, right? what should then pull it in with d-r-u?
[11:00] <apw> linux-generic-lts-raring (or whatever .2 was) should exist in raring and in xenial as a transitional package pointing to linux-generic
[11:00] <apw> so which ever way they upgraded they should be protected
[11:00] <tjaalton> ah, right
[11:02] <apw> though it is possible we dropped those in saucy and then when raring went away allowed direct upgrade to saucy and got it wrong?
[11:03] <apw> knowing the exact seires they upgraded through might help understand if it was bad luck or our fail
[11:09] <tjaalton> this was lts-vivid -> xenial
[11:09] <tjaalton> dunno if it was installed earlier
[11:12] <apw> that package seems to exist in the appropriate places, intalling xenial ought to have installed linux-generic
[11:14] <tjaalton> yeah
[11:17] <apw> but one assume l-g-l-v got pushed off somewhen before that
[11:17] <tjaalton> yep
[14:11] <rtg> cyphermox, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628968/comments/16
[14:11] <ubot5> Ubuntu bug 1628968 in linux (Ubuntu Yakkety) "powerpc 4.8.0-17 fails to boot on PowerMac G5" [Undecided,In progress]
[16:44] <jsalisbury__> dannf, When you get a chance, can you verify bug 1623627 ?  See comment 2
[16:44] <ubot5> bug 1623627 in linux (Ubuntu Xenial) "thunder: faulty TSO padding" [High,Fix committed] https://launchpad.net/bugs/1623627
[16:44] <jsalisbury__> dannf, also bug 1624569
[16:44] <ubot5> bug 1624569 in linux (Ubuntu) "thunder: chip errata w/ multiple CQEs for a TSO packet" [High,In progress] https://launchpad.net/bugs/1624569
[16:45] <dannf> jsalisbury__: yeah, both are on my list. travelling today, will see if i can get it done at the airport.
[16:45] <jsalisbury__> dannf, ack, thanks
[16:45] <dannf> jsalisbury__: how soon do you need results?
[16:46] <jsalisbury__> dannf, at least by the end of next week, which is the end of the cycle
[16:46] <dannf> jsalisbury__: cool - should be no problem
[16:46] <jsalisbury__> dannf, thanks
[16:47] <jsalisbury__> AceLan, could you verify bug 1625932 when you have a chance?  See comment #2
[16:47] <ubot5> bug 1625932 in linux (Ubuntu Xenial) "Backlight does not change when adjust it higher than 50% after S3" [High,Fix committed] https://launchpad.net/bugs/1625932
[19:25] <thesh>  what is the difference between the kernel which is present on kernel.org and the kernel vmlinuz which is present on our system?
[19:29] <thesh> please anybody answer
[19:35] <apw> thesh, the ubuntu delta, the ubuntu configuration, and packaging
[19:36] <thesh> apw,can you explain in more detail
[19:36] <apw> thesh, what are you trying to find out ?
[19:38] <thesh> apw: if we say what is the size of the kernel? then question comes in mind that it will be size of vmlinuz but then what the one which is present on kernel.org?
[19:39] <apw> thesh, i don't think that is very meaningful as the kernel when built consists of vmlinuz and the modules.  the kernel.org kernles are source only so no binaries at all
[19:43] <thesh> apw, what do you mean by consist of vmlinuz and the modules?
[19:44] <apw> thesh, the built form of a kernel is the kernel itself (often vmlinuz) and associated loadable modules in /lib/modules/<version>
[19:47] <thesh> apw,so the build kernel and the kernel from kernel.org are both different?
[19:48] <apw> thesh, kernel.org has just the virgin upstream code, we add ubuntu sauce to that, and then build and publish those binaries
[19:50] <thesh> apw: ok but if we have to refer kernel size so shall we take the reference to the kernel.org which will be in some GB
[19:51] <apw> thesh, what do you mean by kernel size
[19:52] <thesh> apw: kernel size means size of the kernel (in megabytes or gigabytes)
[19:52] <apw> thesh, on disk or in memory when running etc ?
[19:53] <thesh> in memory
[19:59] <thesh> apw:if we have to refer size what should we taken in to consideration disk or memory?
[20:00] <apw> thesh, the only one who knows is you ...
[20:00] <apw> thesh, the in memory consumption is the uncompressed size of the main kernel plus the size of any modules loaded, so a movable feast
[20:06] <thesh> apw:correct me if i am wrong, kernel.org kernel (stable one) contains all the source code which is in some GB and after building that kernel with any flavour on the top of it, its contains loadable modules and the kernel vmlinuz 
[20:07] <apw> thesh, roughtly speaking yes
[20:14] <thesh> apw: thanks