Bug 11806

Summary:	iwl3945 fails with microcode error
Product:	Networking	Reporter:	Johannes Berg (johannes)
Component:	Wireless	Assignee:	Reinette Chatre (reinette.chatre)
Status:	CLOSED CODE_FIX
Severity:	normal	CC:	linville, reinette.chatre, rjw
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	2.6.28 git	Subsystem:
Regression:	Yes	Bisected commit-id:
Bug Depends on:
Bug Blocks:	11808

Description Johannes Berg 2008-10-22 02:36:23 UTC

Latest working kernel version: 2.6.27
Earliest failing kernel version: v2.6.27-3158-g01f9a21 / v2.6.27-3169-gf93b673
Distribution: n/a
Hardware Environment: iwl 3945 wireless
Software Environment:
Problem Description: 3945 driver fails with microcode error

Steps to reproduce: load iwl3945, see it fail

See 
http://thread.gmane.org/gmane.linux.kernel.wireless.general/22395

for more information. I personally don't have this hardware, but the bug should be tracked.



A workaround is available, it is right now to install newer firmware. Commits 01f9a21af3644224ecc899adeea31dc00418ddae and f93b673fcfe2670ccb22434d2ec7660b9f1c3fb8 have been identified by Intel as causing the regression.

Comment 1 John W. Linville 2008-10-24 06:28:00 UTC

Shouldn't this have been considered an API change for the firmware?

Comment 2 Johannes Berg 2008-10-24 06:30:03 UTC

I was hoping we'd collect the outcome of the huge thread on the mailing list here, I lost track.

Comment 3 Reinette Chatre 2008-10-24 08:43:46 UTC

we are working on a solution based on recommendations from that thread. I will take these commits into account also.

Comment 4 Rafael J. Wysocki 2008-10-25 06:33:24 UTC

References : http://marc.info/?l=linux-kernel&m=122450235730661&w=4

Handled-By : Reinette Chatre <reinette.chatre@intel.com>

Comment 5 Rafael J. Wysocki 2008-11-06 16:07:59 UTC

Patch : http://marc.info/?l=linux-wireless&m=122583010822172&w=2

Comment 6 Reinette Chatre 2008-11-11 11:32:03 UTC

The patch is now in Linus's tree (http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14b5433606289dbc5b6fd70ced11462f80e95003 ). Can the bug be closed?

Comment 7 Rafael J. Wysocki 2008-11-11 12:36:46 UTC

Sure, closing.  Thanks!