From: David Relson <relson@osagesoftware.com>
To: linux-msdos <linux-msdos@vger.kernel.org>
Subject: ERROR: Port ... not available
Date: Sat, 4 Jul 2009 16:02:23 -0400 [thread overview]
Message-ID: <20090704160223.71532dc2@osage.osagesoftware.com> (raw)
Hi Bart,
Changing focus...
The first error reported in boot.log is:
ERROR: Port 0xac1c is not available (outw),
"save_vga_state" failed.
Since the port number doesn't appear in hwinfo or lspci, it seems that
adding some debug statements to dosemu might help.
The message above comes from ports, notably port_not_avail_outw() which
calls check_crit_section() which spits out the message. Looks like I
need to trace backwards to see how/why port_not_avail_outw is being
passed address 0xAC1C. Have you any suggestions of a better approach?
Regards,
David
reply other threads:[~2009-07-04 20:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090704160223.71532dc2@osage.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=linux-msdos@vger.kernel.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