Jan Kiszka wrote: > Jan Kiszka wrote: >> Stuart O Anderson wrote: >>> Oh - I forgot to mention - when I boot the machine, about 50% of the >>> time it comes up with the keyboard and mouse locked by the time it >>> gets to a login screen. The rest of the time it's fine until I run my >>> rtnet program. I suspect this is because some interrupt is randomly >>> getting assigned on boot to one processor or the other, and when it's >>> the wrong one things break?
That's why I would like to make things more deterministic by freezing the cpu affinity. Also, if the issue is a race between cpus, one could narrow it down a bit by pushing all Xenomai load on one cpu e.g. >>> >>> ipipe version: 2.0-08 >>> kernel config: attached >>> varying versions: will try this when I have more time >>> playing with affinities: I'm trying to find documentation for >>> /proc/xenomai/affinity - do you know where it is located? >> Don't think we have any, however the usage is straightforward: This is a >> bitmask describing the CPUs on which Xenomai threads and IRQs that will >> be created in the future shall be bound to. Just set it before firing up >> RTnet and your application. >> >> BTW, I found a hint on an "IRQ19 issue" in my archive, but I still need >> to interview my colleague on details. We had such an issue with a SCSI RAID controller. Even after deep debugging inside ipipe, the problem looked like a race during hardware initialization and finally disappeared after reconfiguring the SCSI controller's firmware. So we closed the issue. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
