arm March 2016

arm@lists.fedoraproject.org

23 participants
60 discussions

Fedora-Minimal-armhfp-24-20160308.0
by David Jones 09 Mar '16

09 Mar '16

Hi Installed Fedora-Minimal-armhfp-24-20160308.0-sda.raw Is arm-boot-config still being used? if so it was missing from the image. Regards David

2 1

Fedora ARM & AArch64 Status Meeting Minutes 2016-03-08
by Paul Whalen 08 Mar '16

08 Mar '16

======================================================== #fedora-meeting-2: Fedora ARM and AArch64 Status Meeting ======================================================== Meeting started by pwhalen at 16:01:42 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2016-03-08/fedora_arm_an… . Meeting summary --------------- * 1) ==== Package Status & Issues ==== (pwhalen, 16:10:01) * Mass rebuild for F24 AArch64 complete, now time for cleanups. (pwhalen, 16:11:29) * statistics: {'older': 156, 'local_only': 1, 'remote_only': 322, 'same': 17535, 'newer': 0, 'total_missing_builds': 250} (pwhalen, 16:11:37) * issue with new grub2 build, pbrobinson is working with the maintainer to fix it. (pwhalen, 16:12:09) * f25 for AArch64 is now building as well, about 1200 builds behind there, should be caught up in a couple of days (pwhalen, 16:12:50) * Nightlies for f25 and f24 AArch64 should start within the next couple of days (pwhalen, 16:17:39) * Packages may not be signed (all arches), currently being looked at and should be resolved shortly. (pwhalen, 16:19:04) * 2) ==== Kernel Status ==== (pwhalen, 16:20:16) * gcc 6 breaks booting on numerous ARM devices (bz#1303147) (pwhalen, 16:21:01) * LINK: https://bugzilla.redhat.com/1303147 gcc 6 breaks booting on numerous ARM devices (hrw, 16:21:07) * LINK: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=70128 upstream gcc bug for it (hrw, 16:21:38) * Kernels now booting on Cortex-A7/A15 devices (pwhalen, 16:22:00) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1309147 (initrd on aarch64) needs checking with newer kernel etc (hrw, 16:24:06) * Please resume testing on all devices, report issues to the list/Bugzilla (pwhalen, 16:24:24) * PINE64, Jetson TX1 and Geekbox now enabled as of 4.5.0-0.rc7.git0.1 (pwhalen, 16:27:42) * 3) ==== U-Boot Status ==== (pwhalen, 16:30:16) * Latest - uboot-tools-2016.03-0.4.rc3.fc24 (pwhalen, 16:30:44) * 4) == F24 testing == (pwhalen, 16:34:09) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_24_Branched_20160308_Sum… (pwhalen, 16:34:21) * Please test and add results to the wiki. (pwhalen, 16:35:41) * 5) == Open Floor == (pwhalen, 16:36:34) Meeting ended at 16:40:27 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (54) * pbrobinson (36) * hrw (30) * zodbot (6) * masta (2) * dgilmore (1) * dmarlin (0) * bconoboy (0) * jsmith (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Wandboard Quad network dies under load?
by Derek Atkins 08 Mar '16

08 Mar '16

Hi, I'm having an issue with two different wandboard quad systems; one is running F22, the other is running F23. When the system is under high network load, specifically high transmit load, after a while the network just gives up. Technically it's not VERY high load, only about 2MB/s, but it's high transmit load -- high download load seems to be fine as far as I can tell. I know that "gives up" isn't a very technical term, but I frankly don't know what else to call it. * dmesg doesn't say anything about the link going down * ifconfig shows the interface still has an IP address * arp, however, seems to start failing (and my NFS server has an incomplete arp address) * ping doesn't work to anywhere (regardless of the contents of the arp table) * DNS doesn't work (obviously -- no packets are coming or going). I can usually recover by doing: nmcli con down "Wired connection 1" nmcli con up "Wired connection 1" (the 'up' results in the message "Error: Connection activation failed.") After that I need to pull the ethernet plug, count to 5-10, and then plug it in again. Then I'll get the messages: [30540.554006] fec 2188000.ethernet eth0: Link is Down [30553.558837] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow contro (sorry for the cut messages; minicom serial console doesn't wrap lines) After I do this the system has network again. However it's quite frustrating that I have to go through all these hoops. Note that just pulling the network cable by itself does not seem sufficient to reset the network. Is this a hardware problem or a software problem (or a combination of the two)? I've had it happen on this one system three times today; I can definitely reliably repeat it (although it does take a couple hours until it dies). It's also happened on another system, but I've not seen it happen since I stopped pulling data from it. Any suggestions? I'd like to not have to go out and spend more money to buy an Atom-based solution, even though it might be better for my use case due to AES-NI. Thanks, -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord(a)MIT.EDU PGP key available

3 6

F23 on Wandboard Quad -- kernel doesn't start?
by Derek Atkins 07 Mar '16

07 Mar '16

Hi, I'm trying to run F23 on a Wandboard Quad, but it's not booting. It hangs after the "Starting kernel" output. I followed the instructions at https://fedoraproject.org/wiki/Architectures/ARM/F23/Installation#For_the_W… starting from Fedora-Minimal-armhfp-23-10-sda.raw.xz I installed the image, then copied in the SPL and u-boot.img. But when I try to boot my wandboard I get: U-Boot SPL 2015.07 (Sep 12 2015 - 11:53:19) U-Boot 2015.07 (Sep 12 2015 - 11:53:19 +0000) CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz) Reset cause: POR Board: Wandboard rev C1 I2C: ready DRAM: 2 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment No panel detected: default to HDMI Display: HDMI (1024x768) In: serial Out: serial Err: serial Net: FEC [PRIME] Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 518 bytes read in 49 ms (9.8 KiB/s) Ignoring unknown command: ui Ignoring malformed menu command: autoboot Ignoring malformed menu command: hidden Ignoring unknown command: totaltimeout Fedora-Minimal-armhfp-23-10 Boot Options. 1: Fedora-Minimal-armhfp-23-10 (4.2.3-300.fc23.armv7hl) Enter choice: 1: Fedora-Minimal-armhfp-23-10 (4.2.3-300.fc23.armv7hl) Retrieving file: /initramfs-4.2.3-300.fc23.armv7hl.img 38958034 bytes read in 1833 ms (20.3 MiB/s) Retrieving file: /vmlinuz-4.2.3-300.fc23.armv7hl 5811776 bytes read in 307 ms (18.1 MiB/s) append: enforcing=0 ro root=UUID=b2c019d9-2401-4a22-9a40-36a92a00cdfe Retrieving file: /dtb-4.2.3-300.fc23.armv7hl/imx6q-wandboard.dtb 30792 bytes read in 1235 ms (23.4 KiB/s) Kernel image @ 0x11000000 [ 0x000000 - 0x58ae40 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Loading Ramdisk to 2dad8000, end 2ffff3d2 ... OK Loading Device Tree to 2dacd000, end 2dad7847 ... OK Starting kernel ... And then the system just sits and hangs.. Is this a known problem? I tried with two different SD cards and both fail. I could certainly revert back to F22, but why start 6-months behind? -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord(a)MIT.EDU PGP key available

4 6

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by Paul Whalen 06 Mar '16

06 Mar '16

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2016-03-08 from 16:00:00 to 17: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/3211/

1 0

Raspberry Pi 3
by Jeffrey Ollie 01 Mar '16

01 Mar '16

Built-in WiFi, Bluetooth, 64 bit processor. Is this finally the Raspberry Pi that Fedora will run unmodified on? Sure hope so... https://www.raspberrypi.org/blog/raspberry-pi-3-on-sale/

10 19

NFS server processes spinning?
by Derek Atkins 01 Mar '16

01 Mar '16

Hi, I've got a Wandboard Quad running Fedora 22 (current as of yesterday). This box is a MythTV backend. It's also running an NFS server to serve the 2 TB Sata drive connected to store my recordings. I noticed that the nfs server processes are spinning, even when there are no clients attached. Here's an output from top: top - 16:19:30 up 23:36, 1 user, load average: 2.79, 2.75, 2.66 Tasks: 118 total, 5 running, 113 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.3 us, 38.5 sy, 0.0 ni, 40.7 id, 0.0 wa, 0.0 hi, 20.6 si, 0.0 st KiB Mem : 2064876 total, 62132 free, 73572 used, 1929172 buff/cache KiB Swap: 249852 total, 249432 free, 420 used. 1935800 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1024 root 20 0 0 0 0 R 77.6 0.0 1154:25 nfsd 1023 root 20 0 0 0 0 R 76.6 0.0 1150:27 nfsd 3 root 20 0 0 0 0 R 47.4 0.0 602:37.59 ksoftirqd/0 60 root 20 0 0 0 0 R 13.8 0.0 36:23.26 kswapd0 981 root 20 0 356948 29000 18440 S 4.6 1.4 158:47.23 mythbackend 13 root 20 0 0 0 0 S 1.0 0.0 10:25.97 ksoftirqd/1 18 root 20 0 0 0 0 S 1.0 0.0 9:19.12 ksoftirqd/2 8556 root 20 0 8908 3556 3060 R 1.0 0.2 0:00.16 top Any idea why NFS is spinning like this? I haven't noticed this on my x86-based Fedora servers. -derek -- Derek Atkins 617-623-3745 derek(a)ihtfp.com www.ihtfp.com Computer and Internet Security Consultant

1 1

Fedora ARM & AArch64 Status Meeting Minutes 2016-03-01
by Paul Whalen 01 Mar '16

01 Mar '16

1 0

unsubscribe
by Darrell 01 Mar '16

01 Mar '16

unsubscribe

2 1

unsubscribe
by Darrell 01 Mar '16

01 Mar '16

unsubscribe

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm March 2016