=== henrix_ is now known as henrix
[07:04] <Donkersgoed> hi all
[07:05] <Donkersgoed> I've got a kernel panic on a recent version of 3.8.0 on raring
[07:05] <Donkersgoed> can you help me report it
[07:05] <Donkersgoed> ?
[07:41] <ppisati> moin
[07:52] <Kaloz> apw: hey. did anyone reported shutdown issues since the upgrade of the -11 kernel?
[07:52] <Kaloz> apw: both the new -11 and -12 fails to power off my notebook
[12:09] <apw> Kaloz, nothing i have heard no
[12:10] <apw> Kaloz, can you confirm that booting back to a -10 with the same userspace does poweroff (it might be an upstrart change for instance)
=== ghostcube is now known as Guest46159
[12:49] <ppisati> and if you were wondering, yes, i'm fiddling with my network setup today...
[12:49] <ppisati> and so far the network is winning...
[13:24] <Kaloz> apw: will do later today
[14:08] <ogasawara> ChickenCutlass: heya, do you any sort of reproducer or test case (or bug report) to help us investigate the issues you're seeing with lowmemorykiller?
[14:08] <ogasawara> ChickenCutlass: or are you still trying to get a clear sense from you end of what's going on?
[14:09] <apw> ogasawara, didn't we turn off CONFIG_ANDROID for that just this last upload?
[14:09] <ChickenCutlass> ogasawara, still trying to see what is going on.  I think we have a regression from our old app manager to now mir
[14:09] <rtg> apw, in the distro kernel
[14:09] <apw> ahh
[14:10] <ogasawara> ChickenCutlass: ack, so maybe I'll wait to hear from you for a more defined scope of the problem before I turn my guys loose on it
[14:11] <ChickenCutlass> ogasawara, yes thanks
=== ghostcube_ is now known as ghostcube
[14:16] <infinity> rtg: Oh hey, Tim.  Can I get you to reupload that linux-exynos5 in the kernel ppa using the master orig instead of native?
[14:17] <rtg> infinity, no problem, gimme a bit. I forgot that it was based on a real upstream tarball.
[14:23] <rsalveti> ChicagoBud: ogasawara: yeah, for now I believe the issue is on the userspace side still
[14:25] <ogasawara> rsalveti: ack.  if you discover otherwise, please do let us know and we'll be sure to try and help.
[14:25] <rsalveti> sure, thanks
[15:46] <ppisati> jsalisbury: dude, saw your email, i'll give it a look
[15:46] <jsalisbury> ppisati, great, thanks!  I wasn't sure if you had one of those boards or not.
[15:47] <ppisati> jsalisbury: i've one, and i bet one beer it's the dtb that needs to be updated
[15:48] <ppisati> jsalisbury: and since it's part of the firmware on the board, we don't that automagically everytime we install a new kernel
[15:48] <ppisati> jsalisbury: but it has to be done manually
[15:48] <jsalisbury> ppisati, heh, only one beer
[15:48] <ppisati> jsalisbury: anyhow, i'll updathe the lp bug
[15:48] <jsalisbury> ppisati, thanks, Paolo
[15:48] <ppisati> jsalisbury: dude, it's still one beer... :)
[16:00] <infinity> rtg: Oh, that made it MUCH more auditable, their delta is quite small.  Thanks.
[16:00] <rtg> infinity, anything for you :)
[16:01] <rtg> infinity, maybe you can help me figure out why the network performance is so bad on one of these calxeda nodes.
[16:01] <infinity> rtg: Careful, you don't want to replace Andy as my favourite kernel dude.
[16:01] <infinity> rtg: Only on one node?
[16:02] <rtg> huh, no danger of that. apw is way smarter then me.
[16:02] <rtg> infinity, yep, only 1 of the 4 that I have access to is slow
[16:04] <infinity> rtg: On a different uplink?  Who configured the fabric, and how?
=== kentb-out is now known as kentb
[21:52]  * rtg -> EOW
=== kentb is now known as kentb-out