https://bugzilla.novell.com/show_bug.cgi?id=469038 Summary: iwl3945 causing syslog errors related to LED lights Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jrobiso2@ford.com QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-2.5 Firefox/3.0.5 My syslog shows the following: kernel: Registered led device: iwl-phy0:radio kernel: Registered led device: iwl-phy0:assoc kernel: Registered led device: iwl-phy0:RX kernel: Registered led device: iwl-phy0:TX which is all well and good. However, right away these start showing up in syslogs: "iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28 iwl3945: No space for Tx" cat /sys/class/leds/iwl*assoc/trigger shows: none ide-disk AC-online BAT0-charging-or-full BAT0-charging BAT0-full phy1rx phy1tx [phy1assoc] phy1radio rfkill1 Because I absolutely HATE the LED light blinking in my face over and over again, I figured out (with help) to echo "none" > /sys/class/leds/iwl-*:assoc/trigger. Note that echo'ing "none" to any of the other 4 trigger files did not stop the blinking - only the assoc trigger did. Now cat on the trigger file shows: [none] ide-disk AC-online BAT0-charging-or-full BAT0-charging BAT0-full phy1rx phy1tx phy1assoc phy1radio rfkill1 Anyhow, as soon as I did that (and made it permanent by adding it to the wireless startup scripts) the REPLY_LEDS_CMD errors stopped happening. Please recall that with the old ipw driver (10.X), the led would be off if there was no connection, blinking while making a connection, and solid once the connection was made. In 11.0 we had no led at all. Now, in 11.1, the led blinked all the time, even after the connection was established. My bug for that (# 462967) was made INVALID because supposedly it is supposed to blink like that. I think it should work like it used to - blink only while establishing the connection. So, here's the rub: Could the blinking actually have been caused by the error in the system's attempts to send LEDS_CMDs, and can we fix whatever is causing that error? Reproducible: Always Steps to Reproduce: 1. buy a laptop with an Intel 3945 wireless 2. connect with Network Manager 3. Watch the pretty blinking led -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.