December 2017 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Raspberry Pi 3 interrupt handling
by Roger Oberholtzer 13 Dec '17

13 Dec '17

We have written a minimal kernel interrupt handler for the Raspberry Pi 3. It is running the current 64-bit Tumbleweed kernel. I am curious about the rate of interrupts that we might be able to capture. The ISR does little other than run when a raising edge interrupt happens. We are looking at /proc/interrupts to see how many interrupts have happened. We see that at around 23 kHz we begin to loose interrupts. The system is not doing anything else. Does that seem reasonable? I have not seen any good discussion of this. I think it is rather low. I am guessing that the issue is how the Linux kernel responds to interrupts. The housework in setting things up so that the interrupt can run must be the resource hog. Opinions? Suggestions? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 9

[opensuse-arm] [aarch64] TW on Pinebook?
by Alex Naumov 12 Dec '17

12 Dec '17

Hello, yesterday I finally got my 14'' Pinebook [1]. There is Ubuntu 16.04 MATE as a default OS, but I would like to use openSUSE TW on it of course. So, I found raw.xz XFCE-image for aarch64 [2] and used this command "to burn" image on the microSD card: # unxz -c openSUSE-Tumbleweed-ARM-XFCE-efi.aarch64-2017.06.10-Build2.3.raw.xz | sudo dd of=/dev/mmcblk1p No success. Pinebook tried to boot from microSD card, but... it seems that there is something wrong with bootloader. Here [3] I found this command: # xzcat openSUSE-Tumbleweed-ARM-XFCE-efi.aarch64-2017.06.10-Build2.3.raw.xz | dd bs=4M of=/dev/ mmcblk1p oflag=sync Exactly the same... image is there, echo $? tells 0, but pinebook ignore it. Image on microSD card is marked as a bootable. I checked it with parted(8). I asked Google and it showed me this [4]. This is HOWTO for fedora 21 on Cubietruck, but there is one interesting thing: step (4) Write U-Boot to Media. Do we also need to install bootloader extra? Because, as I said, for me it seems like a bootloader problem. If yes, where is this script or documentation about it? Also I would ask about rootfs-images. Do we have some information/HOWTOs about these? Cheers, Alex [1] https://www.pine64.org/?page_id=3707 [2] http://download.opensuse.org/ports/aarch64/tumbleweed/images/openSUSE-Tumbl… [3] https://en.opensuse.org/HCL:AArch64_EFI [4] https://kashyapc.fedorapeople.org/arm/installing-Fedora-21-on-microSD-card-… -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 7

[opensuse-arm] Raspberry Pi3 fail to boot
by Manu Maier 11 Dec '17

11 Dec '17

Hello, the last Tumbleweed image[1] of Raspberry Pi 3 fails to boot with the message: [ 5.646965] Initramfs unpacking failed: write error [ 5.901972] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007 [ 5.901972] [ 5.911609] CPU: 2 PID: 1 Comm: init Not tainted 4.14.4-1-default #1 [ 5.918290] Hardware name: raspberrypi rpi/rpi, BIOS 2017.11 11/16/2017 [ 5.925244] Call trace: [ 5.927832] [<ffff000008089ea8>] dump_backtrace+0x0/0x248 [ 5.933514] [<ffff00000808a114>] show_stack+0x24/0x30 [ 5.938833] [<ffff0000089192d4>] dump_stack+0x9c/0xc0 [ 5.944149] [<ffff0000080ce688>] panic+0x12c/0x2ac [ 5.949193] [<ffff0000080d3b04>] do_exit+0x99c/0x9a0 [ 5.954417] [<ffff0000080d3b98>] do_group_exit+0x40/0xb0 [ 5.960008] [<ffff0000080e021c>] get_signal+0x2dc/0x548 [ 5.965505] [<ffff000008089178>] do_signal+0x70/0x3f0 [ 5.970820] [<ffff000008089770>] do_notify_resume+0xd0/0x120 [ 5.976772] Exception stack(0xffff00000802bec0 to 0xffff00000802c000) [ 5.983547] bec0: 0000ffffaa00b688 0000000000000000 0000000000000978 0000ffffaa00b680 [ 5.991781] bee0: 0000ffffaa00c000 0000ffffaa00b688 0000000000000003 756e696c65736269 [ 6.000016] bf00: 00000000000000de 0000fffff5ec40e0 0000000000042a98 000000000002f000 [ 6.008251] bf20: 0000fffff5ec40e0 0000000000040688 0000ffffaa2908f8 0000000000000887 [ 6.016484] bf40: 0000ffffaa290f88 0000ffffaa276c18 0000000000000001 0000000000000000 [ 6.024718] bf60: 0000000000000004 0000ffffaa290000 0000000000000000 0000000000000002 [ 6.032952] bf80: 0000ffffaa28cc20 0000fffff5ec40b0 0000fffff5ec4490 0000fffff5ec44d0 [ 6.041186] bfa0: 0000000000000002 0000fffff5ec4240 0000ffffaa26679c 0000fffff5ec4080 [ 6.049421] bfc0: 0000ffffaa27924c 0000000020000000 0000ffffaa00a000 00000000ffffffff [ 6.057655] bfe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 6.065890] [<ffff0000080836c0>] work_pending+0x8/0x10 [ 6.071299] SMP: stopping secondary CPUs [ 6.075431] Kernel Offset: disabled [ 6.079100] CPU features: 0x002004 [ 6.082675] Memory Limit: none [ 6.085893] Rebooting in 90 seconds.. [1] openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2017.12.04-Build2.8.raw.xz Regards, Manu

3 3

[opensuse-arm] Cloud ARM servers
by Bill Merriam 10 Dec '17

10 Dec '17

I discovered today that a hosting provider in Europe offers very cheap ARMv7 and ARMv8 cloud servers. https://www.scaleway.com/ The following observations are from a few hours of testing and may not be correct. It appears the ARM servers are NOT virtualized but run on special miniature servers. The ARMv7 uses a Marvell 385 SOC and the ARMv8 uses a Cavium SOC. Marvell is in the process of buying Cavium. Opensuse does not generally appear among the offered distributions. The exception to this was opensuse 13.2 on the ARMv7 system. I was able to upgrade it to 42.3 but they don't use the kernel from my image. I guess they need a custom kernel. Their kernel has many limitations. It doesn't support iptables so you can't have a firewall. I am hoping someone can convince them to offer an ARMv8 Leap 42.3 with a decent kernel. Bill -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1