From owner-freebsd-wireless@freebsd.org Wed Jan 11 07:50:04 2017 Return-Path: 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 5B50CCAAFAB for ; Wed, 11 Jan 2017 07:50:04 +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 4B1A712F1 for ; Wed, 11 Jan 2017 07:50:04 +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 v0B7o4BV032312 for ; Wed, 11 Jan 2017 07:50:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203887] Integer divide panic Date: Wed, 11 Jan 2017 07:50:04 +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: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ml@netfence.it X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 07:50:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203887 --- Comment #3 from ml@netfence.it --- Hello. As I said, I added the proposed patch a long time ago and had no such panics for more than a year. However my laptop had another one yesterday. ani_state->listen_time is in fact 0! This is strange, since I don't think anything should change it between=20 ani_state->listen_time +=3D listen_time; and ofdm_phy_err_rate =3D ani_state->ofdm_phy_err_count * 1000 / ani_state->listen_time; Is it possible somthing changed this in another thread? (Please forgive my ignorance of the kernel if it's something that stupid). In any case, I'm enabling AH_DEBUG in the kernel. P.S. In the meantime I upgraded to 10.3. --=20 You are receiving this mail because: You are the assignee for the bug.=