All of lore.kernel.org
 help / color / mirror / Atom feed
From: milasudril <milasudril@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1295587] Re: Temporal freeze and slowdown while using emulated sb16
Date: Sun, 26 Mar 2017 15:30:13 -0000	[thread overview]
Message-ID: <20170326153013.30419.50510.malone@soybean.canonical.com> (raw)
In-Reply-To: 20140321093246.9788.71300.malonedeb@soybean.canonical.com

On Windows 98 SE:

 * SB16: System hangs as described in this bug report
 * ES1370: Causes system freeze with back screen at boot time
 * AC97 (as suggested here: https://smcv.pseudorandom.co.uk/2015/discworldnoir/): BSODs during the installation
 * GUS: Device is not even detected

Conclusion: At the moment, there is no way to get audio output from
Windows 98 se VM.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1295587

Title:
  Temporal freeze and slowdown while using emulated sb16

Status in QEMU:
  New

Bug description:
  I have been carrying around this bug since previous versions and on
  different machines: When I use the -soundhw sb16 option, while playing
  any sound on the virtual machine it temporally freezes the emulated
  machine and loops the last bit of such sound effect for 1-2 minutes,
  then goes back to normal speed (until a new sound is played).

  Console shows:

   sb16: warning: command 0xf9,1 is not truly understood yet
   sb16: warning: command 0xf9,1 is not truly understood yet
  (...)
  main-loop: WARNING: I/O thread spun for 1000 iterations

  -One of my emulated machines is Windows 3.11: I managed to overrun
  this bug by switching from the local 1.5 version of the sound blaster
  driver to the 1.0, although since I updated qemu it freezes that
  machine, so I can't test if it still works.

  I am using the 1.7.90 version, but I suffered this bug for over one
  year (confirmed in version 2.0.0-rc0 too)

  this bug happens anytime I use the -soundhw sb16 switch, but the full
  command I am using in this specific case is:

  qemu-system-i386 -localtime -cpu pentium -m 32 -display sdl -vga
  cirrus -hda c.img -cdrom win95stuff.iso -net nic,model=ne2k_pci -net
  user -soundhw sb16

  This bug appears on all my machines: Pentium III running Slackware
  13.0 and freeBSD 10; Dual core T2400, both in Arch, Gentoo and
  Slackware 14.1 (all 32 bits), and a Dual core T4400 64 bits with
  Gentoo and Slackware. Same problem in all of those systems after
  compiling instead of using the distro packages....

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1295587/+subscriptions

  parent reply	other threads:[~2017-03-26 15:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21  9:32 [Qemu-devel] [Bug 1295587] [NEW] Temporal freeze and slowdown while using emulated sb16 alvarez
2014-03-21 11:20 ` [Qemu-devel] [Bug 1295587] " alvarez
2014-03-21 13:28 ` alvarez
2014-03-22 14:46 ` Cole Robinson
2014-03-22 21:36 ` alvarez
2017-03-26 15:30 ` milasudril [this message]
2017-03-26 15:32 ` milasudril
2017-07-23 15:16 ` Blake Lee
2020-05-17 23:45 ` Amaro Jr
2021-04-28  6:01 ` Thomas Huth
2021-06-28  4:17 ` Launchpad Bug Tracker

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=20170326153013.30419.50510.malone@soybean.canonical.com \
    --to=milasudril@gmail.com \
    --cc=1295587@bugs.launchpad.net \
    --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 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.