From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <512ba0a9-fa7b-acd8-6dc6-a3032481934e@siemens.com> Date: Thu, 6 Jan 2022 09:18:58 +0100 MIME-Version: 1.0 Subject: Re: rtnet rt_igb I210 not working with ARM Content-Language: en-US References: From: Jan Kiszka In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Yann Le Chevoir , "xenomai@xenomai.org" On 06.01.22 00:39, Yann Le Chevoir via Xenomai wrote: >>> Hello, >>> >>> I have an issue with rt_igb not working with an Intel I210 on ARM (see >>> system configuration below). >>> With Wireshark, looks like rtping is sending garbage on the network >>> (see below). >>> I notice there is no interrupt in /proc/xenomai/irq (see below). >>> Looks like other people got issues with I210 in the past but I am not >>> sure if they were similar and I am not able to find any conclusion. >>> >>> Below, I show you how I am inserting the kernel module + how I am able >>> to have it working with igb (no realtime) and rt_fec (different driver >>> for the other Ethernet controller on the same board). >>> >>> What can I do to solve this issue? >>> Is there anything else I can try to give you more data? >>> >> >> Could you check if that card works in a standard PC (x86-64) with RTnet? >> Could you also check if latest 3.2.1 makes any difference? Not all fixes on >> RTnet have been backported to very-old-stable. >> >> Jan > > Hello Jan, all, > > Happy new year! > > Sorry for the delay, I needed to update my Linux kernel > (Freescale/linux-fslc) from version 4.9.67 to version 5.4.147 to be able > to compile Xenomai 3.2.1. I am still using I-pipe, not Dovetail, right? Yes, everything up to and including 5.4 is I-pipe, 5.10 and later is dovetail. > I notice that the type of interruption changed since the previous version: > we now have "Using MSI-X interrupts" instead of "Using MSI interrupts". Maybe the host controller of your SoC gained MSI-X support betwen 4.9 and 5.4? Then both the standard driver and rt_igb would try to use that instead (MSI is legacy). > And there is this new error: "Error 2 getting interrupt" which prevents to > have rteth0 configured (see below). That's different from last time. > I notice that the driver igb itself does not work with the new Xenomai > kernel (see below). That's also different from last time. I confirmed that > it works with the non-xenomai kernel though (same kernel 5.4.147 without > the I-pipe patch). 5.4.147 - that is no official ipipe-arm release. Did you integrate the patch yourself base on which I-pipe core revision? And how about ipipe-core-5.4.151-arm-4? > Note: to have the driver igb working with the Xenomai kernel, I can use > the legacy interrupts ("pci=nomsi" on the kernel command line). > Does this "error 2" sound familiar? Is there anything else I can try? ENOENT - you could try search the code for sources of this error code. But it may also come from the PCI or MSI core. > > I did not try with a standard x86-64 PC yet. Do you think it may still > help? I have the feeling that this irq issue is very specific to my arm > SOC. Not unlikely. I'm afraid there is no way around digging for the source of the error code. That can help to understand better what goes wrong Jan -- Siemens AG, Technology Competence Center Embedded Linux