qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: OpenBIOS update broke Linux boot on qemu-system-sparc64
Date: Fri, 24 Jan 2020 17:51:41 +0100	[thread overview]
Message-ID: <82c4a7e1-aafc-70e5-b00a-bd56c9cd1b61@redhat.com> (raw)


 Hi Mark,

today, I noticed that the Sparc64 image from the QEMU advent calendar
2018 does not work anymore with the recent QEMU:

 https://www.qemu-advent-calendar.org/2018/download/day23.tar.xz

The Linux kernel now crashes during the boot process.

Bisecting the issues pointed to:

 commit e9deadb1c10351213845428de7591931f790f111
 Update OpenBIOS images to 3464681b built from submodule.

Do you maybe have an idea what might be going wrong here?

 Thomas



             reply	other threads:[~2020-01-24 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 16:51 Thomas Huth [this message]
2020-01-27  6:50 ` OpenBIOS update broke Linux boot on qemu-system-sparc64 Mark Cave-Ayland

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=82c4a7e1-aafc-70e5-b00a-bd56c9cd1b61@redhat.com \
    --to=thuth@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --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).