I believe I've found another interesting aspect to this issue. I believe it is actually capable of forcing my Motorola Surfboard 6120 cable modem to reboot. When using a wireless connection to do a git repo sync with Cyanogenmod (or anything that involves a substantial download), my cable modem will reboot every few minutes with the following logged errors.
Cable Modem Reboot due to T4 timeout ;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Ranging Request Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
If I use a wired connection and disable wireless, I can do these synchronizes without a problem on the cable modem. Other machines on the network don't have issues, pointing directly at this Intel wireless problem. What I find most interesting about this is that there is a wireless router, switch and Linux router in the networking path within the house. I don't know enough about networking to understand how the wireless driver/hardware could possibly be creating packets that flow through the network and crater the cable modem. Very strange indeed.
I'm pondering whether I need to re-install to roll back to 11.04 where networking was stable. I see that there is ongoing conversation with the Intel wireless driver folks, but does anyone have an idea if/when this might be fixed?
I believe I've found another interesting aspect to this issue. I believe it is actually capable of forcing my Motorola Surfboard 6120 cable modem to reboot. When using a wireless connection to do a git repo sync with Cyanogenmod (or anything that involves a substantial download), my cable modem will reboot every few minutes with the following logged errors.
Cable Modem Reboot due to T4 timeout ;CM-MAC= XX:XX:XX: XX:XX:XX; CMTS-MAC= XX:XX:XX: XX:XX:XX; CM-QOS= 1.1;CM- VER=3.0; CM-MAC= XX:XX:XX: XX:XX:XX; CMTS-MAC= XX:XX:XX: XX:XX:XX; CM-QOS= 1.1;CM- VER=3.0; CM-MAC= XX:XX:XX: XX:XX:XX; CMTS-MAC= XX:XX:XX: XX:XX:XX; CM-QOS= 1.1;CM- VER=3.0; CM-MAC= XX:XX:XX: XX:XX:XX; CMTS-MAC= XX:XX:XX: XX:XX:XX; CM-QOS= 1.1;CM- VER=3.0;
Unicast Maintenance Ranging attempted - No response - Retries exhausted;
Ranging Request Retries exhausted;
No Ranging Response received - T3 time-out;
If I use a wired connection and disable wireless, I can do these synchronizes without a problem on the cable modem. Other machines on the network don't have issues, pointing directly at this Intel wireless problem. What I find most interesting about this is that there is a wireless router, switch and Linux router in the networking path within the house. I don't know enough about networking to understand how the wireless driver/hardware could possibly be creating packets that flow through the network and crater the cable modem. Very strange indeed.
I'm pondering whether I need to re-install to roll back to 11.04 where networking was stable. I see that there is ongoing conversation with the Intel wireless driver folks, but does anyone have an idea if/when this might be fixed?