Re: [Qemu-devel] OS/2 lockups during bootup

[Johannes Martin]

I just tried it again with the latest CVS. I, too, usually see some spikes
in CPU load when those drivers are loaded, but they are rather short in
the "working" case. Frequently, the cpu-usage remains at 99% and that's
the end of it.

I'm running OS/2 Warp 4 with fixpack 15 and device driver fixpack 2
(though the lockup occurs without the fixpacks as well). It does not seem
to matter whether I use -isa or not (not sure whether that affects the
IDE/FDC controller emulation).

:(

        Johannes


On Mon, 30 Aug 2004, Nathan Kunkee wrote:

> Johannes,
> Over this last weekend, I was able to install and boot OS/2 (v3, blue spine)
> through the latest CVS version of CVS. I encountered two problems: After
> copying the last base disk (6 I believe), the installer asked that I eject
> the disk and press enter. Somehow in the process of switching to the monitor
> and back, I could never get that last enter pressed. It turns out that there
> was nothing after that; all the needed files had been copied. The other
> issue I found was even though I had a blank disk image file, OS/2 did not
> install a master boot record. I had to boot with a Win 95 boot disk to add
> one. (fdisk /mbr)  I do see  CPU spike and fall during the load of
> IBM1S506.ADD.
>
> For the rest of the list, I have not had any success with loading sound
> support. I'm using Win XP as a host.. Any thoughts?
>
> Hope that helps, and thanks in advance.....
> Nathan
>
>
> Message: 3
> Date: Sun, 29 Aug 2004 21:52:07 +0200 (CEST)
> From: Johannes Martin <address@hidden>
> Subject: [Qemu-devel] OS/2 lockups during bootup
> To: address@hidden
> Message-ID:
>       <address@hidden>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Hi everybody,
>
> I'm having some trouble booting up OS/2 in qemu (CVS, Linux host). OS/2
> frequently hangs during bootup when loading one of the following device
> drivers:
>       IBM1FLPY.ADD
>       IBM1S506.ADD
>       IBMIDECD.FLT
>       IBMDASD.DMD
>
> The lockup may occur randonmly in any of these drivers or not at all. When
> I reboot OS/2 or restart qemu a couple of times, I usually get past these
> drivers eventually. It takes patience though.
>
> I know that something has gone wrong when qemu starts using 99% of CPU
> time while loading these drivers. I assume the drivers are in some kind of
> loop waiting for some event to happen - I guess it's a timing problem and
> sometimes things don't happen in the right sequence.
>
> Any hints?
>
> Thanks
>       Johannes
>
> _________________________________________________________________
> Check out Election 2004 for up-to-date election news, plus voter tools and
> more! http://special.msn.com/msn/election2004.armx
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

---
Mit zwei Euro im Monat helfen:
        http://www.2-euro-helfen.de/
Help to fight hunger and injustice in our world:
        http://www.devp.org/
        http://www.oxfam.org/