From owner-freebsd-wireless@freebsd.org  Tue Jan 26 20:30:36 2016
Return-Path: <owner-freebsd-wireless@freebsd.org>
Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E465A6E511
 for <freebsd-wireless@mailman.ysv.freebsd.org>;
 Tue, 26 Jan 2016 20:30:36 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6ED5BD4E
 for <freebsd-wireless@FreeBSD.org>; Tue, 26 Jan 2016 20:30:36 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0QKUaN1056179
 for <freebsd-wireless@FreeBSD.org>; Tue, 26 Jan 2016 20:30:36 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-wireless@FreeBSD.org
Subject: [Bug 206112] [rtwn] Under heavy load, "can't map mbuf (error 12)"
 arises
Date: Tue, 26 Jan 2016 20:30:36 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: wireless
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: evil.lombo@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-206112-21060-fIJ28mfhKq@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-206112-21060@https.bugs.freebsd.org/bugzilla/>
References: <bug-206112-21060@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2016 20:30:36 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206112

--- Comment #1 from Simone Mario Lombardo <evil.lombo@gmail.com> ---
A little strange news.

The issue seems arises when the laptop is booted after few hours of being s=
hut
down and it's related to the performance issue I cited; I need to reboot the
machine twice (!) to get nice performance and not getting the error.

I have put three firmware reset in a row in the if_rtwn.c and doubled the w=
ait
time before accessing to the registry after the reset and now the card is
usable after a fresh boot.

I'll test if it is sufficient to keep the wait state longer in the next day=
s or
it needs a "triple" firmware reset.

Simone

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