On 09.07.19 18:33, Jan Kiszka wrote: > On 09.07.19 18:21, Lange Norbert wrote: >> Hello, >> >> maxcpus=1 still causes the spurious int, this time fully locking up. >> >> I attached the debug/irq directory after the cause. >>> Some things that might be relevant: >> - the SOC would use PINCTRL_BROXTON under linux, but this is disabled (not >> fixed up for Xenomai) >> - I have the regular igb driver in use, and am unbinding the network card >> prior to binding the rt_igp driver >> > > Thanks. What's the interrupt number that Xenomai is using? Should be the same > that the Linux driver is using as well.
Found already: Should be IRQ 130-132 for device 00:03.0. If the directory state was like that while Xenomai was still holding those interrupts, the problem it that there are no vectors assigned to them. Can you confirm that rt_igb was still loaded and the interface was up? Are those interrupts MSI or MSI-X? Can't read that from the logs. I probably need to get some rt_igb running somewhere... Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
