/srv/irclogs.ubuntu.com/2016/10/20/#ubuntu-kernel.txt

=== mamarley is now known as Guest427
=== mamarley_ is now known as mamarley
=== mamarley is now known as Guest91007
=== mamarley_ is now known as mamarley
xnoxi wonder if i can run LTS kernel on yakkety, such that i get CLS for my laptop07:50
smbxnox, you surely can run then 18.04 kernel ... at some point08:02
xnoxhm. i'm wondering why we don't keep lts ga kernel in yakkety. Or like forward copy it.08:03
xnoxi should be able to pin to xenial kernel package i think. things should generally work.08:03
smbxnox, its just that I wonder why you want that08:06
smb(and don't assume I have any idea at this time of day about what this CLS ramblings are)08:08
xnoxlive patchign08:08
xnoxbecause it is stated that live patches are not currently built/released for yakkety kernel08:09
smbxnox, so what? its not like you could not reboot your laptop :-P08:11
caribouguys, I must be missing something obvious with my kernel rebuilds:09:10
cariboueven when building the generic package with skipabi=true skipmodule=true, I'm not able to reboot with a rebuilt bzImage 09:11
caribouit just doesn't find the root device upon reboot09:12
caribouFYI I'm working on a bisect & don't want to have to rebuild all modules each & everytime09:12
caribouapw: smb: any thought ? ^^^09:15
caribouif you're not too busy of course :)09:15
smbcaribou, hm... frankly for bisecting I usually (most of the time its on mainline trees anyhow) copy a /boot/config-... into .config and run "make -j32 deb-pkg INSTALL_MOD_STRIP=1"09:16
smbThere is some auto incrementing version of the packages that way, too09:16
caribousmb: which Mainline tree did you use ? kernel.org one ? last time I tried, it complained that it could no find debian/control09:17
smbJust one needs to be careful what number is used with the latest build (they might jump back and forth)09:17
caribousmb: I would prefer to use the mainline as I can't use non-linear tags for the bisect09:18
caribousmb: let me try your command again09:18
smbcaribou, yes the kernel.org one09:18
smbcaribou, note its is just plain make and not dpkg-buildpackage or so09:18
boulabiarHi, how to bug report the new kernel livepatch ?09:47
boulabiarafter installing, my laptop can't sleep anymore09:47
boulabiarubuntu-bug canonical-livepatch don't work, because the package is installed via snap09:48
henrixboulabiar: i guess you'll need to use https://bugs.launchpad.net/ubuntu/+source/canonical-livepatch/+filebug09:50
boulabiarhenrix: something went wrong with the page you asked my to use09:56
boulabiarI've written a full paragraph, then when i clicked send, an error appeared, I repeated this 2 times...09:57
henrixboulabiar: ah, so launchpad is probably in one of those days10:01
ogra_apw, did you forget to binary-new the linux-raspi2 package in xenoal-security/-updates ?10:01
ogra_(seems the images that QA tries to test here at the sprint all ended up with 4.4.0.1029.29)10:03
smbogra_, the version number sounds like the one I would expect10:05
ogra_smb, 10:06
ogra_ linux-raspi2 | 4.4.0-1029.36 | xenial-security/universe  | source10:06
ogra_vs10:06
ogra_ linux-raspi2 | 4.4.0.1029.29 | xenial-security/universe  | armhf10:06
ogra_brad is on it though, i pinged him in person10:07
apwogra_, what is wrong with those versions ?10:19
apwremember one is source and the other is a binary from a _different_ source10:19
ogra_apw, we need 4.4.0-1029.36 in the archive as binaries10:19
ogra_ogra@anubis:~/datengrab/images/snappy$ rmadison -s xenial-updates,xenial-security linux-raspi210:20
ogra_ linux-raspi2 | 4.4.0-1029.36 | xenial-updates/universe  | source10:20
ogra_ linux-raspi2 | 4.4.0-1029.36 | xenial-security/universe | source10:20
ogra_ linux-raspi2 | 4.4.0.1029.29 | xenial-updates/universe  | armhf10:20
ogra_ linux-raspi2 | 4.4.0.1029.29 | xenial-security/universe | armhf10:20
ogra_there is no armhf binary for 4.4.0-1029.36 anywhere 10:20
apwogra_, the binary is _not_ called linux-raspi2 ?10:22
apwyou are asking rmadison for binaries only called linux-raspi210:22
ogra_oh man 10:22
apwtry -S10:23
ogra_indeed you are right, thoughh why do we only get .29 in the snaps then10:23
ogra_https://launchpadlibrarian.net/290161189/buildlog_snap_ubuntu_xenial_armhf_pi2-kernel_BUILDING.txt.gz10:24
ogra_thats a build log from 2h ago 10:24
apwogra_, the linux-raspi2 package is from linux-meta-raspi2 and that is the ight number for that10:24
ogra_Get:5 http://ftpmaster.internal/ubuntu xenial-security/universe armhf linux-image-raspi2 armhf 4.4.0.1029.29 [2324 B]10:24
apwyou should have linux-raspi2 at 4.4.0.1029.29 (note no - in the version)10:24
apwand linux-image-4.4.0-1029 at 4.4.0-1029.36 which is from linux-raspi210:25
ogra_hmm10:25
ogra_Get:2 http://ftpmaster.internal/ubuntu xenial-security/universe armhf linux-image-4.4.0-1029-raspi2 armhf 4.4.0-1029.36 [35.3 MB]10:25
ogra_there is actually is10:25
apwright, so that is exactly as expected10:25
ogra_then i dont get whyy all the bugs are still there :(((10:26
apwogra_, which bugs, ones which are fixed in the -proposed kernel ?10:26
smbogra_, because it only fixes security10:26
smb?10:26
ogra_(teh kernel i tested from proposed yesterday was not oopsing on boot ... the QA team now tests it and has unbootable imges again)10:26
apwogra_, they are not in that kernel it was an embargoed security fix10:26
ogra_err10:27
apwogra_, that is exactly expected10:27
ogra_so you didnt base on that one ? 10:27
apwthat is _how_ embargoed cves work10:27
ogra_damn 10:27
ogra_well, we need the one from proposed today 10:27
apwno we would never do that, it was an untested CVE CRD release10:27
apwogra_, that is gone10:27
ogra_so is there any way to get the fixes in today (we tested the hell out of the proposed kernel yesterday to make sure it can land asap)10:28
apwogra_, that doesn't have the aa fix bear in mind10:29
ogra_it is essential for the snappy RC image that we need to release this week10:29
ogra_(and what you have in the archive is unbootable anyway on pi3 currently)10:29
apwogra_, i might be able to resurect the previous version but that won't have the aa fix which we respan for10:30
sbeattieogra_: jjohansen may have a kernel you can use which was based on the -proposed kernel with the raspi2 fixes + the needed apparmor fix.10:30
ogra_sbeattie, for the archive ? 10:30
sbeattiein a ppa10:30
apwoh yeah thats right, we could do that because there was jj's kernel in a ppa10:30
jjohansenogra_: so based on kernel that was in updates yesterday + the apparmor fix10:30
jjohansenhttps://launchpad.net/~apparmor-dev/+archive/ubuntu/apparmor-devel10:30
apwogra_, anyhow, i'll see where we are with the respins10:30
sbeatties/updates/proposed/10:30
ogra_can we somehow fast-path that in ? (i have the QA team here and i can spin snaps for them from the PPA to get everything tested)10:31
jjohansensbeattie, orgra: so again this is not based on -proposed but on -updates from yesterday10:31
jjohansenthe xenial -proposed kernel has the apparmor backport from yakkety on it10:32
sbeattiejjohansen: oh, updates?10:32
jjohansenyeah -updates from yesterday10:33
ogra_jjohansen, well, we have a kernel that oopses on boot, that was the released kernel and the one formerly in updates ... 10:33
ogra_the only kernel that boots is the one that was in -proposed yesterday 10:34
apwogra_, cna you remember the version number ?10:34
ogra_i can dig it up, i have a test image but that needs some time since i need to set up gear to boot it to run uname 10:35
apwogra_, can you build images/snaps whatever against a PPA10:35
apwif not then it is no point in me trying to find it10:36
ogra_apw, ppisati said it should just be  >= 4.4.0-1028.34  but thats obviously not true when the former proposed kernel wasnt even used10:36
apwwhat should be ?10:36
jjohansenogra_: so xenial -proposed should not be vulnerable to the aa bug, the yakkety version of apparmor had refactored that code and due to that had the fix in it already10:36
ogra_apw, the one with all the fixes :)10:36
apwi need a specific exact version as i have to reach blind into the archive10:37
ogra_yes, i know 10:37
jjohansenthe ppa has the -updates kernel with the apparmor fix based on the assumption you would a released kernel10:37
ogra_as i said, that requires some work10:37
ogra_jjohansen, right, but -updates is a step back and wont boot without some bootloader hackery first 10:38
ogra_apw, i'll ping you as soon as i can give you the version10:38
jjohansenogra_: got it, so I just want to confirm for you from an apparmor pov the ppa kernel based on yesterdays -updates and the xenial -proposed kernel should be functionally equiv. ie not have the bug10:39
apwogra_, oh, a thought, isn't the download of the package from -proposed in the logs of the image build which was good; rather than booting it11:25
ogra_apw, \o/ ... sorry it took so long, found the package version in a build log 12:16
ogra_Get:5 http://ftpmaster.internal/ubuntu xenial-proposed/universe armhf linux-image-raspi2 armhf 4.4.0.1028.28 [2324 B]12:16
ogra_and12:17
ogra_Get:1 http://ftpmaster.internal/ubuntu xenial-proposed/universe armhf linux-image-4.4.0-1028-raspi2 armhf 4.4.0-1028.34 [35.4 MB]12:17
ogra_does that help ?12:18
apwogra_, yes that helps, thanks.12:21
yoasifhi, is there any documentation or way of getting the "extras" package for mainline kernel builds?16:16
tjaaltoni'm hit by https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/163511518:44
ubot5`Ubuntu bug 1635115 in grub2 (Ubuntu) "grub fails zfs root filesystem detection due to failed checksum" [Undecided,Confirmed]18:44
tjaaltonmy home server fails to boot after latest updates to xenial18:44
tjaaltonoh well, no time to fix it now..18:47
mamarleyOoh, that should be probably be marked Critical.18:55
apwi am not sure zfs is support as root/boot is it?18:55
tjaaltonnot in the installer, but i see no reason to make it harder19:16

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