| "sis%d: couldnt map ports/memory" || A fatal initialization error has occurred. |
| "sis%d: couldnt map interrupt" || A fatal initialization error has occurred. |
| "sis%d: watchdog timeout" || The device has stopped responding to the network, or there is a problem with the network connection (e.g. a cable fault). |
| "sis%d: no memory for rx list" || The driver failed to allocate an mbuf for the receiver ring. |
| "sis%d: 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. |
| "sis%d: 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 will not 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 warm boot to have the device properly configured. |
Note that this condition only occurs when warm booting from another operating system. If you power down your system prior to booting
.Fx , the card should be configured correctly.