From owner-freebsd-arm@FreeBSD.ORG Fri Jan 18 17:19:40 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 BBB4316A469; Fri, 18 Jan 2008 17:19:40 +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 43AF013C45B; Fri, 18 Jan 2008 17:19:40 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.1/8.14.1) with ESMTP id m0IHFBVK054238; Fri, 18 Jan 2008 10:15:11 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 18 Jan 2008 10:17:47 -0700 (MST) Message-Id: <20080118.101747.-579326832.imp@bsdimp.com> To: sam@errno.com From: "M. Warner Losh" In-Reply-To: <4790D750.4060702@errno.com> References: <20080117105854.GA44923@zibbi.meraka.csir.co.za> <20080118095439.GA5677@zibbi.meraka.csir.co.za> <4790D750.4060702@errno.com> 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, des@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: Fri, 18 Jan 2008 17:19:40 -0000 In message: <4790D750.4060702@errno.com> Sam Leffler writes: : John Hay wrote: : > 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 : >> : > : > Ok, I found the problem. It looks like something changed and now the : > alignment for the char tmp[...] array in monitor_fdpass.c:mm_send_fd : > and monitor_fdpass.c:mm_receive_fd is different and the arm processors : > do not like it. Attached is my quick fix. : > : > One question that I have is if we should just fix all of these "problems" : > or should something be changed so that these things are aligned again? In : > the last month or two I have come across quite a few of these things that : > used to work on the arm and now do not anymore because of alignment : > changes. : > : > (I have cc'ed des@ because his name pitch up a lot in the openssh cvs logs. : > :-) : > : : This used to work fine so the problem is elsewhere. Sounds like a : toolchain or header change is the root cause. Or some subtle change in the kernel that isn't using the macro (or is now and didn't used to be). John, I don't suppose you'd have time for a binary search? Warner