/srv/irclogs.ubuntu.com/2015/07/09/#ubuntu-kernel.txt

Odd_Blokebjf: Heads up: argyle is running in PS4 at the moment, and we've been asked to move it to PS4.5 by the end of the week.08:13
Laneydid aufs go away in our 4.0?09:29
Laneymy schroots broke :(09:29
Odd_Blokebjf: apw: Oh, it's not by the end of the week, it's by July 15 (next Wednesday).09:34
Odd_Blokebjf: apw: I've redeployed the service, and opened RT #82789 to open up the same firewall holes as we have for the PS4 deployment.09:35
infinityLaney: Erk, it sure did...09:35
infinityapw: Where'd aufs go?09:36
infinityLaney: You can s/aufs/overlay/ for now (or downgrade).09:36
Laneyinfinity: Ya, done that, thanks.09:38
apwinfinity, it was meant to be there, i am sure tim updated it10:32
infinityapw: I'm sure modinfo tells me I don't have it.12:29
infinityAlthought, CONFIG_AUFS_FS=m ...12:29
infinityWha?12:29
apwinfinity, yeah its disabled in the makefile, seems to build just fine, so i am proposing to do a non-abi bumper with it enabled12:52
infinityapw: If it works, that seems reasonable.12:53
bjfOdd_Bloke, so our "cloud provider" has asked us to move to a new cloud but it's up to us to do that? and i suppose any/all firewall exceptions are also up to us to tell them about?13:45
rbasakawe: do you mind posting your /var/log/apt/history.log somewhere from yesterday's grub2 incident? I'd like to see what exactly did what when your system originally broke to understand the issue better.13:49
awerbasak, in a mtg, and just about to join a standup; I'll ping you when I free up13:54
rbasakOK, thanks.13:54
Odd_Blokebjf: Something like that, yes.14:02
Odd_Blokebjf: But they have at least been fairly responsive; new rabbitmq is at 162.213.33.247 and the firewall holes should have been punched.14:03
Odd_Bloke(In their defense, all I had to do was say "copy the PS4 firewall rules", so hopefully they should all be correct)14:03
bjfOdd_Bloke, since we access it via ip addr, it will require code changes14:05
Odd_Blokebjf: Yeah. :(14:06
bjfOdd_Bloke, from what you are telling me. the new one is in place and i should be able to switch over right now if i wanted ... correct?14:07
Odd_Blokebjf: That's my understanding; but check first?14:08
bjfOdd_Bloke, ok ... i'll do a little checking and if it goes well, make the switch14:09
bjfapw, ^^^^ i'll do some testing to make sure the msgq service is working for the systems we want it 14:13
apwbjf, sounds good, as i will need to shock-and-awe on the dashboard14:16
awedid someone say my name?  ;)-14:18
apw:)14:18
apwinfinity, ok just enablnig aufs seems to work just fine, soooo ... i'll get that uploaded14:18
apwogasawara, seems we are missing aufs in the kernel we just did, so i am proposing to do a non-abi bumper for it14:19
awerbasak, http://pastebin.ubuntu.com/11848708/14:19
ogasawaraapw: ack14:19
infinityapw: Works for me.14:19
infinityapw: I can never decide from minute to minute if my schroots should be overlay, aufs, or lvm, but hey, it's nice to be spoiled for choice.14:20
infinityapw: (I still wish overlay could paper over the one or two things that make me keep turning to aufs...)14:20
rtgapw, the 4.0 Wily upload is missing AUFS ?14:21
infinityrtg: Yep.14:21
infinityrtg: It's in the config, but apparently disabled in the Makefile.14:21
infinity(oops)14:21
rtginfinity, oh, damn14:21
rtgsure is14:22
rtgbetter check the 4.1 branch14:22
rtglooks like that one is OK14:23
rbasakawe: thanks!14:23
infinityrtg: Misplaced your cowboy hat in between versions?14:23
awenp14:23
infinityrbasak: So, that totally has apt-get being the culprit, not update-manager.  We can stop panicking.14:24
infinityrbasak: As in, *someone* got impatient that grub wasn't upgrading and ran "apt-get install grub" and said "sure, remove everything" when it prompted.14:25
infinityIn fact, wait.  That's grub1, even.14:25
infinityawe: So, that was totally self-inflicted.14:25
infinityawe: Your manual installation of grub1 removed grub2, and you said "yes".14:26
rbasakinfinity: AIUI, awe had a problem after the update, and he tried to fix it by installing grub14:26
rbasakinfinity: but yes, the problem wasn't cause because the grub2 signed package got removed. Must have been caused by some other thing.14:26
infinityrbasak: Well, there are no removals until that point.14:26
rbasakRight14:26
aweinfinity, I only did the manual install of grub *after* my system stopped rebooting correctly14:27
aweand yes, it was a mistake14:27
awebut didn't really worsen or improve anything14:28
infinityawe: Check.  What are/were the symptoms of "not booting correctly"?14:28
apwrtg, yes, you ripped aufs out and switch the way it was updated for v4.114:29
aweI'm dual-booting a macair osx + utopic14:29
aweafter yesterday morning's update14:29
rtgapw, right, I'm using the upstream mechanism14:29
awemy machine no longer booted into rEFInd14:29
aweI got a "Your screwed screen"14:29
awe( ie. do you wanna re-install OS X from TimeMachine backup, fresh install, go online for help, or bring up disk tools )14:30
apwrtg, indeed, i mean that is why the disablement didn't get carried over, one was against ubuntu/Makefile, the other against fs/Makefile14:30
rtgapw, yup14:30
aweso now on restart, I need to do an Option+Pwr boot, and then select EFI boot14:30
awethe other options being the two OSX recovery partions14:30
infinityawe: Curious.  I don't know much of anything about rEFInd, but since rbasak's been trying to be helpful, I'll let him keep at it. :P14:31
* awe heads to yet another mtg14:31
awethanks infinity14:31
rbasakWell, I'm not sure any more :-/14:31
rbasakNot sure how much more helpful I can be. I was concerned yesterday that there might be a grub2-signed breakage problem, and so when awe's problem appeared, was concerned that it was that.14:32
rbasakBut it wasn't, so perhaps my concern isn't as big of an issue (that's the trouble with a sample size of 1). But that doesn't help at all with awe's actual problem, of which I have no idea.14:32
argesrodsmith: hey, awe had some issues with rEFInd. Maybe you can help?14:36
rodsmithHi. I'm told somebody has a rEFInd question. I'm the current maintainer. What's the question?14:36
rtgapw, there are significant changes to overlayfs in 4.2; perhaps you could add to your TODO list to forward port "UBUNTU: SAUCE: overlay: add backwards compatible overlayfs format support V3"14:36
apwrtg, ack14:36
rtgapw, in unstable master14:36
apwmaster or master-next ?14:36
awerodsmith, rbasak, I just joined a planning meeting; short version... I updated yesterday, and my macair no longer boots into rEFInd14:37
rtgapw, I think I'm gonna drop unstable master-next 'cause it really isn't very useful. what do you think ?14:37
awenow, I have to do an 'Option' + Pwr, and select "EFI Boot" every time14:37
awenot sure if I re-bless from OS X would fix this?14:37
aweThis is the first time an Ubuntu update has broken things for me14:37
rodsmithawe: Can you get into both OS X and Ubuntu via the Option key?14:37
aweI get to rEFInd via the option key, and have only booted Ubuntu from there since14:38
awehaven't checked OSX14:38
rodsmithawe: If you can get into OS X, try re-installing rEFInd.14:38
awewithout the option key14:38
aweI get a "Do you want to re-install or fix things" screen14:38
rodsmithawe: The Ubuntu update probably tried to install/re-install GRUB, which messed things up.14:38
aweright14:39
aweI'll try a re-install from OS X and see if that fixes things14:39
rodsmithawe: The "re-install or fix things" prompt sounds like APT didn't quite set everything up right.14:39
aweright14:39
awethanks14:39
rtgmanjo, smb: I see that dm-raid45 hasn't been updated since April 2009. We are carrying it as a SAUCE driver. Do you think it is still relevant ?15:19
manjortg, wow... I will need to look coz I am not sure who is using that 15:20
smbrtg, depedns on how many people use a non-Intel fakeraid in bios mode... 15:20
smbIntel MSM and DDS should be handled by mdadm nowadays15:21
smbrtg, Sure we will notice (after release) when you rip it out for now15:21
rtgsmb, well, I haven't ripped it out yet. I'm just reviewing SAUCE patches15:22
manjosmb, wasint there an issue where softraid was not write able ? 15:22
manjosmb, May be that issue with mdadm is already fixed 15:22
smbmanjo, at some point long time ago. but afaict Trusty works without dmraid15:23
manjortg, will that impact backport kernels for lts ? 15:23
rtgmanjo, yup15:24
manjough15:24
rtgmaybe it should wait until after 16.04 to be removed15:24
manjowhen does precise sunset? /me does the math15:24
manjo12.04 .. so 17.04? 15:25
rtgyup15:25
manjos**t 15:25
smbrtg, Might be that is what we said before T... But with a crisp memory like mine and we should have written it down... but then maybe we did and I just forgot where15:26
rtgsmb, its no big deal. so far maintenance has been easy, but I wanted to be sure the driver actually still worked15:27
TJ-rtg: If it's any help I can do some tests with a Promise controller; which kernel/ubuntu release would you want testing?15:29
smbrtg, I doubt I ever tested the other module ever again after mdadm worked for Intel... and none of my other hw would have fakeraid beyond levels 115:29
manjortg, also people using vmware stuff might still need that module on precise 15:29
rtgok, I'll defer removing the driver15:29
apwrtg, we if we are removing it in 16.04 we should disable it in the main build and re-enable it in the lts-backport15:47
rtgapw, I was thinking _after_ 16.0415:47
apwthen you might need to support it in the backports up to and including 18.04 in 16.04 even if it is disabled in those releases15:53
apwbecause it _is_ enabled in 16.0415:53
rtgapw, 16.04 is the last backport for 14.04. perhaps we should only enable dm-raid45 in the backport and not in 16.04 proper15:55
apwrtg, that was my suggestion indeed15:57
infinityrtg: I concur with apw (and you).  If you intend to drop drivers, do so in 16.04, but add them back to the lts-x kernel.16:09
rtginfinity, now I just gotta remember to do it16:09
infinityrtg: Though, you could also drop them in wily and add them back to the lts-w kernel too.16:09
infinityrtg: Which gives people some time to get used to the idea.16:09
rtgyup16:10
infinityrtg: Makes an argument for maintaining lts-w starting around, oh, now, though.  So you don't end up with 73 post-its detailing "stuff that needs to happen on top of the backport". :)16:11
rtgthats just too logical16:11
unixabgGreetings, does the 15.04 kernel have multi-layer overlayfs support? (multi-layer meaning more than 2)16:12
apwunixabg, that is a feature of later kernels, so wily may have it iwth the very latest kernels16:15
unixabgapw: humble appreciation for response.16:19
apwunixabg, i don't think 3.19 had it, but i am not 100% sure16:20
unixabgapw: would you know what version would have such support?16:21
unixabgI ask since I am wanting to test it some and I need partial .squashfs files for service packs.16:22
apwunixabg, looks like v4.0 was the first upstream release with it in16:23
apwso only wily very latest kernel would have it16:23
unixabgapw: thank you and I will work on testing with that then.16:28
unixabgapw: what is the shortest route to install and test the 4.x kernel?16:31
apwwell other than running wily, you could install that kernel from the archive by hand16:31
unixabgapw: thank you for the assistance I will download from http://cdimage.ubuntu.com/daily-live/current/17:12
dsdhi, i read that Ubuntu Wily might be based on Linux 4.1. is there a Ubuntu kernel git tree for that already?18:59
rtgdsd, ultimately Wily will release with 4.219:03
dsdi see19:06
dsdand have you started the process of moving the patches from 3.19 to a newer kernel like that?19:07
dsdor is that going to happen a bit later19:07
rtgdsd, All 4.1 work is happening here until 4.2 is released: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily master-next19:08
dsdthanks!19:11
unixabgapw: have you worked on casper? I ask since I see an apw there on a commit message.20:01
apwunixabg, only in a very peripheral way, but the last upload was in my name in trusty yes21:13
SturmFlutGood midnight! Anybody still awake?22:24

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