From: Wolfgang Grandegger <wg@grandegger.com>
To: Willy Lambert <lambert.willy@gmail.com>
Cc: linux-can@vger.kernel.org
Subject: Re: Problem with so Loved interrupts
Date: Thu, 10 Nov 2011 10:52:01 +0100 [thread overview]
Message-ID: <4EBB9EC1.1040508@grandegger.com> (raw)
In-Reply-To: <CAKvQZ_0RhjE3+OBLposEBoU8UL66_3JfV237bWnL5pR0HrRMVQ@mail.gmail.com>
On 11/10/2011 09:56 AM, Willy Lambert wrote:
> 2011/11/9 Willy Lambert <lambert.willy@gmail.com>:
>> ---------- Forwarded message ----------
>> From: Willy Lambert <lambert.willy@gmail.com>
>> Date: 2011/11/9
>> Subject: Problem with so Loved interrupts
>> To: linux-can <linux-can@vger.kernel.org>
>>
>>
>> Hi all,
>> I am having interruption problems again.
>> The symptom is a /proc/interrupt or /proc/xenomia/irq not rising.
>> I am sure of my Hardware because I used an archive of a working linux
>> system and it works. So the wired are Ok, device is responding, BIOS
>> is well configured.
>> I check this : http://comments.gmane.org/gmane.network.socketcan.user/813,
>> and I am sure it is not the case since it worked with the old system
>> and it has been electrically protected.
>> I also recheck this
>> http://old.nabble.com/Re%3A-Trying-to-use-socketCan-on-an-Ixxat-PC-I-04-104-p30752686.html
>> but once again, everything is ok with old software.
Please describe "old system" and "old software".
>> So what did I changed ? I was updating many of my dependencies on my
>> target and even tried 64b, so the road have been very long. What I
>> accuse much is my new kernel. Before it was a 2.6.35.7, now it is a
>> 2.6.38.8 with xenomai patches. I may have forgot to select a kernel
>> option for interrupts...
Well, you get other interrupts and therefore it seem to be specific to
the CAN hardware and the bus/slot it is connected to. You say that it
works with your 2.6.35.7 kernel but does not with 2.6.38.8 on the
*identical* hardware, right? Then I would check the kernel configs for
PNP related differences.
Wolfgang.
next prev parent reply other threads:[~2011-11-10 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKvQZ_1Sf8xSJ2dGC7fO+mBFPQj_rwaeuiYcpJozUD0V5P1dYA@mail.gmail.com>
2011-11-09 18:28 ` Fwd: Problem with so Loved interrupts Willy Lambert
2011-11-10 8:56 ` Willy Lambert
2011-11-10 9:52 ` Wolfgang Grandegger [this message]
2011-11-10 10:56 ` Willy Lambert
2011-11-10 12:07 ` Wolfgang Grandegger
2011-11-10 17:12 ` Willy Lambert
2011-11-14 13:13 ` Willy Lambert
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=4EBB9EC1.1040508@grandegger.com \
--to=wg@grandegger.com \
--cc=lambert.willy@gmail.com \
--cc=linux-can@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox