System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
warpme_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 260 seconds]
warpme_ has quit [Ping timeout: 276 seconds]
warpme_ has joined #linux-rockchip
warpme_ has quit [Ping timeout: 252 seconds]
warpme_ has joined #linux-rockchip
warpme_ has quit [Ping timeout: 248 seconds]
warpme_ has joined #linux-rockchip
warpme_ has quit [Ping timeout: 252 seconds]
ldevulder has joined #linux-rockchip
warpme_ has joined #linux-rockchip
warpme_ has quit [Ping timeout: 272 seconds]
gnuiyl has quit [Ping timeout: 252 seconds]
ungeskriptet has quit [Ping timeout: 260 seconds]
ungeskriptet has joined #linux-rockchip
<detlevc>
CounterPillow: the decoder doesn't support 4:4:4 (well maybe just in black and white), so the 2 (a.k.a. or) is not possible. For point 1, I don't believe this is level 6 (1080p@50 shouldn't need that). I'm not ruling out a display side issue either
warpme has joined #linux-rockchip
warpme_ has joined #linux-rockchip
ungeskriptet has quit [Ping timeout: 245 seconds]
warpme_ has quit [Ping timeout: 260 seconds]
warpme_ has joined #linux-rockchip
warpme_ has quit [Ping timeout: 265 seconds]
erg_ has joined #linux-rockchip
franoosh has quit [Read error: Connection reset by peer]
erg_ has quit [Remote host closed the connection]
franoosh has joined #linux-rockchip
franoosh has quit [Remote host closed the connection]
ungeskriptet has joined #linux-rockchip
franoosh has joined #linux-rockchip
franoosh has quit [Remote host closed the connection]
dsimic has quit [Ping timeout: 252 seconds]
dsimic has joined #linux-rockchip
franoosh has joined #linux-rockchip
franoosh has quit [Remote host closed the connection]
franoosh has joined #linux-rockchip
warpme_ has joined #linux-rockchip
warpme_ has quit [Ping timeout: 244 seconds]
franoosh has quit [Remote host closed the connection]
warpme_ has joined #linux-rockchip
warpme_ has quit [Ping timeout: 252 seconds]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ungeskriptet has quit [Ping timeout: 260 seconds]
ungeskriptet has joined #linux-rockchip
ldevulder has quit [Ping timeout: 268 seconds]
warpme_ has joined #linux-rockchip
warpme_ has quit [Ping timeout: 248 seconds]
vagrantc has joined #linux-rockchip
ldevulder has joined #linux-rockchip
warpme_ has joined #linux-rockchip
warpme has joined #linux-rockchip
warpme_ has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
stikonas has joined #linux-rockchip
<CounterPillow>
diederik: this is somewhat worrying, extcon.c didn't change in a long time and the rockchip inno usb2 phy doesn't have any changes either. Possible we've always been broken and something uncovered the race condition now, needs investigating
ldevulder has quit [Ping timeout: 244 seconds]
<diederik>
yeah, and it's very difficult to reproduce. IIRC when I encountered it a previous time, I rebooted ~50 times ... and it didn't happen a single time
<diederik>
My hope is that 'surrounding code' has improved since then (and especially recently) so that it now happens more often ... which should be beneficial when it comes to fixing it. Or it really was a 'lucky streak'
<CounterPillow>
if I read the code right this may be caused if ida_alloc is broken which would be a huge problem
<CounterPillow>
hm, and it can't be that either because the only recent commit there doesn't touch that code path afaict
<CounterPillow>
ah, I see, it happened in 6.10 as well
<diederik>
Yep, so my guess is that it indeed was always 'broken'.
<CounterPillow>
I'm a bit confused by how the function that's supposed to get us a unique ID returns a non-unique ID. My current guess is that extcon is using two different IDA handles unintentionally. To debug this I'd have to devise some sort of torture test for extcon to see if I can ever reproduce the race.
<diederik>
I can't help with figuring out where/how the code is wrong, but I can collect information and/or try (debug) patches
warpme_ has joined #linux-rockchip
<diederik>
Can you reproduce the "Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after" warning? Because that one I get on almost every boot. If you know where that's coming from, it may be easier to track down where the real problem lies?
warpme has joined #linux-rockchip
warpme has quit [Client Quit]
warpme_ has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
warpme_ has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
warpme_ has quit [Ping timeout: 260 seconds]
cbeznea_ has quit [Ping timeout: 276 seconds]
cbeznea has quit [Ping timeout: 276 seconds]
cbeznea_ has joined #linux-rockchip
cbeznea has joined #linux-rockchip
warpme_ has joined #linux-rockchip
cbeznea_ has quit [Ping timeout: 248 seconds]
cbeznea has quit [Ping timeout: 248 seconds]
warpme_ has quit [Ping timeout: 245 seconds]
ungeskriptet has quit [Remote host closed the connection]
warpme_ has joined #linux-rockchip
warpme_ has quit [Ping timeout: 276 seconds]
warpme_ has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
warpme_ has quit [Ping timeout: 252 seconds]
warpme_ has joined #linux-rockchip
warpme_ has quit [Ping timeout: 252 seconds]
warpme_ has joined #linux-rockchip
warpme_ has quit [Ping timeout: 276 seconds]
stikonas has quit [Remote host closed the connection]