remove obsolete note about D3 power state. this diagnostic is not present

in any of these drivers

7 files changed, 7 insertions, 150 deletions

diff --git a/share/man/man4/dc.4 b/share/man/man4/dc.4
index e1b3874261e..4a96ddfd7f7 100644
--- a/share/man/man4/dc.4
+++ b/share/man/man4/dc.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: dc.4,v 1.49 2013/06/02 20:23:33 tedu Exp $
+.\"	$OpenBSD: dc.4,v 1.50 2013/06/02 20:28:26 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\"	Bill Paul <wpaul@ee.columbia.edu>. All rights reserved.
@@ -253,26 +253,6 @@ possible transmit start threshold settings had been tried, so the
 driver programmed the chip for store and forward mode.
 In this mode, the NIC will not begin transmission until the entire packet
 has been transferred into its FIFO memory.
-.It "dc0: chip is in D3 power state -- setting to D0"
-This message applies only to adapters which support power management.
-Some operating systems place the controller in low power
-mode when shutting down, and some PCI BIOSes fail to bring the chip
-out of this state before configuring it.
-The controller loses all of its PCI configuration in the D3 state,
-so if the BIOS does not set it back to full power mode in time,
-it won't be able to configure it correctly.
-The driver tries to detect this condition and bring
-the adapter back to the D0 (full power) state, but this may not be
-enough to return the driver to a fully operational condition.
-If you see this message at boot time and the driver fails to attach
-the device as a network interface, you will have to perform a second
-warm boot to have the device properly configured.
-.Pp
-Note that this condition only occurs when warm booting from another
-operating system.
-If you power down your system prior to booting
-.Ox ,
-the card should be configured correctly.
 .El
 .Sh SEE ALSO
 .Xr amphy 4 ,
diff --git a/share/man/man4/rl.4 b/share/man/man4/rl.4
index 2520cb1681f..62f980343a3 100644
--- a/share/man/man4/rl.4
+++ b/share/man/man4/rl.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: rl.4,v 1.35 2013/06/02 20:23:33 tedu Exp $
+.\"	$OpenBSD: rl.4,v 1.36 2013/06/02 20:28:26 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -160,27 +160,6 @@ The driver failed to allocate an mbuf for the receiver ring.
 .It "rl0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
-.It "rl0: chip is in D3 power state -- setting to D0"
-This message applies only to adapters which support power
-management.
-Some operating systems place the controller in low power
-mode when shutting down, and some PCI BIOSes fail to bring the chip
-out of this state before configuring it.
-The controller loses all of its PCI configuration in the D3 state, so if
-the BIOS does not set it back to full power mode in time, it won't be able
-to configure it correctly.
-The driver tries to detect this condition and bring the adapter back to the D0
-(full power) state, but this may not be enough to return the driver to a fully
-operational condition.
-If this message appears at boot time and the driver fails to attach
-the device as a network interface, a second warm boot will have to be
-performed to have the device properly configured.
-.Pp
-Note that this condition only occurs when warm booting from another
-operating system.
-If the system is powered down prior to booting
-.Ox ,
-the card should be configured correctly.
 .El
 .Sh SEE ALSO
 .Xr arp 4 ,
diff --git a/share/man/man4/sis.4 b/share/man/man4/sis.4
index 8e63072194a..ed7ba906a27 100644
--- a/share/man/man4/sis.4
+++ b/share/man/man4/sis.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: sis.4,v 1.30 2013/06/02 20:23:34 tedu Exp $
+.\"	$OpenBSD: sis.4,v 1.31 2013/06/02 20:28:26 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\"	Bill Paul <wpaul@ee.columbia.edu>. All rights reserved.
@@ -133,26 +133,6 @@ The driver failed to allocate an mbuf for the receiver ring.
 .It "sis0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
-.It "sis0: chip is in D3 power state -- setting to D0"
-This message applies only to adapters which support power management.
-Some operating systems place the controller in low power
-mode when shutting down, and some PCI BIOSes fail to bring the chip
-out of this state before configuring it.
-The controller loses all of its PCI configuration in the D3 state, so
-if the BIOS does not set it back to full power mode in time, it won't
-be able to configure it correctly.
-The driver tries to detect this condition and bring
-the adapter back to the D0 (full power) state, but this may not be
-enough to return the driver to a fully operational condition.
-If this message appears at boot time and the driver fails to attach
-the device as a network interface, a second warm boot will have to be
-performed to have the device properly configured.
-.Pp
-Note that this condition only occurs when warm booting from another
-operating system.
-If the system is powered down prior to booting
-.Ox ,
-the card should be configured correctly.
 .El
 .Sh SEE ALSO
 .Xr arp 4 ,
diff --git a/share/man/man4/ste.4 b/share/man/man4/ste.4
index 89b194c7a2a..a32eae0753a 100644
--- a/share/man/man4/ste.4
+++ b/share/man/man4/ste.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ste.4,v 1.24 2013/06/02 20:23:34 tedu Exp $
+.\"	$OpenBSD: ste.4,v 1.25 2013/06/02 20:28:26 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -122,28 +122,6 @@ The driver failed to allocate an mbuf for the receiver ring.
 .It "ste0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
-.It "ste0: chip is in D3 power state -- setting to D0"
-This message applies only to adapters which support power
-management.
-Some operating systems place the controller in low power
-mode when shutting down, and some PCI BIOSes fail to bring the chip
-out of this state before configuring it.
-The controller loses all of
-its PCI configuration in the D3 state, so if the BIOS does not set
-it back to full power mode in time, it won't be able to configure it
-correctly.
-The driver tries to detect this condition and bring
-the adapter back to the D0 (full power) state, but this may not be
-enough to return the driver to a fully operational condition.
-If this message appears at boot time and the driver fails to attach
-the device as a network interface, a second warm boot will have to be
-performed to have the device properly configured.
-.Pp
-Note that this condition only occurs when warm booting from another
-operating system.
-If the system is powered down prior to booting
-.Ox ,
-the card should be configured correctly.
 .El
 .Sh SEE ALSO
 .Xr arp 4 ,
diff --git a/share/man/man4/vr.4 b/share/man/man4/vr.4
index 2d8adc77346..b63933997b3 100644
--- a/share/man/man4/vr.4
+++ b/share/man/man4/vr.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: vr.4,v 1.33 2013/06/02 20:23:34 tedu Exp $
+.\"	$OpenBSD: vr.4,v 1.34 2013/06/02 20:28:26 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -144,26 +144,6 @@ The driver failed to allocate an mbuf for the receiver ring.
 .It "vr0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
-.It "vr0: chip is in D3 power state -- setting to D0"
-This message applies only to adapters which support power management.
-Some operating systems place the controller in low power
-mode when shutting down, and some PCI BIOSes fail to bring the chip
-out of this state before configuring it.
-The controller loses all of its PCI configuration in the D3 state, so if the
-BIOS does not set it back to full power mode in time, it won't be able to
-configure it correctly.
-The driver tries to detect this condition and bring
-the adapter back to the D0 (full power) state, but this may not be
-enough to return the driver to a fully operational condition.
-If this message appears at boot time and the driver fails to attach
-the device as a network interface, a second warm boot will have to be
-performed to have the device properly configured.
-.Pp
-Note that this condition only occurs when warm booting from another
-operating system.
-If the system is powered down prior to booting
-.Ox ,
-the card should be configured correctly.
 .El
 .Sh SEE ALSO
 .Xr amphy 4 ,
diff --git a/share/man/man4/wb.4 b/share/man/man4/wb.4
index 731d746e533..eb191c577ef 100644
--- a/share/man/man4/wb.4
+++ b/share/man/man4/wb.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: wb.4,v 1.19 2013/06/02 20:23:34 tedu Exp $
+.\"	$OpenBSD: wb.4,v 1.20 2013/06/02 20:28:26 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -120,26 +120,6 @@ The driver failed to allocate an mbuf for the receiver ring.
 .It "wb0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
-.It "wb0: chip is in D3 power state -- setting to D0"
-This message applies only to adapters which support power management.
-Some operating systems place the controller in low power
-mode when shutting down, and some PCI BIOSes fail to bring the chip
-out of this state before configuring it.
-The controller loses all of its PCI configuration in the D3 state, so if the
-BIOS does not set it back to full power mode in time, it won't be able
-to configure it correctly.
-The driver tries to detect this condition and bring
-the adapter back to the D0 (full power) state, but this may not be
-enough to return the driver to a fully operational condition.
-If this message appears at boot time and the driver fails to attach
-the device as a network interface, a second warm boot will have to be
-performed to have the device properly configured.
-.Pp
-Note that this condition only occurs when warm booting from another
-operating system.
-If the system is powered down prior to booting
-.Ox ,
-the card should be configured correctly.
 .El
 .Sh SEE ALSO
 .Xr amphy 4 ,
diff --git a/share/man/man4/xl.4 b/share/man/man4/xl.4
index 66514766d2e..c52a3b82e97 100644
--- a/share/man/man4/xl.4
+++ b/share/man/man4/xl.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: xl.4,v 1.45 2013/06/02 20:23:34 tedu Exp $
+.\"	$OpenBSD: xl.4,v 1.46 2013/06/02 20:28:26 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998
 .\"     Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -168,26 +168,6 @@ giving up, at which point it issues this message.
 This message may be printed during driver initialization on slower machines.
 If this message appears but the driver continues to function normally, the
 message can probably be ignored.
-.It "xl0: chip is in D3 power state -- setting to D0"
-This message applies only to 3C905B adapters, which support power management.
-Some operating systems place the 3C905B in low power
-mode when shutting down, and some PCI BIOSes fail to bring the chip
-out of this state before configuring it.
-The 3C905B loses all of its PCI configuration in the D3 state, so if the
-BIOS does not set it back to full power mode in time,
-it won't be able to configure it correctly.
-The driver tries to detect this condition and bring
-the adapter back to the D0 (full power) state, but this may not be
-enough to return the driver to a fully operational condition.
-If this message appears at boot time and the driver fails to attach
-the device as a network interface, a second warm boot will have to be
-performed to have the device properly configured.
-.Pp
-Note that this condition only occurs when warm booting from another
-operating system.
-If the system is powered down prior to booting
-.Ox ,
-the card should be configured correctly.
 .It "xl0: WARNING: no media options bits set in the media options register!"
 This warning may appear when using the driver on some Dell Latitude
 docking stations with built-in 3C905-TX adapters.