Bug 32642 - iwl3945: Microcode SW error detected. Restarting 0x82000008
Summary: iwl3945: Microcode SW error detected. Restarting 0x82000008
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-04 18:17 UTC by Clemens Eisserer
Modified: 2011-06-28 18:27 UTC (History)
2 users (show)

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:

Attachments
complete log file (41.13 KB, text/plain)
2011-04-04 18:17 UTC, Clemens Eisserer 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Clemens Eisserer 2011-04-04 18:17:31 UTC 
Created attachment 53472 [details]
complete log file

At home I have a thompson TWG850-4G cable modem with built-in wireless, which causes my notebooks intel-3945 wlan card headacke.

Connection is quite unstable before, with 2.6.38.2 I now get messages like the following:

[  909.817839] iwl3945 0000:02:00.0: Microcode SW error detected. Restarting 0x82000008.
[  909.817849] iwl3945 0000:02:00.0: Loaded firmware version: 15.32.2.9
[  909.817885] iwl3945 0000:02:00.0: Start IWL Error Log Dump:
[  909.817891] iwl3945 0000:02:00.0: Status: 0x0002A2E4, count: 1
[  909.817897] iwl3945 0000:02:00.0: Desc       Time       asrtPC  blink2 ilink1  nmiPC   Line
[  909.818142] iwl3945 0000:02:00.0: SYSASSERT     (0x5) 3542521213 0x008B6 0x13756 0x00320 0x00000 764
[  909.818146] 
[  909.818276] iwl3945 0000:02:00.0: Start IWL Event Log Dump: display last 20 count
[  909.818319] iwl3945 0000:02:00.0: 3542520284 0x00400001      0219
[  909.818344] iwl3945 0000:02:00.0: 3542520285 0x00020041      0211
[  909.818369] iwl3945 0000:02:00.0: 3542520290 0x00000000      0212
Comment 1 Stanislaw Gruszka 2011-04-05 10:53:44 UTC 
Does disable_hw_scan=1 module parameter helps?
Comment 2 John W. Linville 2011-06-07 17:29:35 UTC 
Closing due to lack of response...
Note You need to log in before you can comment on or make changes to this bug.