From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Alexey Galakhov <agalakhov@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Ipipe hangs on ARM MINI2440 after switching clocksource
Date: Thu, 28 Apr 2011 21:01:12 +0200 [thread overview]
Message-ID: <4DB9B978.2010200@domain.hid> (raw)
In-Reply-To: <BANLkTik_MeMvpq2x7N0WmML97uW5=HxsLw@domain.hid>
Alexey Galakhov wrote:
> 2011/4/28 Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
>
>> Well, is not that an effect of kgdb? The timer tick occurs 100 or 1000
>> times per second, so, you can not keep up with gdb. The fact that a new
>> interrupts may occur why handling another interrupt is normal with Adeos.
>>
>> It is not to say that there is no irq loop, but we can not conclude from
>> the symptoms you are describing.
>>
>>
> I understand this possibility. I did a simple test: just switched the
> processor back and forth between "run" and "halt" many many times. I did it
> on hardware (JTAG) level so I believe the CPU was running at full speed. And
> it was catched in one of these interrupt handlers every time, I've never
> seen it in any other function. Thus I believe it was doing nothing else. The
> stack is suspicious as well: it has lots of IRQ stuff, nothing but IRQs,
> even if I interrupt the CPU for the first time.
>
>
>
>> Is there an earlier version of the I-pipe patch which was working?
>>
>>
> Unfortunately I've not tested earlier versions. I'll try. They say it worked
> with linux 2.6.29 (ipipe version not mentioned, but it was just before the
> mini2440 timer3 patch was submitted to mainstream):
> http://www.friendlyarm.net/forum/topic/598
>
> Seems that these guys have the same problem:
> http://www.friendlyarm.net/forum/topic/1108
So, have you tried reverting the timer3 patch?
--
Gilles.
next prev parent reply other threads:[~2011-04-28 19:01 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 13:05 [Adeos-main] Ipipe hangs on ARM MINI2440 after switching clocksource Alexey Galakhov
2011-04-27 15:56 ` Gilles Chanteperdrix
2011-04-27 17:49 ` Alexey Galakhov
2011-04-27 17:55 ` Gilles Chanteperdrix
2011-04-27 18:10 ` Gilles Chanteperdrix
2011-04-28 11:12 ` Alexey Galakhov
2011-04-28 11:16 ` Gilles Chanteperdrix
2011-04-28 11:24 ` Alexey Galakhov
2011-04-28 11:27 ` Gilles Chanteperdrix
2011-04-28 13:37 ` Alexey Galakhov
2011-04-28 13:47 ` Gilles Chanteperdrix
2011-04-28 16:12 ` Alexey Galakhov
2011-04-28 17:05 ` Gilles Chanteperdrix
2011-04-28 18:43 ` Alexey Galakhov
2011-04-28 19:01 ` Gilles Chanteperdrix [this message]
2011-04-28 19:28 ` Alexey Galakhov
2011-04-28 19:32 ` Gilles Chanteperdrix
2011-04-28 19:47 ` Alexey Galakhov
2011-04-29 6:44 ` Gilles Chanteperdrix
2011-04-29 6:49 ` Gilles Chanteperdrix
2011-04-29 11:08 ` Alexey Galakhov
2011-04-29 11:32 ` Gilles Chanteperdrix
2011-04-29 12:08 ` Alexey Galakhov
2011-04-29 12:14 ` Gilles Chanteperdrix
2011-04-29 13:09 ` Alexey Galakhov
2011-04-30 9:55 ` Gilles Chanteperdrix
2011-04-30 17:33 ` Alexey Galakhov
2011-04-30 17:39 ` Alexey Galakhov
2011-04-30 18:41 ` Alexey Galakhov
2011-04-30 20:14 ` Gilles Chanteperdrix
2011-04-30 20:28 ` Alexey Galakhov
2011-04-30 22:01 ` Gilles Chanteperdrix
2011-04-30 22:36 ` Gilles Chanteperdrix
2011-05-01 14:23 ` Alexey Galakhov
2011-05-01 14:34 ` Gilles Chanteperdrix
2011-04-28 18:46 ` Alexey Galakhov
2011-04-28 20:33 ` 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=4DB9B978.2010200@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=adeos-main@gna.org \
--cc=agalakhov@domain.hid \
/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.