Bugzilla – Bug 1979
SYSASSERT (#05) line 262 after triggering S3
Last modified: 2009-05-06 21:59:07
You need to log in before you can comment on or make changes to this bug.
Created an attachment (id=1966) [details] debug=0x0x40000's log Test Environment =============================================== Platform : Intel SDV M3M31 Wireless Card : Intel(R) WiFi Link 4965 OS : Redhat Fedora release 10 (Cambridge) 64bit AP : Cisco 1250 uCode : iwlwifi-4965-2.ucode 228.57.2.23 Source : commit 9b20f0642b71e36378ba7e53263a18d0d40193d2 (Tue Apr 21 10:06:52 2009) Issue ============================================== Microcode SW error detected in log messg after triggering S3. Steps to Reproduce ============================================== 1. rmmod iwlagn 2. modprobe iwlagn 3. ifconfig wlan0 up 4. iwconfig wlan0 channel <CHANNEL> essid <ESSID> -->connect to wireless LAN 5. ifconfig wlan0 <IP_ADDR> 6. echo -n mem > /sys/power/state 7. suspend from S3 and dmesg has echo fw error Part of dmesg log ============================================= Registered led device: iwl-phy6::radio Registered led device: iwl-phy6::assoc Registered led device: iwl-phy6::RX Registered led device: iwl-phy6::TX iwlagn 0000:01:00.0: Microcode SW error detected. Restarting 0x82000000. iwlagn 0000:01:00.0: Start IWL Error Log Dump: iwlagn 0000:01:00.0: Status: 0x000313E6, count: 5 iwlagn 0000:01:00.0: Desc Time data1 data2 line iwlagn 0000:01:00.0: SYSASSERT (#05) 0000000055 0x00000000 0x00000000 262 iwlagn 0000:01:00.0: blink1 blink2 ilink1 ilink2 iwlagn 0000:01:00.0: 0x0C83E 0x0C86A 0x006DA 0x00000 iwlagn 0000:01:00.0: Start IWL Event Log Dump: display count 140, wraps 0 iwlagn 0000:01:00.0: EVT_LOGT:0000000001:0x0000023b:0117 iwlagn 0000:01:00.0: EVT_LOGT:0000000014:0x00000000:1208 iwlagn 0000:01:00.0: EVT_LOGT:0000009626:0x0400009b:0401 iwlagn 0000:01:00.0: EVT_LOGT:0000011796:0x0401009c:0401 iwlagn 0000:01:00.0: EVT_LOGT:0000011809:0x04020010:0401 iwlagn 0000:01:00.0: EVT_LOGT:0000011833:0x00000080:0600 iwlagn 0000:01:00.0: EVT_LOGT:0000011839:0x00000008:0600 iwlagn 0000:01:00.0: EVT_LOGT:0000011846:0x00000100:0600 iwlagn 0000:01:00.0: EVT_LOGT:0000011848:0x00000200:0600 iwlagn 0000:01:00.0: EVT_LOGT:0000011853:0x00000200:0600 iwlagn 0000:01:00.0: EVT_LOGT:0000011855:0x00000117:1005 ... ... ... ... iwlagn 0000:01:00.0: EVT_LOGT:0000000038:0x00000001:1208 iwlagn 0000:01:00.0: EVT_LOGT:0000000048:0x11111111:1110 iwlagn 0000:01:00.0: EVT_LOGT:0000000065:0xf5060020:0454 iwlagn 0000:01:00.0: EVT_LOGT:0000000066:0x00000000:0472 iwlagn 0000:01:00.0: EVT_LOGT:0000000072:0x0000000b:0463 iwlagn 0000:01:00.0: EVT_LOGT:0000000074:0x00fff506:1111 iwlagn 0000:01:00.0: EVT_LOGT:0000000075:0x00000000:0651 iwlagn 0000:01:00.0: EVT_LOGT:0000000076:0x0000015b:0103 iwlagn 0000:01:00.0: EVT_LOGT:0000000102:0x00000125:0603 iwlagn 0000:01:00.0: EVT_LOGT:0000000115:0x0000018d:0604 iwlagn 0000:01:00.0: EVT_LOGT:0000000116:0x000001ad:0610 iwlagn 0000:01:00.0: EVT_LOGT:0000000116:0x00018f8c:0610 iwlagn 0000:01:00.0: EVT_LOGT:0000000117:0x00000000:0610 iwlagn 0000:01:00.0: EVT_LOGT:0000000185:0x00000000:0600 iwlagn 0000:01:00.0: EVT_LOGT:0000000244:0x00000000:1208 iwlagn 0000:01:00.0: EVT_LOGT:0000000345:0x00000653:1055 iwlagn 0000:01:00.0: EVT_LOGT:0000000346:0x000000f1:1055 iwlagn 0000:01:00.0: EVT_LOGT:0000000347:0x00018ea5:1073 iwlagn 0000:01:00.0: EVT_LOGT:0000000350:0x02000000:0600 iwlagn 0000:01:00.0: EVT_LOGT:0000000367:0x00000000:0651 iwlagn 0000:01:00.0: EVT_LOGT:0000000368:0x00000264:0601 iwlagn 0000:01:00.0: EVT_LOGT:0000000000:0x0000023b:0117 iwlagn 0000:01:00.0: EVT_LOGT:0000000042:0x0409001a:0401 iwlagn 0000:01:00.0: EVT_LOGT:0000000049:0x040a0018:0401 iwlagn 0000:01:00.0: EVT_LOGT:0000000070:0x00000000:0125 ieee80211 phy6: I iwl_irq_handle_error Restarting adapter due to uCode error. PM: Finishing wakeup. Restarting tasks ... done. e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX 0000:00:19.0: eth0: 10/100 speed: disabling TSO Registered led device: iwl-phy6::radio Registered led device: iwl-phy6::assoc Registered led device: iwl-phy6::RX Registered led device: iwl-phy6::TX wlan0: no probe response from AP 00:1d:70:93:91:70 - disassociating
Created an attachment (id=1971) [details] print power flags A few questions: - Did this work previously? When? - Does the system have L0s enabled? - Could you please run your test with the attached patch and debug=0x40100 ? Thank you
Log is saying that the driver is not allowing uCode to sleep ... driver must set bit 0 to "1" in POWER_TABLE command flags to allow sleep. With that diagnosis, can someone else take ownership of this bug? Thanks. -- Ben --
(In reply to comment #2) > Log is saying that the driver is not allowing uCode to sleep ... driver > must set bit 0 to "1" in POWER_TABLE command flags to allow sleep. > > With that diagnosis, can someone else take ownership of this bug? > > Thanks. > > -- Ben -- > Your initial diagnosis prompted my questions to Ximin. Seems that bit 0 will not be set to 1 if L0s is enabled. Assigning it to me until we can figure out where problem lies.
reply to Comment #1 >- Did this work previously? When? Do you mean log without this SYSASSERT in what patch (commit) before? >- Does the system have L0s enabled? Could you please tell me how to check system enable L0s or not?
(In reply to comment #4) > reply to Comment #1 > >- Did this work previously? When? > Do you mean log without this SYSASSERT in what patch (commit) before? yes - if we know that this used to work and when then we can run a bisect to determine which change caused this regression. > >- Does the system have L0s enabled? > Could you please tell me how to check system enable L0s or not? Hopefully it will be somewhere in your BIOS. We recently disabled some PS settings. Are you still encountering this problem after these changes?
(In reply to comment #5) > We recently disabled some PS settings. Are you still encountering this problem > after these changes? No, this issue does not appear on 2.6.30-rc4-wl.
(In reply to comment #6) > (In reply to comment #5) > > > We recently disabled some PS settings. Are you still encountering this problem > > after these changes? > > No, this issue does not appear on 2.6.30-rc4-wl. > Marking as FIXED.