/srv/irclogs.ubuntu.com/2013/10/17/#ubuntu-kernel.txt

=== fmasi_afk is now known as fmasi
=== fmasi is now known as fmasi_afk
=== fmasi_afk is now known as fmasi
=== fmasi is now known as fmasi_afk
=== fmasi_afk is now known as fmasi
RoyalDogBiscuitsHeya. Mark has talked many times about "ultrasmooth" graphics. This is achieved with a low-jitter kernel. 11:51
RoyalDogBiscuitsPlease see:  http://ovekarlsen.com/Blog/turning-ubuntu-12-04-into-a-professional-low-jitter-os/11:51
RoyalDogBiscuitsI can answer any questions.11:51
RoyalDogBiscuitsLow-jitter reduces interrputs in the datastreams, giving continuous graphics and audio, that is optimal for a multimedia computer OS.12:19
RoyalDogBiscuitsFor instance Doom 3 which is a very jitter sensitive game, that Carmack not long ago stated was taxing even on modern computers, runs with accurate 72fps. 12:20
RoyalDogBiscuitsThis also on a core 2 duo, and GTX 280.12:20
RoyalDogBiscuitsDoom 3 does three passes pr Open GL frame.12:20
RoyalDogBiscuitsinterrupts :)12:21
ohsixwhy did you change your name?12:32
ohsixand only considering the kernel as a source of jitter is going to majorly miss all the real issues12:34
=== fmasi is now known as fmasi_afk
=== fmasi_afk is now known as fmasi
RoyalDogBiscuitsohsix: It is tried and tested, there is no other real issues.13:04
rtgapw, suppose we oughtta do a signed package for Saucy LTS ?13:14
* henrix -> lunch13:15
apwrtg, hmm, i suppose we might indeed13:18
rtgapw, are you still the expert there ?13:18
apwrtg, yeah i'll take the action indeed13:19
argessmb: hi13:23
smbarges, maybe... :)13:24
arges: ) 13:24
argessmb: bug 100708213:24
ubot2Launchpad bug 1007082 in linux (Ubuntu) "BUG: Bad page state in process node pfn:8e9d9" [Medium,Incomplete] https://launchpad.net/bugs/100708213:24
jpdsAnyone know how I can start to figure out why my laptop is a lot hotter on saucy?14:22
apwjpds, it is sitting on your lap ?14:39
jpdsapw: Partially, but the fan is spinning a lot more than what I'm use to.14:40
ckingmaybe install a raring kernel and see if that changes things14:40
apwjpds, shame you didn't upgrade 3m ago :(14:40
=== gfrog_ is now known as gfrog
brendandhow does dmesg get the timestamps used to mark entries?15:51
brendandis it possible to get that number at any point?15:51
brendandthis number '[ 9231.618344]'15:52
brendandwhich i guess is seconds after boot15:52
kamaltjaalton, hey, so regarding those in-raring-but-not-in-3.8-stable haswell commits . . .   I'd be happy to take the two from upstream in 3.8-stable, if you were to request that16:12
kamaltjaalton, that would be raring's e8c14411e539718 and 0009bd009e9ec8b16:12
tjaaltonkamal: yeah, do you need a formal request?16:14
kamaltjaalton, yes please... an email to me with cc: stable@vger.kernel.org .   The upstream commits to request are:16:15
kamalcommit 21ad833075801a7cd81b5ef1604ffc6c600e5ff9 upstream.16:15
kamalcommit 7b9f35a6dd72f89452c58bbdbaf063027bf857ec upstream.16:15
tjaaltonok, I'll cc the authors too so they can yell 'no!' if they want :)16:16
kamaltjaalton, sure sounds good (I'll also do that when I actually queue up the patches)16:16
tjaaltonnot that I think they should16:16
tjaaltoni'm working on backporting power well changes for haswell, it doesn't support hdmi/dp audio on 3.8 currently16:19
tjaaltonbut getting that in stable might be asking a bit too much, currently at five patches and it's not fully there yet16:20
kamaltjaalton, um . . .  does that relate to 2124b72e6283c4e84a55e71077fee91793f4c801 (which I'm about to queue for 3.8-stable, as requested by Shuduo Sang)16:20
tjaaltonkamal: yes, it needs the other four patches16:20
kamaltjaalton:  212b72e drm/i915: don't disable the power well yet16:20
tjaaltonor at least it applies cleanly after them16:21
tjaaltonbut it's not enough; after unplugging the cable, the hdmi/dp audio device is still listed on audio properties16:21
tjaaltonworks fine on 3.1116:22
tjaaltonand apparently on 3.9-rc516:22
kamaltjaalton, hmm.   I backported 212b72e to 3.8 with no fuss at all (didn't apply cleanly, but was an easy/obvious port).    I wasn't aware that it needed any other patches, but ...16:22
tjaaltonhuh, ok16:22
kamalsee my email (in kteam@) to Shuduo, asking whether it's really even relevant for 3.816:22
kamalSubject: Re: stable: 2124b72e6283c4e84a55e71077fee91793f4c801 need backport16:23
kamaltjaalton, . . . . so now I'm confused.16:23
tjaaltonwell, I thought 7f35610cc33cf7ee0797dc684ccc0057742dc12a is just as wanted16:23
tjaaltonbut, we'll see after some testing16:23
tjaaltonif the one patch is enough then that's good16:23
kamalI can't find 7f35610cc33cf7ee0797dc684ccc0057742dc12a  (which repo?)16:24
tjaaltonoops, mine :)16:25
tjaaltonhang on16:25
tjaaltonfa42e23c1055a4 is better16:25
tjaaltonso, the bisection showed the proposed patch fixing things, but of course i915 got 265 other commits to the driver since 3.8..16:26
kamaltjaalton, well, fwiw fa42e23c1055a4 applies cleanly to my 3.8 tree16:26
tjaaltonyeah it does16:27
kamaltjaalton, and I'd take it if requested (and assuming it actually compiles :-)16:28
tjaaltonthe other commits I'm testing with are cb10799c194369633b18, 6b25a88752e8e and d5f21e4072645d016:28
tjaaltonbut wth.. now I see that this branch doesn't have 2124b72e6283c, grr16:29
tjaaltonso I'll just rerun the tests, maybe things work after pulling it16:30
kamaltjaalton, ok, lmk what you want to do after you sort it all out.  fwiw, all three of those ^^ look fine to me also.16:31
tjaaltonok cool16:31
brendandcking, thanks for the answer on dmesg16:31
tjaaltonsince the primary target is the quantal i915_hsw driver they're probably fine there but would be silly not to have them on 3.8/raring too16:31
tjaaltonespecially since it's all haswell anyway16:32
kamaltjaalton, agreed, plus it makes my life easier for future i915 stable merges16:32
tjaaltonsure16:33
=== fmasi is now known as fmasi_afk

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