<narmstrong>
alyssa: weird stuff, what kernel do you use ?
<narmstrong>
we were reported some weird crashes on recent kernel on the odroid-n2(+), this may be related
chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #linux-amlogic
<armoon>
narmstrong FYI
<armoon>
[ 55.995436] VDDCPU_A: ramp_delay not set
<armoon>
[ 55.997568] VDDCPU_B: ramp_delay not set
<armoon>
[ 56.010274] VDDCPU_A: ramp_delay not set
<armoon>
[ 56.163843] VDDCPU_B: ramp_delay not set
<armoon>
[ 56.171660] VDDCPU_B: ramp_delay not set
<armoon>
[ 56.182001] VDDCPU_B: ramp_delay not set
<armoon>
[ 56.222698] VDDCPU_B: ramp_delay not set
<armoon>
[ 60.378878] VDDCPU_B: ramp_delay not set
<armoon>
[ 60.386728] VDDCPU_B: ramp_delay not set
<armoon>
[ 60.399708] VDDCPU_A: ramp_delay not set
camus has joined #linux-amlogic
<narmstrong>
Not sure this is related
<narmstrong>
If yes it’s a regression
<alyssa>
narmstrong: I built the kernel recently, maybe it broke then?
<alyssa>
drm-misc from a month ago
<alyssa>
5.11 i think
<alyssa>
Curiously, I can start x manually (`$ X`) and launch simple apps over ssh `DISPLAY=:0 glxgears` and that's fine. But then `DISPLAY=:0 i3` crashes the X server
KalAp has joined #linux-amlogic
camus has quit [Read error: Connection reset by peer]
KalAp has left #linux-amlogic [#linux-amlogic]
camus1 has joined #linux-amlogic
camus has joined #linux-amlogic
camus1 has quit [Ping timeout: 264 seconds]
armoon has quit [Quit: Client closed]
vagrantc has joined #linux-amlogic
chewitt_ is now known as chewitt
sputnik has joined #linux-amlogic
sputnik has quit [Remote host closed the connection]