All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Galakhov <agalakhov@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Ipipe hangs on ARM MINI2440 after switching clocksource
Date: Thu, 28 Apr 2011 22:12:22 +0600	[thread overview]
Message-ID: <4DB991E6.90403@domain.hid> (raw)
In-Reply-To: <4DB94C9C.7080904@domain.hid>

On 04/28/2011 05:16 PM, Gilles Chanteperdrix wrote:
> Ok. Better try without this patch first, then try reapplying the patch
> when you are certain that everything else works correctly. The patch
> enables some assembly code that was never actually tested. On my side, I
> will try and test it separately.
So I tried to trace the kernel using gdb and jtag.

It enters the interrupt handler over and over again. If I set a
breakpoint at __ipipe_grab_irq, I see the following:
__ipipe_grab_irq (irq=37, regs=0xc3dd3f08)
__ipipe_grab_irq (irq=30, regs=0xc3dd3f08)
__ipipe_grab_irq (irq=37, regs=0xc3dd3f08)
__ipipe_grab_irq (irq=30, regs=0xc3dd3f08)
and so on. Note the strict order of IRQs 30 and 37.

According to /proc/interrupts running vanilla kernel, these IRQs are:
 30:      36105         s3c  S3C2410 Timer Tick
 37:      12464         s3c  s3c-mci

As far as I can see, these two IRQs are both handled by the same code in
ipipe. And they are both periodic and occur so frequently that they
interrupt each other's handler. Looks like they aren't masked properly
for some reason. So the kernel loops infinitely in these two interrupt
handlers and does never exit them!

--
Alex


  parent reply	other threads:[~2011-04-28 16:12 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 [this message]
2011-04-28 17:05         ` Gilles Chanteperdrix
2011-04-28 18:43           ` Alexey Galakhov
2011-04-28 19:01             ` Gilles Chanteperdrix
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=4DB991E6.90403@domain.hid \
    --to=agalakhov@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=gilles.chanteperdrix@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.