From owner-freebsd-arm@freebsd.org Sun May 24 23:51:22 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EF7022DE66F for ; Sun, 24 May 2020 23:51:22 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [91.121.223.63]) (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 49VcSS6Gwrz3fZK for ; Sun, 24 May 2020 23:51:20 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1590364272; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=89hvFFFV5rIuOeZ7PbkXN9kJwe30HzWzI6YW4CPYIzY=; b=ip5bLXPnvJg9z56q+R2kR+cxTQV7jqaLOYz+2C9ttuYYDbqy5J+HMHUrv3pmihQI8Pqs94 5mxfQwE5l0cwO09vZg7tK3sQIPh1oyl3+Urdw7VmrICJDybrH6s4et6rxh/DevQXd7LpYf jfKuQe4nhWkloTg3ScwDmZQ5QybRMW4= Date: Sun, 24 May 2020 23:51:12 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: "Warner Losh" Cc: "Dan Kotowski" , "freebsd-arm" In-Reply-To: References: <3e81db774e0fc1a3c2251c89b7629e1b@unrelenting.technology> <86119565e5927716a9feebabcb611871@unrelenting.technology> <37858865a8ebddd3fe1e3a228a19ef62@unrelenting.technology> <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> <6E6E4F0C-F85B-428B-B221-C5F704677076@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49VcSS6Gwrz3fZK X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=ip5bLXPn; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 91.121.223.63 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.49 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.980]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:91.121.223.63]; NEURAL_HAM_LONG(-0.98)[-0.978]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.53)[-0.531]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:91.121.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2020 23:51:23 -0000 May 25, 2020 1:15 AM, "Warner Losh" wrote:=0A=0A> On Fri= , May 22, 2020 at 7:46 PM myfreeweb 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