Subject: kern/32270: iwi may not reinitialize after suspend/resume
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <cjs@cynic.net>
List: netbsd-bugs
Date: 12/08/2005 23:50:01
>Number:         32270
>Category:       kern
>Synopsis:       iwi may not reinitialize after suspend/resume
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 08 23:50:01 +0000 2005
>Originator:     Curt Sampson
>Release:        NetBSD 3.0_RC5 2005-12-05
>Organization:
>Environment:
System: NetBSD stoic.cynic.net 3.0_RC5 NetBSD 3.0_RC5 (GENERIC_LAPTOP) #0: Mon Dec 5 16:01:14 JST 2005 cjs@cjs.tabemo.com:/u/netbsd/build/i386-3.2005-12-05/obj/u/netbsd/src-3/sys/arch/i386/compile/GENERIC_LAPTOP i386
Architecture: i386
Machine: i386
>Description:

    After a suspend/resume, it appears that the iwi driver needs to
    re-load the firmware. However, due to fragmentation in kernel memory
    or something like that, it sometimes cannot do so, and produces the
    following error messages:

	iwi0: could allocate firmware DMA memory
	iwi0: could not load main firmware

>How-To-Repeat:

    Configure iwi0 interface. Run for some time. Suspend, then resume.

>Fix:

    Unknown, but a work-around is to put the following in /etc/apm/resume
    before attempting to do anything with the iwi interface:

	dd if=/dev/zero of=/dev/null bs=256m count=1