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