amd64/175183: iwn(4) becomes unresponsive during initial configuration
Sean Bruno
sbruno at FreeBSD.org
Thu Jan 10 18:50:00 UTC 2013
>Number: 175183
>Category: amd64
>Synopsis: iwn(4) becomes unresponsive during initial configuration
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-amd64
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Jan 10 18:50:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Sean Bruno
>Release: PC-BSD 9.1
>Organization:
FreeBSD
>Environment:
FreeBSD powernoodle 9.1-RELEASE FreeBSD 9.1-RELEASE #2: Tue Nov 27 03:45:16 UTC 2012 root at darkstar:/usr/obj/pcbsd-build90/fbsd-source/9.1/sys/GENERIC amd64
>Description:
It appears that iwn(4) is having issues with initial configuration and setup. Using network manager in PC-BSD to add/configure a WPA enabled wireless network will result in iwn(4) becoming completely unresponsive. ifconfig up/down/scan will not do anything. The system will work *just fine* after a power cycle of the laptop. Setting the wireless switch off/on does not fix the issue either and there are no messages in the system logs to indicate what is going on.
This seems to happen on Lenovo Thinkpads T420/T520 with the following wireless chipset.
iwn0 at pci0:3:0:0: class=0x028000 card=0x13118086 chip=0x00858086 rev=0x34 hdr=0x00
vendor = 'Intel Corporation'
device = 'Centrino Advanced-N 6205'
class = network
bar [10] = type Memory, range 64, base 0xf5100000, size 8192, enabled
>How-To-Repeat:
>Fix:
Requres a power cycle of the laptop.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-amd64
mailing list