From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Hartkopp Subject: Re: sja1000 interrupt problem Date: Wed, 11 Dec 2013 17:59:54 +0100 Message-ID: <52A89A0A.7010803@hartkopp.net> References: <52831FC7.3040509@hartkopp.net> <201311131008.55018.pisa@cmp.felk.cvut.cz> <5287E6B2.8020709@hartkopp.net> <85256584a266750b1330cfae8bebd55c@grandegger.com> <5288D236.403@hartkopp.net> <5288FB91.9050703@grandegger.com> <52892B21.9000501@grandegger.com> <333c0fd4238558062478212eb0704b04@grandegger.com> <52A71B6C.3050600@hartkopp.net> <8e5f03acb59e16a0ebcd31499a533f15@grandegger.com> <52A73BB1.7070701@hartkopp. net> <52A783B2.5020002@grandegger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mo-p00-ob.rzone.de ([81.169.146.160]:51165 "EHLO mo-p00-ob.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751408Ab3LKQ76 (ORCPT ); Wed, 11 Dec 2013 11:59:58 -0500 In-Reply-To: <52A783B2.5020002@grandegger.com> Sender: linux-can-owner@vger.kernel.org List-ID: To: Wolfgang Grandegger Cc: Austin Schuh , Pavel Pisa , linux-can@vger.kernel.org Bad news. Unfortunately the patch did not have the wanted effect and the interrupt #19 dropped again the late evening. I'm currently running the setup overnight with the same kernel but only without -rt to make sure it definitely is a -rt issue. On 10.12.2013 22:12, Wolfgang Grandegger wrote: >> >> for (i = 0; i < channels; i++) { >> + > > Please do not add unrelated changes. > Was not intended. I added/removed some code here ... > > BTW: while browsing Austin's function trace I realized that we do access > also the inactive device if interrupts are shared. I think we should use > a shadow register variable for SJA1000_IR. Hope to find some time over > the weekend to provide a patch. ?? AFAIK the interrupt is registered in sja1000_open (=> ifconfig up). So why do we access an inactive (ifconfig down) device then? Regards, Oliver