aboutsummaryrefslogtreecommitdiff
path: root/share/man/man4/isp.4
diff options
context:
space:
mode:
authorSheldon Hearn <sheldonh@FreeBSD.org>2000-03-02 14:54:02 +0000
committerSheldon Hearn <sheldonh@FreeBSD.org>2000-03-02 14:54:02 +0000
commit4e86fcacf69e8dac21f67db61babdcae80903dc2 (patch)
tree11e6c1004800534c82bd3b37f48ff4dda29e2989 /share/man/man4/isp.4
parentb22b0eaef005d00199fe216b0544647dc3682cf0 (diff)
Notes
Diffstat (limited to 'share/man/man4/isp.4')
-rw-r--r--share/man/man4/isp.43
1 files changed, 2 insertions, 1 deletions
diff --git a/share/man/man4/isp.4 b/share/man/man4/isp.4
index c16c7329e7cc4..92ddaff48656f 100644
--- a/share/man/man4/isp.4
+++ b/share/man/man4/isp.4
@@ -198,7 +198,8 @@ as they should.
Sometimes, when booting, the driver gets stuck waiting for the Fibre Channel
f/w to tell it that the loop port database is ready.
In this case you'll
-see an announcement that the loop state has a value of 0x1. To unwedge
+see an announcement that the loop state has a value of 0x1.
+To unwedge
the system, unplug and replug the fibre channel connection, or otherwise
cause a LIP (Loop Initialization Primitive sequence)- this will kick the f/w
into getting unstuck.