/srv/irclogs.ubuntu.com/2018/07/30/#ubuntu-kernel.txt

=== himcesjf_ is now known as him-cesjf
Laneyha;lp14:23
LaneyI'm getting https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/175351814:25
ubot5Ubuntu bug 1753518 in grub2-signed (Ubuntu) "package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1" [Undecided,Confirmed]14:25
Laney+ grub-install --target=x86_64-efi --auto-nvram14:25
LaneyInstalling for x86_64-efi platform.14:25
LaneyCould not delete variable: Invalid argument14:25
Laneygrub-install: error: efibootmgr failed to register the boot entry: Block device required.14:25
Laneydpkg: error processing package grub-efi-amd64-signed (--configure):14:25
Laney installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 114:25
Laneyetc14:25
Laneygrub-install: info: executing efibootmgr </dev/null >/dev/null.14:27
Laneygrub-install: info: executing efibootmgr -b 0000 -B.14:27
LaneyCould not delete variable: Invalid argument14:27
Laneygrub-install: error: efibootmgr failed to register the boot entry: Block device required.14:27
apwLaney, uff, cyphermox ^ 14:40
apwi asusme that is on upgrade of a grub2 ...14:41
Laneyyeah grub-efi-amd64-signed14:41
apwcosmic ?14:41
Laneynope bionic14:41
Laney *** 1.93.3+2.02-2ubuntu8.2 50014:41
Laney        500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages14:41
sforsheeLocutusOfBorg: we have a 4.17 kernel that's about ready for cosmic-release, except that it needs the virtualbox from -proposed to pass adt. Is that going to promote soon?14:43
apwLaney, what kernel are you runing14:43
apwwhen that fails14:43
Laneylaney@nightingale> uname -a                                                                                     ~14:44
LaneyLinux nightingale 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux14:44
LocutusOfBorgsforshee, I'm not the one blocking it14:44
LocutusOfBorgask release team14:44
apwLocutusOfBorg, what is blocking it14:45
LocutusOfBorgwhen I requested to make xorg migrate, it was only blocked by qtbase14:45
LocutusOfBorgsorry, only blocked by xorg14:45
LocutusOfBorgnow it is entangled with qtbase too14:45
LocutusOfBorgsoooo, I don't care anymore14:46
=== SimonNL is now known as SimonNL_Afk
=== SimonNL_Afk is now known as SimonNL
danieru98jsalisbury, just finished testing your test kernel for bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783906 , i've posted an update there, long story short, you were right about reverting 2dc0b46b5ea3, that fixes that bug20:02
ubot5Ubuntu bug 1783906 in linux (Ubuntu Cosmic) "Linux 4.15 and onwards fails to initialize some hard drives" [Medium,In progress]20:02
danieru98Should i mark that bug as fixed, or wait for any further updates?20:02
jsalisburydanieru98, wait for further updates.  I need to investigate that commit further to see if it can be simply reverted or needs to be fixed properly.20:03
jsalisburydanieru98, I'll probably need to ping the patch author, but I'll cc the bug report, so it gets all the email exchange.20:04
danieru98jsalisbury, okay, if you need me to test any other kernel feel free to just ask me. i'll keep my eyes on on that bug report for any updates20:05
jsalisburydanieru98, thanks!20:10
tyhickssforshee: hey - for the /sys/class/net changes that I did for LXD, is it alright if I just "backport" them to ubuntu-unstable/master (currently 4.18 based) in order to land them in cosmic? I'd prefer to just ignore 4.15 for now20:28
sforsheetyhicks: yes however you may also want to backport to 4.17 (cosmic/master-next)20:29
tyhickssforshee: oh, should I *only* do cosmic/master-next rather than unstable/master?20:30
tyhicksthey cherry pick to unstable/master but I haven't tried cosmic/master-next yet20:31
sforsheeshould do both if it's easy, but if 4.17 is a big pain it's not that big of a deal20:33
tyhickssforshee: I'll figure out how to do both but 4.17 is a pain because lxd still isn't working there due to the 55956b59df33 ("vfs: Allow userns root to call mknod on owned filesystems.")20:38
sforsheetyhicks: that's odd, lxd adt tests pass on our 4.17 kernel20:39
tyhickssforshee: sorry, I meant 4.18 is a pain20:40
tyhicks4.17 doesn't have that commit20:40
sforsheetyhicks: that makes more sense20:41
sforsheeoh yes the mknod thing ...20:41
tyhicksright20:42
tyhicksthat never got reverted20:42
sforsheetyhicks: I'll check in with brauner about that tomorrow, we're gonna need a resolution on that soon20:43
tyhickssforshee: I think there's a workaround in lxd now but it hasn't been released yet, IIRC20:43
sforsheeyeah I had thought they had a fix for lxd20:44
sforsheebut still problems because of systemd's everywhere without the fix20:44
tyhicksright20:44
stgraber3.0.2 liblxc will have the workaround but yeah, won't necessarily help with the containers...20:44
stgraberI think the LXD snap should also already include all the needed bits for 4.1820:45
stgraberyeah, it does, so "snap install lxd" would get you a LXD with the needed liblxc bits20:45
sforsheestgraber: I do know that adt is failing for both lxc and lxd on 4.18, I haven't had ac hance to look into it yet20:45
stgraberyeah, that'll most likely fail until we push 3.0.2. We could cherry-pick just that one commit if that's the only thing that's blocking you with 4.18.20:48
sforsheeoh no that's far from the only thing20:48
stgrabersforshee, tyhicks: btw, looks like the fix from jjohansen in bug 1780227 works fine, do you know if this is already in the relevant branches for the next round of SRUs?20:48
ubot5bug 1780227 in linux (Ubuntu Bionic) "locking sockets broken due to missing AppArmor socket mediation patches" [Critical,Triaged] https://launchpad.net/bugs/178022720:48
jjohansenstgraber: it is not, in yet20:49
tyhicksstgraber: not your problem but it looks like something in snappy is broke on 4.18 so I can't install the snap: https://paste.ubuntu.com/p/87rksWFPKk/ :)20:50
tyhicksI can work around this in my test kernel build so no worries20:50
stgrabertyhicks: sounds apparmor related, do you see a denial?20:51
tyhicksthat's the first thing I looked for20:51
tyhickshmm, there are some odd denials earlier in the logs20:52
tyhicksaudit: type=1400 audit(1532983771.976:97): apparmor="DENIED" operation="ptrace" profile="/usr/lib/snapd/snap-confine" pid=1422 comm="snap-confine" requested_mask="read" denied_mask="read" peer="unconfined"20:52
tyhicksthat sounds like a familiar issue20:52
jdstrandit is20:54
jdstrandjj fixed an issue that was a trace into a read20:55
jdstrandsnapd isn't fixed yet20:55
jdstrandhttps://forum.snapcraft.io/t/custom-kernel-error-on-readlinkat-in-mount-namespace/6097/2120:56
tyhicksjdstrand: ack, thanks - don't escalate priorities for it on my behalf as I can work around it in order to get my testing done20:56
jdstrandtyhicks: you are on 4.18?20:56
tyhicksjdstrand: yes20:56
jdstrandyeah20:56
jdstrandthat is that20:56
tyhicksalright, good to know20:57
jdstrandtyhicks: it is pretty high on the list, but not all the way up20:58
jdstrandtyhicks: if it comes time when you think it should be escalated, ping me20:58
tyhicksjdstrand: as sforshee mentioned above, there are several other things blocking 4.18 landing in cosmic but it is coming soon20:59
tyhicksdropping a bare ptrace rule into /etc/apparmor.d/usr.lib.snapd.snap-confine.real is going to let me do what I need to do21:01
jdstrandtyhicks: so will 'ptrace read peer=unconfined,' :)21:04
jdstrandI'll do a quick PR for that, and do the interrogating later21:04

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