06:27 <sams> how do i lock the os to current kernel?

06:28 <sams> ive reinstalled like 5 times and every time after a kernel update it doesnt boot

06:35 <IgorPec> which board?

06:36 <Herc> armbian-config>System>Freeze

06:40 <sams> nm i got it with apt-mark

06:47 <IgorPec> sams which hw you are using?

06:47 <IgorPec> we want to prevent this

06:49 <sams> orange pi 4

06:49 <IgorPec> aha, that has some issues on some boards with kernel 5.15.y

06:56 <IgorPec> fixing the problem ...

07:04 <Herc> ah, thats a better plan ofc

07:28 <Armbian-Discord> <c​ats> Yeah, I honestly wish I came here when I was having sopine issues. Could've helped fix the updates way earlier lol

07:59 <Armbian-Discord> <I​gorPec> the only solution is proper auto testing

07:59 <Armbian-Discord> <I​gorPec> relying to upstream is mistake in way too big %

08:26 <Armbian-Discord> <c​ats> mhm

08:27 <Armbian-Discord> <c​ats> I almost wonder how that could be automated

08:27 <Armbian-Discord> <c​ats> Maybe a bunch of the boards with some kind of serial monitor on each?

08:27 <Armbian-Discord> <c​ats> On build, update each one, wait for a full boot, otherwise notify

08:30 <Smedles> hi all... installed the latest updates onto a RockPi 4B and now it won't boot :(

08:39 <Smedles> uggh and usb keyboard isn't working either :(

09:02 <IgorPec> cats: well autotesting is complicated, yes, serial console grabbing too

09:02 <Armbian-Discord> <c​ats> Yeah =\

09:02 <IgorPec> smedless: borked update was already removed, trying to find the clue

09:02 <Armbian-Discord> <c​ats> Like serial console grabbing isn't too bad

09:02 <Armbian-Discord> <c​ats> if you had the ability to use many usb to serial/uart adapters, wire each board up

09:03 <Armbian-Discord> <c​ats> But then you'd also have to run every single board

09:03 <IgorPec> i have build a test system to check upgrades

09:03 <Armbian-Discord> <c​ats> And hook it into a system that does serial console scanning to ensure it booted

09:03 <IgorPec> but still its impossible to check all scenarios

09:03 <Armbian-Discord> <c​ats> yeah

09:03 <Armbian-Discord> <c​ats> I think "did it boot? cool" and building a framework around that is good

09:03 <IgorPec> also serial consoles are only on a few

09:03 <Armbian-Discord> <c​ats> =\

09:04 <IgorPec> https://github.com/armbian/scripts/blob/master/.github/workflows/smoke-tests.yml

09:04 <ArmbianHelper> ^ scripts/smoke-tests.yml at master · armbian/scripts · GitHub

09:04 <IgorPec> nothing glorious - power on - upgrade test, performance test, log, power off

09:05 <IgorPec> on cca 50 devices

09:24 <Smedles> IgorPec: I fixed it - copied /boot from sd to /boot of the emmc

09:24 <Smedles> https://forum.armbian.com/topic/24198-latest-kernel-updates-caused-a-failed-boot/

09:24 <ArmbianHelper> ^ Latest kernel updates caused a failed boot - ROCK Pi 4 series - Armbian Community Forums

09:25 <Smedles> just means the rockpi at the holiday house will be down until I can get down there again to fix it :P

09:43 <Armbian-Discord> <I​gorPec> this update only caused troubles on some RK3399 boards, while no troubles on the other. In 99% of cases its enough we test on rk3399 board ...

09:44 <Smedles> great, now my aeotec zwave stick isn't being recognised

09:45 <Armbian-Discord> <I​gorPec> https://github.com/armbian/build/pull/4369

09:45 <ArmbianHelper> ^ Revert "Add an attempt counter, which helps buggy PCIe links. (#4308)" by igorpecovnik · Pull Request #4369 · armbian/build · GitHub

09:45 <Armbian-Discord> <I​gorPec> were you running custom kernel build before?

09:50 <Smedles> fixed aeotec stick - reinstalled older kernel from armbian-config

09:51 <Armbian-Discord> <I​gorPec> but those are two different incidents

15:23 <Armbian-Discord> <d​ave> @IgorPec are we really sure it's my patch...?

15:24 <Armbian-Discord> <d​ave> @Smedles: run lspci and lsusb for me please.

15:26 <Armbian-Discord> <I​gorPec> yes, work when removed. i also have troubles to epxlain

15:28 <Armbian-Discord> <d​ave> it's a compiler/ARM core bug

15:28 <CosmicDJ> which Armbian version will ship with https://github.com/armbian/build/commit/78a406d73fec1099b2e646711cb045f7e4332d0f ?

15:28 <ArmbianHelper> ^ Add rk3399's rng to kernel dts. · armbian/build@78a406d · GitHub

15:28 <Armbian-Discord> <d​ave> https://github.com/OP-TEE/optee_client/issues/99

15:28 <ArmbianHelper> ^ rpi3/benchmark: unsupported exclusive issue when executing LDXR (load-exclusive) · Issue #99 · OP-TEE/optee_client · GitHub

15:29 <Armbian-Discord> <d​ave> wait is that where it crashed though

15:29 <Armbian-Discord> <I​gorPec> yes, look like. dont' have much else as i am tight with time

15:30 <Armbian-Discord> <I​gorPec> i'll be back in 1h or so

15:30 <Armbian-Discord> <I​gorPec> can hook up serial then

15:31 <Armbian-Discord> <d​ave> try disabling CONFIG_KCMP and/or CONFIG_RSEQ.

15:32 <Armbian-Discord> <d​ave> eh I don't think that's it, never mind

18:30 <Armbian-Discord> <c​oder1337> hi, i clicked on Diagnostics of armbian-config because i wanted to make sure it's turned off. but then it wanted to upload something which i cancelled crtl+c). could this have caused any leak of sensitive personal data/logs of the device or what would usually be uploaded? there should always be a confirmation dialog if the user really wants to upload data to some place, this seems a bit too talkative. :x

19:28 <Armbian-Discord> <I​gorPec> this is armbian. we don't sent sensitive information anywhere

19:29 <Armbian-Discord> <I​gorPec> run: armbianmonitor -u in the command line

19:29 <Armbian-Discord> <I​gorPec> this is the script - in case you want to check - https://github.com/armbian/build/blob/master/packages/bsp/common/usr/bin/armbianmonitor

19:29 <ArmbianHelper> ^ build/armbianmonitor at master · armbian/build · GitHub