_whitelogger__ has quit [Ping timeout: 240 seconds]
_whitelogger___ has joined #linux-exynos
krzk has joined #linux-exynos
prahal__ has joined #linux-exynos
prahal__ has quit [Quit: prahal__]
prahal__ has joined #linux-exynos
dlan has quit [Ping timeout: 240 seconds]
Guest42384 has joined #linux-exynos
Guest42384 has quit [Ping timeout: 240 seconds]
dlan_ has joined #linux-exynos
krzk has quit [Quit: Wychodzi]
Wizzup has quit [Quit: reboot]
Wizzup has joined #linux-exynos
prahal__ has quit [Quit: prahal__]
prahal__ has joined #linux-exynos
Wizzup has quit [Remote host closed the connection]
Wizzup has joined #linux-exynos
meridion has quit [Remote host closed the connection]
meridion has joined #linux-exynos
liquidAcid has joined #linux-exynos
zombah has quit [Quit: Leaving]
<steev>
Wizzup: isn't it 773022 for gcc compile issues?
<Wizzup>
steev: not just for gcc issues
<Wizzup>
but also, yes
<Wizzup>
ah, I misread.
<Wizzup>
Yes, it is.
<steev>
hm
<Wizzup>
also for chromium
<steev>
both zero_chaos and i run into this weird issue with the xu, where if it's under heavy load, sometimes it doesn't wake up processors in ondemand cpufreq, and if you try echoing performance to cpufreq's settings... boom goes the dynamite
<steev>
the command itself actually freezes
<liquidAcid>
steev, try with CONFIG_DETECT_HUNG_TASK
<steev>
liquidAcid: have that... it doesn't really help?
<liquidAcid>
steev, have you decreased the timeout?
<liquidAcid>
usually 2min iirc
<steev>
10 seconds
<steev>
of course, part of the issue is, once that lockup of doing performance > scaling_governor, all commands stop responding
<liquidAcid>
ah, i thought only the echo then hangs with D
<Wizzup>
steev: stupid solution: set the default governor to performance
<steev>
Yeah that's what I did. The dmesg output at boot isn't particularly happy but meh