NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/42114: iwn0: could not lock memory



The following reply was made to PR kern/42114; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost, 
        gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
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@localhost 
(demelier.david%gmail.com@localhost) 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@localhost:/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
 


Home | Main Index | Thread Index | Old Index