1 files changed, 23 insertions, 106 deletions
diff --git a/share/man/man4/man4.vax/uda.4 b/share/man/man4/man4.vax/uda.4
index 4507f54393e..2448fa50e92 100644
--- a/share/man/man4/man4.vax/uda.4
+++ b/share/man/man4/man4.vax/uda.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: uda.4,v 1.11 2003/03/06 17:52:07 jason Exp $
+.\"	$OpenBSD: uda.4,v 1.12 2003/03/06 19:29:14 jason Exp $
 .\"	$NetBSD: uda.4,v 1.3 1996/03/03 17:14:10 thorpej Exp $
 .\"
 .\" Copyright (c) 1980, 1987, 1991 Regents of the University of California.
@@ -227,7 +227,7 @@ Something went wrong while trying to determine the status of
 a disk drive.
 This is followed by an error detail.
 .Pp
-.It uda%d: unit %d, next %d
+.It "uda%d: unit %d, next %d"
 This probably never happens, but I wanted to know if it did.
 I have no idea what one should do about it.
 .Pp
@@ -235,53 +235,37 @@ I have no idea what one should do about it.
 The controller found a drive whose unit number is too large.
 Valid unit numbers are those in the range [0..7].
 .Pp
-.It "ra%d: don't have a partition table for %s; using (s,t,c)=(%d,%d,%d)"
-The controller found a drive whose media identifier (e.g. `RA 25')
-does not have a default partition table.
-A temporary partition
-table containing only an `a' partition has been created covering
-the entire disk, which has the indicated numbers of sectors per
-track (s), tracks per cylinder (t), and total cylinders (c).
-Give the pack a label with the
-.Xr disklabel 8
-utility.
-.Pp
 .It "uda%d: uballoc map failed"
 Unibus resource map allocation failed during initialization.
 This can only happen if you have 496 devices on a Unibus.
 .Pp
-.It uda%d: timeout during init
+.It "uda%d: timeout during init"
 The controller did not initialize within ten seconds.
 A hardware problem, but it sometimes goes away if you try again.
 .Pp
-.It uda%d: init failed, sa=%b
+.It "uda%d: init failed, sa=%b"
 The controller refused to initialize.
 .Pp
-.It uda%d: controller hung
+.It "uda%d: controller hung"
 The controller never finished initialization.
 Retrying may sometimes fix it.
 .Pp
-.It ra%d: drive will not come on line
-The drive will not come on line, probably because it is spun down.
-This should be preceded by a message giving details as to why the
-drive stayed off line.
-.Pp
-.It uda%d: still hung
+.It "uda%d: still hung"
 When the controller hangs, the driver occasionally tries to reinitialize
 it.
 This means it just tried, without success.
 .Pp
-.It panic: udastart: bp==NULL
+.It "panic: udastart: bp==NULL"
 A bug in the driver has put an empty drive queue on a controller queue.
 .Pp
-.It uda%d: command ring too small
+.It "uda%d: command ring too small"
 If you increase
 .Dv NCMDL2 ,
 you may see a performance improvement.
 (See
 .Pa /sys/arch/vax/uba/uda.c . )
 .Pp
-.It panic: udastart
+.It "panic: udastart"
 A drive was found marked for status or on-line functions while performing
 status or on-line functions.
 This indicates a bug in the driver.
@@ -300,7 +284,7 @@ operation, the driver will reset it and retry pending I/O .
 If
 it occurs during configuration, the controller may be ignored.
 .Pp
-.It uda%d: stray intr
+.It "uda%d: stray intr"
 The controller interrupted when it should have stayed quiet.
 The interrupt has been ignored.
 .Pp
@@ -308,26 +292,26 @@ The interrupt has been ignored.
 The controller reported an error during the named initialization step.
 The driver will retry initialization later.
 .Pp
-.It uda%d: version %d model %d
+.It "uda%d: version %d model %d"
 An informational message giving the revision level of the controller.
 .Pp
-.It uda%d: DMA burst size set to %d
+.It "uda%d: DMA burst size set to %d"
 An informational message showing the
 .Tn DMA
 burst size, in words.
 .Pp
-.It panic: udaintr
+.It "panic: udaintr"
 Indicates a bug in the generic
 .Tn MSCP
 code.
 .Pp
-.It uda%d: driver bug, state %d
+.It "uda%d: driver bug, state %d"
 The driver has a bogus value for the controller state.
 Something is quite wrong.
 This is immediately followed by a
 .Sq panic: udastate .
 .Pp
-.It uda%d: purge bdp %d
+.It "uda%d: purge bdp %d"
 A benign message tracing BDP purges.
 I have been trying to figure out what BDP purges are for.
 You might want to comment out this
@@ -346,45 +330,17 @@ The
 .Em detail
 message tells why.
 .Pp
-.It uda%d: ra%d: unknown type %d
+.It "uda%d: ra%d: unknown type %d"
 The type index of the named drive is not known to the driver, so the
 drive will be ignored.
 .Pp
-.It "ra%d: changed types! was %d now %d"
-A drive somehow changed from one kind to another, e.g., from an
-.Tn RA80
-to an
-.Tn RA60 .
-The numbers printed are the encoded media identifiers (see
-.Ao Pa vax/mscp.h Ac
-for the encoding).
-The driver believes the new type.
-.Pp
-.It "ra%d: uda%d, unit %d, size = %d sectors"
-The named drive is on the indicated controller as the given unit,
-and has that many sectors of user-file area.
-This is printed during configuration.
-.Pp
 .It "uda%d: attempt to get status for ra%d failed:  `detail'"
 A status request failed.
 The
 .Em detail
 message should tell why.
 .Pp
-.It ra%d: bad block report: %d
-The drive has reported the given block as bad.
-If there are multiple bad blocks, the drive will report only the first;
-in this case this message will be followed by `+ others'.
-Get
-.Tn DEC
-to forward the
-block with
-.Tn EVRLK .
-.Pp
-.It ra%d: serious exception reported
-I have no idea what this really means.
-.Pp
-.It panic: udareplace
+.It "panic: udareplace"
 The controller reported completion of a
 .Tn REPLACE
 operation.
@@ -392,16 +348,16 @@ The driver never issues any
 .Tn REPLACE Ns s ,
 so something is wrong.
 .Pp
-.It panic: udabb
+.It "panic: udabb"
 The controller reported completion of bad block related I/O .
 The
 driver never issues any such, so something is wrong.
 .Pp
-.It uda%d: lost interrupt
+.It "uda%d: lost interrupt"
 The controller has gone out to lunch, and is being reset to try to bring
 it back.
 .Pp
-.It panic: mscp_go: AEB_MAX_BP too small
+.It "panic: mscp_go: AEB_MAX_BP too small"
 You defined
 .Dv AVOID_EMULEX_BUG
 and increased
@@ -431,23 +387,6 @@ but was not, or cannot now be, configured into the running system.
 is one of `available attention' (an `I am here' message) or
 `stray response op 0x%x status 0x%x' (anything else).
 .Pp
-.It ra%d: bad lbn (%d)?
-The drive has reported an invalid command error, probably due to an
-invalid block number.
-If the lbn value is very much greater than the
-size reported by the drive, this is the problem.
-It is probably due to an improperly configured partition table.
-Other invalid commands indicate a bug in the driver, or hardware trouble.
-.Pp
-.It ra%d: duplicate ONLINE ignored
-The drive has come on-line while already on-line.
-This condition can probably be ignored (and has been).
-.Pp
-.It ra%d: io done, but no buffer?
-Hardware trouble, or a bug; the drive has finished an I/O
-request,
-but the response has an invalid (zero) command reference number.
-.Pp
 .It "Emulex SC41/MS screwup: uda%d, got %d correct, then changed 0x%x to 0x%x"
 You turned on
 .Dv AVOID_EMULEX_BUG ,
@@ -457,7 +396,7 @@ The number of correctly handled requests is
 reported, along with the expected and actual values relating to
 the bug being avoided.
 .Pp
-.It panic: unrecoverable Emulex screwup
+.It "panic: unrecoverable Emulex screwup"
 You turned on
 .Dv AVOID_EMULEX_BUG ,
 but Emulex was too clever and
@@ -466,7 +405,7 @@ Try turning on
 .Dv MSCP_PARANOIA
 instead.
 .Pp
-.It uda%d: bad response packet ignored
+.It "uda%d: bad response packet ignored"
 You turned on
 .Dv MSCP_PARANOIA ,
 and the driver caught the controller in
@@ -475,29 +414,7 @@ The lie has been ignored, and the controller will soon be
 reset (after a `lost' interrupt).
 This is followed by a hex dump of the offending packet.
 .Pp
-.It ra%d: bogus REPLACE end
-The drive has reported finishing a bad sector replacement, but the
-driver never issues bad sector replacement commands.
-The report is ignored.
-This is likely a hardware problem.
-.Pp
-.It "ra%d: unknown opcode 0x%x status 0x%x ignored"
-The drive has reported something that the driver cannot understand.
-Perhaps
-.Tn DEC
-has been inventive, or perhaps your hardware is ill.
-This is followed by a hex dump of the offending packet.
-.Pp
-.It "ra%d%c: hard error %sing fsbn %d [of %d-%d] (ra%d bn %d cn %d tn %d sn %d)."
-An unrecoverable error occurred during transfer of the specified
-filesystem block number(s),
-which are logical block numbers on the indicated partition.
-If the transfer involved multiple blocks, the block range is printed as well.
-The parenthesized fields list the actual disk sector number
-relative to the beginning of the drive,
-as well as the cylinder, track and sector number of the block.
-.Pp
-.It uda%d: %s error datagram
+.It "uda%d: %s error datagram"
 The controller has reported some kind of error, either `hard'
 (unrecoverable) or `soft' (recoverable).
 If the controller is going on