March 2019 - arm - Fedora mailing-lists

Bluetooth on Udoo Neo ?
by Ken Harris 25 Jun '19

25 Jun '19

Is it possible to enable Bluetooth on Udoo Neo ? FYI, it uses the TI WL1831 module. I tried : hciattach -n ttymxc2 texas ... but got "Initialization timed out." I also tried various combinations of bit rates and flow control. Any tips are welcome. -K

2 2

Kernel 5.0 value add for Fedora arm?
by Robert Moskowitz 22 Jun '19

22 Jun '19

I am looking at summaries of features in the 5.0 kernel. I will have to dig into what the Fscrypt algorithm is and what that means, but.. I see support for RPi touchscreen. Will this add RPi touchscreen support for Fedora-arm? I suspect a lot more is needed than just a driver. What about other touchscreen for other arm SOC? Anything else I should look at and maybe take advantage of.... thanks. Good weekend to all.

3 2

Bug report for IP address changes?
by Jeffrey Walton 01 May '19

01 May '19

Hi Everyone, What component should receive the bug report for the IP address changes on armv7 and aarch64? Jeff

4 5

Problem with uboot 2019.04-rc2 and Cubieboad2
by Robert Moskowitz 19 Apr '19

19 Apr '19

The environment is only the uboot on the uSD and all partitions on the sata HD. I have been doing this for years now with no problem. uboot has always switched to looking for the sata hd for partitions if no partitions on the uSD: U-Boot SPL 2018.09-rc3 (Sep 05 2018 - 19:12:48 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2018.09-rc3 (Sep 05 2018 - 19:12:48 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubieboard2 I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 Loading Environment from FAT... ** No valid partitions found ** In: serial Out: serial Err: serial SCSI: Target spinup took 0 ms. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ** Invalid partition 1 ** scanning bus for devices... Device 0: (0:0) Vendor: ATA Prod.: WDC WD800BEVS-75 Rev: 04.0 Type: Hard Disk Capacity: 76319.0 MB = 74.5 GB (156301488 x 512) Found 1 device(s). Device 0: (0:0) Vendor: ATA Prod.: WDC WD800BEVS-75 Rev: 04.0 Type: Hard Disk Capacity: 76319.0 MB = 74.5 GB (156301488 x 512) ... is now current device Scanning scsi 0:2... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 567 bytes read in 33 ms (16.6 KiB/s) Ignoring unknown command: ui Ignoring malformed menu command: autoboot Ignoring malformed menu command: hidden Ignoring unknown command: totaltimeout CentOS-Userland-7-armv7hl-generic-Minimal-1810 Boot Options. 1: CentOS-Userland-7-armv7hl-generic-Minimal-1810 (4.14.82-201.el7.armv7hl) Enter choice: 1: CentOS-Userland-7-armv7hl-generic-Minimal-1810 (4.14.82- 201.el7.armv7hl) Retrieving file: /initramfs-4.14.82-201.el7.armv7hl.img Yes, this particular event is with the current Centos arm image, but that should not matter. I have to get this Centos image built and installed before I can test with Fedora arm image.... I grabbed a more recent uboot via: Fedora-Minimal-armhfp-30-20190301.n.0-sda When I try booting with the uboot in that image I get: U-Boot SPL 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubieboard2 I2C: ready DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... ** No valid partitions found ** In: serial Out: serial Err: serial SCSI: Target spinup took 0 ms. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: sunxi_set_gate: (CLK#66) unhandled eth0: ethernet@1c50000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 3 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ** Invalid partition 1 ** scanning bus for devices... data abort pc : [<7ef86b0e>] lr : [<7ef82d89>] reloc pc : [<4a01ab0e>] lr : [<4a016d89>] sp : 7af43ad0 ip : 0000001c fp : 000000c0 r10: 00000000 r9 : 7af4bed8 r8 : 00000000 r7 : 7af43d50 r6 : 7efc4894 r5 : 7efcc2f8 r4 : 7efcc2f8 r3 : 00000000 r2 : 00000000 r1 : ea000016 r0 : 7efcc2f8 Flags: nZcv IRQs off FIQs off Mode SVC_32 Code: e92dbd10 f8d045f0 b0858080 1000f8d8 (f8d14604) Resetting CPU ... resetting ... U-Boot SPL 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubieboard2 I2C: ready DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... ** No valid partitions found ** In: serial Out: serial Err: serial and so forth.... If there is a rc3 available, please tell me what image to grab for it and I can test with that. Meanwhile, it seems there is a problem here. thanks

3 9

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 31 Mar '19

31 Mar '19

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-04-02 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/9431/

1 0

grub2-mkconfig: command not found
by Jeffrey Walton 27 Mar '19

27 Mar '19

Hi Everyone, I deleted several old kernels today. grub.cfg listed an old kernel. I attempted to regenerate grub.cfg but experienced: grub2-mkconfig: command not found What tool do we use to generate the grub menu? Thanks in advance.

1 0

Problem with kernel-5.0.3-200.fc29.armv7hl on Raspberry PI 3B/3B+
by William Jacobs 27 Mar '19

27 Mar '19

Yesterday I installed the above referenced kernel on two Raspberry PIs, a 3B+ and a 3B. I also installed it on a BeagleBone Black and a Hummingboard2 (nxp i.mx6 Quad CPU). On the BeagleBone Black and the Hummingboard, no problems at all, so this appears to be specific to the Raspberry PI platform or CPU. The Raspberry PI's are both actually running, but I noticed that top tells me that the load average is 4.0. But these things are not actually doing anything. Top does not show any process using more than 0.7% CPU and that it tells me that each core is nearly 100% idle. dmesg is not giving me any significant errors. I have worked at finding the problem for a few hours and have not found a lot. But here is what I have found: If I reboot to kernel 4.20.16, the problem goes away. When booted into kernel 5.0.3 dmesg gives this line: [ 16.342693] systemd[1]: Mounting Kernel Debug File System... but I see nothing that indicated why this might be happening. Anyone else try kernel 5.0.3 on a Raspberry Pi? Any thoughts on where to look for the problem? Thanks very much! Will

2 2

testing Fedora-Minimal-armhfp-30-20190326.n.0-sda on Cubieboard2
by Robert Moskowitz 27 Mar '19

27 Mar '19

I am at IETF104, and only brought a Cubieboard2 and forgot my sata drive and sata adapter. Thus all testing is uSD and USB only until next Monday. I installed minimal on a 4GB uSD and deleted all partitions, leaving only the uboot. I installed minimal on a 16GB uSD and expanded the rootfs to the full size of the card. First test was uboot only in the uSD slot and the full image USB connected (uSD USB adapter). The boot failed. We are still on the rc2 broken uboot: U-Boot SPL 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubieboard2 I2C: ready DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... ** No valid partitions found ** In: serial Out: serial Err: serial SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: sunxi_set_gate: (CLK#66) unhandled eth0: ethernet@1c50000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning bus 2 for devices... 2 USB Device(s) found scanning bus 3 for devices... 1 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ** Invalid partition 1 ** scanning bus for devices... Found 0 device(s). Device 0: unknown device Device 0: EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80008d80 ... EHCI timed out on TD - token=0x80008d80 Vendor: Mass Rev: Prod: Storage Device Type: Removable Hard Disk Capacity: 14992.0 MB = 14.6 GB (30703616 x 512) ... is now current device EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80008d80 ... The uboot DID recognize the USB device, but did not boot it. The second test was to put the full image in the uSD slot. This booted up properly, went through the console first boot dialog and then I could log in as root. Next test used the F29 uboot on the 4Gb uSD in the uSD slot and the full image on the USB adapter: U-Boot SPL 2018.09 (Sep 11 2018 - 10:09:46 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2018.09 (Sep 11 2018 - 10:09:46 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubieboard2 I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 Loading Environment from FAT... ** No valid partitions found ** In: serial Out: serial Err: serial SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ** Invalid partition 1 ** scanning bus for devices... Found 0 device(s). Device 0: not available Device 0: device type unknown ... is now current device Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 10.0.6.251 (20 ms) *** ERROR: `serverip' not set etc.... So this uboot seems better, but it is not recognizing the USB drive. Is there a later uboot than that in F29 (Fedora-Minimal-armhfp-29-1.2-sda) for me to test with? Otherwise I don't see any other testing I can do until I get back Monday.

1 0

ASUS Tinkerboard support
by Jeffrey Walton 26 Mar '19

26 Mar '19

Hi Everyone, I've got a ASUS Tinkerboard. I like ASUS motherboards, but I am not happy with the Debian 9 image and its performance. MySQL performance blows, and takes over 2 minutes to create 4 tables. I'd like to try a Fedora image if possible. I found some past posts about Fedora for the board, like [1], but I can't tell if it is supported. [1] https://ask.fedoraproject.org/en/question/119755/fedora-27-pi-working-on-as… [2] https://tinkerboarding.co.uk/forum/archive/index.php/thread-1826.html Does Fedora support the Tinkerboard? Jeff

4 4

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 24 Mar '19

24 Mar '19

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-03-26 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/9431/

1 0

Ceph (last release) on aarch64
by Pierre-Francois RENARD 23 Mar '19

23 Mar '19

Hello all, I am trying to build a ceph cluster based on 4 raspberry3B+. Following the official CEPH documentation is a dead end as packages are only available for readhat/centos and not fedora ! I tried to used the el7 repository but the are conflicts and lacks with fedora repos. Did I miss something ? I am now trying to compile from sources. it is still ongoing ( 16% after 24h !) I am considering cross compilation from a X86_64 hosts but I cannot find any recent ( and probably uptodate ) documentation, any clue on that ? Thanks Fox

10 13

Re: [Test-Announce] Fedora 30 Candidate Beta-1.4 Available Now!
by Adam Williamson 21 Mar '19

21 Mar '19

On Thu, 2019-03-21 at 01:36 +0000, rawhide(a)fedoraproject.org wrote: > According to the schedule [1], Fedora 30 Candidate Beta-1.4 is now > available for testing. Please help us complete all the validation > testing! For more information on release validation testing, see: > https://fedoraproject.org/wiki/QA:Release_validation_test_plan > > Test coverage information for the current release can be seen at: > https://www.happyassassin.net/testcase_stats/30 > > You can see all results, find testing instructions and image download > locations, and enter results on the Summary page: > > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Summary > > The individual test result pages are: > > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Installation > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Base > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Server > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Cloud > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Desktop > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Security_Lab > > All Beta priority test cases for each of these test pages [2] must > pass in order to meet the Beta Release Criteria [3]. > > Help is available on #fedora-qa on irc.freenode.net [4], or on the > test list [5]. Hey folks! So, unfortunately we had some trouble getting a candidate build done, but now we have one. The go/no-go meeting is on Thursday at 17:00 UTC - that's in about 11 hours. Obviously time is tight to do the testing, but if folks could help test as much stuff as possible, that'd be great. We do have one outstanding blocker bug, but there's a chance it'll get downgraded at the meeting, so it'd be great if we could complete the testing for all Beta tests on this compose. If there isn't enough time, though, no-one will blame us :) Thanks everyone! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 17 Mar '19

17 Mar '19

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-03-19 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/9431/

1 0

how to make a working f28 sd card for odroid-hc2 ?
by Torbjorn Jansson 14 Mar '19

14 Mar '19

Hello for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers. the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora. all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host) 1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch 2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8" (sdf in this case is my sd card) 3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd 4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin . ./sd_fusing.sh /dev/sdf ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck. last few lines on serial console is something like: Starting firewalld - dynamic firewall daemon... Starting Initial Setup configuration program... then some stuff related to usb & my disk then on first boot a few lines related to OpenSSH key generation rebooting hangs at same place with exception of SSH keys. to get a bit further i can mount the root filesystem manually on my other computer and remove the following two files: rm /etc/systemd/system/graphical.target.wants/initial-setup.service rm /etc/systemd/system/multi-user.target.wants/initial-setup.service this gets rid of the initial setup but then i get a whole bunch of services failing and boot being really really slow, it takes probably 10-15 minutes for everything to time out and get to the logon prompt. when i get it root doesn't work. this is where i kind of gave up. i know i somehow managed to get a bootable image several months ago, but i'm not sure if i then had to manually set root password by editing passwd or shadow before trying to boot. things on my wish list for this board: easier installation and updated packages that work. for example arm-image-installer with a board definition for odroid. may be usefull even if we have to run sd_fusing manualy after anyway, possibly with a text saying so. this also would help to make --addconsole work uboot that recognized hc2 so it loads the right file dtb file for hc2, one that works and is appropriate.

7 19

Raspberry Pi 3B+ fails to boot aarch64 image
by Jan Kratochvil 13 Mar '19

13 Mar '19

Hello, sorry it may not be really Fedora specific but all images fail to boot for me except for the plain 32-bit Raspbian. Fedora 29 aarch64 Workstation fails on: https://www.jankratochvil.net/t/rpi3fail.jpg [FAILED] Failed to start Avahi mDNS/DNS-SD Stack. ... [FAILED] Failed to start Modem Manager etc. No graphical screen ever appears. Fedora 29 arm also failed, I do not remember now how. Various 64-bit Debian-derivatives also fail to boot. Tried both MicroSD 16GB 23MB/s card and USB flashdisk 16GB 16MB/s. Using official Raspberry power supply with their logo 5.1V 2.5A. Any idea? Thanks, Jan

3 11

Fedora-Xfce-armhfp-30-20190312.n.0-sda crashed last night
by Robert Moskowitz 13 Mar '19

13 Mar '19

The last messages last night were: Mar 12 21:21:54 localhost systemd[1]: Started dnf makecache. Mar 12 21:21:54 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 12 21:21:54 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 12 21:21:50 localhost systemd[1]: Starting dnf makecache... Mar 12 21:21:54 localhost dnf[32080]: Metadata cache refreshed recently. Mar 12 21:21:54 localhost systemd[1]: dnf-makecache.service: Succeeded. Mar 12 21:21:54 localhost systemd[1]: Started dnf makecache. Mar 12 21:21:54 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 12 21:21:54 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Then, some point later, a drive problem and crash. note the drive is a Kingston SSD: scanning bus for devices... Device 0: (0:0) Vendor: ATA Prod.: KINGSTON SV300S3 Rev: 541A Type: Hard Disk Capacity: 228936.5 MB = 223.5 GB (468862128 x 512) Here is what appeared on the console (note I have booted the system back up this morning): # [49033.321960] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:3: reading directory lblock 0 [49033.333133] EXT4-fs error (device sda3) in ext4_reserve_inode_write:5903: Journal has aborted [49033.354708] EXT4-fs error (device sda3): ext4_journal_check_start:61: Detected aborted journal [49033.363535] EXT4-fs (sda3): Remounting filesystem read-only [49033.375324] EXT4-fs (sda3): ext4_writepages: jbd2_start: 4054 pages, ino 262658; err -30 [49033.391407] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49033.410833] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49033.429168] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49033.447931] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49033.467215] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49033.485748] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49033.504649] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49033.522691] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49038.328845] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49038.348733] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49038.370459] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49038.386797] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49038.404675] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49038.419659] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:3: reading directory lblock 0 [49038.431818] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49038.452657] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:0: reading directory lblock 0 [49038.465314] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:2: reading directory lblock 0 [49038.477341] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:1: reading directory lblock 0 [49043.336333] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:1: reading directory lblock 0 [49043.355629] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:1: reading directory lblock 0 [49043.372138] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:1: reading directory lblock 0 [49043.390238] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:1: reading directory lblock 0 [49043.403614] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:1: reading directory lblock 0 [49043.420805] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:1: reading directory lblock 0 [49043.436772] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:1: reading directory lblock 0 [49043.449376] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:1: reading directory lblock 0 [49043.461505] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:1: reading directory lblock 0 [49043.476116] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:1: reading directory lblock 0 [49078.110404] EXT4-fs error (device sda3): ext4_find_entry:1438: inode #6412: comm kworker/u4:3: reading directory lblock 0 [49078.144537] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [49078.152223] CPU: 1 PID: 1 Comm: systemd Tainted: G C 5.0.0-300.fc30.armv7hl #1 [49078.160743] Hardware name: Allwinner sun7i (A20) Family [49078.165994] [<c0312560>] (unwind_backtrace) from [<c030c9a0>] (show_stack+0x18/0x1c) [49078.173740] [<c030c9a0>] (show_stack) from [<c0b29a00>] (dump_stack+0x80/0x9c) [49078.180966] [<c0b29a00>] (dump_stack) from [<c0350750>] (panic+0xe8/0x2d0) [49078.187844] [<c0350750>] (panic) from [<c0355444>] (do_exit+0x5d0/0xaec) [49078.194543] [<c0355444>] (do_exit) from [<c0355a00>] (do_group_exit+0x64/0xe0) [49078.201764] [<c0355a00>] (do_group_exit) from [<c0360238>] (get_signal+0x230/0x718) [49078.209418] [<c0360238>] (get_signal) from [<c030c108>] (do_work_pending+0xcc/0x4c0) [49078.217158] [<c030c108>] (do_work_pending) from [<c030106c>] (slow_work_pending+0xc/0x20) [49078.225324] Exception stack(0xef115fb0 to 0xef115ff8) [49078.230372] 5fa0: be2c6fc0 be2c719c 00000080 b6cc5d04 [49078.238543] 5fc0: be2c7198 00000000 b6f62000 00000011 ffffffff 00000000 005df204 be989b9c [49078.246713] 5fe0: 00000010 be2c6fb0 005abdb4 b6e432bc a00e0010 ffffffff [49078.253334] CPU0: stopping [49078.256053] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 5.0.0-300.fc30.armv7hl #1 [49078.264737] Hardware name: Allwinner sun7i (A20) Family [49078.269969] [<c0312560>] (unwind_backtrace) from [<c030c9a0>] (show_stack+0x18/0x1c) [49078.277710] [<c030c9a0>] (show_stack) from [<c0b29a00>] (dump_stack+0x80/0x9c) [49078.284931] [<c0b29a00>] (dump_stack) from [<c030fff0>] (handle_IPI+0x1ac/0x348) [49078.292324] [<c030fff0>] (handle_IPI) from [<c03025bc>] (gic_handle_irq+0x80/0x88) [49078.299889] [<c03025bc>] (gic_handle_irq) from [<c0301a0c>] (__irq_svc+0x6c/0x90) [49078.307361] Exception stack(0xc1201f38 to 0xc1201f80) [49078.312408] 1f20: 00000000 00989c68 [49078.320578] 1f40: 00000000 c031d820 00000000 00000000 c1200000 00000000 c1208df4 410fc074 [49078.328748] 1f60: c1201f90 c1208e3c c1203d00 c1201f88 c03093b8 c0309394 600f0013 ffffffff [49078.336922] [<c0301a0c>] (__irq_svc) from [<c0309394>] (arch_cpu_idle+0x24/0x54) [49078.344317] [<c0309394>] (arch_cpu_idle) from [<c037ec68>] (do_idle+0x10c/0x230) [49078.351711] [<c037ec68>] (do_idle) from [<c037efe0>] (cpu_startup_entry+0x20/0x28) [49078.359280] [<c037efe0>] (cpu_startup_entry) from [<c1000e8c>] (start_kernel+0x3fc/0x490) [49078.367460] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]--- [49078.376359] ------------[ cut here ]------------ [49078.380978] WARNING: CPU: 1 PID: 1 at kernel/sched/core.c:1181 set_task_cpu+0xfc/0x248 [49078.388882] Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat ip6table_nat nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat_ipv4 nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables vfat fat sun4i_codec rc_cec snd_soc_core sun4i_backend ac97_bus snd_pcm_dmaengine axp20x_pek snd_seq snd_seq_device axp20x_adc snd_pcm joydev snd_timer sun4i_gpadc_iio sunxi_cedrus(C) snd v4l2_mem2mem sun4i_ts nvmem_sunxi_sid soundcore videobuf2_dma_contig videobuf2_memops sunxi_wdt sunxi_cir videobuf2_v4l2 videobuf2_common videodev sun4i_drm_hdmi media sun4i_drm sun4i_frontend leds_gpio cpufreq_dt lz4 lz4_compress zram dm_multipath axp20x_battery axp20x_ac_power axp20x_usb_power industrialio axp20x_regulator pinctrl_axp209 mmc_block sun4i_tcon sun8i_tcon_top drm_kms_helper dwmac_sunxi syscopyarea sysfillrect stmmac_platform [49078.389026] sysimgblt stmmac fb_sys_fops drm sunxi phy_generic sun4i_gpadc musb_hdrc i2c_mv64xxx rtc_sunxi ahci_sunxi libahci_platform sun4i_ss des_generic ehci_platform udc_core ohci_platform sunxi_mmc phy_sun4i_usb sun4i_dma sunrpc [49078.496659] CPU: 1 PID: 1 Comm: systemd Tainted: G C 5.0.0-300.fc30.armv7hl #1 [49078.505168] Hardware name: Allwinner sun7i (A20) Family [49078.510395] [<c0312560>] (unwind_backtrace) from [<c030c9a0>] (show_stack+0x18/0x1c) [49078.518134] [<c030c9a0>] (show_stack) from [<c0b29a00>] (dump_stack+0x80/0x9c) [49078.525356] [<c0b29a00>] (dump_stack) from [<c03505b4>] (__warn+0xdc/0xf8) [49078.532229] [<c03505b4>] (__warn) from [<c0350978>] (warn_slowpath_null+0x40/0x4c) [49078.539794] [<c0350978>] (warn_slowpath_null) from [<c0378a14>] (set_task_cpu+0xfc/0x248) [49078.547966] [<c0378a14>] (set_task_cpu) from [<c03797a4>] (try_to_wake_up+0x308/0x49c) [49078.555878] [<c03797a4>] (try_to_wake_up) from [<c03c9264>] (hrtimer_wakeup+0x28/0x30) [49078.563790] [<c03c9264>] (hrtimer_wakeup) from [<c03c97c4>] (__hrtimer_run_queues+0x190/0x2dc) [49078.572394] [<c03c97c4>] (__hrtimer_run_queues) from [<c03ca0cc>] (hrtimer_interrupt+0x118/0x2b8) [49078.581262] [<c03ca0cc>] (hrtimer_interrupt) from [<c0991898>] (arch_timer_handler_phys+0x30/0x38) [49078.590220] [<c0991898>] (arch_timer_handler_phys) from [<c03b4788>] (handle_percpu_devid_irq+0xbc/0x22c) [49078.599783] [<c03b4788>] (handle_percpu_devid_irq) from [<c03af66c>] (generic_handle_irq+0x24/0x34) [49078.608822] [<c03af66c>] (generic_handle_irq) from [<c03afd38>] (__handle_domain_irq+0xa0/0xb8) [49078.617514] [<c03afd38>] (__handle_domain_irq) from [<c0302598>] (gic_handle_irq+0x5c/0x88) [49078.625858] [<c0302598>] (gic_handle_irq) from [<c0301a0c>] (__irq_svc+0x6c/0x90) [49078.633330] Exception stack(0xef115e60 to 0xef115ea8) [49078.638379] 5e60: 00000055 2e56b000 c123ce90 c123ce90 c134c198 00000000 00000000 00000000 [49078.646549] 5e80: ef115ed8 00000000 ef115f64 00000504 00000000 ef115eb0 c0350864 c0350868 [49078.654714] 5ea0: 60070013 ffffffff [49078.658205] [<c0301a0c>] (__irq_svc) from [<c0350868>] (panic+0x200/0x2d0) [49078.665078] [<c0350868>] (panic) from [<c0355444>] (do_exit+0x5d0/0xaec) [49078.671775] [<c0355444>] (do_exit) from [<c0355a00>] (do_group_exit+0x64/0xe0) [49078.678993] [<c0355a00>] (do_group_exit) from [<c0360238>] (get_signal+0x230/0x718) [49078.686643] [<c0360238>] (get_signal) from [<c030c108>] (do_work_pending+0xcc/0x4c0) [49078.694380] [<c030c108>] (do_work_pending) from [<c030106c>] (slow_work_pending+0xc/0x20) [49078.702545] Exception stack(0xef115fb0 to 0xef115ff8) [49078.707591] 5fa0: be2c6fc0 be2c719c 00000080 b6cc5d04 [49078.715761] 5fc0: be2c7198 00000000 b6f62000 00000011 ffffffff 00000000 005df204 be989b9c [49078.723929] 5fe0: 00000010 be2c6fb0 005abdb4 b6e432bc a00e0010 ffffffff [49078.730534] ---[ end trace 1e9429e735db4f06 ]---

1 0

dnf error - Fedora-Xfce-armhfp-30-20190312.n.0-sda
by Robert Moskowitz 12 Mar '19

12 Mar '19

I did a dnf update successfully. Then a 'dnf list > dnf.lst' to get the packages available. Then tried to install tigervnc-server: # dnf install tigervnc-server Fedora Modular 30 - armhfp 0.0 B/s | 0 B 00:00 Failed to synchronize cache for repo 'fedora-modular' Error: Failed to synchronize cache for repo 'fedora-modular'

1 0

Initial testing of Fedora-Xfce-armhfp-30-20190312.n.0-sda
by Robert Moskowitz 12 Mar '19

12 Mar '19

This is my first bootup of F30-arm-Xfce. I am running on a Cubieboard2, using the F29 uboot. /boot and / are on the sata drive, per my regular Cubie setup. Setting up monitor and keyboard for the test is a bit of a pain, my KVM does not support HDMI, so I use a real keyboard and mouse and disconnect my monitor from my work notebook for first boot and initial testing. I hope to at least use the KVM keyboard/mouse for next testing. I am please to observe that the video handling is snappier than it was with F29-Xfce. The 1st config GUI was actually bearable, and when I selected items like setting the root password, feeling that a shade was being pulled up was less. It actually went up much faster than back in my F29 testing. The Xfce desktop itself is reasonable speed-wise. So what ever was done with the video handling (I remember comments about the Cubie GPU and GTK3), thanks! Still no Xfce GUI date/time applet. This is an Xfce issue, and I will take it to their list. Again. Next to try the KVM, then see if I can get VNC working... More comments as time allows.

1 1

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 10 Mar '19

10 Mar '19

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-03-12 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/9431/

1 0

Re: Banana Pi-R1 stabil
by Gerhard Wiesinger 07 Mar '19

07 Mar '19

On 07.03.2019 16:31, Maxime Ripard wrote: > On Wed, Mar 06, 2019 at 09:03:00PM +0100, Gerhard Wiesinger wrote: >> while true; do echo "========================================"; echo -n >> "CPU_FREQ0: "; cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq; >> echo -n "CPU_FREQ1: "; cat >> /sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq; sleep 1; done& >> ./stress/cpuburn-a7 > Run cpufreq-ljt-stress-test > On ALL Banana Pi R1 I have and Banana Pro OK, see below Ciao, Gerhard ./cpufreq-ljt-stress-test The cjpeg and djpeg tools from libjpeg-turbo are not found. Trying to download and compile them. Downloading libjpeg-turbo-1.3.1.tar.gz ... done Extracting libjpeg-turbo-1.3.1.tar.gz ... done Compiling libjpeg-turbo, please be patient ... done Creating './whitenoise-1920x1080.jpg' ... done CPU stress test, which is doing JPEG decoding by libjpeg-turbo at different cpufreq operating points. Testing CPU 0 960 MHz ............................................................ OK 912 MHz ............................................................ OK 864 MHz ............................................................ OK 720 MHz ............................................................ OK 528 MHz ............................................................ OK 312 MHz ............................................................ OK 144 MHz ............................................................ OK Testing CPU 1 960 MHz ............................................................ OK 912 MHz ............................................................ OK 864 MHz ............................................................ OK 720 MHz ............................................................ OK 528 MHz ............................................................ OK 312 MHz ............................................................ OK 144 MHz ............................................................ OK Overall result : PASSED

1 0

Re: Banana Pi-R1 stabil
by Gerhard Wiesinger 06 Mar '19

06 Mar '19

On 06.03.2019 08:36, Maxime Ripard wrote: > >> Yes, there might at least 2 scenarios: >> >> 1.) Frequency switching itself is the problem > But that code is also the one being used by the BananaPro, which you > reported as stable. Yes, BananaPro is stable (with exactly same configuration as far as I know) .... > >> 2.) lower frequency/voltage operating points are not stable. >> >> For both scenarios: it might be possible that the crash happens on idle CPU, >> high CPU load or just randomly. Therefore just "waiting" might be better >> than 100% CPU utilization.But will test also 100% CPU. >> >> Therefore it would be good to see where the voltages for different >> frequencies for the SoC are defined (to compare). > In the device tree. > >> I'm currently testing 2 different settings on the 2 new Banana Pi R1 with >> newest kernel (see below), so 2 static frequencies: >> >> # Set to specific frequency 144000 (currently testing on Banana Pi R1 #1) >> >> # Set to specific frequency 312000 (currently testing on Banana Pi R1 #2) >> >> If that's fine I'll test also further frequencies (with different loads). > Look, you can come up with whatever program you want for this, but if > I insist on running that cpustress program (for the 4th time now), is > that it's actually good at it and caught all the cpufreq issues we've > seen so far. As I wrote, I run several stress tests also with the program you mention. But test combination require a minimum testing time to get verifiable results. The combinations are: - idle cpu vs. 100% CPU - on demand governor vs. several fixed frequencies. So far stable testing conditions for idle CPU and 100% CPU with command line below and cpuburn-a7 program: # Set to max performance (stable)=> frequency 960000 # Set to specific frequency 144000 (stable) # Set to specific frequency 312000 (stable) TODO list to test with "idle" CPU and 100% CPU: # Set to specific frequency 528000 (next step tested) # Set to specific frequency 720000 (next step tested) # Set to specific frequency 864000 # Set to specific frequency 912000 # Set to ondemand My guess is (but it is just a guess which has to be verified): - stable in all fixed frequencies in idle CPU and 100% CPU condition as well as on demand and 100% CPU - not stable with ondemand and "idle" CPU (so real frequency switching will happen often) > > Feel free to not trust me on this, but I'm not sure how the discussion > can continue if you do. > You missed my point from my previous mail: "But will test also 100% CPU.". See command line below. Ciao, Gerhard Test script: while true; do echo "========================================"; echo -n "CPU_FREQ0: "; cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq; echo -n "CPU_FREQ1: "; cat /sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq; sleep 1; done& ./stress/cpuburn-a7

1 0

Re: Banana Pi-R1 stabil
by Gerhard Wiesinger 05 Mar '19

05 Mar '19

On 05.03.2019 10:28, Maxime Ripard wrote: > On Sat, Mar 02, 2019 at 09:42:08AM +0100, Gerhard Wiesinger wrote: >> On 01.03.2019 10:30, Maxime Ripard wrote: >>> On Thu, Feb 28, 2019 at 08:41:53PM +0100, Gerhard Wiesinger wrote: >>>> On 28.02.2019 10:35, Maxime Ripard wrote: >>>>> On Wed, Feb 27, 2019 at 07:58:14PM +0100, Gerhard Wiesinger wrote: >>>>>> On 27.02.2019 10:20, Maxime Ripard wrote: >>>>>>> On Sun, Feb 24, 2019 at 09:04:57AM +0100, Gerhard Wiesinger wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> I've 3 Banana Pi R1, one running with self compiled kernel >>>>>>>> 4.7.4-200.BPiR1.fc24.armv7hl and old Fedora 25 which is VERY STABLE, the 2 >>>>>>>> others are running with Fedora 29 latest, kernel 4.20.10-200.fc29.armv7hl. I >>>>>>>> tried a lot of kernels between of around 4.11 >>>>>>>> (kernel-4.11.10-200.fc25.armv7hl) until 4.20.10 but all had crashes without >>>>>>>> any output on the serial console or kernel panics after a short time of >>>>>>>> period (minutes, hours, max. days) >>>>>>>> >>>>>>>> Latest known working and stable self compiled kernel: kernel >>>>>>>> 4.7.4-200.BPiR1.fc24.armv7hl: >>>>>>>> >>>>>>>> https://www.wiesinger.com/opensource/fedora/kernel/BananaPi-R1/ >>>>>>>> >>>>>>>> With 4.8.x the DSA b53 switch infrastructure has been introduced which >>>>>>>> didn't work (until ca8931948344c485569b04821d1f6bcebccd376b and kernel >>>>>>>> 4.18.x): >>>>>>>> >>>>>>>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drive… >>>>>>>> >>>>>>>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/driver… >>>>>>>> >>>>>>>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/dri… >>>>>>>> >>>>>>>> I has been fixed with kernel 4.18.x: >>>>>>>> >>>>>>>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/driver… >>>>>>>> >>>>>>>> >>>>>>>> So current status is, that kernel crashes regularly, see some samples below. >>>>>>>> It is typically a "Unable to handle kernel paging request at virtual addres" >>>>>>>> >>>>>>>> Another interesting thing: A Banana Pro works well (which has also an >>>>>>>> Allwinner A20 in the same revision) running same Fedora 29 and latest >>>>>>>> kernels (e.g. kernel 4.20.10-200.fc29.armv7hl.). >>>>>>>> >>>>>>>> Since it happens on 2 different devices and with different power supplies >>>>>>>> (all with enough power) and also the same type which works well on the >>>>>>>> working old kernel) a hardware issue is very unlikely. >>>>>>>> >>>>>>>> I guess it has something to do with virtual memory. >>>>>>>> >>>>>>>> Any ideas? >>>>>>>> [47322.960193] Unable to handle kernel paging request at virtual addres 5675d0 >>>>>>> That line is a bit suspicious >>>>>>> >>>>>>> Anyway, cpufreq is known to cause those kind of errors when the >>>>>>> voltage / frequency association is not correct. >>>>>>> >>>>>>> Given the stack trace and that the BananaPro doesn't have cpufreq >>>>>>> enabled, my first guess would be that it's what's happening. Could you >>>>>>> try using the performance governor and see if it's more stable? >>>>>>> >>>>>>> If it is, then using this: >>>>>>> https://github.com/ssvb/cpuburn-arm/blob/master/cpufreq-ljt-stress-test >>>>>>> >>>>>>> will help you find the offending voltage-frequency couple. >>>>>> For me it looks like they have all the same config regarding cpu governor >>>>>> (Banana Pro, old kernel stable one, new kernel unstable ones) >>>>> The Banana Pro doesn't have a regulator set up, so it will only change >>>>> the frequency, not the voltage. >>>>> >>>>>> They all have the ondemand governor set: >>>>>> >>>>>> I set on the 2 unstable "new kernel Banana Pi R1": >>>>>> >>>>>> # Set to max performance >>>>>> echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor >>>>>> echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor >>>>> What are the results? >>>> Stable since more than around 1,5 days. Normally they have been crashed for >>>> such a long uptime. So it looks that the performance governor fixes it. >>>> >>>> I guess crashes occour because of changing CPU voltage and clock changes and >>>> invalid data (e.g. also invalid RAM contents might be read, register >>>> problems, etc). >>>> >>>> Any ideas how to fix it for ondemand mode, too? >>> Run https://github.com/ssvb/cpuburn-arm/blob/master/cpufreq-ljt-stress-test >>> >>>> But it doesn't explaing that it works with kernel 4.7.4 without any >>>> problems. >>> My best guess would be that cpufreq wasn't enabled at that time, or >>> without voltage scaling. >>> >> Where can I see the voltage scaling parameters? >> >> on DTS I don't see any difference between kernel 4.7.4 and 4.20.10 regarding >> voltage: >> >> dtc -I dtb -O dts -o >> /boot/dtb-4.20.10-200.fc29.armv7hl/sun7i-a20-lamobo-r1.dts >> /boot/dtb-4.20.10-200.fc29.armv7hl/sun7i-a20-lamobo-r1.dtb > This can be also due to configuration being changed, driver support, etc. Where will the voltages for scaling then be set in detail (drivers, etc.)? > >> There is another strange thing (tested with >> kernel-5.0.0-0.rc8.git1.1.fc31.armv7hl, kernel-4.19.8-300.fc29.armv7hl, >> kernel-4.20.13-200.fc29.armv7hl, kernel-4.20.10-200.fc29.armv7hl): >> >> There is ALWAYS high CPU of around 10% in kworker: >> >> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND >> 18722 root 20 0 0 0 0 I 9.5 0.0 0:47.52 >> [kworker/1:3-events_freezable_power_] >> >> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND >> 776 root 20 0 0 0 0 I 8.6 0.0 0:02.77 >> [kworker/0:4-events] > The first one looks like it's part of the workqueue code. Any guessed reason for that? > >> Therefore CPU doesn't switch to low frequencies (see below). > You said previously that those crashes were happening when the board > was changing frequency, so I'm confused? For the ondemand setting: due to the high load of kworker, the frequency is not changing often to lower values (but does some time and crashes also regularly) For the performance setting: frequency is fixed (to maximum in the current configuration) and is stable > >> Any ideas? > Run the cpustress program I told you to use already twice. Had no time to try it yet. Will do. See also my comment below regarding idle CPU and high CPU. > >> BTW: Still stable at aboout 2,5days on both devices. So solution IS the >> performance governor. > No, the performance governor prevents any change in frequency. My > guess is that a lower frequency operating point is not working and is > crashing the CPU. > Yes, there might at least 2 scenarios: 1.) Frequency switching itself is the problem 2.) lower frequency/voltage operating points are not stable. For both scenarios: it might be possible that the crash happens on idle CPU, high CPU load or just randomly. Therefore just "waiting" might be better than 100% CPU utilization.But will test also 100% CPU. Therefore it would be good to see where the voltages for different frequencies for the SoC are defined (to compare). I'm currently testing 2 different settings on the 2 new Banana Pi R1 with newest kernel (see below), so 2 static frequencies: # Set to specific frequency 144000 (currently testing on Banana Pi R1 #1) # Set to specific frequency 312000 (currently testing on Banana Pi R1 #2) If that's fine I'll test also further frequencies (with different loads). Thnx. Ciao, Gerhard # Set to max performance (stable) echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo "144000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq echo "960000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo "144000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq echo "960000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq # Set to ondemand (not stable) echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo "ondemand" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo "144000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq echo "960000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo "144000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq echo "960000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq # Set to specific frequency 144000 (currently testing on Banana Pi R1 #1) echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo "144000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq echo "144000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo "144000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq echo "144000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq # Set to specific frequency 312000 (currently testing on Banana Pi R1 #2) echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo "312000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq echo "312000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo "312000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq echo "312000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq # Set to specific frequency 528000 (untested) echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo "528000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq echo "528000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo "528000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq echo "528000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq # Set to specific frequency 720000 (untested) echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo "720000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq echo "720000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo "720000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq echo "720000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq # Set to specific frequency 864000 (untested) echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo "864000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq echo "864000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo "864000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq echo "864000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq # Set to specific frequency 912000 (untested) echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo "912000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq echo "912000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo "912000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq echo "912000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq # Set to specific frequency 960000 (untested) echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo "960000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq echo "960000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo "960000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq echo "960000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 03 Mar '19

03 Mar '19

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-03-05 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/9431/

1 0

Raspberry Pi 3 B+ with Aarch64 image changing IP every half hour
by Jeffrey Walton 02 Mar '19

02 Mar '19

This is kind of unusual. Raspberry Pi 3 B+ with Aarch64 image. My SSH session keeps dying. I've noticed it happens about every half hour. When I log into the physical machine I see the IP address has changed. My DHCP server's default lease time is 60 minutes (max lease 120 minutes). 60 minutes is aggressive and it is intended to scavenge old leases quickly because of of device activity in my lab. Many devices are started up, a test is run, and then shutdown immediately. If I allow them to hang around for days or weeks then I sometimes run out of addresses in the subnet. I'm guessing the RPI is trying to renew at 30 minutes. Looking at DMESG I don't see a renew request; only a message about wlan0: [ 33.641372] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 33.658658] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 33.701586] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 33.776179] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 33.839349] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 34.384878] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 35.183999] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 380.555159] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 696.561166] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1012.565499] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1328.575936] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1644.604460] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready <disconnect around here> The RPI is the only device exhibiting the behavior. Does anyone know how to sidestep the problem? Thanks in advance.

3 6

What repos should be used for RPI3 B+?
by Jeffrey Walton 02 Mar '19

02 Mar '19

Hi Everyone, I need to sort out the dnf problems after a RPI3 B+ install using Fedora-Minimal-armhfp-29-1.2-sda.raw.xz. Searching for DNF and repos is returning hits for tradition Fedora desktops (like https://fedoraproject.org/wiki/Repositories) Would someone please provide the dnf tweaks needed or cat a working conf file and post it here? Thanks in advance.

5 9

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm March 2019