From: Berry Kercheval kerch@parc.xerox.com
Subject: panic: ataintr: wait busy
Date: Thu, 7 Sep 1995 20:42:45 -0400 [thread overview]
Message-ID: <19950908004245.r4oEKvuME9545-CJJnFdaR_AHwZ5p5mwp3D4UnoRZv8@z> (raw)
The machine I can use for plan9 was finally delivered. It's a 486 with an
Adaptec 1542 of some flavor. When I boot I get wait busy panics. I updated
my disks this afternoon and when I copy b.com and 9dos to C: and do
C:\b sd!0
It sees both of the disks I have installed, but after 9dos boots I get this:
5569 free pages, 22276K bytes, swap 11126K, highwater 1112K, headroom 1388K
CPU is a 33 MHz Intel486DX (cpuid: ax 400 dx 0)
scsi0: aha1542: port 330 irq 14 dma5
panic: wait busy cmd=0 status=ff
Anyone seen this one before? A search for adaptec and ataintr in my 9fans
archive didn't help much.
--berry
Berry Kercheval :: Xerox Palo Alto Research Center
next reply other threads:[~1995-09-08 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-08 0:42 Berry [this message]
1995-09-08 17:42 Dave
1995-09-08 18:43 jmk
1995-09-11 12:51 Joseph
1995-09-11 17:22 Berry
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=19950908004245.r4oEKvuME9545-CJJnFdaR_AHwZ5p5mwp3D4UnoRZv8@z \
--to=9fans@9fans.net \
/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).