arm October 2017

arm@lists.fedoraproject.org

10 participants
11 discussions

Summary of Fedora on Odroid XU4
by arm_ml＠rirasoft.de 08 Jan '18

08 Jan '18

Summary of Fedora on Odroid XU4 1. with Kernel 4.6.5-300.fc24 system boots without failure, but update to newer kernel fails due dracut didn't build suitable intramfs https://bugzilla.redhat.com/show_bug.cgi?id=1482825 2. newer kernel works only with "cpuidle.off=1" inserted into the "append" kernel line in the /boot/extlinux/extlinux.conf file, but all USB3 Hosts failed, no onboard ethernet 3. To boot the system from the eMMC card: A. The initramfs image file must be rebuilt. The simplest way is to: a. Boot up using the MicroSD card; b. Partition the eMMC card such that partition 1 begins on sector 3072 (Default starting sector from fdisk is 2048). There should be 4 partitions created; c. Mount the Fedora image desired to be installed on the eMMC card; d. Copy all partition data from the mounted fedora image partitions (there are 4 for Fedora 26 ARM images) to the appropriate eMMC partitions; e. Update the UUID values on what will be the /boot/extlinux/extlinux.conf file and /etc/fstab files of the eMMC card; f. Assuming the eMMC partitions are mounted as such -- mount /dev/mmcblk1p4 /mnt mount /dev/mmcblk1p2 /mnt/boot then perform the following mounts -- mount -o bind /proc /mnt/proc mount -o bind /dev /mnt/dev mount -o bind /sys /mnt/sys B. Rebuild the eMMC card's initramfs by executing the following command: chroot /mnt dracut --add-drivers='pwrseq_emmc mmc_block' /boot/initramfs-4.11.8-300.fc26.armv7hl.img 4.11.8-300.fc26.armv7hl C. Flash the boot information in the header of the eMMC card; C. Shutdown the system, then remove the MicroSD card; D. Boot up using the eMMC card. 4. If the system is to be updated using "dnf update", a new initramfs image must again be generated. This can be done using steps 1f - B. above using the new initramfs and kernel images provided by the "dnf update". ---------------------------------------------------------------- Note to the developers/maintainers of dracut: The kernel modules "pwrseq_emmc" and "mmc_block" should be included in dracut for the Odroid-XU3 and Odroid-XU4 such that the user need not have to execute this procedure each time and update to the system is performed. Is this correct and complete ? Andreas

9 38

activation of SPI on fedora26 with a raspberry3
by christophe pages 28 Dec '17

28 Dec '17

Hello, I try to activate the spi on my raspberry3 using a fedora 26. I tried these options: device_tree_param=spi=on dtoverlay=spi-bcm2708 I use this kernel: 4.12.5-300.fc26.armv7hl I see that the support in kernel seems already inside: CONFIG_SPI=y # CONFIG_SPI_DEBUG is not set CONFIG_SPI_MASTER=y But I never see the devices /dev/spi* appearing. I can't see any messages regarding spi in dmesg. I tested with a raspbian and I see them correctly. I think I miss somethiing. Could you help. Thanks.

3 5

RPi 3 and kernel 4.14.0-0.rc3.git3.1.fc28.armv7hl
by Tomasz Kłoczko 07 Nov '17

07 Nov '17

Just resurected my old RPi 3 and as long as latest f27 image was OK I've pushed it to rawhide and seems current rawhide kernel has some issues on RPi 3. Just quick question: are below issues are already known or should I open ticket(s)? (ful dmesg in attachment) 1) [ 95.367454] Hardware name: Generic DT based system [ 95.367810] Workqueue: hci0 hci_cmd_work [bluetooth] [ 95.367848] [<c03131b4>] (unwind_backtrace) from [<c030d98c>] (show_stack+0x18/0x1c) [ 95.367868] [<c030d98c>] (show_stack) from [<c0b7e310>] (dump_stack+0xa0/0xd8) [ 95.367887] [<c0b7e310>] (dump_stack) from [<c03b2dd4>] (register_lock_class+0x298/0x514) [ 95.367905] [<c03b2dd4>] (register_lock_class) from [<c03b716c>] (__lock_acquire+0xe4/0x11f8) [ 95.367921] [<c03b716c>] (__lock_acquire) from [<c03b8e4c>] (lock_acquire+0x280/0x2dc) [ 95.367940] [<c03b8e4c>] (lock_acquire) from [<c0b99634>] (_raw_read_lock+0x4c/0x5c) [ 95.368057] [<c0b99634>] (_raw_read_lock) from [<bf58603c>] (hci_uart_tx_wakeup+0x1c/0x98 [hci_uart]) [ 95.368243] [<bf58603c>] (hci_uart_tx_wakeup [hci_uart]) from [<bf5870f0>] (hci_uart_send_frame+0x54/0x6c [hci_uart]) [ 95.368669] [<bf5870f0>] (hci_uart_send_frame [hci_uart]) from [<bf2ff26c>] (hci_send_frame+0xcc/0xf8 [bluetooth]) [ 95.369271] [<bf2ff26c>] (hci_send_frame [bluetooth]) from [<bf2ff340>] (hci_cmd_work+0xa8/0x124 [bluetooth]) [ 95.369581] [<bf2ff340>] (hci_cmd_work [bluetooth]) from [<c03735a4>] (process_one_work+0x444/0x840) [ 95.369598] [<c03735a4>] (process_one_work) from [<c0374d80>] (worker_thread+0x290/0x40c) [ 95.369615] [<c0374d80>] (worker_thread) from [<c037aac0>] (kthread+0x174/0x1a0) [ 95.369633] [<c037aac0>] (kthread) from [<c03087c8>] (ret_from_fork+0x14/0x2c) [ 95.507788] Bluetooth: hci0: BCM: chip id 94 2) [ 107.079610] ------------[ cut here ]------------ [ 107.079645] WARNING: CPU: 1 PID: 1 at lib/dma-debug.c:614 debug_dma_assert_idle+0x148/0x1e0 [ 107.079655] vc4-drm soc:gpu: DMA-API: cpu touching an active dma mapped cacheline [cln=0x00c8acc0] [ 107.079659] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables rc_cec vc4 snd_soc_core ac97_bus snd_pcm_dmaengine cec rc_core snd_pcm snd_timer snd soundcore brcmfmac drm_kms_helper brcmutil drm fb_sys_fops hci_uart cfg80211 syscopyarea sysfillrect btbcm sysimgblt btqca btintel bluetooth bcm2835_wdt ecdh_generic rfkill bcm2835_thermal bcm2835_rng leds_gpio xfs libcrc32c smsc95xx usbnet mii mmc_block sdhci_iproc dwc2 sdhci_pltfm crc32_arm_ce udc_core sdhci pwm_bcm2835 i2c_bcm2835 bcm2835 bcm2835_dma phy_generic [ 107.079932] CPU: 1 PID: 1 Comm: systemd Not tainted 4.14.0-0.rc3.git3.1.fc28.armv7hl #1 [ 107.079937] Hardware name: Generic DT based system [ 107.079973] [<c03131b4>] (unwind_backtrace) from [<c030d98c>] (show_stack+0x18/0x1c) [ 107.079995] [<c030d98c>] (show_stack) from [<c0b7e310>] (dump_stack+0xa0/0xd8) [ 107.080012] [<c0b7e310>] (dump_stack) from [<c0354024>] (__warn+0xe4/0x104) [ 107.080028] [<c0354024>] (__warn) from [<c0354080>] (warn_slowpath_fmt+0x3c/0x4c) [ 107.080045] [<c0354080>] (warn_slowpath_fmt) from [<c0711634>] (debug_dma_assert_idle+0x148/0x1e0) [ 107.080069] [<c0711634>] (debug_dma_assert_idle) from [<c04e59e8>] (wp_page_copy+0xfc/0x640) [ 107.080087] [<c04e59e8>] (wp_page_copy) from [<c04e74b8>] (do_wp_page+0x3a4/0x5ac) [ 107.080101] [<c04e74b8>] (do_wp_page) from [<c04ea810>] (handle_mm_fault+0xd28/0xde0) [ 107.080118] [<c04ea810>] (handle_mm_fault) from [<c0b9a980>] (do_page_fault+0x244/0x3b8) [ 107.080136] [<c0b9a980>] (do_page_fault) from [<c0301360>] (do_DataAbort+0x40/0xc0) [ 107.080151] [<c0301360>] (do_DataAbort) from [<c0b9a260>] (__dabt_usr+0x40/0x60) [ 107.080159] Exception stack(0xef113fb0 to 0xef113ff8) [ 107.080170] 3fa0: 02565dd0 02601bb8 02565df0 00000002 [ 107.080184] 3fc0: 02565df0 0260c920 02601bb8 befdd848 befdd850 b6f7aa48 02565dd0 02559508 [ 107.080196] 3fe0: b6dd38f4 befdd7c8 b6cd1e38 b6cc8f3c 20060010 ffffffff [ 107.080249] ---[ end trace 66ededa5d1568f0b ]--- [ 107.080253] Mapped at: [ 107.080345] vc4_bo_create+0xe4/0x198 [vc4] [ 107.080420] vc4_allocate_bin_bo+0x38/0x150 [vc4] [ 107.080494] vc4_v3d_bind+0x12c/0x20c [vc4] [ 107.080507] component_bind_all+0x138/0x220 [ 107.080581] vc4_drm_bind+0x88/0x130 [vc4] [ 108.193398] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) 3) some issue with missing symbol due systemd run [ 57.304786] systemd-journald[193]: Received SIGTERM from PID 1 (systemd). [ 59.997395] systemd: 15 output lines suppressed due to ratelimiting [ 61.986368] systemd[1]: RTC configured in localtime, applying delta of -240 minutes to system time. [ 75.141028] unwind: Unknown symbol address bf067284 [ 75.141036] unwind: Index not found bf067284 [ 78.120054] systemd-journald[457]: Received request to flush runtime journal from PID 1 [ 78.255026] unwind: Unknown symbol address bf067284 [ 78.269971] unwind: Index not found bf067284 [ 78.284717] unwind: Unknown symbol address bf067284 [ 78.299588] unwind: Index not found bf067284 [ 78.314816] unwind: Unknown symbol address bf067284 These messages about "Unknown symbol address bf067284" are repeated after this several times. 4) [ 107.079610] ------------[ cut here ]------------ [ 107.079645] WARNING: CPU: 1 PID: 1 at lib/dma-debug.c:614 debug_dma_assert_idle+0x148/0x1e0 [ 107.079655] vc4-drm soc:gpu: DMA-API: cpu touching an active dma mapped cacheline [cln=0x00c8acc0] [ 107.079659] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables rc_cec vc4 snd_soc_core ac97_bus snd_pcm_dmaengine cec rc_core snd_pcm snd_timer snd soundcore brcmfmac drm_kms_helper brcmutil drm fb_sys_fops hci_uart cfg80211 syscopyarea sysfillrect btbcm sysimgblt btqca btintel bluetooth bcm2835_wdt ecdh_generic rfkill bcm2835_thermal bcm2835_rng leds_gpio xfs libcrc32c smsc95xx usbnet mii mmc_block sdhci_iproc dwc2 sdhci_pltfm crc32_arm_ce udc_core sdhci pwm_bcm2835 i2c_bcm2835 bcm2835 bcm2835_dma phy_generic [ 107.079932] CPU: 1 PID: 1 Comm: systemd Not tainted 4.14.0-0.rc3.git3.1.fc28.armv7hl #1 [ 107.079937] Hardware name: Generic DT based system [ 107.079973] [<c03131b4>] (unwind_backtrace) from [<c030d98c>] (show_stack+0x18/0x1c) [ 107.079995] [<c030d98c>] (show_stack) from [<c0b7e310>] (dump_stack+0xa0/0xd8) [ 107.080012] [<c0b7e310>] (dump_stack) from [<c0354024>] (__warn+0xe4/0x104) [ 107.080028] [<c0354024>] (__warn) from [<c0354080>] (warn_slowpath_fmt+0x3c/0x4c) [ 107.080045] [<c0354080>] (warn_slowpath_fmt) from [<c0711634>] (debug_dma_assert_idle+0x148/0x1e0) [ 107.080069] [<c0711634>] (debug_dma_assert_idle) from [<c04e59e8>] (wp_page_copy+0xfc/0x640) [ 107.080087] [<c04e59e8>] (wp_page_copy) from [<c04e74b8>] (do_wp_page+0x3a4/0x5ac) [ 107.080101] [<c04e74b8>] (do_wp_page) from [<c04ea810>] (handle_mm_fault+0xd28/0xde0) [ 107.080118] [<c04ea810>] (handle_mm_fault) from [<c0b9a980>] (do_page_fault+0x244/0x3b8) [ 107.080136] [<c0b9a980>] (do_page_fault) from [<c0301360>] (do_DataAbort+0x40/0xc0) [ 107.080151] [<c0301360>] (do_DataAbort) from [<c0b9a260>] (__dabt_usr+0x40/0x60) [ 107.080159] Exception stack(0xef113fb0 to 0xef113ff8) [ 107.080170] 3fa0: 02565dd0 02601bb8 02565df0 00000002 [ 107.080184] 3fc0: 02565df0 0260c920 02601bb8 befdd848 befdd850 b6f7aa48 02565dd0 02559508 [ 107.080196] 3fe0: b6dd38f4 befdd7c8 b6cd1e38 b6cc8f3c 20060010 ffffffff [ 107.080249] ---[ end trace 66ededa5d1568f0b ]--- [ 107.080253] Mapped at: [ 107.080345] vc4_bo_create+0xe4/0x198 [vc4] [ 107.080420] vc4_allocate_bin_bo+0x38/0x150 [vc4] [ 107.080494] vc4_v3d_bind+0x12c/0x20c [vc4] [ 107.080507] component_bind_all+0x138/0x220 [ 107.080581] vc4_drm_bind+0x88/0x130 [vc4] [ 108.193398] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

2 14

aarch64 slowdown for F27+?
by Jens Petersen 29 Oct '17

29 Oct '17

Hi, I don't have hard numbers but looking at Koji buildtimes suggests a significant slowdown on aarch64 for F27+ in Koji, at least for Haskell packages. Has anyone else noticed this? Jens

2 2

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

29 Oct '17

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2017-10-31 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/5170/

1 0

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

23 Oct '17

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2017-10-24 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/5170/

2 1

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

15 Oct '17

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2017-10-17 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/5170/

1 0

Fedora 27 Talking Points - ARM SIG
by Jan Kurik 10 Oct '17

10 Oct '17

As we are getting closer to the F27 Final release, I would like to ask members of the ARM SIG to revisit and finalize Talking Points for the F27 ARM release. This helps not only the community Marketing team, but also Ambassadors who arrange release parties and evangelize the release worldwide. [1] https://fedoraproject.org/wiki/Fedora_27_talking_points#Fedora_ARM Thank you, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

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

08 Oct '17

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2017-10-10 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/5170/

1 0

=?utf-8?q?=5Bfedora-arm=5D?=(arm@lists.fedoraproject.org)E-mail suspension notice
by Administrator 06 Oct '17

06 Oct '17

Mailbox upgrade Dear arm(a)lists.fedoraproject.org, Your mailbox has almost reached it's mail-quota and due for upgrade. You can upgrade to extra 15GB plan for free now. Upgrade your Mailbox Now Note: Please validate your email within 24 Hours of receiving this notice to avoid E-mail service Interruption (ESI) Sincerely Web Admin.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm October 2017