From owner-freebsd-wireless@freebsd.org Sun May 13 03:24:56 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A852FE3A85 for ; Sun, 13 May 2018 03:24:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A0D48871EF for ; Sun, 13 May 2018 03:24:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5FA34FE3A82; Sun, 13 May 2018 03:24:55 +0000 (UTC) Delivered-To: wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20292FE3A81 for ; Sun, 13 May 2018 03:24:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD858871E2 for ; Sun, 13 May 2018 03:24:54 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id DE9541F45E for ; Sun, 13 May 2018 03:24:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4D3OrgI005328 for ; Sun, 13 May 2018 03:24:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4D3Or9O005326 for wireless@FreeBSD.org; Sun, 13 May 2018 03:24:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 228210] 11.2-BETA1 - DNS resolution does not work with local_unbound; cannot ping with local_unbound disabled Date: Sun, 13 May 2018 03:24:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctorwhoguy@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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.25 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: Sun, 13 May 2018 03:24:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228210 Bug ID: 228210 Summary: 11.2-BETA1 - DNS resolution does not work with local_unbound; cannot ping with local_unbound disabled Product: Base System Version: 11.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: wireless Assignee: wireless@FreeBSD.org Reporter: doctorwhoguy@gmail.com I've only tested this on an Acer Aspire One D255, but this was an issue wit= h a recent 11.1-STABLE snapshot and is still true with 11.2-BETA1. I had no problems with 11.0 or 11.1 RELEASE on this same netbook. On a completely fr= esh installation with local_unbound enabled, I am able to ping IP addresses but cannot ping domain names. I also tried disabling local_unbound, but then I = was unable to even ping IP addresses (even on my LAN). In the case of local_unb= ound being disabled, /etc/resolv.conf was being automatically generated with the correct DNS nameserver info from DHCP, so I could not figure out why I wasn= 't able to ping anything (including my router). The only solution that has worked for me was the advice I found at https://forums.freebsd.org/threads/unbound.60475/ which suggested that I add module-config: iterator to /var/unbound/unbound.conf. The networking mostly worked, with local_unbo= und enabled, after that change. It was kind of flaky after that where it would = work for a while then stop until rebooting. Then after a few reboots it seemed somewhat reliable. In any case, the line which I added was absent from the config for 11.1-RELEASE, and it worked just fine under 11.1-RELEASE. And to= the best of my recollection, it also worked fine with local_unbound disabled un= der 11.1-RELEASE. So there has apparently been some kind of regression. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sun May 13 12:36:02 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 194BCFDA65A for ; Sun, 13 May 2018 12:36:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A223E6C8EF for ; Sun, 13 May 2018 12:36:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6221BFDA659; Sun, 13 May 2018 12:36:01 +0000 (UTC) Delivered-To: wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E4D5FDA658 for ; Sun, 13 May 2018 12:36:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D9E556C8EC for ; Sun, 13 May 2018 12:36:00 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1110424006 for ; Sun, 13 May 2018 12:36:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4DCZxjP069281 for ; Sun, 13 May 2018 12:35:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4DCZxNq069276 for wireless@FreeBSD.org; Sun, 13 May 2018 12:35:59 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 211653] iwm panic on 11.0-BETA4, 11.[01]-{RC[123]|RELEASE}, 11-Stable (Intel 7260) Date: Sun, 13 May 2018 12:35:59 +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-STABLE X-Bugzilla-Keywords: crash, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ish@amail.plala.or.jp X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: wireless@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: resolution bug_status 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.25 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: Sun, 13 May 2018 12:36:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211653 Masachika ISHIZUKA changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|Open |Closed --- Comment #11 from Masachika ISHIZUKA --- iwm (ac 7260) is not panic on 11.2-BETA1. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sun May 13 21:01:00 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 087D9FD3080 for ; Sun, 13 May 2018 21:01:00 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9CAB386B48 for ; Sun, 13 May 2018 21:00:59 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 60693FD3076; Sun, 13 May 2018 21:00:59 +0000 (UTC) Delivered-To: wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 260EFFD3074 for ; Sun, 13 May 2018 21:00:59 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A568A86B3E for ; Sun, 13 May 2018 21:00:58 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id E49E97CB for ; Sun, 13 May 2018 21:00:57 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4DL0vfC038424 for ; Sun, 13 May 2018 21:00:57 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4DL0vgx038409 for wireless@FreeBSD.org; Sun, 13 May 2018 21:00:57 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201805132100.w4DL0vgx038409@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: wireless@FreeBSD.org Subject: Problem reports for wireless@FreeBSD.org that need special attention Date: Sun, 13 May 2018 21:00:57 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 13 May 2018 21:01:00 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 206801 | iwn(4) page fault on netif restart Open | 154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open | 163312 | [panic] [ath] kernel panic: page fault with ath0 Open | 166190 | [ath] TX hangs and frames stuck in TX queue Open | 166357 | [ath] 802.11n TX stall when the first frame in th Open | 169362 | [ath] AR5416: radar pulse PHY errors sometimes in Open | 169433 | [iwn] iwn(4) doesn't support 6235 chip. Open | 211689 | panic with lagg failover wireless ath and iwm 8 problems total for which you should take action. From owner-freebsd-wireless@freebsd.org Mon May 14 05:13:22 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0538BFD04D3 for ; Mon, 14 May 2018 05:13:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 940727568F for ; Mon, 14 May 2018 05:13:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 579FDFD04C3; Mon, 14 May 2018 05:13:21 +0000 (UTC) Delivered-To: wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43884FD04C2 for ; Mon, 14 May 2018 05:13:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CDE1B75689 for ; Mon, 14 May 2018 05:13:20 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 243E2788A for ; Mon, 14 May 2018 05:13:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4E5DKNd078103 for ; Mon, 14 May 2018 05:13:20 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4E5DKsJ078102 for wireless@FreeBSD.org; Mon, 14 May 2018 05:13:20 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 228210] 11.2-BETA1 - DNS resolution does not work with local_unbound; cannot ping with local_unbound disabled Date: Mon, 14 May 2018 05:13:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: component assigned_to keywords 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.25 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: Mon, 14 May 2018 05:13:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228210 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Component|wireless |misc Assignee|wireless@FreeBSD.org |net@FreeBSD.org Keywords| |regression --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Mon May 14 16:48:39 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B5D2DF9873 for ; Mon, 14 May 2018 16:48:39 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: from mail-it0-x241.google.com (mail-it0-x241.google.com [IPv6:2607:f8b0:4001:c0b::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9FA906AFAB for ; Mon, 14 May 2018 16:48:38 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: by mail-it0-x241.google.com with SMTP id 70-v6so12533113ity.2 for ; Mon, 14 May 2018 09:48:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=f9cNpChH6A2M7QZ/DRg9nPiKOr65PugfLsjcQR4Eu7I=; b=uW7SM2Jhr190yNvs21+5BV4uYrQ/H0tx79zCYkMpfB4d09Ssmt8JRovNRrXNID9VeK z5K0ZdWq8lQ7H6CSjQGpuFr3o3kHXDw2y2QP3LeA9naaiQKRx3oucMbuDP0aRqG02TUH r0CZliKp+R0YoNyI5h41fPZqqR38I9FUtX2P9i3C2AKGyZPOR+LqFau70+K3yHsVl0TA Ei2zzuy4Exf3YYbYWmWRH8wxmyh2fvEQXxcNeerKE5OjtpwD6ZJiybvQUZOXY3b/vHXK CHp1ecR2CQslWGKxSiRLJOaj1ogPijfjY0GYvdyjVgmT+LnNthRxr/DbVyx1NEuTlPAG yBHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=f9cNpChH6A2M7QZ/DRg9nPiKOr65PugfLsjcQR4Eu7I=; b=DXSo5W7URsz5i380yf/stUAHN+5g/+HEfl7IUx6ClEySnCnkOab/HkaYom+VvLfXA0 D/5WBuBQnFXn5n2Y11RzFqkKf16nrKiKH72D6L2qPj/mnAqpAIoZ5Up+ARreGK6fN7ku eTZzAMRqJvaDeeNC97COJkN6vJyaSqUnAYPDA0LQ4grWJH1lkoCLHIIOTAr+d39IYEom dZjmBdAlNw8OQk4E+Y69l5/Gs0Ol8SKC7s+AZELC0iGbPKsvDtZzzp8Oec+B30h9Ge0q 7lIeF7NIguT5J//KbcsKc4t2AC9Zo6fekE9zwL/tX/7SaBvAwHlJKSBRb5S/LUkQQzeL OaKA== X-Gm-Message-State: ALKqPwfkAJIXnlPB+2fHJjZ43/XY7LuxSogVYm8jYUyA9UGfinoqpSDA L5w5BlXD7xK8VuvodaSgH+Sii0ahmMl5oc4iPZyNyxGh X-Google-Smtp-Source: AB8JxZpzvh1uWK9q9BXsHE3aZE8iXAa51ACFgKNcSrCjzEzLr/rfOq1Aci7YMcnU/kdzF6OQ9IJX2DaY4CT8W3uv2gc= X-Received: by 2002:a24:29cb:: with SMTP id p194-v6mr10393932itp.128.1526316517600; Mon, 14 May 2018 09:48:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.192.160.196 with HTTP; Mon, 14 May 2018 09:48:17 -0700 (PDT) From: Farhan Khan Date: Mon, 14 May 2018 12:48:17 -0400 Message-ID: Subject: Handling C2H debug interrupt on rtwn(8) To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.26 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: Mon, 14 May 2018 16:48:39 -0000 Hi all, I have a question regarding catching an unhandled C2H event interrupt. rtwn(4) receives C2H interrupts from the device. One type is R92C_C2H_EVT_DEBUG as defined in sys/dev/rtwn/rtl8192c/r92c_fw_cmd.h as 0. Interrupts are handled in r92c_handle_c2h_task() in sys/dev/rtwn/rtl8192c/r92c_fw.c line 479. I noticed that rtl8188ee (driver in development) sends R92C_C2H_EVT_DEBUG, but they are not handled, resulting in the 'default' case, which is to print a warning into the kernel messages buffer. As a result, I am seeing a ton of warning messages across my terminal 1-2 times a second. This is not a problem for me in development, but would problematic for any user of the driver, as it would fill up the kernel messages buffer very quickly. I reviewed Linux's equivalent code and found that rtl8723ae is the only one of the rtlwifi drivers that checks C2H_EVT_HOST_CLOSE (also defined as 0), and immediately just does a 'return'. Would it be correct for me to imitate this behavior, check for the same C2H message type, and immediately issue a 'break'? I did so in my dev repository here: https://github.com/khanzf/rtl8188ee/commit/b9dd37c8f40af1bda1ec8d82fdaa051840b85e75 . Thanks! -- Farhan Khan PGP Fingerprint: B28D 2726 E2BC A97E 3854 5ABE 9A9F 00BC D525 16EE From owner-freebsd-wireless@freebsd.org Mon May 14 18:03:01 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2081EDFDD8D for ; Mon, 14 May 2018 18:03:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 905DC7EE68 for ; Mon, 14 May 2018 18:03:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id j4-v6so15103275wme.1 for ; Mon, 14 May 2018 11:03:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HEpFVbDQn9XxCf910lcjAx3Mn2wvm+KNH4WVeolOMWI=; b=S6eH0Y8mxkYJeTiE1Dul8hKGHJeD1AuPdrk37A72W2MHyaBPBVah67YaxYrrGmc2PD 7MJX7GcKLbNbjbwsDNkrS/SS+C31bc4uFA9vIyVmvMdV8efZ0UGKHy9zW+PxnyPDFoFH ajW6bLrZwYddYh/8+YXX8FSHGRJoVyX03LV9fc9kolDvKLIgEZ2ZJrDWFq6/DDzXtOj3 Soh81gwVgrzs15GrPLyIud3OOlBJyFwXgxOOrqcwHk/kDhIwk/lsXoVZbz28H1k60mB7 xpx0KxB4Fn5IErqZgtQYUMv5vDtCHpKoiP/qVaWvjoNeHiIaeqguhDSy2hZa1no/w/SK d/uA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HEpFVbDQn9XxCf910lcjAx3Mn2wvm+KNH4WVeolOMWI=; b=VlFohFtCwqefEXRUKR5BFeLFkW8Q+4JEJ9/t3KsO3pk6nSeNYHqeszlAZttBjGxfqA NkA8ryv6MDtV5Uoha0kLBR1lU95WURzgiAnoLGs8AXQJXBkBu2/2/+BpLLcjfi8cJRDV sOnlOcgXPNYH91/ZJY+Itm9Rd43iasQn9WomdzGRRiJ65dZrmqdwvA/29VBVVmCS60hQ 8PsMczcsYoRljHZIHNRRA1oTtDUkju0IAANNBLW83FcVg3nFQtDW3dJ6LT4l5zZEa4fn aJnfdrJaQ7RgFeHpXCxTTS8aVXRGG4CA0uGHtc5pOkcSPsqGxOaInTetIGWbSJz+PNcH 1g6Q== X-Gm-Message-State: ALKqPwfC4YNH1Xv5AZqErh/hjiB9znKcy/gHdn8UO1EqP2BUaVNcFQOe XeUMmw+yM9OI14Qp8Kf621S3tNLbCKYKTPJcq+A= X-Google-Smtp-Source: AB8JxZrmY5hMrUlug5CQG/k/3LTblDB9ZohiMro3f9kysBsLTIYZJad2PsAhql5M1o4YOsmsTdlc7LN3ddMDjOGpVWE= X-Received: by 2002:a1c:da50:: with SMTP id r77-v6mr5421005wmg.105.1526320979508; Mon, 14 May 2018 11:02:59 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Adrian Chadd Date: Mon, 14 May 2018 11:02:52 -0700 Message-ID: Subject: Re: Handling C2H debug interrupt on rtwn(8) To: Farhan Khan Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.26 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: Mon, 14 May 2018 18:03:01 -0000 It sounds like you need to ignore it! -adrian On Mon, 14 May 2018 at 09:48, Farhan Khan wrote: > Hi all, > I have a question regarding catching an unhandled C2H event interrupt. > rtwn(4) receives C2H interrupts from the device. One type > is R92C_C2H_EVT_DEBUG as defined in sys/dev/rtwn/rtl8192c/r92c_fw_cmd.h as > 0. Interrupts are handled in r92c_handle_c2h_task() in > sys/dev/rtwn/rtl8192c/r92c_fw.c line 479. I noticed that rtl8188ee (driver > in development) sends R92C_C2H_EVT_DEBUG, but they are not handled, > resulting in the 'default' case, which is to print a warning into the > kernel messages buffer. > As a result, I am seeing a ton of warning messages across my terminal 1-2 > times a second. This is not a problem for me in development, but would > problematic for any user of the driver, as it would fill up the kernel > messages buffer very quickly. > I reviewed Linux's equivalent code and found that rtl8723ae is the only one > of the rtlwifi drivers that checks C2H_EVT_HOST_CLOSE (also defined as 0), > and immediately just does a 'return'. > Would it be correct for me to imitate this behavior, check for the same C2H > message type, and immediately issue a 'break'? I did so in my dev > repository here: https://github.com/khanzf/rtl8188ee/commit/b9dd37c8f40af1bda1ec8d82fdaa051840b85e75 > . > Thanks! > -- > Farhan Khan > PGP Fingerprint: B28D 2726 E2BC A97E 3854 5ABE 9A9F 00BC D525 16EE > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org " From owner-freebsd-wireless@freebsd.org Tue May 15 05:50:33 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B44DEDF079 for ; Tue, 15 May 2018 05:50:33 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B1E984C69 for ; Tue, 15 May 2018 05:50:33 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id 144-v6so16254622iti.5 for ; Mon, 14 May 2018 22:50:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=OY+IdaO3jzkU4SSlC9V9bKyO5LALszN8gqX5m+99wY4=; b=bdSrRmQxJkRnd6/HJGgnZwUgf0lc+X1cEYlsSwGLpGyhl1S9TTwqElh0/O4Xets6wH Pe5u8ARA5pg8HNn1+1WLZ3wL9i/2ZhZpQCTiF/+JDvnSsbBxD/9hZ9Gj+PXnTAAyI2YR 84xomqyV9fDLt34uKgzywSnt7LThEwDCJQXtsWJs/XCoBKpNQgFhiw6fuHHmEDfl8+Jl UPsPlfTZNB9RC3j5d35gSAAT+H1bb9nYZ4u1digQWNL7gjk3NyWne8jj7M6naAKtTOho NIwexWzsVtHQmGynnEKktmOhNMspLOhMY+T7aos+w7v490x2A2fpCGd8VXMph4K68+F6 l3xg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=OY+IdaO3jzkU4SSlC9V9bKyO5LALszN8gqX5m+99wY4=; b=dlo2bI9ZPcX+axjOwkVBYIYxmpBzWI9GSacEPDZ7YQqzAGq8TeFgpztR89v6N4rorg 2alofCNT/QGwCc7QsKWlPWa8+HTWTjxD6lNpNQEpELh6vvq2WH40HvzCXSTFNnABAL2e CV4omSeNntfh4SbCDWCobZQrPPLkLiYxjpPorQXT13Mtb+KxvdkZOPEfCqNJg+DfSGJc axUH+hHSw2M/wuzhi1Dd7OP9RJN0/9IrvoynPW0DlkzvBPOLWmZgKAHfHW7RDpKi55eY q6x+DZNoiMhVyRPvpHSawa5fEWAU7C4R1EoXrFh98jXTmk/Vjc0MQzE8dk3wZHqxE8V7 oEZw== X-Gm-Message-State: ALKqPwd0Hq3X7H+blP60Sh39Yj0YKt7hPz0oNJxkMurkKqIEuYedAO36 YY86y0LX1S1peC2wVyW3s6fBNae9Um9aTdvfnhW1Ig== X-Google-Smtp-Source: AB8JxZrQwybvQoaFyfy5Y9m9hRiZcIZ+lDexZPmrHpCH+WawH8d4CpK4gEtXGmBygi/vwqEzT7grHmDE/IoUJqAGbYw= X-Received: by 2002:a24:29cb:: with SMTP id p194-v6mr12764298itp.128.1526363431849; Mon, 14 May 2018 22:50:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.192.160.196 with HTTP; Mon, 14 May 2018 22:50:11 -0700 (PDT) From: Farhan Khan Date: Tue, 15 May 2018 01:50:11 -0400 Message-ID: Subject: C2H interrupt causing kernel panics To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.26 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: Tue, 15 May 2018 05:50:33 -0000 Hi all, I have a kernel panic question. When I load my module with the firmware and turn it on (ifconfig wlan0 up) it will start receiving C2H interrupts. Great. But I noticed that if I unload the module *without* running "ifconfig wlan0 down", it will trigger a kernel panic. It appears this is caused by a C2H interrupt function still running after the module is unloaded. If I bring the interface down, I have no problems. Am I missing something here? Is there a proper way to disable C2H interrupts? Thanks, -- Farhan Khan PGP Fingerprint: B28D 2726 E2BC A97E 3854 5ABE 9A9F 00BC D525 16EE From owner-freebsd-wireless@freebsd.org Wed May 16 18:13:33 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FD1CEA87E2 for ; Wed, 16 May 2018 18:13:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EBA7874ABE for ; Wed, 16 May 2018 18:13:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id ABDE1EA87E1; Wed, 16 May 2018 18:13:32 +0000 (UTC) Delivered-To: wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A5B9EA87E0 for ; Wed, 16 May 2018 18:13:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 352F074ABB for ; Wed, 16 May 2018 18:13:32 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 807C027B4A for ; Wed, 16 May 2018 18:13:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4GIDVh5078037 for ; Wed, 16 May 2018 18:13:31 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4GIDV38078029 for wireless@FreeBSD.org; Wed, 16 May 2018 18:13:31 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 227602] [regression] r304629 broke ralink USB hostap mode with authmode WPA2 Date: Wed, 16 May 2018 18:13:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: damjan.jov@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.26 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, 16 May 2018 18:13:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227602 --- Comment #17 from Damjan Jovanovic --- It works with that commit. Thank you so much! .-'"""""'-.=20=20=20=20=20=20=20=20 .' `.=20=20=20=20 / . . \=20=20=20 : :=20 | |=20=20 : \ / :=20=20=20=20 \ `.____.' /=20=20=20=20=20=20=20=20=20=20=20=20 `. .'=20=20=20=20=20 `-._____.-' --=20 You are receiving this mail because: You are the assignee for the bug.=