[08:29] <infinity> zequence: http://launchpad.net/bugs/1420562 <-- It's that time again.
[09:03] <zequence> infinity: Ah, time to bring out the git then.
[14:46] <Free99> Hey all, I think your experimental kernel is crashing on resume from sleep but at random
[14:47] <Free99> 3.19.0-rc7-generic on a 14.04 system
[17:09] <cyphermox> jsalisbury: apw: hey; I've updated bug 1359689; seems like it could be a drm bug in the kernel rather than an issue with plymouth -- if I use 3.19 rc1, things appear to work properly.
[17:13] <tjaalton> oh goodie, 3.19 doesn't take all my ram as disk cache like 3.18 did
[17:28] <jsalisbury> cyphermox, thanks for the update.  We may be able to do a "Reverse" bisect to find the commit that fixes this.
[17:32] <jsalisbury> cyphermox, ahh, I see you already found a commit that should help.  I'll build a test kernel with that commit and ask others affected to test.
[18:00] <hallyn> apw: hey.  not sure whether you have time to care... cpuset.cpus works fine in vivid.  but in the mainline kernel builds it does not
[18:00] <hallyn> upstream introduced cpuset.effective_cpus, whose calculation appears to be bogus
[18:01] <hallyn> so that when you set cpuset.cpus to 1 , it doesn't confine you to cpu 1, as evidenced among other ways by 'grep -i cpu /proc/self/status'
[18:02] <hallyn> (i can try taking it to lkml, but wasn't sure if this was something you'd be interested in)
[18:05] <cyphermox> jsalisbury: I mentioned the commit because I tried to build my own kernel with it, but there's more required than just that commit
[18:06] <cyphermox> looks like there may be other things from drm-next than landed along with it for the atomic thing
[18:07] <jsalisbury> cyphermox, ok, thanks.  I'll do some research.