/srv/irclogs.ubuntu.com/2017/01/19/#ubuntu-kernel.txt

=== mamarley_ is now known as mamarley
=== inaddy is now known as tinoco
=== Elimin8r is now known as Elimin8er
=== eichiro_ is now known as eichiro
=== samkottler_ is now known as samkottler
=== AceLan_ is now known as AceLan
=== manjo` is now known as manjo
=== alai` is now known as alai
=== _ruben_ is now known as _ruben
LocutusOfBorgapw, please sync kernel modules from virtualbox08:53
LocutusOfBorg5.1.14 has important fixes08:53
LocutusOfBorgalso the kernel that will go in 16.04.2 probably needs updates from here https://launchpad.net/ubuntu/+source/virtualbox/5.0.32-dfsg-0ubuntu1.16.04.208:54
LocutusOfBorgapw, I'm back :)09:57
=== mhcerri_ is now known as mhcerri
apwLocutusOfBorg, the .2 kernel will be the hwe kernel and has (in theory) 11:35
apw    Vileda SuperMocio 3 Action Refill - Twin Pack by Vileda11:35
apwno not that11:35
apw5.1.6-dfsg-211:35
LocutusOfBorgtooo old11:35
LocutusOfBorg5.1.14 has fixes11:35
apwthat is what is _in_ yakkety, which is where the kernel comes from11:35
LocutusOfBorgso kernel 4.8?11:36
apwyes, it will be essentially yakkety's kernel11:36
LocutusOfBorgok fine then11:36
LocutusOfBorgfixes are for kernel 4.9+11:36
LocutusOfBorgso, please apply them for zesty only11:37
apwack11:52
LocutusOfBorgbut question: most changes are build fixes for newer kernels, how do you handle them? I can't understand how you can update the kernel without updating vbox kernel modules too11:58
=== jdstrand_ is now known as jdstrand
jsalisburystgraber, I'll post a link to a test kernel in bug 1655842? shortly13:05
ubot5bug 1655842 in linux (Ubuntu Xenial) ""Out of memory" errors after upgrade to 4.4.0-59" [High,Triaged] https://launchpad.net/bugs/165584213:05
=== ben_r_ is now known as ben_r
montvidhi there. i would like to ask for a kernel fix as written in http://askubuntu.com/questions/674179/ubuntu-device-flash-fails-on-nexus-7-2013-android-5-0-2-cant-copy-image-to the device is officialy supported but completly not installing for more than a year now. see bug https://bugs.launchpad.net/canonical-devices-system-image/+bug/149675614:33
ubot5Ubuntu bug 1496756 in Canonical System Image "Nexus 7 devices which ship with android 5 need revised storage drivers" [High,Confirmed]14:33
montvidhow come a device that is supported officialy does not work at all for over a year?14:34
montvidi asked popey in ubuntu touch and he answered he has no idea what to do...14:35
montvidi see people in xda fixed their twrp recovery, made a kitkat boot image and are good. is there a possibility to merge these changes in ubuntu touch kernel?14:38
montvidbecause the nexus 7 device bought in 2015 and later do not install at all. How can it have support if it does not boot?14:41
montvidany ideas? 14:43
montvid:)14:43
LocutusOfBorgmontvid, the patch posted on askubuntu is already inside the kernel AFAIK14:48
LocutusOfBorgcommit 6636bad839d9936e73e48c4841eda83a58fcdb5314:48
LocutusOfBorg$ git tag --contains 6636bad839d9936e73e48c4841eda83a58fcdb53 |head -n 114:48
LocutusOfBorgv3.1114:48
LocutusOfBorgthe first one was kernel 3.11, shipping that fix14:48
montvidbut nexus 7 is on 3.4.0 as i understand?14:49
LocutusOfBorgso, the fix is already there14:50
LocutusOfBorgs/is/should be14:50
montvidis the fix applied to ubuntu recovery too? because yesterday it did not install. it installed with github files only.14:51
montvidhttps://github.com/ddagunts/UTCWM_N7_patch/blob/master/boot.img?raw=true14:52
montvidusing this repo i could install ubuntu touch stable14:53
montvidi get the same error as in the bug link14:54
montvidif i try to use official builds of boot.img and recovery.img14:54
montvidthanks for the info LocutusOfBorg 14:55
LocutusOfBorgI'm not an Ubuntu kernel developer unfortunately, so I don't know how they patch it14:55
montvidwell android devices can not change kernel versions. they stay in the same branch nexus 7 2013 is in 3.4 branch and cant go to 3.5 14:58
montvidor 3.1114:58
montvidcan anyone change the bug status from high to critical?14:59
montvidbecause of this bug one cant install and run the system. seems critical :)15:00
LocutusOfBorgwhich bug?15:06
montvid <montvid> hi there. i would like to ask for a kernel fix as written in http://askubuntu.com/questions/674179/ubuntu-device-flash-fails-on-nexus-7-2013-android-5-0-2-cant-copy-image-to the device is officialy supported but completly not installing for more than a year now. see bug https://bugs.launchpad.net/canonical-devices-system-image/+bug/149675615:07
ubot5Ubuntu bug 1496756 in Canonical System Image "Nexus 7 devices which ship with android 5 need revised storage drivers" [High,Confirmed]15:07
montvidsorry for the dublicate15:07
LocutusOfBorgmterry, ^^ seems that I can't change the bug severity :)15:10
montvidthanks for trying15:10
montvidmaybe you could add a comment? i dont have a login...15:11
LocutusOfBorgit won't add much value :/15:11
montvidi understand. 15:15
caribousmb: FYI, uploaded crash 7.1.7-1ubuntu1; autopkgtest found a bug which is fixed in post 7.1.7 so I have just uploaded a ubuntu2 with the upstream fix15:36
=== JanC_ is now known as JanC
smbcaribou, oh ok. I just recently saw some crash going to the archive but have not looked closely at the version numbers15:44
caribousmb: well, it got stucked into -proposed following a failure in DEP8 test15:45
caribousmb: the failure is specific to live crash session so I missed it by testing on a _real_ kernel crash15:45
smbcaribou, Ah, but at least good to see the dep8 testing being good for something15:46
caribousmb: indeed; I should have run it before uploading though15:46
smbcaribou, True, though I must admit that often I forget that part, too. 15:48
stgraberjsalisbury: thanks15:59
jsalisburystgraber, good timing.  The build just finished.  Once second, I'll scp it and drop a link15:59
jsalisburystgraber, http://kernel.ubuntu.com/~jsalisbury/lp1655842/armhf/16:01
stgraberjsalisbury: thanks. I'll install that on one of the boards and see if it shows OOM over the next 24 hours (it's a jenkins runner)16:01
jsalisburystgraber, thanks16:01
=== ratliff_ is now known as ratliff
setuidIs there a way to parallelize update-initramfs on a test box with hundreds of kernels? 19:58
setuidupdate-grub takes hours19:58
setuidIt20:00
setuidIt's a pipeline from a failed apt-get, so running dpkg --configure -a 20:00
setuidThis sort of works, but it's ugly: ls -1 /boot/vmlinuz* | cut -b9-40 | while read line; do sudo update-initramfs -c -k $line & done;20:17

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!