From: jmk@plan9.bell-labs.com jmk@plan9.bell-labs.com
Subject: [9fans] atapi cdrom without ide HDD
Date: Sat, 22 May 1999 12:01:16 -0400 [thread overview]
Message-ID: <19990522160116.rLAj4vfc_WeFVE2YzLQAKwF5Ye3z8-XDsaP_-U26u9o@z> (raw)
okamoto@granite.cias.osakafu-u.ac.JP:
and then, got an error message like:
/bin/9660srv 200: err stack 1: 114f 1872 3cf3 0 0 0
and 9660srv died.
looks like a 9660srv bug.
i know nothing about the internals of 9660srv, but i just took
a look and it seems it tries to implement an error stack just as the
kernel does. this error comes out when the stack has not been
completely popped by the time the code gets back to the main loop.
the numbers printed are the PC's of 'waserror' functions in the
code. use acid on the 9660srv binary to find the 'waserror's then
check there are no code paths out which don't have a corresponding
'poperror'.
next reply other threads:[~1999-05-22 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-22 16:01 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-05-24 0:46 okamoto
1999-05-21 9:23 okamoto
1999-05-21 3:37 okamoto
1999-05-21 3:11 okamoto
1999-05-21 2:26 okamoto
1999-05-20 4:04 okamoto
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=19990522160116.rLAj4vfc_WeFVE2YzLQAKwF5Ye3z8-XDsaP_-U26u9o@z \
--to=jmk@plan9.bell-labs.com \
/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).