[08:40] <apw> zkanda, which series are you trying to run it, what is your root disk stored on?
[08:43] <zkanda> apw:  model is UX501VW, the root disk is on one for the partition. But have a weird naming scheme. Not the usual sda.
[08:44] <apw> zkanda, what does you disk get named as ?
[08:46] <apw> and which series of ubuntu are you installing on it
[08:52] <zkanda> Wait, let me look at it.
[08:54] <zkanda> apw: disk get name as something like  this: nvme0n1p2, latest 15.10 ubuntu.
[09:09] <tjaalton> you'd need newer initramfs-tools
[09:10] <tjaalton> nvme module location changed, so 4.4 and up won't boot since the initrd doesn't include it
[09:13] <zkanda> tjaalton: How do I do that? Just a link where I could follow is good. Searching didn
[09:13] <zkanda> 'didn't yield good information.
[09:16] <tjaalton> https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1524879
[09:16] <ubot5`> Launchpad bug 1524879 in initramfs-tools (Ubuntu) "initramfs-tools, Xenial is missing NVME kernel driver" [High,Fix released]
[09:17] <tjaalton> apw: looks like it regressed something
[09:18] <apw> tjaalton, do we know zkanda is even running xenial ?
[09:19] <apw> zkanda, what version of initramfs-tools is installed on your system (dpkg -l initramfs-tools)
[09:19] <tjaalton> apw: using mainline kernels on any release has the same bug
[09:19] <tjaalton> it's 15.10
[09:19] <tjaalton> mainline kernels 4.4 and up that is
[09:19] <apw> tjaalton, right .. then then we would expect mainline 4.4 to not work on anything before 16.04
[09:19] <tjaalton> yep
[09:21] <zkanda> Ok, any advice what should I do from this? Sorry I'm not too familiar on how this things work. :(
[09:21] <tjaalton> you could just modify the hook manually
[09:22] <apw> i suspect that is the "simplest" as you are unlikely to be able to install initramfs-tools from xenial without a bunch of pre-requisites
[09:23] <apw> i seem to remember merging up a bunch of stuff to make that work
[09:23] <zkanda> tjaalton: How do I do that? Don't know how hook works.
[09:24] <zkanda> Can I just try Xenial Alpha then? Would that work? I actually tried the Xenial Mate, but it didn't boot either.
[09:24] <zkanda> I forgot the actual error when trying it out though.
[09:25] <tjaalton> edit /usr/share/initramfs-tools/hook-functions, add what's on the first comment on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807000
[09:25] <ubot5`> Debian bug 807000 in initramfs-tools "initramfs-tools: module nvme not included in block modules on kernel > 4.2" [Normal,Fixed]
[09:26] <tjaalton> then run update-initramfs -u -k all
[09:26] <apw> tjaalton, i don't think they want to us -k all
[09:26] <apw> until they know they ahve done _one_ right
[09:27] <tjaalton> 4.2 still boots
[09:28] <tjaalton> or -k $whatever
[09:28] <tjaalton> dunno what it would be for some random mainline
[09:28] <zkanda> Ok, I'll try that later, still at work so I can't experiment around. haha
[10:44] <xnox> apw, we really should backport that change.... all the way back to trusty?
[10:44] <xnox> apw, are we doing kernel-lts-xenial for trusty?
[10:53] <apw> xnox, yes, we are, infact vrey much now ...
[10:53] <apw> xnox, i'll file a bug for that now ... as it owuld be a pre-requisite for that indeed
[10:59] <apw> xnox, i've added a task to LP: #1524879 ... note the fix got refixed in a later upload, anyhow will put it on my todo
[10:59] <ubot5`> Launchpad bug 1524879 in initramfs-tools (Ubuntu Trusty) "initramfs-tools, Xenial is missing NVME kernel driver" [High,Triaged] https://launchpad.net/bugs/1524879
[11:26] <zkanda> tjaalton: That didn't seem to fix the issue, disk still not found
[11:29] <tjaalton> zkanda: did you run update-initramfs?
[11:29] <zkanda> Yes I did.
[11:29] <zkanda> Note this is kernel 4.5
[11:29] <tjaalton> doesn't matter
[11:34] <zkanda> tjaalton: is there anything I can look to verify that the nvme module is updated?
[12:08] <tjaalton> zkanda: unpack the initrd to see it's there. if it isn't you didn't fix hook-functions enough
[12:41] <jjohansen> apw: So the lockinng patchbomb, is at git://kernel.ubuntu.com/jj/ubuntu-xenial.git patch-bomb
[12:41] <jjohansen> It has the mount patch that tim reverted with a fixup: patch for it that fixes an rcu locking problem that the original patch had. I haven't folded that fixup in yet so you guys could easily see the diff
[12:42] <apw> jjohansen, ack
[12:42] <jjohansen> I haven't managed to get to cleaning up the full queue yet, there are several fixups that need to be folded into other patches a few bug links to add etc.
[12:43] <jjohansen> apw: if you want to just pull the mount patch + fixup, its the 2nd and 3rd patches in the queue
[12:43] <jjohansen> the 1st one is for a minor mount auditing issue
[12:44] <jjohansen> the audit patch does slightly change the mount sleep fix patch, I should have probably changed the ordering
[12:45] <jjohansen> apw: its passed my testing but I haven't run stgraber's tests nor have I tested on anything but amd64 yet
[12:45] <apw> jjohansen, 39 patches, ugg
[12:45] <rtg> jjohansen, wow, you want all of these ?
[12:46] <apw> you've got a lot of unannotated titles in there (no apparmor prefixes) is that expected ?
[12:46] <jjohansen> apw: like I said I need to clean it up yet
[12:46] <apw> jjohansen, oh ok ... rtg ^
[12:47] <jjohansen> rtg: sadly yes, its all backported fixups to locking and ref counting, and fallout around it
[12:47] <jjohansen> it fixes kees's bug
[12:47] <apw> rtg, if we applied the cleaned version to something and uploaded it to unstable, we could get the adt tests for lxc etc run against it
[12:47] <rtg> jjohansen, well, we can wait until you are ready. no use in doing this twice.
[12:48] <rtg> apw, yeah, could do that
[12:48] <jjohansen> rtg: if you want we could cherry-pick out the mount patch + its fixup and just apply that atm,
[12:48] <rtg> jjohansen, that is the one causing problems right now, correct ?
[12:49] <jjohansen> rtg: yes, its the fix you reverted, patch #3 is a fixup to that patch
[12:49] <apw> sounds like we should take that one for master-next, and shove the whole thing on a test kernel
[12:50] <rtg> jjohansen, 'fix-up: kern_mount fail path should not be doing put_buffers()' I presume
[12:50] <jjohansen> rtg: yes
[12:52] <jjohansen> rtg: give me a minute to rebase the patch series, as it stands patch1 causes a conflct with #2 and #3 so you can clean cherry-pick them
[12:52] <rtg> jjohansen, yeah, I was just noticing that
[12:52] <rtg> jjohansen, just holler when you are ready
[13:10] <jjohansen> rtg: ok repushed with -f , the mount patch and its fixup are now the 1st and 2nd patch in the queue, and the old patch #1 gets completely dropped because it turns out to be superfluous with the reorder
[13:11] <rtg> jjohansen, got it. I'll upload the whole pile to our unstable PPA for some testing.
[13:11] <rtg> and cherry-pick just the 2 for master-next
[13:11] <jjohansen> rtg: okay, thanks. I'll work on cleanup the commit messages and folding some of the patches together. No point in keeping fixups to patches in the queue
[13:12] <jjohansen> that is fixups separate
[13:12] <rtg> jjohansen, agreed
[13:13] <rtg> jjohansen, in fact, would it hurt if I just squashed those 2 ? it might prevent a bisect problem for jsalisbury  sometime in the future.
[13:14] <jjohansen> rtg: no, I would squash them, I just kept them separate so you and apw could see what the fix was
[13:14] <rtg> cool
[14:19] <jdstrand> ogasawara, cking: thanks!
[14:19] <cking> jdstrand, my pleasure, I'll wait to see what the upstream developer thinks
[14:20] <jdstrand> cking: ack. let me know if you need anything
[14:20] <cking> jdstrand, ok, I may ask you to test the fix at some point
[14:20] <jdstrand> sure thing
[16:07] <manjo> rtg, when I cross build on tangerine for arm64 .. /lib/modules/$(uname -r)/build/scripts/<blah> are all built for x64 .. is there a way to force to build everything arm64?
[16:08] <rtg> dpkg-buildpackage -d -aarm64
[16:09] <manjo> yep that was my cmd line 
[16:09] <rtg> manjo, within the right chroot ?
[16:09] <manjo> yeah within xenial chroot 
[16:10] <manjo> wily/xenial does the same thing 
[16:13] <rtg> manjo, you could try '/usr3/ubuntu/kteam-tools/buildscripts/ukb-make --release=$RELEASE --arch=$ARCH --branch=$BRANCH --clean --repo=`pwd`'
[16:13] <rtg> which is how I do all of my builds
[16:14] <manjo> rtg, so I don't need to dchroot blah .. just run this on the pwd ie kernel source 
[16:14] <rtg> yup
[16:14] <manjo> what is branch ? 
[16:15] <rtg> the branch in your local repo. I assume you are developing on master
[16:15] <manjo> ah yes master 
[16:15] <manjo> so if I drop --branch it would use master ? 
[16:15] <rtg> manjo, can't remember
[16:15] <manjo> ok I will figure out 
[16:20] <manjo> rtg, oops that script won't work if I did a dpkg-source -x extract of a dsc ... 
[16:20] <rtg> manjo, only works from a repo
[16:24] <manjo> rtg, do you have an arm64 cross compiled headers-generic  package I can use? I want to see if your script builds stuff under linux/scripts correctly
[16:25] <manjo> rtg, I think that makefile might not support cross compile flags 
[16:27] <manjo> probably that is the right thing to do ie build those x64 when you are building on x64 ?
[16:28] <rtg> manjo, y'all ain't makin' no sense to me - wtf are you trying to do ?
[16:30] <ogra_> dont you need to set ARCH= and CROSS_COMPILE= too ? 
[16:30] <manjo> ☺ there are a bunch of tools under linux/scripts/*.c which gets built as x64 when I cross compile for arm64... from looking that makefile May be it does not support cross compile
[16:30] <manjo> and it could be the right thing to do ie .. build them for the native platform coz some of theose tools are used for the build itself 
[16:30] <ogra_> iirc "dpkg-buildpackage -d -aarm64" isnt enough
[16:31] <rtg> I've specifically disable tools generation when cross compiling. its just too much of a PITA
[16:31] <ogra_> yeah, the deps will bite
[16:32] <rtg> manjo, if you want tools, then you'll have to upload to a PPA for a native build
[16:33] <manjo> yeah that is a PITA ☺ coz it takes like 3hrs on native PPA 
[16:33] <rtg> I can't help that
[16:33] <ogra_> get a dragonboard ;)
[16:33] <manjo> I know .. just saying 
[16:56] <rtg> jsalisbury, are you pursuing bug #1540731 with upstream now that you've identified the regression ?
[16:56] <ubot5`> bug 1540731 in Mir "SocketMessenger::update_session_creds() fails to get client PID, causing "[ FAILED ] PromptSessionClientAPI.client_pid_is_associated_with_session" on kernel 4.4 (but kernel 4.3 works)" [Critical,Confirmed] https://launchpad.net/bugs/1540731
[16:58] <jsalisbury> rtg, yes.  I have an email to respond to
[16:58] <jsalisbury> rtg, and there is a new patch to replace the revert, so I can get it tested
[16:59] <rtg> jsalisbury, cool
[18:39] <melodie> hello
[18:41] <melodie> I am looking for hardware supported info, especially the Intel CPU Skylake : either i5 or i7 (4 brands AFAIK)
[18:41] <melodie> I read here: http://www.phoronix.com/scan.php?page=news_item&px=intel-skl-prelim-support
[18:41] <melodie> it's of last summer, how is it now?
[18:41] <melodie> can we have accelerated/3D and all working well?
[18:42] <melodie> I have to help someone build the specs of his new machine and his favorite distro is Kubuntu. He does current office work and reworks his pictures (gimp mostly). He wants it to be very snappy. (the machine will have 8 GB ram to start with)
[18:42] <melodie> what do you think?
[18:45] <melodie> no one around at this time, for insights about hardware?
[19:20] <Pithegorus> hye how do i customize ubuntu kernel?
[19:35] <melodie> KillerSingam by recompiling it
[19:36] <melodie> hi garrettr 
[19:37] <melodie> do you have knowledge about the intel CPUs and the kernels available at Ubuntu? I'm told that for a i5 or i7 Skylake I would need a Xenial  and I wonder if there is another way to get a 4.3 or 4.4 kernel image in let's say, Wily?
[19:37] <melodie> I have to provide a machine to a friend who uses Kubuntu (and a good machine)
[19:38] <melodie> he knows not about hardware and software, but I have to give him the best and stable possible because he also uses it for his work
[19:38] <melodie> what do you think?
[19:38] <melodie> (I asked around here one hour ago, and no answer so far)
[19:39] <KillerSingam> how do i recompile my kernel
[19:39] <melodie> KillerSingam you seek for the documentation first
[19:40] <melodie> https://help.ubuntu.com/community/Kernel/Compile
[19:40] <melodie> thanks to Qwant, the search engine. ;)
[19:40] <KillerSingam> qwant?
[19:41] <melodie> https://www.qwant.com/
[19:41] <melodie> yes, I've qwanted for you
[19:42] <KillerSingam> can i use that qwantum  for my girlfriend?
[19:48] <melodie> this is not a bouquet of flowers, nor a perfume. It's a search engine
[19:48] <melodie> so go compile your kernel now! what are you waiting for,
[19:48] <melodie> ?
[19:50] <KillerSingam> if i did compile my kernel.. how do i install it
[20:06] <arges> melodie: Xenial works just fine on a skylake i7 for me. Basing on an LTS release (like xenial) would provide the most stable path depending on your timeframe.
[20:10] <melodie> arges how stable is Kubuntu Xenial is something I should test, I guess
[20:10] <arges> melodie: of course, and also release the actual release isn't until April
[20:10] <melodie> my timeframe is not large, if you are referring to how long to I have to build the specs for this tower. A couple days, then it has to be ordered
[20:11] <melodie> I know it's not before April, however I have upgraded my own custom edition (Bento Openbox Remix) and it works fine (it was better with nouveau than with the nvidia driver, but my tower is an old box)
[20:12] <melodie> arges the person for whom I'm building the specs needs it for his daily work, which is common current work, and also to edit pictures, he makes photos and edits them with Gimp
[20:13] <melodie> he will have the machine start with 8 GB RAM and we can add more if needed. Just now I'm not quite sure which version Kubuntu and which version processor I should pick up
[20:13] <melodie> I was looking here: http://ark.intel.com/fr/products/88192/Intel-Core-i7-6600U-Processor-4M-Cache-up-to-3_40-GHz
[20:13] <melodie> and to the latest here:
[20:14] <melodie> http://ark.intel.com/fr/products/family/88392/6th-Generation-Intel-Core-i7-Processors#@Desktop
[20:16] <melodie> arges may I continue?
[20:16] <arges> melodie: I'm not entirely sure which works best. But if you do run into issues please file bugs. : )
[20:18] <melodie> arges I don't get to provide specs and use, I only provide specs and the end user will have to get the perfect choice :D
[20:19] <melodie> this is why the choice is difficult (where would be the fun otherwise?) XD
[20:19] <melodie> http://www.ldlc.com/informatique/pieces-informatique/processeur/c4300/+fb-C000000192+fv579-5524+fv160-13685.html
[20:19] <melodie> I have been shown the first one on the list, then when the guy said "Skylake" I thought omg! that's new! how is that with the kernel?
[20:19] <melodie> :)
[20:19] <melodie> and after I did a search I thought the best would be asking the chans for insights
[20:21] <arges> melodie: I understand. And yes, I was mainly trying to answer 'does the Ubuntu kernel support Skylake CPUs?'
[20:23] <melodie> arges now I'm going to grab a Kubuntu Xenial, install it on a box (I have enough computers to give it a try on bare metal) and see how it goes.
[20:24] <melodie> arges I thank you for your kindness
[20:24] <arges> melodie: good luck
[20:24] <melodie> :)
[20:24] <melodie> thanks!
[20:35] <KillerSingam> melodie
[20:35] <KillerSingam> hi
[20:36] <KillerSingam> melodie how to recompile my kernel where do i get the source
[20:42] <melodie> KillerSingam you read the page that I pointed you to, then you follow the first link you find in it. surely you know how to read? https://help.ubuntu.com/community/Kernel/Compile