On 4.x and -current systems the following messages can occur when the memory mapped buffers are set up.
If the kernel is booted with the verbose flag turned on then the extra information is printed when the driver is probed. These messages are also seen when the RAY_DBG_BOOTPARAM bit in the RAY_DEBUG option is turned on, as is the case for all existing versions of the driver.
| "ray?: cannot transmit - not running" | A packet was ready for transmission but the NIC is not connected to a BSS. May occur when removing the PCCard. |
| "ray?: cannot transmit - no network" | The wireless NIC has roamed from an access point and not connected with a new one yet. |
| "ray?: cannot transmit - ECF busy" | The controller firmware was busy when a packet was about to be sent out. It will be retried automatically. |
| "ray?: mbuf too long ??" | Should never happen, and if it does represents something wrong in the generic Ethernet driver in the kernel. |
| "ray?: could not pullup ether" | Problem with re-aligning mbufs. Very unlikely to happen. |
| "ray?: unknown framing type ??" | An impossible error - mail the author. |
| "ray?: could not translate packet" | An error occurred when trying to re-frame a packet for transmission. |
| "ray?: ECF busy, dropping packet" | The NIC was busy just before a packet was to be transmitted. |
| "ray?: tx completed but status is fail" | Typically associated with transmissions to out of range NICs. |
| "ray?: packet too big or too small" | A received packet was impossibly small or too large to fit into an mbuf. |
| "ray?: MGETHDR failed" | The driver could not get a mbuf to store a received packet into. Try increasing MAXUSERS in your kernel configuration. |
| "ray?: MCLGET failed" | The driver could not get a mbuf to store a received packet into. Try increasing MAXUSERS in your kernel configuration. |
| "ray?: bad length current 0x?? pktlen 0x??" | The lengths of a fragmented packet were inconsistent. |
| "ray?: bad rcs index 0x??" | The index of the buffer used for part of a fragmented packet is outside of the usable range. |
| "ray?: header not version 0 fc0 0x??" | The received IEEE 802.11 packet had an unknown header type. Represents link corruption or non standard nodes in the network. |
| "ray?: unknown packet fc0 0x??" | The received IEEE 802.11 packet type is unknown. Represents link corruption or non standard nodes in the network. |
| "ray?: reserved DATA packet subtype 0x??" | The received IEEE 802.11 data packet has a reserved (i.e., not allowed) subtype. Represents link corruption or non standard nodes in the network. |
| "ray?: MGT TODS/FROMDS wrong fc1 0x??" | The received IEEE 802.11 management packet had a malformed header. Represents link corruption or non standard nodes in the network. |
| "ray?: unexpected MGT packet subtype 0x??" | The received IEEE 802.11 management packet was of a subtype that the NIC should have processed. Benign, but might represent buggy firmware. |
| "ray?: reserved MGT packet subtype 0x??" | The received IEEE 802.11 management packet has a reserved (i.e., not allowed) subtype. Represents link corruption or non standard nodes in the network. |
| "ray?: open system authentication request" | Self explanatory and for testing "Aviator Pro" interworking. |
| "ray?: authentication failed with status ??" | Self explanatory and currently represents a bug as the driver never requests authentication. |
| "ray?: shared key authentication request" | Self explanatory and for testing "Aviator Pro" interworking. |
| "ray?: reserved authentication subtype 0x??" | An authentication request has been received for a reserved (i.e., not allowed) subtype. Represents link corruption or non standard nodes in the network. |
| "ray?: CTL TODS/FROMDS wrong fc1 0x??" | The received IEEE 802.11 management packet had a malformed header. Represents link corruption or non standard nodes in the network. |
| "ray?: unexpected CTL packet subtype 0x??" | The received IEEE 802.11 control packet was of a subtype that the NIC should have processed. Benign, but might represent buggy firmware. |
| "ray?: reserved CTL packet subtype 0x??" | The received IEEE 802.11 control packet has a reserved (i.e., not allowed) subtype. Represents link corruption or non standard nodes in the network. |
| "ray?: bad ccs index 0x??" | The NIC has generated an interrupt with an incorrect control block. |
"ray?: unexpected UPDATE_APM"
"ray?: unexpected TEST_MEM"
"ray?: unexpected SHUTDOWN"
"ray?: unexpected DUMP_MEM"
"ray?: unexpected START_TIMER" |
| | The NIC has generated an interrupt signalling that the indicated command has completed. At present these commands are never issued by the driver, so they represent firmware/hardware/driver bugs. |
| "ray?: unknown command 0x??" | The NIC has generated an interrupt for an unknown command completion. Represents firmware/hardware/driver bugs. |
| "ray?: unexpected JAPAN_CALL_SIGNAL" | The NIC has generated an interrupt with a control block requesting processing of a packet that is only ever used in Japanese RCR certification tests. Represents firmware/hardware/driver bugs unless you are trying to certify the NICs in Japan (in which case you would have to of modified the driver and this manual is out of date). |
| "ray?: spinning" | The controller firmware was busy when a command was about to be issued. If the driver spins for too long then it will panic. See the BUGS section for details. |
| "ray?: freeing free ccs 0x??" | Benign warning that may occur when the NIC is ejected. |
|
