02:20 <alyssa----> has anyone seen "rcu: INFO: rcu_sched self-detected stall on CPU" on rk3288 (veyron chromebook) with mainline?

02:22 <alyssa----> on other boots sporadically "cpu cpu0: _set_opp_voltage: failed to change cpu frequency", also some rk3x-i2c errors, isn't mainline fun?

02:25 <alyssa----> https://groups.google.com/forum/#!topic/linux.kernel/BluyNBQEA1c looks possibly relevant

02:29 <alyssa----> booting off USB (and an older USB), SD card seems a lot happier ... wondering if this is a race condition / timeout somewhere

02:31 <vagrantc> haven't booted one in a while...

02:32 <alyssa----> vagrantc: heh, me neither :)

02:32 <alyssa----> (before today)

02:34 <alyssa----> actually reproducable from the SD card too. should have version controlled by .config, ugh

02:40 <alyssa----> probably shouldn't be building the kernel on another veyron, but hey, cross compilers

04:33 <alyssa----> well, I guess I had my own good kernel. and now all my other compiles are failing. I don't even know what I changed in that rev, I forgot to backup .config ugh

09:27 <robmur01> alyssa----: if you're using a 5.5 or newer kernel plus sufficiently modern userspace you're probably seeing all manner of weirdness from time bouncing around randomly

09:27 <robmur01> try this - https://lore.kernel.org/linux-arm-kernel/20200409050508.96753-1-jaedon.shin@gmail.com/

09:28 <robmur01> not sure about I2C though - can't say I've seen that on my 3288 box

12:00 <Esmil> alyssa----: the kernel as actually one of the easiest pieces of software to cross compile. most distros come with aarch64-linux-gnu- and arm-linux-gnu- packages and then you just do make CROSS_COMPILE=aarch64-linux-gnu- all

12:01 <Esmil> (although if you want to compile the vdso for running 32bit userspace on a 64bit kernel you also need CROSS_COMPILE_COMPAT=arm-linux-gnu-

12:03 <Esmil> so make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- CROSS_COMPILE_COMPAT=arm-linux-gnu- all

13:28 <alyssa----> Esmil: you lost me somewhere around "CROSS_COMPILE=" ;)

13:31 <alyssa----> robmur01: worth a try

13:33 <mps> Esmil: I can confirm that is how I cross compiled kernels for long time on debian, i.e. ' make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- ....'

13:34 <mps> now I'm build them native on arm boxes

13:36 <alyssa----> I'm also grumpy whenever I amend my .config the whole kernel tries to rebuild. Setup ccache but still a major ;-;

13:36 <alyssa----> not unique to the kernel ofc. but there are a lot more dials to fiddle with there :)

13:48 <alyssa----> thanks :)

13:52 <alyssa----> robmur01: applied, but things are still not happy yet. down we go :)

14:46 <alyssa----> Hm, ok

14:46 <alyssa----> Did a pretty rough config with everything =y/=n to avoid the messy net of modules / initramfs / load from disk etc

14:47 <alyssa----> also enabled a bunch of rockchip related things that weren't in defconfig

14:47 <alyssa----> and it seems to work. minus wifi naturally ;-;

14:59 <alyssa----> missing regulatory.db, it's definitely there.. not my day for reading things off disk :)

15:47 <alyssa----> okay, pulled upstream files and am past that, now it's just ... not probing, I guess. Weeee

16:02 <alyssa----> I have to say, "linux user trying to get wifi working" is classic :)

16:34 <hanetzer> hey, anyone know offhand what the kernel parameter is to get serial output over one of the usb things ?

16:35 <hanetzer> specifically rk3288/rk3399, I remember its a thing, but forget the name.

16:36 <hanetzer> ah! rockchip.usb_uart