LiquidAcid has quit [Quit: Leaving]
Tenkawa has joined #linux-exynos
Tenkawa has joined #linux-exynos
krzk has joined #linux-exynos
Tenkawa has quit [Quit: leaving]
EmilMedve has joined #linux-exynos
amitk has joined #linux-exynos
pekka30 has joined #linux-exynos
EmilMedve has quit [Quit: Leaving.]
amitk has quit [Read error: Connection reset by peer]
amitk has joined #linux-exynos
amitk has quit [Ping timeout: 260 seconds]
amitk has joined #linux-exynos
zombah has joined #linux-exynos
gordan has joined #linux-exynos
EmilMedve has joined #linux-exynos
EmilMedve has quit [Quit: Leaving.]
afaerber has quit [Quit: Ex-Chat]
gordan has quit [Read error: Connection reset by peer]
gordan has joined #linux-exynos
gordan has quit [Ping timeout: 255 seconds]
dlezcano has quit [Ping timeout: 240 seconds]
dlezcano has joined #linux-exynos
LiquidAcid has joined #linux-exynos
Vasco_O is now known as Vasco
afaerber has joined #linux-exynos
gordan has joined #linux-exynos
<
LiquidAcid>
anyone familiar with mutex debugging?
<
LiquidAcid>
[ 2.319113] PC is at exynos_bus_probe+0x1b4/0x514
<
LiquidAcid>
[ 2.323800] LR is at __mutex_unlock_slowpath+0xb0/0x1a4
<
LiquidAcid>
hmm, adding more mutex debug options sadly doesn't reveal more
amitk has quit [Quit: leaving]
zombah has quit [Quit: Leaving]
gordan has quit [Quit: Konversation terminated!]
<
daniels>
LiquidAcid: ffffffdc and similar addresses means that you're passing in a NULL pointer somewhere you shouldn't be
<
daniels>
LiquidAcid: try adding printks through exynos_bus_probe to see where those are hitting
afaerber has quit [Quit: Ex-Chat]
zombah has joined #linux-exynos
pekka30 is now known as pekka_afk
afaerber has joined #linux-exynos
Vasco is now known as Vasco_O
LiquidAcid has quit [Quit: Leaving]
nashpa has quit [Ping timeout: 272 seconds]