From owner-freebsd-wireless@freebsd.org Fri May 4 00:54:53 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 EF670FC1E76 for ; Fri, 4 May 2018 00:54:52 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 853B875FB4 for ; Fri, 4 May 2018 00:54:52 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1fEOzp-000NA9-83; Thu, 03 May 2018 17:54:49 -0700 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id w440smJf089040; Thu, 3 May 2018 17:54:48 -0700 (PDT) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Thu, 3 May 2018 17:54:48 -0700 From: Oleksandr Tymoshenko To: Tim Chase Cc: "freebsd-wireless@freebsd.org" Subject: Re: ath0: could not map interrupt (again?) Message-ID: <20180504005448.GA89012@bluezbox.com> References: <20180502165745.59a5bfc4@bigbox.christie.dr> <20180502211001.550d290c@bigbox.christie.dr> <20180503192743.639240d0@bigbox.christie.dr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180503192743.639240d0@bigbox.christie.dr> X-Operating-System: FreeBSD/11.1-RELEASE-p4 (amd64) User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Tim Chase (freebsd@tim.thechases.com) wrote: > On 2018-05-02 21:10, Tim Chase wrote: > > On 2018-05-02 23:21, Adrian Chadd wrote: > > > CAn you try booting freebsd-head and see if it's any better? > > [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 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: Fri, 04 May 2018 00:54:53 -0000 Tim Chase (freebsd@tim.thechases.com) wrote: > On 2018-05-02 21:10, Tim Chase wrote: > > On 2018-05-02 23:21, Adrian Chadd wrote: > > > CAn you try booting freebsd-head and see if it's any better? > > > > At your advice, I created a boot image of 12.0-CURRENT r333017 but > > see the same "could not map interrupt" in my dmesg that I got on > > 11.x > > If it makes any difference, booting OpenBSD 6.3 on the machine says > they're both successfully on INT 17 (the ath0/athn0 works there) > > ppb0 at pci0 dev 28 function 0 "Intel SCH PCIE" rev 0x07: apic 2 int 17 > ... > athn0 at pci2 dev 0 function 0 "Atheros AR9281" rev 0x01: apic 2 int 17 > athn0: AR9280 rev 2 (2T2R), ROM rev 22, address 00:24:d2:b3:8c:b4 > > so it looks like the interrupt *can* be shared, it just appears that > FreeBSD is doing something peculiar with it. It looks like PCI bridge allocates interupt without RF_SHAREABLE (see dev/pci/pci_pci.c, pcib_alloc_pcie_irq). Could you test this patch [1]? I am not sure if non-shareable IRQs for PCI/PCI bridge is a design decision or it's just that nobody has hit this problem before. [1] https://people.freebsd.org/~gonzo/patches/pci_pci-shareable-irq.diff -- gonzo