#v4l 2016-04-26,Tue

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***DaRock has quit IRC (Quit: DaRock) [00:18]
........... (idle for 50mn)
crazy_imp has quit IRC (Ping timeout: 276 seconds) [01:08]
_franck__ has quit IRC (Ping timeout: 250 seconds) [01:21]
..................................................................................................................................... (idle for 11h0mn)
pinchartlposciak: ping [12:21]
hverkuilhaven't been able to get hold of posciak for some time now :-( [12:25]
pinchartl:-/
I know that Pawel was still alive two weeks ago
hopefully that hasn't changed :-)
[12:26]
.... (idle for 19mn)
hverkuilneg: ping [12:47]
neg: mailed you instead [12:58]
neghverkuil: pong [13:03]
hverkuilneg: see email
isn't it time to continue the metadata discussion? Or am I off by an hour?
[13:03]
neghverkuil: thanks got it, I'm writing up the commit msg right now. Final test and the patch should be out within the hour. Thanks for ping :-) [13:06]
pinchartlhverkuil: it can be [13:15]
........... (idle for 52mn)
hverkuilHmm, no meeting at all? [14:07]
mchehabhverkuil, pinchartl: sorry, I won't be able to do it today [14:08]
pinchartlmchehab: ok
I'll be flying tomorrow so I won't be available
and visiting a customer on Thursday-Friday, so won't be available either
[14:08]
mchehabok. when you'll be available? [14:08]
pinchartland will take the week off (with e-mail access in the evening) next week
I'll come back on the 7th of May
(or possibly earlier if the weather is really bad)
[14:09]
hverkuilI'm traveling myself around that time and will be gone May 5-9. [14:10]
mchehabSo, May, 10 seems to be the first available date
I may need to travel on May, but the travel is not scheduled yet...
so, we may try to reserve the date, subject to changes
[14:12]
pinchartlI'll try to post a new patch series soon, we can discuss it over e-mail up to either an agreement or a lack of disagreement that would require IRC :-) [14:13]
mchehabOK
I'd suggest you to write a RFC with the approach you want to take before the actual patches, as this helps ;)
[14:13]
pinchartlwell, the patches are already written, there's only minor changes left, so I can as well post the code too
it helps understanding the RFC :-)
[14:15]
............................ (idle for 2h17mn)
***benjiG has left [16:32]
......... (idle for 44mn)
awalls1 has left [17:16]
.... (idle for 17mn)
koike_ is now known as koike [17:33]
..... (idle for 22mn)
shuahmchehab: okay I have a fix for you for the media_ioctl use-after-free problem with driver unbind case, tested it with 3 drivers (uvcvideo, em28xx, and au0828)
Changes are limited and should backport easily
[17:55]
mchehabgood [18:10]
..... (idle for 23mn)
shuahmchehab: there is a DEBUG_LOCKS_WARN_ON(chain_hlocks[chain->base + j] != id) error I am seeing when I remove em28xx usb device I have
This is on 4.6-rc5
This is a new check that went into 4.6-rc1 I think
[18:33]
mchehabinteresting. what does that mean? [18:35]
shuahpotential lock collision - I haven't looked into it to understand more than that :)
PU: 2 PID: 1853 at kernel/locking/lockdep.c:2098 __lock_acquire+0x2f15/0x5f30
[ 627.715866] DEBUG_LOCKS_WARN_ON(chain_hlocks[chain->base + j] != id)
http://pastebin.com/7eXpgDdG
[18:44]
mchehabwe had some false-positive lock warnings in the past
not sure if this is the case of this one
looking at the logs, it could be the case
[  628.057660]  class_idx:43 -> chain_key:000000000000002b (timekeeper_lock){-.-...}, at: [<ffffffff81290d62>] update_wall_time+0x72/0x910
[  628.066459]  class_idx:183 -> chain_key:00000000000000b7 (&dev->mutex){......}
I've no idea about that timekeeper locks
but we don't hold/release at em28xx
on a very quick view, it seems a false positive
[18:48]
.... (idle for 18mn)
shuahokay [19:10]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)