Search the Community

Showing results for tags 'mainline'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues / peer to peer technical support
    • Reviews, Tutorials, Hardware hacks
    • Help wanted
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker - supported boards and images only
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner A64, H5, H6 and H616
    • Armada A388, A3700
    • Amlogic S905(x), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Development
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android fanboys's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues
  • Kobol Forum's Helios4
  • Kobol Forum's Helios64

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Location


Interests

  1. Hello Folks, Good day. I hope you're doing great. I'm trying to make the OrangePI 10.1 inch MIPI DSI (product page) work on the most recent (mainline) Armbian build. Building the image using the OrangePI source repositories and following the instructions on OPi4B manual enables the LCD and touch, However, my intention is to make the LCD + Touch work on the most recent Armbian Focal (mainline). I've setup my Armbian build env but I cannot see to find how to enable this MIPI screen on any build options. Here's the instructions from Page #20 of OPi 4B manual: Download the Linux source code and make the following changes in dts --- a/arch/arm64/boot/dts/rockchip/rk3399-orangepi-lcd.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3399-orangepi-lcd.dtsi @@ -40,12 +40,12 @@ max-x = <800>; max-y = <1280>; tp-size = <101>; // <911> for 8 inch // <101> for 10 inch - status = "disable"; + status = "okay"; }; }; &dsi { - status = "disable"; + status = "okay"; panel@1 { compatible = "simple-panel-dsi"; reg = <0>; That specific file doesn't exist on the Armbian build directory tree. I'm not familiar enough with the dts and dtsi files to be integrating it. I've been searching the forum for answers but, so far, I'm not able to make it work. I'm looking for help on enable it and appreciate any pointers or guidance that can help make the LCD + Touch work on a mainline kernel version. I linked some dts files from the OrangePI source repository that "might" help. I'm thankful for any help. Thank you.
  2. I logged an issue a little while ago with Armbian running on the Tinkerboard that the screen when rotated 90 degrees couldn't draw the screen at any speed. I have been playing with a few alternatives incl going back to the original tinkeros. All have issues so I was delighted to see the FOCAL port. I am using the recommended Waveshare 7" touchscreen that you advertise on the home page as tested 3rd party hardware. Both the desktop and the server versions of Focal come up with the error Configure crtc 0 failed setting mode when I manually set the supported resolution of 1024 x 600 at 60Hz using xrandr Exactly the same settings on TinkerOS works perfectly., but has many other issues! In the /var/log/Xorg.0.log file there is an message Allocate new frame buffer 1024 x 600 stride failed to set mode : Invalid argument. I used cvt to generate the modeline using settings 1024 600 60 then I used xrandr --newmode and added the modeline xrandr --addmode HDMI-1 1024x600_60.00 When I set the output to use this setting xrandr --output HDMI-1 --mode "1024x600_60.00" I get the error crtc 0 failed. As mentioned this works on TinkerOS and is the device that is included in the tested 3rd party hardware. What I am doing wrong? Thanks in advance.
  3. Enable in armbian-config USB and this no detect USB OTG and additional USB host on the board no working any usb device (microphone, usb storage, keyboard, etc.) that connects detects it Any help you can give me
  4. Hello people, I use a Tinker Board as a low power desktop computer for browsing, office documents and general tinkering, and after all this time it got personalized enough to worry about loosing all this setup and it is a hassle to just overwrite everything every time a new image comes around. Was wondering if it is possible to use apt dist-upgrade as means to get from Bionic Desktop 5.4 to Focal Desktop 5.4 as can be done on x86 platforms without breaking everything?
  5. Device: Orange Pi +2e. Environment one 16GB SD Card and 16GB eMMC onboard. Output from Armbianmonitor attached. The eMMC device onboard is always detected as mmcblk2. Irrespective of whether SD Card is present or not or if you boot from SD Card or eMMC. This is observed only on 20.05 and 20.08 builds. It does not happen on 20.02 build. [ 3.769548] sun8i-h3-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pc not found, using dummy regulator [ 3.781702] mmc0: host does not support reading read-only switch, assuming write-enable [ 3.784384] mmc0: new high speed SDHC card at address aaaa [ 3.785778] mmcblk0: mmc0:aaaa JULIE 14.8 GiB [ 3.790317] mmcblk0: p1 [ 3.790822] mmc1: new high speed SDIO card at address 0001 [ 3.795670] sunxi-mmc 1c11000.mmc: initialized, max. request size: 16384 KB [ 3.915829] mmc2: new DDR MMC card at address 0001 [ 3.917341] mmcblk2: mmc2:0001 AJTD4R 14.6 GiB [ 3.918284] mmcblk2boot0: mmc2:0001 AJTD4R partition 1 4.00 MiB [ 3.919325] mmcblk2boot1: mmc2:0001 AJTD4R partition 2 4.00 MiB [ 3.922791] mmcblk2: p1 [ 4.143718] usb 6-1: new full-speed USB device number 2 using ohci-platform --Rajesh
  6. This topic has been discussed earlier but there is not concrete mechanism explained to achieve this. Ideally I would like to display a boot logo or boot splash during startup. The device is Orange Pi Plus 2e. As per experience and as mentioned on this forum earlier plymouth was not useful in this case. I tried to set logo="enabled" in /boot/armbianEnv.txt but this doesn't help. When Armbian loads for first time on the device from the image downloaded from this site, it displays 'Initializing Boot Loader' logo image. Pretty cool!!! Can we have something like this for a custom image displayed each time on reboot. I understand that this will be displayed only till kernel loads, but that is good enough of me. I can settle with this limited functionality, but am lost on how to do this. Any pointers or suggestion will be highly appreciated. Stay safe! Regards -R
  7. Hi, I'm here again, the quarantine is almost over (sadly 'cause here in italy we are a bunch of a****le) and I finally get rid of my kodi 17 on retrorangepi 4.2 (old) that give me a lot of problems (with wifi connection lost, scraper that didn't update, and freeze, not for sure a problem with retrorangepi itself). so... I have something in my mind now that I'm back to home with my new FTTH internet connection. I want to setup an armbian image with or withot desktop for octoprint Armbian with 5.4 kernel (xfce debian) is really slow and temperature (with heatsink) don't go under 60°C on idle, with retrorangepi based on Debian Jessie, temps go from 45°C to 50°C on idle. So maybe - MAYBE - the problem could be the kernel? If so, because I don't care about security in this particular case (I need OPI just to execute octoprint on local), Could downgrade kernel (by using a legacy version) bring to an improvement on performance/temp? and give me the possibility to install package like octoprint or deluge? or some dependancy are linked to the kernel version? I know that maybe it will be a stupid question, but I'm wasting a lot of time with this board, because I'm so stubborn (and broke). thank you
  8. I am using a orangepi win plus. I have attached a ssd1306 OLED display to the board, using i2c1 interface, using the luma.oled library as driver. import sys from PIL import Image from PIL import ImageDraw from PIL import ImageFont import subprocess from luma.core.interface.serial import i2c from luma.core.render import canvas from luma.oled.device import ssd1306, ssd1325, ssd1331, sh1106 from time import sleep serial = i2c(port=1, address=0x3C) device = ssd1306(serial, rotate=0) width=device.width height=device.height image = Image.new('1', (device.width, device.height)) # Get drawing object to draw on image. draw = ImageDraw.Draw(image) # Draw a black filled box to clear the image. draw.rectangle((0,0,device.width,device.height), outline=0, fill=0) padding = 2 top = padding bottom = device.height-padding # Move left to right keeping track of the current x position for drawing shapes. x = 0 while True: # Draw a black filled box to clear the image. draw.rectangle((0,0,width,height), outline=0, fill=0) # Shell scripts for system monitoring from here : https://unix.stackexchange.com/questions/119126/command-to-displa$ cmd = "hostname -I | cut -d\' \' -f1" IP = subprocess.check_output(cmd, shell = True ) cmd = "top -bn1 | grep load | awk '{printf \"CPU Load: %.2f\", $(NF-2)}'" CPU = subprocess.check_output(cmd, shell = True ) cmd = "free -m | awk 'NR==2{printf \"Mem: %s/%sMB %.2f%%\", $3,$2,$3*100/$2 }'" MemUsage = subprocess.check_output(cmd, shell = True ) cmd = "df -h | awk '$NF==\"/\"{printf \"Disk: %d/%dGB %s\", $3,$2,$5}'" Disk = subprocess.check_output(cmd, shell = True ) # Write two lines of text. draw.text((x, top),"IP:"+str(IP,encoding = "utf-8"), font=font, fill=255) draw.text((x, top+8),str(CPU,encoding = "utf-8"), font=font, fill=255) draw.text((x, top+16),str(MemUsage,encoding = "utf-8"), font=font, fill=255) draw.text((x, top+25),str(Disk,encoding = "utf-8"), font=font, fill=255) device.display(image) sleep(0.5) At the kernel version 5.3.9, the display worked perfectly, without any problem. But after updating the kernel version to above 5.4.20, the same code don't work at all. Traceback (most recent call last): File "./test_oled.py", line 12, in <module> device = ssd1306(serial, rotate=0) File "/usr/local/lib/python3.6/dist-packages/luma/oled/device/__init__.py", line 188, in __init__ self.clear() File "/usr/local/lib/python3.6/dist-packages/luma/core/mixin.py", line 46, in clear self.display(Image.new(self.mode, self.size)) File "/usr/local/lib/python3.6/dist-packages/luma/oled/device/__init__.py", line 220, in display self.data(list(buf)) File "/usr/local/lib/python3.6/dist-packages/luma/core/device.py", line 46, in data self._serial_interface.data(data) File "/usr/local/lib/python3.6/dist-packages/luma/core/interface/serial.py", line 119, in data write(list(data[i:i + block_size])) File "/usr/local/lib/python3.6/dist-packages/luma/core/interface/serial.py", line 128, in _write_large_block self._bus.i2c_rdwr(self._i2c_msg_write(self._addr, [self._data_mode] + data)) File "/usr/local/lib/python3.6/dist-packages/smbus2/smbus2.py", line 637, in i2c_rdwr ioctl(self.fd, I2C_RDWR, ioctl_data) TimeoutError: [Errno 110] Connection timed out Because the luma.oled library just uses the linux kernel i2c interface like the /dev/i2c-1, so it is more likely a bug related to kernel.
  9. If anyone has troubles with HDMI when using 5.x kernels, and has enough skills to recompile an armbian, give this a try : https://github.com/Miouyouyou/build And then either answer here, or in the bug report : https://github.com/armbian/build/pull/1887
  10. Hello, Wish a good health everyone nowadays! I'm using Orange Pi PC Plus with small aluminium heatsink running Armbian Buster (mainline kernel 5.4.y). SD Card is Samsung EVO Plus 32gb. The CPU governor was set to 480 to 1200, conservative. The system are fresh, just after install. After ~5 minutes of idle uptime temperature comes to 85 and up. Is that heatsink are not good enough? And the second issue I've faced - too quiet sound output from AV-out. The most quiet is Chromium, it is nasty quiet. Sound from local video files in mpv player are bit(2 times) louder both from mp4 and webm, also mp3. Have not tested HDMI(because my display have only DVI). And when I tested it again before posting, Bluetooth A2DP audio stopped working with my phone. The sound from phone over BT was bit louder, than from Chromium, same as in mpv player. Thanks, Paul
  11. Hello people, I have an Asus Tinker Board S and decided to use the Mainline Armbian for this board, love the new panfrost driver but seems it is glitching all over the place, icons in the menu disappear and reappear when mouse hovers over them, tick boxes do not show if they are ticked and only flicker when mouse is over them and applications menu keep redrawing all over when trying to use among the most prominent problems. Other operating systems work well in this matter. Anyone else is having these problems with the mainline 5.4.28 kernel build?
  12. I am changing the file/folder permission using chown but is it not permanent chown proxy:proxy a.log ls -l total 0 -rw-r--r-- 1 proxy proxy 0 Apr 10 07:30 a.log Now after some time that include reboot ls -l total 0 -rw-r--r-- 1 root root 0 Apr 10 07:30 a.log I am using armbian on orange pi zero plus uname -r 5.4.14-sunxi64
  13. Hello guys. After a long time unsuccesfully trying to use a NanoPi Neo to record I2S data, I wonder if is there some NanoPi board that is capable of such thing. Can you suggest one? Thank you very much!
  14. Has anybody seen this message at boot: [ 5.352826] CPU4: failed to come online [ 5.352835] CPU4: failed in unknown state : 0x0 [ 10.481328] CPU5: failed to come online [ 10.481336] CPU5: failed in unknown state : 0x0 Then, the A72 cores don't show up (unsurprisingly since these are the two cores that somehow did not come online). On top of that, the kernel throws a backtrace (related to sound if I understand correctly): ------------[ cut here ]------------ [ 13.014782] WARNING: CPU: 3 PID: 1 at kernel/irq/manage.c:1990 request_threaded_irq+0x144/0x180 [ 13.014784] Modules linked in: [ 13.014793] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.4.26-rockchip64 #20.02.5 [ 13.014795] Hardware name: Pine64 RockPro64 (DT) [ 13.014799] pstate: a0000005 (NzCv daif -PAN -UAO) [ 13.014804] pc : request_threaded_irq+0x144/0x180 [ 13.014808] lr : request_threaded_irq+0x6c/0x180 [ 13.014810] sp : ffff80001004b9b0 [ 13.014813] x29: ffff80001004b9b0 x28: 0000000000000000 [ 13.014817] x27: ffff0000ef78c0c0 x26: ffff8000111c8d98 [ 13.014822] x25: 0000000000000000 x24: 0000000000000007 [ 13.014826] x23: ffff0000f0914870 x22: ffff800010b2dce0 [ 13.014830] x21: ffff0000f142a000 x20: 0000000000000000 [ 13.014834] x19: ffff80001141bee0 x18: 0000000000000001 [ 13.014838] x17: ffff800011188d00 x16: ffff800011188d08 [ 13.014843] x15: ffffffffffffffff x14: ffff80001137b508 [ 13.014847] x13: ffff00016f1e14b7 x12: ffff0000ef1e14c3 [ 13.014851] x11: ffff0000f67ac268 x10: 0000000000000040 [ 13.014855] x9 : ffff80001139f028 x8 : ffff80001139f020 [ 13.014859] x7 : ffff0000f10002a8 x6 : 0000000000000000 [ 13.014863] x5 : ffff0000f1000248 x4 : 0000000000000000 [ 13.014867] x3 : 0000000000000000 x2 : 0000000000000000 [ 13.014871] x1 : 0000000000000007 x0 : 0000000000031600 [ 13.014875] Call trace: [ 13.014880] request_threaded_irq+0x144/0x180 [ 13.014887] snd_mtpav_probe+0x15c/0x3d8 [ 13.014893] platform_drv_probe+0x50/0xa0 [ 13.014899] really_probe+0xd8/0x300 [ 13.014902] driver_probe_device+0x54/0xe8 [ 13.014906] __device_attach_driver+0x80/0xb8 [ 13.014910] bus_for_each_drv+0x78/0xc8 [ 13.014915] __device_attach+0xd4/0x130 [ 13.014918] device_initial_probe+0x10/0x18 [ 13.014922] bus_probe_device+0x90/0x98 [ 13.014927] device_add+0x3c4/0x5f0 [ 13.014930] platform_device_add+0x10c/0x230 [ 13.014934] platform_device_register_full+0xc8/0x140 [ 13.014940] alsa_card_mtpav_init+0x74/0xd0 [ 13.014945] do_one_initcall+0x74/0x1b0 [ 13.014950] kernel_init_freeable+0x194/0x22c [ 13.014957] kernel_init+0x10/0xfc [ 13.014961] ret_from_fork+0x10/0x18 [ 13.014969] ---[ end trace 34ce35f0c45c0a90 ]--- Mathias
  15. Hello, I have two Banana Pi Pro boards with current Armbian 20.02.1_Bananapipro_buster_current_5.4.20_minimal, kernel 5.4.20-sunxi and both have small SSD connected (WD 120GB and Goodram 120GB). fdisk -l doesn't show any drive's except sdcard (and ram drives). Is there any way I can get it working?
  16. Hi, can anyone let me know if we can enable a UART port from a DTB file? Means like compile DTB to DTS, make changes and then again recompile it to a DTB like we do in the script.bin file of legacy kernel. Earlier I have used to mention "overlays=uart1 uart2" in the armbianEnv.txt file but, this didn't work for me .
  17. Hi everyone, I have a problem when work on OPi zero wifi which is running Armbian linux sunxi 4.19.62. I used nmtui to configure wifi connection with static ip. It works fine even rebooting or re-powering up however I tried to power off the router and the result is it has never reconnected again. Next, I plugged in the ethernet cable into RJ45 port, the connection is established. I use sudo ifconfig to show the information, I saw that both the wifi (static) and ethernet are correctly then I can access via ssh or scanning the ip. One again, I continued plugging out the ethernet cable, all connections were disappeared even wifi and connection via ssh is failed. Is there anyone face on this issue? Giving me some help, please.
  18. Hi! Now that the camera interface has been merged in mainline Kernel, I would like to try to use the OrangePi OV5640 camera module on my OrangePi One. So with the latest Armbian Bionic (20.02.1, kernel 5.4.20), I have been trying to get a device tree overlay. But for now, it fails to compile with: $ sudo armbian-add-overlay sun8i-h3-csi.dts Compiling the overlay Error: sun8i-h3-csi.dts:27.23-24 syntax error FATAL ERROR: Unable to parse input tree Error compiling the overlay My current overlay looks like this: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { csi_mclk_pin: csi-mclk-pin { pins = "PE1"; function = "csi"; }; }; }; fragment@1 { target = <&i2c2>; __overlay__ { status = "okay"; ov5640: camera@3c { compatible = "ovti,ov5640"; reg = <0x3c>; pinctrl-names = "default"; pinctrl-0 = <&csi_mclk_pin>; clocks = <&ccu CLK_CSI_MCLK>; clock-names = "xclk"; AVDD-supply = <&reg_aldo1>; DOVDD-supply = <&reg_dldo3>; DVDD-supply = <&reg_eldo3>; reset-gpios = <&pio 4 14 GPIO_ACTIVE_LOW>; /* CSI-RST-R: PE14 */ powerdown-gpios = <&pio 4 15 GPIO_ACTIVE_HIGH>; /* CSI-STBY-R: PE15 */ port { ov5640_ep: endpoint { remote-endpoint = <&csi_ep>; bus-width = <8>; data-shift = <2>; /* lines 9:2 are used */ hsync-active = <1>; /* Active high */ vsync-active = <0>; /* Active low */ data-active = <1>; /* Active high */ pclk-sample = <1>; /* Rising */ }; }; }; }; }; fragment@2 { target = <&csi>; __overlay__ { status = "okay"; port { csi_ep: endpoint { remote-endpoint = <&ov5640_ep>; bus-width = <8>; hsync-active = <1>; /* Active high */ vsync-active = <0>; /* Active low */ data-active = <1>; /* Active high */ pclk-sample = <1>; /* Rising */ }; }; }; }; }; So the line 27, which seem to trigger the error is: `clocks = <&ccu CLK_CSI_MCLK>;` Also, according to the documentation, the regulator fields are required but this board does not have much regulators (like AXP209), so I have no idea what to write here. But this is my first time writing a device-tree overlay so I am not sure what is wrong with this line. Could someone guide me to get my overlay right? And, does anyone already got the CSI interface working with OV5460 sensor on a H3 based board? Thank you.
  19. I want to drive 2 SPI devices on my orangepi zero. I enabled `spi-spidev` and `spi-add-cs1` overlays and set `param_spidev_spi_bus` to 1. But by I still get only `/dev/spi1.0` available. When I add `param_spidev_spi_cs=1`, I get `/dev/spi1.1` but `/dev/spi1.0` disappears. Do I see it correctly that I can choose *either* `/dev/spi1.0` *or* `/dev/spi1.1` but not both with that overlay? How can I activate both cs pins? There are a bunch of example custom files out there, but none are meant specifically for the setup where I need spi1 (instead of spi0) and need to use a GPIO pin for cs1. And I can't really find any docs on how to write my own overlay. So any help is appreciated.
  20. Using Armbian_20.02.1 with 5.4 kernel on NEO2 board, I'm running into an issue trying to get the USB OTG working with the g_ether module. When I run modprobe g_ether I see the following in dmesg: [ 490.490582] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I've also tried compiling my own img using the Armbian builder but it looks like all the correct OTG options are already selected by default. Any ideas what I'm doing wrong?
  21. Hello I have problem with UART after some random time i have got serial8250_interrupt with dmesg log. After that my software reading/writing is broken from UART. [88124.598598] irq 42: nobody cared (try booting with the "irqpoll" option) [88124.598617] CPU: 0 PID: 10713 Comm: sas-statistics- Not tainted 5.3.7-sunxi #5.99.191031 [88124.598620] Hardware name: Allwinner sun8i Family [88124.598657] [<c010d751>] (unwind_backtrace) from [<c010a32d>] (show_stack+0x11/0x14) [88124.598674] [<c010a32d>] (show_stack) from [<c0923da9>] (dump_stack+0x69/0x78) [88124.598689] [<c0923da9>] (dump_stack) from [<c0164135>] (__report_bad_irq+0x25/0x98) [88124.598700] [<c0164135>] (__report_bad_irq) from [<c01643f7>] (note_interrupt+0x1b3/0x1f0) [88124.598712] [<c01643f7>] (note_interrupt) from [<c0161e27>] (handle_irq_event_percpu+0x43/0x54) [88124.598724] [<c0161e27>] (handle_irq_event_percpu) from [<c0161e71>] (handle_irq_event+0x39/0x50) [88124.598734] [<c0161e71>] (handle_irq_event) from [<c0164da7>] (handle_fasteoi_irq+0x6f/0xec) [88124.598745] [<c0164da7>] (handle_fasteoi_irq) from [<c016121d>] (generic_handle_irq+0x1d/0x28) [88124.598756] [<c016121d>] (generic_handle_irq) from [<c01616cd>] (__handle_domain_irq+0x45/0x84) [88124.598772] [<c01616cd>] (__handle_domain_irq) from [<c05c4c7d>] (gic_handle_irq+0x39/0x68) [88124.598786] [<c05c4c7d>] (gic_handle_irq) from [<c0101ae5>] (__irq_svc+0x65/0x94) [88124.598791] Exception stack(0xc470bbe8 to 0xc470bc30) [88124.598801] bbe0: 0ee73000 00000000 0ee73000 c0ec2280 00400040 00400040 [88124.598810] bc00: 00000013 00000082 ffffe000 cf83f000 c0f03080 c0f04d68 0000d7b4 c470bc38 [88124.598816] bc20: c0120193 c01022a0 40000133 ffffffff [88124.598828] [<c0101ae5>] (__irq_svc) from [<c01022a0>] (__do_softirq+0x88/0x2a4) [88124.598839] [<c01022a0>] (__do_softirq) from [<c0120193>] (irq_exit+0x87/0x98) [88124.598850] [<c0120193>] (irq_exit) from [<c01616d1>] (__handle_domain_irq+0x49/0x84) [88124.598861] [<c01616d1>] (__handle_domain_irq) from [<c05c4c7d>] (gic_handle_irq+0x39/0x68) [88124.598870] [<c05c4c7d>] (gic_handle_irq) from [<c0101ae5>] (__irq_svc+0x65/0x94) [88124.598874] Exception stack(0xc470bcd0 to 0xc470bd18) [88124.598881] bcc0: c10448b0 80000013 ca466800 0000efa6 [88124.598890] bce0: c104679c cd12b2a8 cdc21f40 cdc456c0 c470bd80 00004b00 00000000 cd12b274 [88124.598897] bd00: 40000bbe c470bd20 c061db8b c0937f30 00000033 ffffffff [88124.598911] [<c0101ae5>] (__irq_svc) from [<c0937f30>] (_raw_spin_unlock_irqrestore+0x1c/0x20) [88124.598928] [<c0937f30>] (_raw_spin_unlock_irqrestore) from [<c061db8b>] (dw8250_set_termios+0x2b/0xc8) [88124.598944] [<c061db8b>] (dw8250_set_termios) from [<c0615bb1>] (uart_change_speed+0x29/0xac) [88124.598957] [<c0615bb1>] (uart_change_speed) from [<c061610b>] (uart_set_termios+0x6b/0xe4) [88124.598968] [<c061610b>] (uart_set_termios) from [<c06059c3>] (tty_set_termios+0x107/0x170) [88124.598979] [<c06059c3>] (tty_set_termios) from [<c0605e47>] (set_termios+0x113/0x2c0) [88124.598988] [<c0605e47>] (set_termios) from [<c06063d3>] (tty_mode_ioctl+0x3a7/0x45c) [88124.599002] [<c06063d3>] (tty_mode_ioctl) from [<c0601a2b>] (tty_ioctl+0x12b/0x888) [88124.599018] [<c0601a2b>] (tty_ioctl) from [<c025f83d>] (do_vfs_ioctl+0x8d/0x6b4) [88124.599031] [<c025f83d>] (do_vfs_ioctl) from [<c025fe8d>] (ksys_ioctl+0x29/0x40) [88124.599041] [<c025fe8d>] (ksys_ioctl) from [<c0101001>] (ret_fast_syscall+0x1/0x62) [88124.599046] Exception stack(0xc470bfa8 to 0xc470bff0) [88124.599054] bfa0: 00000000 011f6d44 00000000 00005402 b48fe654 00000000 [88124.599062] bfc0: 00000000 011f6d44 00000000 00000036 00000000 b6f0f968 00000000 b48fe6dc [88124.599068] bfe0: 00000036 b48fe648 b6579631 b64fc746 [88124.599072] handlers: [88124.599082] [<975f99af>] serial8250_interrupt [88124.599088] Disabling IRQ #42 [128279.185919] hrtimer: interrupt took 529282 ns
  22. Just built some fresh le potato images from master. Error message is Wrong Ramdisk image format. Console dump here: http://ix.io/2c0y I think it's related to stuff going on here, but not sure how to troubleshoot yet https://github.com/armbian/build/blob/master/config/sources/families/include/meson64_common.inc#L34
  23. Dear all, Starting from NAND memory used to work fine on the nanopi neo plus2, however with the new boards (both v1.2 and v2.0 revision) we just obtained it frequently doesn't want to reboot, while a cold boot works fine (I tried also earlier u-boot versions (2019.04, 2018.11) without much success for the reboot from NAND). The re-boot process stops at this point (from the serial console): [ OK ] Reached target Shutdown. [ 152.452083] reboot: Restarting system U-Boot SPL 2019.10-armbian (Jan 25 2020 - 19:56:27 +0100) DRAM: 1024 MiB Trying to boot from MMC2 I suspected the problem to be in the u-boot, since the friendlyarm on NAND reboots without a hitch. I found a work-around for the latest stretch image (Armbian_20.02.0-rc1_Nanopineoplus2_stretch_current_5.4.14.7z), by doing the following: boot friendlyarm image from NAND and copy the sunxi-spl.bin: sudo dd if=/dev/mmcblk2 of=sunxi-spl-friendlyarm.bin count=4 bs=8k skip=1 boot armbian from NAND and update u-boot: switched to linux-image-next-sunxi64=5.90 kernel via armbian-config / System / Other / switch dd if=sunxi-spl-friendlyarm.bin of=/dev/mmcblk2 count=4 bs=8k seek=1 conv=fsync The atached armbianmonitor -u upload is from after a fresh reboot with the working configuration. Kind regards, Dennis
  24. Just wanted to note this - target NanoPi NEO2 - task at hand is Byte-UnixBench.... https://github.com/sfx2000/byte-unixbench more to follow...
  25. Hello, I am using up to date Armbian Buster. TP-Link TL-WN722N V1 USB WiFi dongle causes system crashes after kernel upgrade to 5.4.12-meson64 #19.11.8 SMP PREEMPT Thu Jan 16 20:12:23 CET 2020 aarch64 GNU/Linux. Before updating the kernel, I had no such problem. Feb 12 20:17:15 xxx systemd[1]: Found device AR9271 802.11n. Feb 12 20:17:15 xxx systemd[1]: Started ifup for wlx54e6fc8d208e. Feb 12 20:17:15 xxx wpa_supplicant[2360]: Successfully initialized wpa_supplicant Feb 12 20:17:15 xxx sh[2344]: wlx54e6fc8d208e=wlx54e6fc8d208e Feb 12 20:17:17 xxx wpa_supplicant[2361]: Using interface wlx54e6fc8d208e with hwaddr 54:e6:fc:8d:20:8e and ssid "mynetwork" Feb 12 20:17:17 xxx wpa_supplicant[2361]: wlx54e6fc8d208e: interface state UNINITIALIZED->ENABLED Feb 12 20:17:17 xxx wpa_supplicant[2361]: wlx54e6fc8d208e: AP-ENABLED Feb 12 20:17:17 xxx wpa_supplicant[2361]: wlx54e6fc8d208e: CTRL-EVENT-CONNECTED - Connection to 54:e6:fc:8d:20:8e completed [id=0 id_str=] Feb 12 20:17:20 xxx systemd[1]: systemd-rfkill.service: Succeeded. Feb 12 20:17:41 xxx wpa_supplicant[2361]: wlx54e6fc8d208e: AP-STA-CONNECTED 2c:d0:5a:38:bd:3b Feb 12 20:18:00 xxx sshd[2403]: Accepted password for myuser from 10.0.0.5 port 22 ssh2 Feb 12 20:18:00 xxx sshd[2403]: pam_unix(sshd:session): session opened for user myuser by (uid=0) Feb 12 20:18:00 xxx systemd[1]: Created slice User Slice of UID 1001. Feb 12 20:18:00 xxx systemd[1]: Starting User Runtime Directory /run/user/1001... Feb 12 20:18:00 xxx systemd-logind[1584]: New session 7 of user myuser. Feb 12 20:18:00 xxx systemd[1]: Started User Runtime Directory /run/user/1001. Feb 12 20:18:00 xxx systemd[1]: Starting User Manager for UID 1001... Feb 12 20:18:00 xxx systemd[2406]: pam_unix(systemd-user:session): session opened for user myuser by (uid=0) Feb 12 20:18:00 xxx systemd[2406]: Reached target Paths. Feb 12 20:18:00 xxx systemd[2406]: Reached target Sockets. Feb 12 20:18:00 xxx systemd[2406]: Reached target Timers. Feb 12 20:18:00 xxx systemd[2406]: Reached target Basic System. Feb 12 20:18:00 xxx systemd[2406]: Reached target Default. Feb 12 20:18:00 xxx systemd[2406]: Startup finished in 123ms. Feb 12 20:18:00 xxx systemd[1]: Started User Manager for UID 1001. Feb 12 20:18:00 xxx systemd[1]: Started Session 7 of user myuser. Feb 12 20:18:48 xxx sshd[2505]: Received disconnect from 10.0.0.5 port 22:11: disconnected by user Feb 12 20:18:48 xxx sshd[2505]: Disconnected from user myuser 10.0.0.5 port 22 Feb 12 20:18:48 xxx sshd[2403]: pam_unix(sshd:session): session closed for user myuser Feb 12 20:18:48 xxx systemd[1]: session-7.scope: Succeeded. Feb 12 20:18:48 xxx systemd-logind[1584]: Session 7 logged out. Waiting for processes to exit. Feb 12 20:18:48 xxx systemd-logind[1584]: Removed session 7. Feb 12 20:18:54 xxx wpa_supplicant[2361]: wlx54e6fc8d208e: AP-STA-DISCONNECTED 2c:d0:5a:38:bd:3b Feb 12 20:18:56 xxx kernel: ath: phy0: Unable to remove station entry for: 2c:d0:5a:38:bd:3b Message from syslogd@localhost at Feb 12 20:18:59 ... kernel:[ 571.404886] Internal error: Oops: 96000004 [#1] PREEMPT SMP Message from syslogd@localhost at Feb 12 20:18:59 ... kernel:[ 571.612865] Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Message from syslogd@localhost at Feb 12 20:18:59 ... kernel:[ 571.623551] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b Second one: Feb 12 20:23:08 xxx wpa_supplicant[2125]: Using interface wlx54e6fc8d208e with hwaddr 54:e6:fc:8d:20:8e and ssid "mynetwork" Feb 12 20:23:08 xxx wpa_supplicant[2125]: wlx54e6fc8d208e: interface state UNINITIALIZED->ENABLED Feb 12 20:23:08 xxx wpa_supplicant[2125]: wlx54e6fc8d208e: AP-ENABLED Feb 12 20:23:08 xxx wpa_supplicant[2125]: wlx54e6fc8d208e: CTRL-EVENT-CONNECTED - Connection to 54:e6:fc:8d:20:8e completed [id=0 id_str=] Feb 12 20:23:11 xxx systemd[1]: systemd-rfkill.service: Succeeded. Message from syslogd@localhost at Feb 12 20:23:25 ... kernel:[ 77.921372] Internal error: Oops: 96000004 [#1] PREEMPT SMP Message from syslogd@localhost at Feb 12 20:23:25 ... kernel:[ 78.152254] Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:25 xxx kernel: Unable to handle kernel paging request at virtual address 0005001700000048 Feb 12 20:23:25 xxx kernel: Mem abort info: Feb 12 20:23:25 xxx kernel: ESR = 0x96000004 Feb 12 20:23:25 xxx kernel: EC = 0x25: DABT (current EL), IL = 32 bits Feb 12 20:23:25 xxx kernel: SET = 0, FnV = 0 Feb 12 20:23:25 xxx kernel: EA = 0, S1PTW = 0 Feb 12 20:23:25 xxx kernel: Data abort info: Feb 12 20:23:25 xxx kernel: ISV = 0, ISS = 0x00000004 Feb 12 20:23:25 xxx kernel: CM = 0, WnR = 0 Feb 12 20:23:25 xxx kernel: [0005001700000048] address between user and kernel address ranges Feb 12 20:23:25 xxx kernel: Internal error: Oops: 96000004 [#1] PREEMPT SMP Feb 12 20:23:25 xxx kernel: Modules linked in: ath9k_htc ath9k_common ath9k_hw mac80211 ath cfg80211 rfkill libarc4 cdc_ether usbnet uas nf_log_ipv4 nf_log_common nft_limit cpufreq_powersave cpufreq_conservative xt_tcpudp xt_multiport xt_LOG xt_limit xt_conntrack nft_counter nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink meson_rng rng_core meson_gxbb_wdt scpi_hwmon ip_tables x_tables dwmac_generic realtek dwmac_meson8b Feb 12 20:23:25 xxx kernel: CPU: 1 PID: 2125 Comm: wpa_supplicant Not tainted 5.4.12-meson64 #19.11.8 Feb 12 20:23:25 xxx kernel: Hardware name: Hardkernel ODROID-C2 (DT) Feb 12 20:23:25 xxx kernel: pstate: 60000005 (nZCv daif -PAN -UAO) Feb 12 20:23:25 xxx kernel: pc : __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:25 xxx kernel: lr : __kmalloc_node_track_caller+0x4c/0x288 Feb 12 20:23:25 xxx kernel: sp : ffff800010603710 Feb 12 20:23:25 xxx kernel: x29: ffff800010603710 x28: 0000000000000014 Feb 12 20:23:25 xxx kernel: x27: ffff80001249d3c0 x26: ffff000042d90d00 Feb 12 20:23:25 xxx kernel: x25: 00000000ffffffff x24: 0000000000159801 Feb 12 20:23:25 xxx kernel: x23: ffff800011c67510 x22: 00000000ffffffff Feb 12 20:23:25 xxx kernel: x21: 00000000000928c0 x20: 0005001700000048 Feb 12 20:23:25 xxx kernel: x19: ffff000007303800 x18: 0000000000000000 Feb 12 20:23:25 xxx kernel: x17: 0000000000000000 x16: 0000000000000000 Feb 12 20:23:25 xxx kernel: x15: 0000000000000000 x14: 85a901e7583f6960 Feb 12 20:23:25 xxx kernel: x13: 3c82001b6c5b05ca x12: 32d0f6c2e6c1b305 Feb 12 20:23:25 xxx kernel: x11: ed25b09923fa1d1c x10: 32b5a2a8b0fc50fa Feb 12 20:23:25 xxx kernel: x9 : 0000000000000000 x8 : ffff00003c5a1020 Feb 12 20:23:25 xxx kernel: x7 : 0000000000000000 x6 : ffff00003c5a1020 Feb 12 20:23:25 xxx kernel: x5 : 0000000000000020 x4 : 0000000000000000 Feb 12 20:23:25 xxx kernel: x3 : 0000000000159801 x2 : 0000000000000000 Feb 12 20:23:25 xxx kernel: x1 : ffff00003c56aac0 x0 : 0000000000000001 Feb 12 20:23:25 xxx kernel: Call trace: Feb 12 20:23:25 xxx kernel: __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:25 xxx kernel: __kmalloc_reserve.isra.56+0x44/0xa0 Feb 12 20:23:25 xxx kernel: pskb_expand_head+0x70/0x2d0 Feb 12 20:23:25 xxx kernel: netlink_trim+0xa0/0xe0 Feb 12 20:23:25 xxx kernel: netlink_unicast+0x54/0x1f8 Feb 12 20:23:25 xxx kernel: nl80211_tx_mgmt+0x32c/0x370 [cfg80211] Feb 12 20:23:25 xxx kernel: genl_family_rcv_msg+0x1dc/0x3b0 Feb 12 20:23:25 xxx kernel: genl_rcv_msg+0x58/0xd0 Feb 12 20:23:25 xxx kernel: netlink_rcv_skb+0x58/0x118 Feb 12 20:23:25 xxx kernel: genl_rcv+0x34/0x48 Feb 12 20:23:25 xxx kernel: netlink_unicast+0x180/0x1f8 Feb 12 20:23:25 xxx kernel: netlink_sendmsg+0x198/0x338 Feb 12 20:23:25 xxx kernel: sock_sendmsg+0x44/0x50 Feb 12 20:23:25 xxx kernel: ____sys_sendmsg+0x250/0x290 Feb 12 20:23:25 xxx kernel: ___sys_sendmsg+0x80/0xc0 Feb 12 20:23:25 xxx kernel: __sys_sendmsg+0x68/0xb8 Feb 12 20:23:25 xxx kernel: __arm64_sys_sendmsg+0x20/0x28 Feb 12 20:23:25 xxx kernel: el0_svc_common.constprop.2+0x88/0x150 Feb 12 20:23:25 xxx kernel: el0_svc_handler+0x20/0x80 Feb 12 20:23:25 xxx kernel: el0_svc+0x8/0xc Feb 12 20:23:25 xxx kernel: Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:25 xxx kernel: ---[ end trace 7b6592514db85574 ]--- Message from syslogd@localhost at Feb 12 20:23:26 ... kernel:[ 78.799696] Internal error: Oops: 96000004 [#2] PREEMPT SMP Message from syslogd@localhost at Feb 12 20:23:26 ... kernel:[ 79.010560] Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:26 xxx kernel: Unable to handle kernel paging request at virtual address 0005001700000048 Feb 12 20:23:26 xxx kernel: Mem abort info: Feb 12 20:23:26 xxx kernel: ESR = 0x96000004 Feb 12 20:23:26 xxx kernel: EC = 0x25: DABT (current EL), IL = 32 bits Feb 12 20:23:26 xxx kernel: SET = 0, FnV = 0 Feb 12 20:23:26 xxx kernel: EA = 0, S1PTW = 0 Feb 12 20:23:26 xxx kernel: Data abort info: Feb 12 20:23:26 xxx kernel: ISV = 0, ISS = 0x00000004 Feb 12 20:23:26 xxx kernel: CM = 0, WnR = 0 Feb 12 20:23:26 xxx kernel: [0005001700000048] address between user and kernel address ranges Feb 12 20:23:26 xxx kernel: Internal error: Oops: 96000004 [#2] PREEMPT SMP Feb 12 20:23:26 xxx kernel: Modules linked in: ath9k_htc ath9k_common ath9k_hw mac80211 ath cfg80211 rfkill libarc4 cdc_ether usbnet uas nf_log_ipv4 nf_log_common nft_limit cpufreq_powersave cpufreq_conservative xt_tcpudp xt_multiport xt_LOG xt_limit xt_conntrack nft_counter nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink meson_rng rng_core meson_gxbb_wdt scpi_hwmon ip_tables x_tables dwmac_generic realtek dwmac_meson8b Feb 12 20:23:26 xxx kernel: CPU: 1 PID: 7 Comm: kworker/u8:0 Tainted: G D 5.4.12-meson64 #19.11.8 Feb 12 20:23:26 xxx kernel: Hardware name: Hardkernel ODROID-C2 (DT) Feb 12 20:23:26 xxx kernel: Workqueue: phy0 ath9k_led_work [ath9k_htc] Feb 12 20:23:26 xxx kernel: pstate: 60000005 (nZCv daif -PAN -UAO) Feb 12 20:23:26 xxx kernel: pc : __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:26 xxx kernel: lr : __kmalloc_node_track_caller+0x4c/0x288 Feb 12 20:23:26 xxx kernel: sp : ffff80001005bbe0 Feb 12 20:23:26 xxx kernel: x29: ffff80001005bbe0 x28: 0000000000000000 Feb 12 20:23:26 xxx kernel: x27: ffff00000735a0b8 x26: ffff80001005bd70 Feb 12 20:23:26 xxx kernel: x25: 00000000ffffffff x24: 0000000000159801 Feb 12 20:23:26 xxx kernel: x23: ffff800011c62c54 x22: 00000000ffffffff Feb 12 20:23:26 xxx kernel: x21: 0000000000082a20 x20: 0005001700000048 Feb 12 20:23:26 xxx kernel: x19: ffff000007303800 x18: 0000000000000010 Feb 12 20:23:26 xxx kernel: x17: 0000000000000000 x16: 0000000000000000 Feb 12 20:23:26 xxx kernel: x15: 0000000000000000 x14: 3239353662372065 Feb 12 20:23:26 xxx kernel: x13: 0000000000000000 x12: 0000000000000001 Feb 12 20:23:26 xxx kernel: x11: 0000000000000000 x10: 00000000000009f0 Feb 12 20:23:26 xxx kernel: x9 : ffff80001005bd60 x8 : fefefefefefefeff Feb 12 20:23:26 xxx kernel: x7 : 0000000000000001 x6 : 0000000000000064 Feb 12 20:23:26 xxx kernel: x5 : 000000000000000c x4 : 0000000000000000 Feb 12 20:23:26 xxx kernel: x3 : 0000000000159801 x2 : 0000000000000000 Feb 12 20:23:26 xxx kernel: x1 : ffff000007395580 x0 : 0000000000000001 Feb 12 20:23:26 xxx kernel: Call trace: Feb 12 20:23:26 xxx kernel: __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:26 xxx kernel: __kmalloc_reserve.isra.56+0x44/0xa0 Feb 12 20:23:26 xxx kernel: __alloc_skb+0x84/0x198 Feb 12 20:23:26 xxx kernel: ath9k_wmi_cmd+0x6c/0x1c8 [ath9k_htc] Feb 12 20:23:26 xxx kernel: ath9k_reg_rmw+0x7c/0x170 [ath9k_htc] Feb 12 20:23:26 xxx kernel: ath9k_hw_set_gpio+0xa8/0xf0 [ath9k_hw] Feb 12 20:23:26 xxx kernel: ath9k_led_work+0x28/0x30 [ath9k_htc] Feb 12 20:23:26 xxx kernel: process_one_work+0x1e0/0x338 Feb 12 20:23:26 xxx kernel: worker_thread+0x40/0x440 Feb 12 20:23:26 xxx kernel: kthread+0x120/0x128 Feb 12 20:23:26 xxx kernel: ret_from_fork+0x10/0x18 Feb 12 20:23:26 xxx kernel: Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:26 xxx kernel: ---[ end trace 7b6592514db85575 ]--- Message from syslogd@localhost at Feb 12 20:23:47 ... kernel:[ 99.419758] Internal error: Oops: 96000004 [#3] PREEMPT SMP Message from syslogd@localhost at Feb 12 20:23:47 ... kernel:[ 99.642872] Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:46 xxx kernel: Unable to handle kernel paging request at virtual address 0005001700000048 Feb 12 20:23:46 xxx kernel: Mem abort info: Feb 12 20:23:46 xxx kernel: ESR = 0x96000004 Feb 12 20:23:46 xxx kernel: EC = 0x25: DABT (current EL), IL = 32 bits Feb 12 20:23:46 xxx kernel: SET = 0, FnV = 0 Feb 12 20:23:46 xxx kernel: EA = 0, S1PTW = 0 Feb 12 20:23:46 xxx kernel: Data abort info: Feb 12 20:23:46 xxx kernel: ISV = 0, ISS = 0x00000004 Feb 12 20:23:46 xxx kernel: CM = 0, WnR = 0 Feb 12 20:23:46 xxx kernel: [0005001700000048] address between user and kernel address ranges Feb 12 20:23:47 xxx kernel: Internal error: Oops: 96000004 [#3] PREEMPT SMP Feb 12 20:23:47 xxx kernel: Modules linked in: ath9k_htc ath9k_common ath9k_hw mac80211 ath cfg80211 rfkill libarc4 cdc_ether usbnet uas nf_log_ipv4 nf_log_common nft_limit cpufreq_powersave cpufreq_conservative xt_tcpudp xt_multiport xt_LOG xt_limit xt_conntrack nft_counter nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink meson_rng rng_core meson_gxbb_wdt scpi_hwmon ip_tables x_tables dwmac_generic realtek dwmac_meson8b Feb 12 20:23:47 xxx kernel: CPU: 1 PID: 1557 Comm: systemd-timesyn Tainted: G D 5.4.12-meson64 #19.11.8 Feb 12 20:23:47 xxx kernel: Hardware name: Hardkernel ODROID-C2 (DT) Feb 12 20:23:47 xxx kernel: pstate: 60000005 (nZCv daif -PAN -UAO) Feb 12 20:23:47 xxx kernel: pc : __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:47 xxx kernel: lr : __kmalloc_node_track_caller+0x4c/0x288 Feb 12 20:23:47 xxx kernel: sp : ffff8000105f37c0 Feb 12 20:23:47 xxx kernel: x29: ffff8000105f37c0 x28: 0000000000000000 Feb 12 20:23:47 xxx kernel: x27: 0000000000000cc0 x26: 0000000000000000 Feb 12 20:23:47 xxx kernel: x25: 00000000ffffffff x24: 0000000000159801 Feb 12 20:23:47 xxx kernel: x23: ffff800011c62c54 x22: 00000000ffffffff Feb 12 20:23:47 xxx kernel: x21: 0000000000082cc0 x20: 0005001700000048 Feb 12 20:23:47 xxx kernel: x19: ffff000007303800 x18: 0000000000000000 Feb 12 20:23:47 xxx kernel: x17: 0000000000000000 x16: 0000000000000000 Feb 12 20:23:47 xxx kernel: x15: 0000000000000000 x14: 0000000000000000 Feb 12 20:23:47 xxx kernel: x13: 0000000000000001 x12: 0000000000000000 Feb 12 20:23:47 xxx kernel: x11: 0000000000000000 x10: 0000000000000000 Feb 12 20:23:47 xxx kernel: x9 : 0000000000000000 x8 : 00000000000005c8 Feb 12 20:23:47 xxx kernel: x7 : 0000000000000014 x6 : 0000000000000000 Feb 12 20:23:47 xxx kernel: x5 : ffff000042d90e00 x4 : ffff00007fbb42f0 Feb 12 20:23:47 xxx kernel: x3 : 0000000000159801 x2 : 0000000000000000 Feb 12 20:23:47 xxx kernel: x1 : ffff00007ef4e3c0 x0 : 0000000000000001 Feb 12 20:23:47 xxx kernel: Call trace: Feb 12 20:23:47 xxx kernel: __kmalloc_node_track_caller+0x150/0x288 Feb 12 20:23:47 xxx kernel: __kmalloc_reserve.isra.56+0x44/0xa0 Feb 12 20:23:47 xxx kernel: __alloc_skb+0x84/0x198 Feb 12 20:23:47 xxx kernel: alloc_skb_with_frags+0x50/0x1e0 Feb 12 20:23:47 xxx kernel: sock_alloc_send_pskb+0x200/0x238 Feb 12 20:23:47 xxx kernel: sock_alloc_send_skb+0x1c/0x28 Feb 12 20:23:47 xxx kernel: __ip_append_data.isra.59+0x770/0xc10 Feb 12 20:23:47 xxx kernel: ip_make_skb+0xe8/0x140 Feb 12 20:23:47 xxx kernel: udp_sendmsg+0x794/0xa10 Feb 12 20:23:47 xxx kernel: inet_sendmsg+0x40/0x68 Feb 12 20:23:47 xxx kernel: sock_sendmsg+0x44/0x50 Feb 12 20:23:47 xxx kernel: __sys_sendto+0xcc/0x130 Feb 12 20:23:47 xxx kernel: __arm64_sys_sendto+0x24/0x30 Feb 12 20:23:47 xxx kernel: el0_svc_common.constprop.2+0x88/0x150 Feb 12 20:23:47 xxx kernel: el0_svc_handler+0x20/0x80 Feb 12 20:23:47 xxx kernel: el0_svc+0x8/0xc Feb 12 20:23:47 xxx kernel: Code: d5384101 b9402262 b9401020 11000400 (f8626a99) Feb 12 20:23:47 xxx kernel: ---[ end trace 7b6592514db85576 ]---