From owner-freebsd-arm@FreeBSD.ORG Tue Jul 22 04:15:24 2008 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF98D106566C for ; Tue, 22 Jul 2008 04:15:24 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 80D148FC0A for ; Tue, 22 Jul 2008 04:15:24 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m6M4CFJH083656; Mon, 21 Jul 2008 22:12:15 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 21 Jul 2008 22:12:26 -0600 (MDT) Message-Id: <20080721.221226.-890724651.imp@bsdimp.com> To: ticso@cicely.de, ticso@cicely7.cicely.de From: "M. Warner Losh" In-Reply-To: <20080722003612.GF58113@cicely7.cicely.de> References: <20080117105854.GA44923@zibbi.meraka.csir.co.za> <20080722003612.GF58113@cicely7.cicely.de> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org Subject: Re: sshd broken on arm? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2008 04:15:24 -0000 In message: <20080722003612.GF58113@cicely7.cicely.de> Bernd Walter writes: : On Thu, Jan 17, 2008 at 12:58:54PM +0200, John Hay wrote: : > Hi Guys, : > : > I just did a new build using RELENG_7 for the arm (Avila boards) and then : > found that I cannot ssh into them. The sshd crash with a bus error just : > after you entered your username and password. My build of mid November : > did not do it. Anybody got ideas? : > : > The last part of "sshd -Dddd" on the arm board looks like this: : > : > debug1: server_input_channel_req: channel 0 request pty-req reply 0 : > debug1: session_by_channel: session 0 channel 0 : > debug1: session_input_channel_req: session 0 req pty-req : > debug1: Allocating pty. : > debug3: mm_request_send entering: type 25 : > debug3: monitor_read: checking request 25 : > debug3: mm_answer_pty entering : > debug1: session_new: init : > debug1: session_new: session 0 : > debug3: mm_pty_allocate: waiting for MONITOR_ANS_PTY : > debug3: mm_request_receive_expect entering: type 26 : > debug3: mm_request_receive entering : > debug3: mm_request_send entering: type 26 : > ssh_mm_receive_fd: recvmsg: expected received 1 got 0 : > debug1: do_cleanup : > debug1: PAM: cleanup : > Bus error (core dumped) : > debug3: PAM: sshpam_thread_cleanup entering : : Have we dropped the ball on fixing this? : With a recent -current I see excatly the same symptoms. Yes! We have... Warner