narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
vagrantc has quit [Ping timeout: 250 seconds]
sputnik_ has quit [Ping timeout: 244 seconds]
sputnik_ has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 245 seconds]
Darkmatter66 has joined #linux-amlogic
return0xe has joined #linux-amlogic
return0e has quit [Ping timeout: 252 seconds]
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
wens has quit [Ping timeout: 252 seconds]
wens has joined #linux-amlogic
<narmstrong> poulecaca: good work !
return0xe has quit [Remote host closed the connection]
return0xe has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 272 seconds]
Darkmatter66 has quit [Read error: Connection reset by peer]
Darkmatter66 has joined #linux-amlogic
Lyude has quit [Read error: Connection reset by peer]
Lyude has joined #linux-amlogic
vdehors has joined #linux-amlogic
<Lyude> n
<Lyude> oops
* ndufresne generally do that with :wq
AntonioND has joined #linux-amlogic
Darkmatter66_ has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 268 seconds]
vagrantc has joined #linux-amlogic
ldevulder_ has quit [Ping timeout: 252 seconds]
AntonioND has quit [Quit: Quit]
<Lyude> https://paste.fedoraproject.org/paste/KTntShsAD10QIkYkXaLWDA has anyone hit an issue like this, where the kernel consistently hangs on the khadas vim2 right after the hctosys message at the end of that log gets printed?