_whitelogger has joined #linux-exynos
mixfix41 has quit [Ping timeout: 246 seconds]
nighty- has joined #linux-exynos
_whitelogger has joined #linux-exynos
mszyprow has joined #linux-exynos
PabloPL has joined #linux-exynos
<memeka> mszyprow: Ping
<memeka> mszyprow: thermal thermal_zone0: failed to read out thermal zone (-22)
<memeka> For all thermal zones
<krzk> memeka: It might be known reason of too early probing
<krzk> We had such cases before, some were fixed
<memeka> is there a patch I can look at?
<krzk> memeka: for example ffe6e16f14faf5af6bae7293ebddb481a1d77ae6
<memeka> thanks i will try and check if i can fix ut
krzk has quit [Quit: leaving]
PabloPL has quit [Quit: PabloPL]
<mszyprow> memeka: pong
<mszyprow> memeka: if you mean the message during boot, then it is strange, but okay
<mszyprow> memeka: thermal core tries to read thermal zones before the driver gets registered fully
<memeka> mszyprow: yeah the messages during boot. ... i don't remember them during 4.18 (last i tried before 5.0)
<mszyprow> memeka: annoying, but harmless
<memeka> and they are not there in 4.14 either
<mszyprow> memeka: you can check in /sys that thermal zones are there and report correct values: cat /sys/class/thermal/thermal_zone*/temp
<memeka> mszyprow: they are there
<memeka> $ cat /sys/class/thermal/thermal_zone*/temp
<memeka> 56000
<memeka> 59000
<memeka> 54000
<memeka> 58000
<memeka> 54000
<mszyprow> memeka: those messages are there for quite a long time
<mszyprow> memeka: quick grep shows me that they are since v4.17-rc1
<mszyprow> memeka: Bartlomiej Zolnierkiewicz worked on fixing thermal core, but maintainers are not very responsive afair...
<memeka> right, they were not in 4.14 then :P
krzk has joined #linux-exynos
<memeka> krzk: how does that patch make sense?
<memeka> if (a || b) then ... else if (b) ...
<aalm> huh, that doesn't make sense
<mszyprow> memeka: broken merge commit :/
<memeka> :|
<mszyprow> memeka: see what commit 19785cf93b6c4252981894394f2dbd35c5e5d1ec did on exynos_tmu.c :/
<mszyprow> memeka: no idea how the maintainer did that mess
<memeka> crazy :)
<memeka> aalm: yes that makes sense :)
chewitt has quit [Quit: Adios!]
afaerber has quit [Quit: Leaving]
afaerber has joined #linux-exynos
afaerber has quit [Ping timeout: 250 seconds]
<krzk> I don't get why there was merge conflict at first place (no changes in the same time)...
<mszyprow> krzk: blame thermal maintainers for applying patches separately on -fixes and -next branches and not merging the first one to the latter later
PabloPL has joined #linux-exynos
PabloPL has quit [Remote host closed the connection]
PabloPL has joined #linux-exynos
<PabloPL> [<8014893c>] (do_raw_spin_lock) from [<8012d574>] (__queue_work+0x10c/0x304)
<PabloPL> [<8012d574>] (__queue_work) from [<8012d7a0>] (queue_work_on+0x34/0x40)
<PabloPL> [<8012d7a0>] (queue_work_on) from [<8016184c>] (call_timer_fn+0x24/0x94)
<PabloPL> [<8016184c>] (call_timer_fn) from [<80161944>] (expire_timers+0x88/0x94)
<PabloPL> [<80161944>] (expire_timers) from [<801626e8>] (run_timer_softirq+0xd0/0x1a4)
<PabloPL> [<801626e8>] (run_timer_softirq) from [<8010223c>] (__do_softirq+0xfc/0x2b8)
<PabloPL> [<8010223c>] (__do_softirq) from [<8011aa2c>] (irq_exit+0x10c/0x110)
<PabloPL> [<8011aa2c>] (irq_exit) from [<8014f2d0>] (__handle_domain_irq+0x58/0xa8)
<PabloPL> [<8014f2d0>] (__handle_domain_irq) from [<803933b0>] (vic_handle_irq+0x60/0xa0)
<PabloPL> [<803933b0>] (vic_handle_irq) from [<80101a0c>] (__irq_svc+0x6c/0xa8)
<PabloPL> Anyone have any idea what's going on ?
<PabloPL> Looking in kernel OOPS, it's in kernel/locking/spinlock_debug.c
<PabloPL> SPIN_BUG_ON(lock->magic != SPINLOCK_MAGIC, lock, "bad magic");
<PabloPL> Unable to handle kernel paging request at virtual address 13a03004
<PabloPL> I'm getting this after starting pvrsrvinit library (to try init sgx540 gpu) - binary is running fine, but getting this kernel oops
mszyprow has quit [Ping timeout: 250 seconds]
afaerber has joined #linux-exynos
nighty- has quit [Remote host closed the connection]
<krzk> PabloPL: looks like memory corruption
<krzk> could be caused by wrong memory accesses (buffer overflow, no range checking, use-after-free)
<PabloPL> and i'm getting it only after trying to use powervr
<PabloPL> there are two irq used there (one from gpu and one from vsync - also used by fimd)
<krzk> PabloPL: I don't see anything which could help to narrow the case... you can try to enable regular debug configs - maybe it will slightly help
<krzk> DEBUG_ATOMIC_SLEEP, SCHED_STACK_END_CHECK, DEBUG_LOCK_ALLOC, DEBUG_RT_MUTEXES,DEBUG_LIST, DEBUG_PAGEALLOC, SPARSE_RCU_POINTER, DEBUG_NOTIFIERS, DEBUG_MUTEXES, DEBUG_SPINLOCK
<krzk> and maybe some more - I did not refresh this list for some time
<PabloPL> krzk: ok, thanks. at first i'll try to check which irq is "problematic". last time i had similar problem ended with https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=5cf9a338db94cfd570aa2607bef1b30996f188e3
genii has joined #linux-exynos
<PabloPL> but it's good - there is always something to do ;)
Wizzup has quit [Ping timeout: 246 seconds]
Wizzup has joined #linux-exynos
PabloPL has quit [Remote host closed the connection]
Wizzup has quit [Ping timeout: 240 seconds]
Wizzup has joined #linux-exynos
PabloPL has joined #linux-exynos
PabloPL has quit [Remote host closed the connection]
PabloPL has joined #linux-exynos
mszyprow|home has joined #linux-exynos
sle85276 has joined #linux-exynos
PabloPL has quit [Remote host closed the connection]
afaerber has quit [Quit: Leaving]
PabloPL has joined #linux-exynos
PabloPL has quit [Remote host closed the connection]
afaerber has joined #linux-exynos
sle85276 has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
mszyprow|home has quit [Ping timeout: 246 seconds]
mszyprow|home has joined #linux-exynos
mszyprow|home has quit [Ping timeout: 246 seconds]
Wizzup has quit [Ping timeout: 240 seconds]
Wizzup has joined #linux-exynos