=== FourDollars_ is now known as FourDollars
=== rsalveti_ is now known as rsalveti
=== Ursinha__ is now known as Ursinha_
=== rsalveti_ is now known as rsalveti
=== psivaa-afk is now known as psivaa
=== davmor2_ is now known as davmor2
margainfinity, hey there. The installer is still not matching the latest kernel, I thought it was going to be updated soon... Is there an ETA on that?12:37
caribouapw: smb: I have just realised that /etc/default/grub.d/kexec-tools.cfg is the script responsible for setting up crashkernel= as a boot argument13:14
caribouapw: smb: any reason for that ? this is a requirement for kdump-tools, not kexec itself13:14
caribouthank god we are doing good QA on our flagship software13:26
apwcaribou, sounds like it is missplaced at best13:39
caribouapw: kdump-tools is not the only reverse depends of kexec-tools so that variable may be defined for things that have nothing to do with crashkernel13:40
caribou(petitboot & pxe-kexec)13:41
apwcaribou, i suppose... all it does is "make a hole in ram" so it could be used by other things for the same side-effect13:41
caribouapw: yes, it has minimal impact13:42
caribouapw: maybe it is worth moving it to kdump-tools package13:42
caribouapw: plus this is Ubuntu specific13:42
smbYeah, guess a misnomer from times when all was mushed together13:46
apwcaribou, presumably debian has to have handling for that cmdline thing as well tho ?13:47
apwwhere do they do it?13:47
caribouapw: nope, it is a manual addition to /etc/default/grub documented in the README13:47
apwcaribou, oh right, so we can move it to whever it makes most sense and then upstream it to debian :)13:48
caribouapw: there is on linux-crashdump metapackage on debian13:48
apwanyhow very likely we put it in kexec tools because it _is_ related to kexec tools ...13:49
apwso it might make sense there really, because you have kexec --crash or whatever to use it don't you13:49
caribouapw: true13:49
caribouapw: I was looking at LP: #131811113:50
ubot5Launchpad bug 1318111 in kexec-tools (Ubuntu) "Adds more and more copies of ‘crashkernel=384M-:128M’ in /etc/default/grub when upgrading or reinstalling grub-pc" [Medium,Confirmed] https://launchpad.net/bugs/131811113:50
smbapw, thats what I meant with mushed together...13:54
apwoh that is very broken, sigh13:55
xnoxcaribou, i think there is a fix for that in mdadm package where Laney fixed a "similar" bug.14:33
caribouxnox: mdadm ??? oh, maybe a more generic fix14:34
caribouxnox: that would explain why I can no longer reproduce it14:34
caribouI'll fetch the source14:34
xnoxcaribou, well, it's a bit tricky. grub.d hooks can readd things over and over and over again. there was a bug in the way mdadm was doing it.14:34
xnoxthere was a feedback loop and it depended on how many kernels one was generating the initramfs for....14:35
xnoxso try to have multiple kernels installed and have update-grub run across them all or some such.14:35
caribouxnox: yeah, that's what I'm testing atm14:36
caribouxnox: lp: #146556714:37
ubot5Launchpad bug 1465567 in mdadm (Ubuntu Vivid) "Kernel panic - not syncing: Too many boot init vars at `nomdmonddf'" [Undecided,Fix released] https://launchpad.net/bugs/146556714:37
smoser does that stack trace look important ?14:54
smoserroot fs got remounted read only  and i'm just going to reboot.14:54
smoserthe reason i ask if it looks important is that its quite possible that the underlying disk in this vmware system is foobarred.14:54
smoser(the provider has done that before, so if it smells like that I wont open a bug).14:55
xnox[700872.486476] sd 2:0:0:0: [sda] task abort on host 2, ffff88001e46900014:56
xnox[700882.773096] sd 2:0:0:0: [sda] Failed to get completion for aborted cmd ffff88001e46900014:56
xnoxhardware problem =)14:56
smoserxnox, thanks.15:03
=== Ursinha_ is now known as Ursinha
=== jdstrand_ is now known as jdstrand
=== sforshee` is now known as sforshee
=== ghostcube_ is now known as ghostcube
jderoseAny insight into why 4.2.0-19 wasn't released last week, if it will be released this week?19:21
apwwe do try and avoid releasing on friday so we acoid breaking people at the weekend20:07
jderoseapw: was the reason 4.2.0-19 wasn't released due to regressions found, or because of the holidays? just eager for 4.2.0-19 as it fixes as critical NVMe + suspend issue :)20:22
jderoseapw: BTW, this is the specific fix we're waiting for - http://kernel.ubuntu.com/git/ubuntu/ubuntu-wily.git/commit/?h=master-next&id=babbf7db6d39d809ae132394f1196463ef118ca021:21
jderosewithout it, suspend/resume is broken on UEFI systems with NVMe drives (and UEFI is, AFAIK, required to work with NVMe drives at all)21:22
stgrabersdeziel: bjf is looking for someone who can test fixes22:04
sdezielbjf: I'm ready to test when you are22:04
bjfsdeziel, thanks, jsalisbury ^22:05
bjfsdeziel, are we talking Trusty?22:05
sdezielbjf: yes, I can test both 3.13 and 3.16 on trusty22:06
bjfsdeziel, thanks22:06
bjfsdeziel, we've duplicated it here. i don't think we'll need you22:25
sdezielbjf: OK, I'm still available if you think I can help22:25
sdezielthanks for looking into this22:25
bjfsdeziel, we'll probably want you to test as soon as we've identified the bad commit but that might take a bit22:26
sdezielbjf: OK, no problem22:26
sdezielbjf: I didn't bisect it myself but looking at the changelog, "fib_rules: fix fib rule dumps across multiple skbs" seems like a potential culprit22:27
=== bladernr` is now known as bladernr

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