qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Artyom Tarasenko <atar4qemu@gmail.com>
To: Bug 1588328 <1588328@bugs.launchpad.net>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Subject: Re: [Qemu-devel] [Bug 1588328] Re: Qemu 2.6 Solaris 9 Sparc Segmentation Fault
Date: Fri, 17 Jun 2016 13:42:37 +0200	[thread overview]
Message-ID: <CACXAS8CoXEx4zv9bpgYhgY=vWPo_CfJ5qxb5HqRkd-R4ehyONA@mail.gmail.com> (raw)
In-Reply-To: <20160614214445.25180.18565.malone@gac.canonical.com>

Can you guys check if the problem persists when qemu is launched with
the -singlestep option?
I think it's in general a good idea always check TCG-related problems
with -singlestep , because it helps to find out whether a bug is in
the optimizer or generator module of TCG.

Artyom

On Tue, Jun 14, 2016 at 11:44 PM, Mark Cave-Ayland
<mark.cave-ayland@ilande.co.uk> wrote:
> Thanks for the test case. It appears that this is a regression that
> occurred somewhere between 2.5 and 2.6 - bisecting now.
>
> --
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> https://bugs.launchpad.net/bugs/1588328
>
> Title:
>   Qemu 2.6 Solaris 9 Sparc Segmentation Fault
>
> Status in QEMU:
>   New
>
> Bug description:
>   Hi,
>   I tried the following command to boot Solaris 9 sparc:
>   qemu-system-sparc -nographic -boot d -hda ./Spark9.disk -m 256 -cdrom sol-9-905hw-ga-sparc-dvd.iso -serial telnet:0.0.0.0:3000,server
>
>   It seems there are a few Segmentation Faults, one from the starting of
>   the boot. Another at the beginning of the commandline installation.
>
>   Trying 127.0.0.1...
>   Connected to localhost.
>   Escape character is '^]'.
>   Configuration device id QEMU version 1 machine id 32
>   Probing SBus slot 0 offset 0
>   Probing SBus slot 1 offset 0
>   Probing SBus slot 2 offset 0
>   Probing SBus slot 3 offset 0
>   Probing SBus slot 4 offset 0
>   Probing SBus slot 5 offset 0
>   Invalid FCode start byte
>   CPUs: 1 x FMI,MB86904
>   UUID: 00000000-0000-0000-0000-000000000000
>   Welcome to OpenBIOS v1.1 built on Apr 18 2016 08:19
>     Type 'help' for detailed information
>   Trying cdrom:d...
>   Not a bootable ELF image
>   Loading a.out image...
>   Loaded 7680 bytes
>   entry point is 0x4000
>   bootpath: /iommu@0,10000000/sbus@0,10001000/espdma@5,8400000/esp@5,8800000/sd@2,0:d
>
>   Jumping to entry point 00004000 for type 00000005...
>   switching to new context:
>   SunOS Release 5.9 Version Generic_118558-34 32-bit
>   Copyright 1983-2003 Sun Microsystems, Inc.  All rights reserved.
>   Use is subject to license terms.
>   WARNING: /iommu@0,10000000/sbus@0,10001000/espdma@5,8400000/esp@5,8800000/sd@0,0 (sd0):
>         Corrupt label; wrong magic number
>
>   Segmentation Fault
>   Configuring /dev and /devices
>   NOTICE: Couldn't set value (../../sun/io/audio/sada/drv/audiocs/audio_4231.c, Line #1759 0x00 0x88)
>   audio may not work correctly until it is stopped and restarted
>   Segmentation Fault
>   Using RPC Bootparams for network configuration information.
>   Skipping interface le0
>   Searching for configuration file(s)...
>   Search complete.
>
>   ....
>
>   What type of terminal are you using?
>    1) ANSI Standard CRT
>    2) DEC VT52
>    3) DEC VT100
>    4) Heathkit 19
>    5) Lear Siegler ADM31
>    6) PC Console
>    7) Sun Command Tool
>    8) Sun Workstation
>    9) Televideo 910
>    10) Televideo 925
>    11) Wyse Model 50
>    12) X Terminal Emulator (xterms)
>    13) CDE Terminal Emulator (dtterm)
>    14) Other
>   Type the number of your choice and press Return: 3
>   syslog service starting.
>   savecore: no dump device configured
>   Running in command line mode
>   /sbin/disk0_install[109]: 143 Segmentation Fault
>   /sbin/run_install[130]: 155 Segmentation Fault
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1588328/+subscriptions
>



-- 
Regards,
Artyom Tarasenko

SPARC and PPC PReP under qemu blog: http://tyom.blogspot.com/search/label/qemu

  reply	other threads:[~2016-06-17 11:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 11:58 [Qemu-devel] [Bug 1588328] [NEW] Qemu 2.6 Solaris 9 Sparc Segmentation Fault Zhen Ning Lim
2016-06-02 20:45 ` [Qemu-devel] [Bug 1588328] " Mark Cave-Ayland
2016-06-04  4:40 ` Zhen Ning Lim
2016-06-04 12:45 ` Mark Cave-Ayland
2016-06-05  6:04 ` Zhen Ning Lim
2016-06-14  3:34 ` Zhen Ning Lim
2016-06-14 21:44 ` Mark Cave-Ayland
2016-06-17 11:42   ` Artyom Tarasenko [this message]
2016-06-17 12:35     ` Mark Cave-Ayland
2016-06-24 18:03 ` Mark Cave-Ayland
2016-06-28  4:38 ` Zhen Ning Lim
2016-06-28 21:26 ` Mark Cave-Ayland
2016-06-29  7:04 ` Zhen Ning Lim
2016-06-29 10:58 ` Mark Cave-Ayland
2016-06-29 14:32 ` Zhen Ning Lim
2016-06-29 20:33 ` Mark Cave-Ayland
2016-06-30  4:22 ` Zhen Ning Lim
2016-06-30  6:48 ` Mark Cave-Ayland
2016-06-30  8:33 ` Zhen Ning Lim
2016-06-30  9:40 ` Zhen Ning Lim
2016-06-30 13:41 ` Zhen Ning Lim
2016-07-01 16:26 ` Mark Cave-Ayland
2016-07-02 11:28 ` Zhen Ning Lim
2016-07-02 15:18 ` Mark Cave-Ayland
2016-07-02 18:13 ` Mark Cave-Ayland
2016-07-03  6:29 ` Zhen Ning Lim
2016-07-07 13:47 ` Mark Cave-Ayland
2017-01-19 14:25 ` Thomas Huth

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='CACXAS8CoXEx4zv9bpgYhgY=vWPo_CfJ5qxb5HqRkd-R4ehyONA@mail.gmail.com' \
    --to=atar4qemu@gmail.com \
    --cc=1588328@bugs.launchpad.net \
    --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).