Date: Sun, 24 May 2020 23:51:12 +0000 From: greg@unrelenting.technology To: "Warner Losh" <imp@bsdimp.com> Cc: "Dan Kotowski" <dan.kotowski@a9development.com>, "freebsd-arm" <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <a105c5eb39b54f2a02a9b21d1f71b4bf@unrelenting.technology> In-Reply-To: <CANCZdfrt=ijzc5rLyzZkqRy8JTwEhWhwXawGGWT85xM1mUvWXg@mail.gmail.com> References: <CANCZdfrt=ijzc5rLyzZkqRy8JTwEhWhwXawGGWT85xM1mUvWXg@mail.gmail.com> <SBSqkdZA-3beqJyVy2tMuk5GRmV22DVVnz_8sNDhYCNOjNPe1wgoiSCoOitGhtlBspk-Gk2MKFv4sUyJKy58mKOBpXrGtZoRQKqmDvB1xIg=@a9development.com> <LqTdXCGMiTFwSobCq9LtV5QVLOZ42AiBDUTC9UrdM67cUlD_I8Y7no-8F7d_vs3VDJwIFJLgHTSZVrbkIXXeZ_-hcU0FxfWj0dr-GvhKXHA=@a9development.com> <b04385d558850dc1dfa60fc398c9ac6c@unrelenting.technology> <CAPv3WKdyOzegfK4NJjKzXQTp9jGV9VkDRWxY%2BhDudzWQKkRfEQ@mail.gmail.com> <3e81db774e0fc1a3c2251c89b7629e1b@unrelenting.technology> <86119565e5927716a9feebabcb611871@unrelenting.technology> <f801aa134da12d1b4a34b87dbc180b4a@unrelenting.technology> <37858865a8ebddd3fe1e3a228a19ef62@unrelenting.technology> <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> <xoiJF1ZUP3-rgbxC8ZmJGQNpsJSyK4zsAXhbLl8Ml96Da1lBPGwPqn0ANf7q-GgthPAWePSR9QDCM5vKysd_3e2aGtp-0egUXu6AW3bhLDg=@a9development.com> <CANCZdfqbd_u35toFYKr4LKkCBwnRhutM5knjnVcGR018Jfo1Vw@mail.gmail.com> <6E6E4F0C-F85B-428B-B221-C5F704677076@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
May 25, 2020 1:15 AM, "Warner Losh" <imp@bsdimp.com> wrote:=0A=0A> On Fri= , May 22, 2020 at 7:46 PM myfreeweb <greg@unrelenting.technology> wrote:= =0A> =0A> It's not really polling the I/O. It's waiting for an interrupt = to keep it going. No interrupt, no=0A> update in the status -> panic. So = I'm guessing there's an interrupt issue at play here of some=0A> sort. Th= e polling path, which needs to be redone, doesn't use the same timeout st= uff, so it doesn't=0A> check to see if there's any complete requests befo= re failing (which is why it needs to be redone).=0A> We could likely just= throw it all away because it was there before we configured everything w= ith a=0A> config interrupt hook.=0A> Not sure about the root cause of the= interrupt issue is...a=0A=0AYep, I came to that understanding later in t= he thread.=0AIt's really weird but interrupts not working seems to make m= ost sense.=0A=0AOn the SAS HBA, the interrupt handler did a debug print t= hough..=0Aoddly enough, before intr_setup_irq's DEBUG print
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a105c5eb39b54f2a02a9b21d1f71b4bf>