NetBSD Problem Report #32270
From cjs@cynic.net Thu Dec 8 23:49:36 2005
Return-Path: <cjs@cynic.net>
Received: from ironic.cynic.net (ironic.cynic.net [221.116.240.13])
by narn.netbsd.org (Postfix) with ESMTP id A90EF63B850
for <gnats-bugs@gnats.NetBSD.org>; Thu, 8 Dec 2005 23:49:35 +0000 (UTC)
Message-Id: <20051208234919.65EAA100F5@stoic.cynic.net>
Date: Fri, 9 Dec 2005 08:49:19 +0900 (JST)
From: cjs@cynic.net
To: gnats-bugs@netbsd.org
Subject: iwi may not reinitialize after suspend/resume
X-Send-Pr-Version: 3.95
>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
>Closed-Date:
>Last-Modified: Tue Aug 25 11:00:03 +0000 2009
>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
>Release-Note:
>Audit-Trail:
From: Lubomir Sedlacik <salo@Xtrmntr.org>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/32270: iwi may not reinitialize after suspend/resume
Date: Fri, 9 Dec 2005 01:26:07 +0100
--V4b9U9vrdWczvw78
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Dec 08, 2005 at 11:50:01PM +0000, cjs@cynic.net wrote:
> >Description:
>=20
> 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:
>=20
> iwi0: could allocate firmware DMA memory
> iwi0: could not load main firmware
this is a well known issue with iwi(4) in netbsd-3. this and other
related bugs are fixed in -current for some time now. the problem is
that the iwi(4) in HEAD is quite different to the one on netbsd-3,
including major net80211 update.
the proper long term fix would be to backport net80211 changes and all
the related wireless drivers changes to netbsd-3, for 3.1, ideally.
feel free to help.
regards,
(status of this PR should be probably changed to "suspended")
--=20
-- Lubomir Sedlacik <salo@{NetBSD,Xtrmntr,silcnet}.org> --
--V4b9U9vrdWczvw78
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)
iD8DBQFDmM8fiwjDDlS8cmMRAtEZAJ4rVOUSl2beznZcEzi1V6NBdsDztQCeIUCp
pRdpM9JGLnoHiJUzDEhUEl0=
=toCG
-----END PGP SIGNATURE-----
--V4b9U9vrdWczvw78--
From: Curt Sampson <cjs@cynic.net>
To: gnats-bugs@netbsd.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Subject: Re: kern/32270: iwi may not reinitialize after suspend/resume
Date: Fri, 9 Dec 2005 15:47:20 +0900 (JST)
On Fri, 9 Dec 2005, Lubomir Sedlacik wrote:
> the proper long term fix would be to backport net80211 changes and all
> the related wireless drivers changes to netbsd-3, for 3.1, ideally.
That seems to me to be a short-term fix; it dies when netbsd-3 dies and
the work is wasted. This being the case, I feel we might as well stick
with the short-term fix of "dd bs=256m."
My idea of a long-term fix is to release netbsd-4 sooner.
> (status of this PR should be probably changed to "suspended")
We have a workaround; perhaps it would be better to close it?
cjs
--
Curt Sampson <cjs@cynic.net> +81 90 7737 2974
The power of accurate observation is commonly called cynicism
by those who have not got it. --George Bernard Shaw
From: matthew green <mrg@eterna.com.au>
To: Curt Sampson <cjs@cynic.net>
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, gnats-bugs@netbsd.org
Subject: re: kern/32270: iwi may not reinitialize after suspend/resume
Date: Fri, 09 Dec 2005 20:00:57 +1100
IMO, the work around is, at best, unreliable. on my system sometimes
500mb works sometimes 600mb. sometimes 700mb. once i needed 750mb.
the system has 1GB of ram.
it may be the case that the fix for this problem could be pulled up
without the rest of the changes - curt, could you try applying
sys/dev/pci/if_iwi.c rev 1.27 to 3.0 branch?
.mrg.
State-Changed-From-To: open->feedback
State-Changed-By: jmcneill@NetBSD.org
State-Changed-When: Tue, 25 Aug 2009 10:43:38 +0000
State-Changed-Why:
This should be fixed in 5.0 and HEAD, can you confirm?
State-Changed-From-To: feedback->open
State-Changed-By: jmcneill@NetBSD.org
State-Changed-When: Tue, 25 Aug 2009 10:56:15 +0000
State-Changed-Why:
Submitter no longer has the hardware, can anyone else test it?
From: Curt Sampson <cjs@cynic.net>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, netbsd-bugs@netbsd.org,
gnats-admin@netbsd.org, jmcneill@NetBSD.org
Subject: Re: kern/32270 (iwi may not reinitialize after suspend/resume)
Date: Tue, 25 Aug 2009 19:54:53 +0900
> This should be fixed in 5.0 and HEAD, can you confirm?
Unfortunately, I cannot; I no longer have the laptop that had that issue.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.