qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Fedora ARM <arm@lists.fedoraproject.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] boot arm fedora via u-boot in qemu
Date: Wed, 22 Oct 2014 00:16:53 +0200	[thread overview]
Message-ID: <1413929813.7230.1.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <CAFEAcA8Ufm3FpwD-Q3WEeau+GMXqniV+gNhq0pa+i_-KfCb+kg@mail.gmail.com>

On Di, 2014-10-21 at 20:11 +0100, Peter Maydell wrote:
> On 21 October 2014 19:31, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > Looking them up in System.map finds me:
> >
> > c04eee18 T __loop_delay
> > c0868a28 T panic
> >
> > Ok, so the kernel came successfully though the uncompressing +
> > relocation + enable paging, but paniced before earlyprintk can print
> > something.
> >
> > Guess I'll have to fetch the vmlinux with debug info so I can get a full
> > stack trace and see where it paniced, but not today.
> 
> IIRC you should be able to fish the kernel log out of the
> memory buffer where it's currently sitting. I forget what
> the symbol name for that is, though.

Hmm, it says "Ignoring memory range 0x60000000 - 0x80000000".
That looks fishy.

"if (base < phys_offset)" in early_init_dt_add_memory_arch triggers.
Seems __pa() isn't working correctly.

Any chance this can be caused by setting some uboot env var incorrectly?
There is a confusing high number of *_addr_* variables ...

cheers,
  Gerd

  reply	other threads:[~2014-10-21 22:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 13:33 [Qemu-devel] boot arm fedora via u-boot in qemu Gerd Hoffmann
2014-10-21 13:42 ` Hans de Goede
2014-10-21 17:01   ` Gerd Hoffmann
2014-10-21 13:47 ` Peter Maydell
2014-10-21 18:31   ` Gerd Hoffmann
2014-10-21 19:11     ` Peter Maydell
2014-10-21 22:16       ` Gerd Hoffmann [this message]
2014-10-22  9:59         ` Gerd Hoffmann
2014-10-26 19:29           ` Rabin Vincent

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=1413929813.7230.1.camel@nilsson.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=arm@lists.fedoraproject.org \
    --cc=crobinso@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).