Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 06 Nov 2016 12:26:48 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-wireless@FreeBSD.org
Subject:   [Bug 214264] iwn on 11.0 (Centrino Wireless-N 2230)
Message-ID:  <bug-214264-21060@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214264

            Bug ID: 214264
           Summary: iwn on 11.0 (Centrino Wireless-N 2230)
           Product: Base System
           Version: 11.0-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: wireless
          Assignee: freebsd-wireless@FreeBSD.org
          Reporter: neptunium.element@gmail.com
                CC: freebsd-amd64@FreeBSD.org
                CC: freebsd-amd64@FreeBSD.org

I have Centrino Wireless-N 2230 adapter (Lenovo IdeaPad S400) which worked =
well
on 10.X. On 11.0-p2 I experienced a lot of problems with it.

Sometimes (albeit not always), on boot, I see something like this:

---------------------------------------------------------------------------
iwn0: scan timeout
iwn0: iwn_read_firmware: ucode rev=3D0x12a80601
wlan0: link state changed to UP
iwn0: iwn_intr: fatal firmware error
firmware error log:
  error type      =3D "UNKNOWN" (0x00002529)
  program counter =3D 0x00029DDC
  source line     =3D 0x000000AC
  error data      =3D 0x0000000100000036
  branch link     =3D 0x00029DBE00029DBE
  interrupt link  =3D 0x0000EC7A00000000
  time            =3D 7160
driver status:
  tx ring  0: qid=3D0  cur=3D0   queued=3D0=20=20
  tx ring  1: qid=3D1  cur=3D0   queued=3D0=20=20
  tx ring  2: qid=3D2  cur=3D0   queued=3D0=20=20
  tx ring  3: qid=3D3  cur=3D2   queued=3D0=20=20
  tx ring  4: qid=3D4  cur=3D0   queued=3D0=20=20
  tx ring  5: qid=3D5  cur=3D0   queued=3D0=20=20
  tx ring  6: qid=3D6  cur=3D0   queued=3D0=20=20
  tx ring  7: qid=3D7  cur=3D0   queued=3D0=20=20
  tx ring  8: qid=3D8  cur=3D0   queued=3D0=20=20
  tx ring  9: qid=3D9  cur=3D60  queued=3D0=20=20
  tx ring 10: qid=3D10 cur=3D0   queued=3D0=20=20
  tx ring 11: qid=3D11 cur=3D0   queued=3D0=20=20
  tx ring 12: qid=3D12 cur=3D0   queued=3D0=20=20
  tx ring 13: qid=3D13 cur=3D0   queued=3D0=20=20
  tx ring 14: qid=3D14 cur=3D0   queued=3D0=20=20
  tx ring 15: qid=3D15 cur=3D0   queued=3D0=20=20
  tx ring 16: qid=3D16 cur=3D0   queued=3D0=20=20
  tx ring 17: qid=3D17 cur=3D0   queued=3D0=20=20
  tx ring 18: qid=3D18 cur=3D0   queued=3D0=20=20
  tx ring 19: qid=3D19 cur=3D0   queued=3D0=20=20
  rx ring: cur=3D42
iwn0: iwn_panicked: controller panicked, iv_state =3D 5; restarting
wlan0: link state changed to DOWN
iwn0: iwn_read_firmware: ucode rev=3D0x12a80601
wlan0: link state changed to UP
wlan0: link state changed to DOWN
iwn0: scan timeout
iwn0: iwn_read_firmware: ucode rev=3D0x12a80601
wlan0: link state changed to UP
---------------------------------------------------------------------------

Despite this, wifi works after it. However, often (albeit not always) after
suspend/resume, iwn0 cannot reconnect, with messages like this:

---------------------------------------------------------------------------
Nov  1 22:07:07 neptunium kernel: iwn0: iwn_read_firmware: ucode rev=3D0x12=
a80601
Nov  1 22:07:07 neptunium wpa_supplicant[39597]: wlan0: CTRL-EVENT-SCAN-FAI=
LED
ret=3D-1 retry=3D1
Nov  1 22:07:08 neptunium wpa_supplicant[39597]: ioctl[SIOCS80211, op=3D103,
val=3D0, arg_len=3D128]: Operation now in progress
Nov  1 22:07:08 neptunium wpa_supplicant[39597]: wlan0: CTRL-EVENT-SCAN-FAI=
LED
ret=3D-1 retry=3D1
Nov  1 22:07:09 neptunium wpa_supplicant[39597]: ioctl[SIOCS80211, op=3D103,
val=3D0, arg_len=3D128]: Operation now in progress
Nov  1 22:07:09 neptunium wpa_supplicant[39597]: wlan0: CTRL-EVENT-SCAN-FAI=
LED
ret=3D-1 retry=3D1
Nov  1 22:07:10 neptunium wpa_supplicant[39597]: ioctl[SIOCS80211, op=3D103,
val=3D0, arg_len=3D128]: Operation now in progress
Nov  1 22:07:10 neptunium wpa_supplicant[39597]: wlan0: CTRL-EVENT-SCAN-FAI=
LED
ret=3D-1 retry=3D1
---------------------------------------------------------------------------

or like this:

---------------------------------------------------------------------------
ifa_maintain_loopback_route: deletion failed for interface lo0: 48
wlan0: Ethernet address: 68:17:29:a1:b7:47
iwn0: iwn_read_firmware: ucode rev=3D0x12a80601
iwn0: iwn_read_firmware: ucode rev=3D0x12a80601
ifa_maintain_loopback_route: deletion failed for interface lo0: 48
ifa_maintain_loopback_route: deletion failed for interface wlan0: 3
wlan0: Ethernet address: 68:17:29:a1:b7:47
iwn0: iwn_read_firmware: ucode rev=3D0x12a80601
iwn0: iwn_read_firmware: ucode rev=3D0x12a80601
---------------------------------------------------------------------------

I'm aware of bug #208758 and bug #213444, which describe problems similar to
mine.=20

As for recommendations from bug #208758, I cannot kldload/kldunload if_iwn
(it's in the kernel), and device enable iwn0 (after disabling) causes immed=
iate
reboot.

As for recommendations from #213444, I'm currently testing=20
create_args_wlan0=3D"-ht"
However, AFAIU, it will not resolve "fatal firmware error".

As I said, I have no problems with iwn on 10.X.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214264-21060>