From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39430)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1XgeEA-0000JD-Qn
	for qemu-devel@nongnu.org; Tue, 21 Oct 2014 14:32:20 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1XgeE1-0002yy-Tx
	for qemu-devel@nongnu.org; Tue, 21 Oct 2014 14:32:14 -0400
Received: from mx1.redhat.com ([209.132.183.28]:38713)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1XgeE1-0002yt-MN
	for qemu-devel@nongnu.org; Tue, 21 Oct 2014 14:32:05 -0400
Message-ID: <1413916318.14632.32.camel@nilsson.home.kraxel.org>
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Tue, 21 Oct 2014 20:31:58 +0200
In-Reply-To: <CAFEAcA8pJfuMfi9=LnXNXOzCnusjNsaDjeGOXdgWksNkjiOQBw@mail.gmail.com>
References: <1413898431.14632.25.camel@nilsson.home.kraxel.org>
	<CAFEAcA8pJfuMfi9=LnXNXOzCnusjNsaDjeGOXdgWksNkjiOQBw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] boot arm fedora via u-boot in qemu
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

  Hi,

> > Any hints how to go on with debugging?
> 
> Use the gdbstub to find out where the kernel is getting
> stuck? "Kernel produces no output" just means "we didn't
> get far enough through early boot for the kernel to start
> sending output to the UART. You might find it useful to
> turn on the earlyprintk support, and/or to build the
> kernel with debug-UART-via-semihosting and add the
> -semihosting argument to the QEMU command line.

earlyprintk doesn't change anything.

Ok, that leaves gdb.  Stuck here:

(gdb) info reg
[ ... ]
lr       0xc0868bf4
pc       0xc04eee18

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.

cheers,
  Gerd