NetBSD Problem Report #42114

From www@NetBSD.org  Wed Sep 23 08:54:23 2009
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id 2B97963B8DF
	for <gnats-bugs@gnats.netbsd.org>; Wed, 23 Sep 2009 08:54:23 +0000 (UTC)
Message-Id: <20090923085423.0047E63B850@www.NetBSD.org>
Date: Wed, 23 Sep 2009 08:54:22 +0000 (UTC)
From: demelier.david@gmail.com
Reply-To: demelier.david@gmail.com
To: gnats-bugs@NetBSD.org
Subject: iwn0: could not lock memory
X-Send-Pr-Version: www-1.0

>Number:         42114
>Category:       kern
>Synopsis:       iwn0: could not lock memory
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Sep 23 08:55:00 +0000 2009
>Closed-Date:    Wed Apr 05 08:22:57 +0000 2017
>Last-Modified:  Wed Apr 05 08:22:57 +0000 2017
>Originator:     Demelier David
>Release:        NetBSD -current
>Organization:
>Environment:
NetBSD Fraise.malikania.org 5.99.16 NetBSD 5.99.16 (Fraise 0.1) #1: Mon Sep 21 13:15:25 CEST 2009  root@Fraise.malikania.org:/usr/home/markand/obj/sys/arch/amd64/compile/Fraise amd64

>Description:
Using the iwn(4) driver with wpa_supplicant / dhcpcd at boot makes a lot of "iwn0: could not lock memory".

The drivers works perfectly, these warnings doesn't block my connection, I can use the network.
>How-To-Repeat:

>Fix:

>Release-Note:

>Audit-Trail:
From: christos@zoulas.com (Christos Zoulas)
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, 
	gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc: 
Subject: Re: kern/42114: iwn0: could not lock memory
Date: Wed, 23 Sep 2009 17:45:14 -0400

 On Sep 23,  8:55am, demelier.david@gmail.com (demelier.david@gmail.com) wrote:
 -- Subject: kern/42114: iwn0: could not lock memory

 | >Number:         42114
 | >Category:       kern
 | >Synopsis:       iwn0: could not lock memory
 | >Confidential:   no
 | >Severity:       non-critical
 | >Priority:       low
 | >Responsible:    kern-bug-people
 | >State:          open
 | >Class:          sw-bug
 | >Submitter-Id:   net
 | >Arrival-Date:   Wed Sep 23 08:55:00 +0000 2009
 | >Originator:     Demelier David
 | >Release:        NetBSD -current
 | >Organization:
 | >Environment:
 | NetBSD Fraise.malikania.org 5.99.16 NetBSD 5.99.16 (Fraise 0.1) #1: Mon Sep 21 13:15:25 CEST 2009  root@Fraise.malikania.org:/usr/home/markand/obj/sys/arch/amd64/compile/Fraise amd64
 | 
 | >Description:
 | Using the iwn(4) driver with wpa_supplicant / dhcpcd at boot makes a lot of "iwn0: could not lock memory".
 | 
 | The drivers works perfectly, these warnings doesn't block my connection, I can use the network.
 | >How-To-Repeat:

 Are you sure you mean iwn and not wpi? I can't find the lock memory string
 anywhere in the driver.

 christos

From: David DEMELIER <demelier.david@gmail.com>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/42114: iwn0: could not lock memory
Date: Thu, 24 Sep 2009 12:26:59 +0200

 No no I'm really using the iwn(4) driver for my intel 4965.

 Cheers.
 David

 2009/9/23 Christos Zoulas <christos@zoulas.com>:
 > The following reply was made to PR kern/42114; it has been noted by GNATS=
 .
 >
 > From: christos@zoulas.com (Christos Zoulas)
 > To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
 > =A0 =A0 =A0 =A0gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
 > Cc:
 > Subject: Re: kern/42114: iwn0: could not lock memory
 > Date: Wed, 23 Sep 2009 17:45:14 -0400
 >
 > =A0On Sep 23, =A08:55am, demelier.david@gmail.com (demelier.david@gmail.c=
 om) wrote:
 > =A0-- Subject: kern/42114: iwn0: could not lock memory
 >
 > =A0| >Number: =A0 =A0 =A0 =A0 42114
 > =A0| >Category: =A0 =A0 =A0 kern
 > =A0| >Synopsis: =A0 =A0 =A0 iwn0: could not lock memory
 > =A0| >Confidential: =A0 no
 > =A0| >Severity: =A0 =A0 =A0 non-critical
 > =A0| >Priority: =A0 =A0 =A0 low
 > =A0| >Responsible: =A0 =A0kern-bug-people
 > =A0| >State: =A0 =A0 =A0 =A0 =A0open
 > =A0| >Class: =A0 =A0 =A0 =A0 =A0sw-bug
 > =A0| >Submitter-Id: =A0 net
 > =A0| >Arrival-Date: =A0 Wed Sep 23 08:55:00 +0000 2009
 > =A0| >Originator: =A0 =A0 Demelier David
 > =A0| >Release: =A0 =A0 =A0 =A0NetBSD -current
 > =A0| >Organization:
 > =A0| >Environment:
 > =A0| NetBSD Fraise.malikania.org 5.99.16 NetBSD 5.99.16 (Fraise 0.1) #1: =
 Mon Sep 21 13:15:25 CEST 2009 =A0root@Fraise.malikania.org:/usr/home/markan=
 d/obj/sys/arch/amd64/compile/Fraise amd64
 > =A0|
 > =A0| >Description:
 > =A0| Using the iwn(4) driver with wpa_supplicant / dhcpcd at boot makes a=
  lot of "iwn0: could not lock memory".
 > =A0|
 > =A0| The drivers works perfectly, these warnings doesn't block my connect=
 ion, I can use the network.
 > =A0| >How-To-Repeat:
 >
 > =A0Are you sure you mean iwn and not wpi? I can't find the lock memory st=
 ring
 > =A0anywhere in the driver.
 >
 > =A0christos
 >
 >

From: Patrick Welche <prlw1@cam.ac.uk>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/42114 iwn0: could not lock memory
Date: Thu, 23 Mar 2017 13:25:02 +0000

 As you are using a 4965, did this help?

 Author: msaitoh <msaitoh>
 Date:   Sat May 21 12:51:47 2011 +0000

     Add newer Wireless WiFi Link 4965 devices, Centrino Wireless-N 1030
     and Centrino Advanced-N 6230

 Locking changed quite a bit since then too - do you still see an issue?

 (Actually, that commit probably won't help, but the question still stands)

State-Changed-From-To: open->feedback
State-Changed-By: prlw1@NetBSD.org
State-Changed-When: Thu, 23 Mar 2017 13:33:31 +0000
State-Changed-Why:
a question was asked


From: David Demelier <demelier.david@gmail.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/42114
Date: Wed, 5 Apr 2017 09:27:00 +0200

 Sorry guys I don't have this laptop anymore.

State-Changed-From-To: feedback->closed
State-Changed-By: martin@NetBSD.org
State-Changed-When: Wed, 05 Apr 2017 08:22:57 +0000
State-Changed-Why:
Submitter can't test and the -current driver does not even contain the
error message any more - assume fixed.


>Unformatted:

Home	PR Database Search