From: erik quanstrom <quanstro@quanstro.net>
To: YAMANASHI Takeshi <9.nashi@gmail.com>, 9fans@cse.psu.edu
Subject: Re: [9fans] Venti Install
Date: Mon, 26 Mar 2007 07:39:16 -0400 [thread overview]
Message-ID: <20070326113916.F3DAA21EC6@medicine-bow.quanstro.net> (raw)
In-Reply-To: <2ef8db43c822a2580c7bedfb69d78a86@orthanc.cc.titech.ac.jp>
are you sure this is a DMA problem. there are lots of
places in the kernel that return Ebadctl.
pc/devether.c:266: error(Ebadctl);
pc/ethersink.c:31: error(Ebadctl);
pc/ethervgbe.c:1082: error(Ebadctl);
pc/sdata.c:2202: error(Ebadctl);
pc/sdata.c:2208: error(Ebadctl);
pc/sdata.c:2212: error(Ebadctl);
pc/sdata.c:2218: error(Ebadctl);
pc/sdata.c:2223: error(Ebadctl);
pc/sdata.c:2227: error(Ebadctl);
pc/sdata.c:2232: error(Ebadctl);
pc/sdata.c:2236: error(Ebadctl);
pc/sdata.c:2242: error(Ebadctl);
pc/sdata.c:2245: error(Ebadctl);
pc/sdmv50xx.c:1170: cmderror(cb, Ebadctl);
pc/wavelan.c:1120: error(Ebadctl);
port/devpnp.c:615: error(Ebadctl);
port/devpnp.c:623: error(Ebadctl);
port/devproc.c:1056: error(Ebadctl);
port/devproc.c:1357: error(Ebadctl);
port/devproc.c:1367: error(Ebadctl);
port/devproc.c:1372: error(Ebadctl);
port/devproc.c:1379: error(Ebadctl);
port/devsd.c:97: error(Ebadctl);
port/devsd.c:155: error(Ebadctl);
port/devsd.c:1230: error(Ebadctl);
port/devsd.c:1255: error(Ebadctl);
port/devsd.c:1258: error(Ebadctl);
port/devsd.c:1267: error(Ebadctl);
port/devsd.c:1273: error(Ebadctl);
port/devsegment.c:387: error(Ebadctl);
port/error.h:25: extern char Ebadctl[]; /* bad process or channel control request */
ppc/devether.c:256: error(Ebadctl);
YAMANASHI Takeshi <9.nashi@gmail.com> writes
|
| Yeah. DMA helps a lot on venti formatting.
| However, I saw this ominous message on my console when
| installing another tip9ug host on VMware ESX 3.0 Server
| which only supports Buslogic SCSI adaptor.
|
| init: starting /bin/rc
| echo: write error: bad process or channel control request
| echo: write error: bad process or channel control request
|
| I guess someone tried to turn DMA on for the SCSI drive and failed.
next prev parent reply other threads:[~2007-03-26 11:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 8:36 YAMANASHI Takeshi
2007-03-26 11:39 ` erik quanstrom [this message]
2007-03-26 11:49 ` Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2007-03-26 7:29 YAMANASHI Takeshi
2007-03-26 7:40 ` Bruce Ellis
2007-03-26 8:23 ` Charles Forsyth
2007-03-26 8:29 ` Bruce Ellis
2007-03-19 22:54 Devon H. O'Dell
2007-03-19 23:00 ` Russ Cox
2007-03-19 23:02 ` Devon H. O'Dell
2007-03-19 23:06 ` Russ Cox
2007-03-19 23:12 ` Devon H. O'Dell
2007-03-19 23:01 ` john
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=20070326113916.F3DAA21EC6@medicine-bow.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9.nashi@gmail.com \
--cc=9fans@cse.psu.edu \
/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).