Peter Pastor wrote:
> Hey Gilles,
>
> Thanks for the hint. I "fixed" this problem by loading the nvidia driver
> (instead of nv) as default. Now the graphic cards uses IRQ 24 which does not
> collide with IRQ 11 of the CAN bus card (see attached lspci.txt).
>
> The only other device that uses IRQ 11 is
> # 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port
> [8086:3406] (rev 13)
>
> But I guess that is ok, is it ? I checked the FAQs and went through the list
> but I feel I can't do much. I will try a few things and disable everything
> that is unneeded. The FAQ list also suggests to enable CONFIG_PCI_MSI which
> is disabled right now. What would now be a reasonable thing to do ?
Keep PCI_MSI disabled. The FAQ is wrong and should be fixed.
>
> How can I find out and about which device is causing the address space
> collision ?
>
> # address space collision: host bridge window [mem 0xd7f00000-0xe0000000]
> conflicts with PCI Bus 0000:00 [mem 0xe0000000-0xf7ffffff]
>
> I attached the syslog of the latest boot. I enabled some debugging infos
> which hopefully allow to trace down the problem. Interestingly, this time,
> the kernel spit out
>
> # RT-Socket-CAN 0.90.2 - (C) 2006 RT-Socket-CAN Development Team
>
> right before it froze.
You should try and put some printks in RTCan code to see how far it
goes. But I guess Wolfgang may be of more help.
--
Gilles.
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
