All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Tianchi Huang <gz.eddie.htc@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Xenomai 3.0-rc3 Interruption on Arietta G25 (AT91SAM9G25 chip)
Date: Thu, 26 Mar 2015 17:40:26 +0100	[thread overview]
Message-ID: <20150326164026.GX15125@hermes.click-hack.org> (raw)
In-Reply-To: <20150326163548.GW15125@hermes.click-hack.org>

On Thu, Mar 26, 2015 at 05:35:48PM +0100, Gilles Chanteperdrix wrote:
> On Thu, Mar 26, 2015 at 05:26:57PM +0100, Tianchi Huang wrote:
> > eddie@eddie-VirtualBox:~/Desktop/xenomai-3/linux-3.14.17/arch/arm/mach-at91$
> > objdump -t *.o | grep gpio_irq_handler -H
> > (standard input):0000c17c l     F .text 000000d4 gpio_irq_handler
> > (standard input):0018db84 l     F .text 000000d0 gpio_irq_handler
> > eddie@eddie-VirtualBox:~/Desktop/xenomai-3/linux-3.14.17/arch/arm/mach-at91$
> > objdump -t *.o > log
> 
> Look for the symbol gpio_irq_handler in the vmlinux file, then run
> addr2line to see where the symbol comes from.

Actually you already have the address of the problematic
gpio_irq_handler in the backtrace you sent. If you did not change
any kernel option, it is still valid, so you just need to run
addr2line against the vmlinux binary to find where the function is
defined. 

-- 
					    Gilles.


  reply	other threads:[~2015-03-26 16:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 11:07 [Xenomai] Xenomai 3.0-rc3 Interruption on Arietta G25 (AT91SAM9G25 chip) Tianchi Huang
2015-03-23 22:09 ` Gilles Chanteperdrix
2015-03-24 15:55   ` Tianchi Huang
2015-03-24 16:01     ` Gilles Chanteperdrix
2015-03-24 16:13       ` Gilles Chanteperdrix
2015-03-25  8:58         ` Tianchi Huang
     [not found]           ` <CAJT0owE7vtJDWM289=4cNR_LuUqPWAO60nvg9D0NiTQWeN9Xbg@mail.gmail.com>
2015-03-26 14:31             ` Gilles Chanteperdrix
2015-03-26 14:52               ` Tianchi Huang
2015-03-26 14:54                 ` Gilles Chanteperdrix
2015-03-26 15:19                   ` Tianchi Huang
2015-03-26 15:40                   ` Tianchi Huang
2015-03-26 15:44                     ` Gilles Chanteperdrix
2015-03-26 15:58                       ` Tianchi Huang
2015-03-26 16:00                         ` Gilles Chanteperdrix
2015-03-26 16:26                           ` Tianchi Huang
2015-03-26 16:35                             ` Gilles Chanteperdrix
2015-03-26 16:40                               ` Gilles Chanteperdrix [this message]
2015-03-26 16:56                               ` Tianchi Huang
2015-03-26 16:57                                 ` Gilles Chanteperdrix
2015-03-26 17:25                                   ` Tianchi Huang
2015-03-26 14:32             ` Gilles Chanteperdrix
2015-03-26 17:08               ` Paul Janzen
2015-03-26 18:30                 ` Gilles Chanteperdrix
2015-03-26 18:51                   ` Paul Janzen
2015-03-26 18:58                     ` Gilles Chanteperdrix
2015-03-26 19:32                       ` Paul Janzen
2015-03-26 19:52                         ` 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=20150326164026.GX15125@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=gz.eddie.htc@gmail.com \
    --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.