After reviewing previous communication again, I saw Andrew's message: "I can reproduce it. But none of the kernel debug tools helped me get any further. I think the next step is to explain the problem to Russell King and see if he has any ideas."
Andrew, do you think you could report this issue to Russell King and the kernel arm list. You're the most knowledgeable people on this thread. If you need any more details (e.g. about the networking issues) I'm sure some Debian users can provide more information. Thanks so much for all your help on Orion/Kirkwood kernel support! Martin * Martin Michlmayr <t...@cyrius.com> [2019-07-31 16:46]: > Andrew, > > As discussed previously (going back to 2017), there is an issue on > Kirkwood devices with 1 GB RAM. People see: > external abort on linefetch (0x814) > > You were able to reproduce this issue in the end and suggested > to set CONFIG_VMSPLIT_3G > > Two users confirmed that while this makes the original issue go away, > networking no longer works. > > Can you recommend where to go from there? What information do you > need or where should we report this issue? > > Thanks, > > Here are the two relevant links which report networking as broken > after setting CONFIG_VMSPLIT_3G: > > https://lists.debian.org/debian-arm/2018/06/msg00003.html > https://lists.debian.org/debian-arm/2019/04/msg00031.html > > > > * Martin Michlmayr <t...@cyrius.com> [2019-05-09 13:25]: > > I'm adding Andrew Lunn in hope this can be tracked down. This relates > > to Kirkwood machines with 1 GB of RAM. CONFIG_VMSPLIT_3G seems to > > lead to network problems. > > > > * Timo Jyrinki <timo.jyri...@gmail.com> [2019-04-26 14:29]: > > > ti 23. huhtik. 2019 klo 1.37 Matti Viljanen (matti.vilja...@kapsi.fi) > > > kirjoitti: > > > > I have a Fujitsu Q703 aka. QNap TS-221, with 1GB of RAM and 6282 variant > > > > chip inside, and I have hit this behavior. > > > ... > > > > it get an IP address but the LEDs blink normally - I think this is the > > > > same situation Timo had. I have used the recovery image QNap provided > > > > and re-flashed the kernel by flash-debian script (and manually cat-ing, > > > > too), but soon I should have my TTL serial adaptor ready. > > > > > > Thanks a lot for testing, and confirming something goes wrong with > > > CONFIG_VMSPLIT_3G. > > > > > > > I would like to help testing, if you have any ideas. What should I try > > > > next? > > > > > > Alas I'm out of my depth on the topic regarding what to try next if > > > wanting to use the whole 1GB of RAM. > > > > > > The workaround limiting RAM to 768MB works fine, and since no variant > > > seems to have over 1GB RAM, maybe it's acceptable tradeoff for most so > > > this hasn't seen more progress. The workaround in u-boot with the > > > adapter is described at > > > https://lists.debian.org/debian-arm/2018/06/msg00000.html , and after > > > setting that I've used my TS-221 for the past year. It can also be set > > > via fw_printenv and fw_setenv (not tested myself) as instructed at > > > http://karuppuswamy.com/wordpress/2012/04/16/u-boot-tools-for-debian-arm-linux-in-qnap-server/. > > > fw_printenv gives me the following on the last line: > > > bootargs=console=ttyS0,115200 root=/dev/ram initrd=0xa00000,0x900000 > > > ramdisk=34816 mem=768M > > > > > > -Timo > > > > -- > > Martin Michlmayr > > https://www.cyrius.com/ > > -- > Martin Michlmayr > https://www.cyrius.com/ -- Martin Michlmayr https://www.cyrius.com/
