kralo

I set up a third device, CM4, Kernel 5.19.1, reproducer does not take long. Can I do something to produce more meaningful debug traces? ``` A 23 11:30:45 rpidmareproducer[911]: now...

No, olokos. Spamming these issues with megabytes of logs won't get us anywhere. I am able to find stacktraces, and I can annotate the line numbers because I compile the...

I compiled the kernel with `CONFIG_CMA_DEBUG=y` and `CONFIG_CMA_DEBUGFS=y`. This led me to the bcm2835-unicam.c and I enabled more verbose debug output with ``` $ cat /etc/modprobe.d/unicam.conf # 3 is very...

I can reproduce the errors when checking with the guard patterns, this was an excellent idea. However, to anyone trying this I recommend checking for (memcmp () != 0) ```...

Thank you. I tried with ` libcamera-jpeg -n -v --mode 1280:800:8:U -o test3.jpg` , looks correct.

The triq.org viewer seems to be sensible to the filename and gets slow, so this is another try `capt_rtlsdr_f868.625M_s2400000_onesample_larger_wMbusT1.cu8` [2861_sample2.cu8.zip](https://github.com/merbanan/rtl_433/files/14474688/2861_sample2.cu8.zip)

This currently works very nicely, @barnex might you consider closing this? ``` # ls -l /etc/localtime lrwxrwxrwx 1 root root 25 12. Mär 00:15 /etc/localtime -> ../usr/share/zoneinfo/UTC # target/release/coreutils touch...

I could run successfully on my local machine and the test currently passes in CI. Is this worth keeping around?

I looked into this. Looks like the rust issue got solved (not returning `-1` anymore). You have an excellent reproducer. Note that my gnu stat output is a little different...

https://github.com/uutils/coreutils/issues/2688#issuecomment-955769210 the `test_cp::test_closes_file_descriptors ... ok` passes, and the initial report > > ``` > $ name="0123456789ABCDEF" > $ name="${name}${name}${name}${name}" > $ name="${name}${name}${name}${name}" > $ name="${name:0:255}" > $ mkdir deep &&...