From owner-freebsd-arm@freebsd.org Sat Sep 29 18:52:24 2018 Return-Path: Delivered-To: freebsd-arm@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 440BE10A8774 for ; Sat, 29 Sep 2018 18:52:24 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B652283664 for ; Sat, 29 Sep 2018 18:52:23 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w8TIqErv058436 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 29 Sep 2018 11:52:16 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w8TIqDVk058435; Sat, 29 Sep 2018 11:52:13 -0700 (PDT) (envelope-from fbsd) Date: Sat, 29 Sep 2018 11:52:13 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-ID: <20180929185213.GA58381@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2018 18:52:24 -0000 For the first time in a few months I connected a monitor, Dell keyboard and mouse to my Pi3, presently running 12.0-ALPHA7 r338964 GENERIC arm64 which have all worked well since I got the Pi3 around six months ago. With the peripherals connected, the serial console spews Timeout poll on interrupt endpoint and does not seem to accept normal inputs, so it isn't possible to get into the debugger, boot an old kernel or otherwise try to sort out what's going on. disconnecting the monitor had no effect. Removing the keyboard/mouse restores normal behavior. Anybody got a hint what might be wrong? FWIW, this OS/kernel pair were compiled and installed with neither mouse/keyboard nor monitor connected. I wouldn't expect that to matter, but... Thanks for reading, bob prohaska