Uploaded image for project: 'Core ReactOS'
  1. Core ReactOS
  2. CORE-20107

Debug Serial Port initialization hang in release builds

    XMLWordPrintable

Details

    Description

      Hi,

      I am new to ReactOS, so forgive me if I miss something here.

      I am one of the active developers of Bochs and in testing its function, we tried to boot ReactOS and found a few issues within the Bochs emulation. One of them was posted here on this forum a while ago at CORE-17716.

      In the process of fixing that issue, I came across a different issue. Please see the following URL for more information.
      https://github.com/bochs-emu/Bochs/issues/506#issuecomment-2781129391

      Even though that link shows a release from a little while ago, I tried the latest (g00f4a0f) today and I still get the same results.

      I tried with QEMU and Oracle VM VirtualBox and believe to get the same results on those two as well, though I did not single step the emulation as I show I did in the Bochs issue above.

      Not familiar with ReactOS at all, I can only assume that ReactOS is setting up four calling functions, possibly one for each serial port, 0 through 3.

      I did notice that these four 32-bit addresses are loaded from a file instead of created on the fly, because from the time that sector is loaded, the four dwords remain static all the way from the lower 0x30000 area where the file is loaded, to physical address 0x00513508 where the four addresses are moved to, through to the point where the linear modification is made to reside at linear address 0x80513508.

      Please note that this is an issue with the release version choosing (Debug) on the boot menu. If the release version doesn't support the (Debug) option, should this option be removed from the menu? Am I missing something that with the release version is assumed and/or documented somewhere that you should not choose the (Debug) option. Or is this a valid issue.

      Since I can image that many people are booting the latest, if not a recent image within their favorite emulator, am I simply missing something?

      I ask because I believe the issue I show at the Bochs URL above no longer applies to Bochs but now applies to ReactOS, but want to verify before I close the Bochs issue assuming so.

      Thank you,

      Ben

      Attachments

        Activity

          People

            hbelusca hbelusca
            BenLunt BenLunt
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: