[09:03] <SirDMZ> Ok, so i've built a new pbuilder and the kernel still FTBFS in that. http://pastebin.com/KAhXkKMF
[11:54] <karooga> Hi anyone familiar with vmebus?
[12:38] <zyga> hey, are the new 3.13-based kernels for precise and trusty being released via some fast track this time around?
[13:54] <zyga> bjf: hey
[13:54] <zyga> bjf: the man I wanted to talk to
[13:55] <bjf> zyga, what's up?
[14:13] <rtg> kamal, could you have a look at https://lists.ubuntu.com/archives/kernel-team/2014-July/046963.html ? it is affecting 3.13 stable.
[14:15] <kamal> rtg, ok, will do
[14:17] <rtg> kamal, it has regressed kirkland's orange box (if you need a tester)
[14:19] <kamal> rtg, ack.  looks like upstream has a fix in the works -- I'll see what we can do for 3.13-stable asap
[14:20] <rtg> kamal, I couldn't find the upstream patch in linux-next, so its still pretty green
[14:20] <kamal> rtg, yes
[15:03] <kirkland> kamal: rtg: yes, please I need that fix in trusty-updates ASAP, urgently
[15:03] <kirkland> kamal: rtg: I'm happy to test
[15:25] <rtg> apw, do you have patches for https://bugs.launchpad.net/bugs/1354397 ?
[15:26] <apw> rtg, ahh i am working on that one, slowly, as the list i have which is in another bug, fails to apply like at the first hurdle
[15:26] <rtg> apw, are they for Trusty or Utopic ?
[15:27] <apw> rtg, for trusty at least, i started on friday and flushed the context
[15:37] <rtg> smoser, do you have any reproducers for https://bugs.launchpad.net/bugs/1354459 ? Maybe we can get IBM to have a look.
[16:02] <smoser> rtg, it fails ~ 20% of time maybe
[16:02] <smoser> boot fails.
[16:02] <smoser> maybe only 10% .
[16:02] <rtg> smoser, just idling ?
[16:02] <smoser> well, boot is hardly idling
[16:03] <smoser> it doesnt make it up to the point where it is doing anything useful.
[16:03] <rtg> smyes, but otherwise
[16:03] <smoser> i think i've seen it fail both in d-i kernel and in iscsi remote root boot.
[16:04] <rtg> smoser, does it happen on more then one ? I think there are some OPAL version differences
[16:04] <smoser> i have onyl really tried doing install and such to one machine.
[16:04] <smoser> so my sample set is a bit small
[16:04] <rtg> infinity, ^^ have you seen any bare metal problems ?
[16:05] <rtg> smoser, we have a bunch of these machines, so I'm surprised the issue is not more widespread
[16:07] <infinity> rtg: No, but I don't do a lot of bare metal testing (yet).
[16:07] <rtg> infinity, ok, I thought we had.
[16:08] <infinity> rtg: We almost entirely run in VMs.  This needs to change, obviously.
[16:08] <infinity> rtg: And will change a bit as host LE KVM starts working, so we can run Ubuntu on Ubuntu.
[16:08] <rtg> infinity, do you anticipate installing more bare metal machines soon ?
[16:08] <rtg> when KVM starts working I assume
[16:09] <infinity> rtg: Over the coming weeks, perhaps.  It's not an urgency for me, yet, though it should be for the cert people pretty soon.
[16:09] <smoser> rtg, infinity it is important, its "supported" for maas.
[16:09] <infinity> rtg: But yes, once we have a working KVM solution, the plan would be to flatten all the machines we have and run Ubuntu on all of them.
[16:10] <smoser> and is not entirely un-useful either. u
[16:10] <smoser> it can be useful for lxc host.
[16:10] <smoser> to run ppc64el "bare metal".
[16:10] <infinity> smoser: Sure, it's useful for some usecases (whole machine use, or lxc), but neither of those is currently my use-case.
[16:10] <infinity> smoser: But my use-case should be getting fixed pretty soon.
[16:11] <smoser> infinity, you are not the only person ;)
[16:11] <infinity> smoser: I know I'm not, but Tim was asking if *I* do a lot of bare metal, and the answer is currently no.
[16:11] <infinity> smoser: Other people should definitely be testing it more.
[16:11] <infinity> smoser: And one of those people will soon be me.
[16:12] <rtg> smoser, have the cert folks started on bare metal yet ?
[16:12] <smoser> rtg, i believ they have started.
[16:58] <rtg> kamal, https://bugs.launchpad.net/bugs/1354469 looks like another 3.13 stable regression
[17:07] <apw> rtg, that is the driver update you did isn't it?
[17:08] <rtg> apw, a staging driver ? I don't remember that
[17:08] <rtg> lemme look again
[17:10] <rtg> apw,ah, it was ppisati
[17:10] <apw> nominally it was "us" at least
[17:19] <rtg> kamal, nm about bug #1354469. I found an upstream patch and have sent it to the k-team list.
[18:03] <kamal> rtg, but should I really never-mind?  that seems like a good candidate for 3.13-stable anyway, doesn't it?
[18:03] <rtg> kamal, I don't think those patches came in via stable, but I have not checked.
[18:04] <kamal> rtg, not tagged for stable, but sounds like maybe it should be
[18:04] <kamal> *have ben
[18:04] <kamal> *have been   (sigh)
[18:05] <rtg> kamal, IIRC the rtl8821ae patches were backports proposed by ppisati.
[18:06] <kamal> rtg, ok I'll take stock and bug him
[18:11] <rtg> kamal, just checked. there are no updates in your 3.13 stable for drivers/staging/rtl8821ae/rtl8821ae, so I'm sure this is not your problem.
[18:11] <kamal> rtg, excellent -- thanks!
[18:18] <retabell> just filled a bugreport
[18:18] <retabell> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355318
[20:07] <zartoosh__> HI using ubuntu 14.04 I get this error. BUG: Bad page map in process sshd  pte:01000000 pmd:23ed32067
[20:11] <apw> zartoosh__, that would be unexpected, you should file a bug against linux when it occurs
[20:13] <zartoosh__> apw, thanks for your reply, should I file that against linux kernel, or ubuntu kernel. Please advise? thx
[20:14] <apw> ubuntu kernel in the first instance, if it proves to be upstream we can move it up then
[20:14] <apw> zartoosh__, file the bug and report the number here, as that sounds like something needing investigating
[20:19] <zartoosh__> apw thank you will do, last question:  that what number ?
[20:19] <apw> the bug numbre
[20:28] <zartoosh__> apw thank you.
[21:03] <henrix> ~/quit