All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Baozi <baozich@gmail.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Domain 0 crashed when booting OMAP5 uEVM
Date: Tue, 13 Aug 2013 17:10:07 +0800	[thread overview]
Message-ID: <20130813091007.GA16513@cbz-workstation> (raw)
In-Reply-To: <5208D969.6090708@linaro.org>

On Mon, Aug 12, 2013 at 01:47:37PM +0100, Julien Grall wrote:
> > (XEN)     size=2 sign=0 write=0 reg=0
> > (XEN)     eat=0 cm=0 s1ptw=0 dfsc=7
> > (XEN) dom0 IPA 0x000000004ae06704
> > (XEN) P2M @ 02fdbf80 mfn:0xfedfc
> > (XEN) 1ST[0x1] = 0x00000000fedfe6ff
> > (XEN) 2ND[0x57] = 0x00000000ac9796ff
> > (XEN) 3RD[0x6] = 0x0000000000000000
> > (XEN) ----[ Xen-4.4-unstable  arm32  debug=y  Not tainted ]----
> > (XEN) CPU:    0
> > (XEN) PC:     c0033410
> 
> To help you, you can use "addr2line -e vmlinux address" to find the
> faulty line in linux. Where address is your pc.

$addr2line -e vmlinux 0xc0033410
/home/cbz/src/linux/arch/arm/mach-omap2/prminst44xx.c:52

I checked the codes around line 52 in prminst44xx:

45 /* Read a register in a PRM instance */
46 u32 omap4_prminst_read_inst_reg(u8 part, s16 inst, u16 idx)
47 {
48         BUG_ON(part >= OMAP4_MAX_PRCM_PARTITIONS ||
49                part == OMAP4430_INVALID_PRCM_PARTITION ||
50                !_prm_bases[part]);
51         return __raw_readl(_prm_bases[part] + inst + idx);
52 }

So I think I have to implement a .specific_mapping such as
exynos5_specific_mapping in arch/arm/platforms/exynos5.c?

Just one more question. Read from OMAP5 datasheet, its IO memory address
space ranges from 0 to 2G (with holes of course). Do I have to map all
of them?

Cheers,

Baozi

  parent reply	other threads:[~2013-08-13  9:10 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 12:24 Domain 0 crashed when booting OMAP5 uEVM Chen Baozi
2013-08-12 12:47 ` Julien Grall
2013-08-12 14:15   ` Andrii Anisov
2013-08-12 14:30   ` Andrii Anisov
2013-08-12 15:08     ` Julien Grall
2013-08-12 15:32       ` Andrii Anisov
2013-08-12 15:40         ` Andrii Anisov
2013-08-13  2:40           ` Chen Baozi
2013-08-13  7:56     ` Chen Baozi
2013-08-13  8:45       ` Chen Baozi
2013-08-13  9:55         ` Julien Grall
2013-08-12 14:54   ` Andrii Anisov
2013-08-13  9:10   ` Chen Baozi [this message]
2013-08-13  9:36     ` Andrii Anisov
2013-08-13  9:40       ` Chen Baozi
2013-08-13  9:58       ` Julien Grall
2013-08-14  9:46         ` Chen Baozi
2013-08-14  9:55           ` Julien Grall
2013-08-14 12:38             ` Chen Baozi
2013-08-15  9:13               ` Julien Grall
2013-08-15  9:47                 ` Chen Baozi
2013-08-15 10:07                   ` Julien Grall
2013-08-15 10:54                     ` Andrii Anisov
2013-08-15 11:00                       ` Chen Baozi
2013-08-15 11:07                         ` Andrii Anisov
2013-08-15 10:59                     ` Chen Baozi
2013-08-15 12:24                       ` Ian Campbell
2013-08-15 12:43                         ` Julien Grall
2013-08-14 16:07             ` Andrii Anisov
2013-08-14 19:47               ` Julien Grall
2013-08-14  9:53       ` Chen Baozi
2013-08-14 16:03         ` Andrii Anisov
2013-08-15  2:31           ` Chen Baozi
2013-08-15  7:37             ` Chen Baozi
2013-08-15  8:34               ` Andrii Anisov
2013-08-15  8:51                 ` Chen Baozi
2013-08-15  9:12                   ` Andrii Anisov
2013-08-15  9:17                     ` Chen Baozi
2013-08-15  8:45               ` Andrii Anisov

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=20130813091007.GA16513@cbz-workstation \
    --to=baozich@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=xen-devel@lists.xen.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.