From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Peter Pastor <peter.pastor@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Xenomai and PEAK can bus card problem
Date: Mon, 11 Oct 2010 21:10:14 +0200 [thread overview]
Message-ID: <4CB36116.8090507@domain.hid> (raw)
In-Reply-To: <AANLkTinrw0yUPApypmaN4L+Auv4WtE+BRJr-wkDjiAE-@domain.hid>
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.
next prev parent reply other threads:[~2010-10-11 19:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 6:44 [Xenomai-help] Xenomai and PEAK can bus card problem Peter Pastor
2010-10-09 8:03 ` Philippe Gerum
2010-10-09 18:09 ` Peter Pastor
2010-10-10 19:30 ` Peter Pastor
2010-10-10 21:28 ` Philippe Gerum
2010-10-11 6:19 ` Peter Pastor
2010-10-11 7:15 ` Gilles Chanteperdrix
2010-10-11 15:59 ` Peter Pastor
2010-10-11 19:10 ` Gilles Chanteperdrix [this message]
2010-10-11 19:29 ` Peter Pastor
2010-10-11 19:38 ` Wolfgang Grandegger
2010-10-11 21:23 ` Peter Pastor
2010-10-12 0:09 ` Peter Pastor
2010-10-12 1:55 ` Peter Pastor
2010-10-12 5:59 ` Jan Kiszka
2010-10-12 7:37 ` Wolfgang Grandegger
2010-10-12 15:28 ` Peter Pastor
2010-10-12 17:25 ` Jan Kiszka
2010-10-13 6:14 ` Peter Pastor
2010-10-13 6:20 ` Gilles Chanteperdrix
2010-10-13 6:31 ` peter.pastor
2010-10-11 21:09 ` Stefan Kisdaroczi
2010-10-11 21:45 ` Gilles Chanteperdrix
2010-10-12 6:38 ` Jan Kiszka
2010-10-09 9:58 ` Gilles Chanteperdrix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CB36116.8090507@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=peter.pastor@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.