From owner-freebsd-arm@FreeBSD.ORG Sat Feb 23 17:00:37 2013 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4662716B for ; Sat, 23 Feb 2013 17:00:37 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id D7341911 for ; Sat, 23 Feb 2013 17:00:29 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r1NH0TnZ082732 for ; Sat, 23 Feb 2013 10:00:29 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r1NH06VK056063; Sat, 23 Feb 2013 10:00:06 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: FreeBSD/armv6z/clang on Raspberry Pi 512MB (with U-Boot + ubldr) From: Ian Lepore To: Mats Mellstrand In-Reply-To: <010BA15C-C907-43C4-8886-2DE84CE62689@exmandato.se> References: <2659960079254C38ACD2F1DCBB7A1A19@ad.peach.ne.jp> <722ED669-A682-4F25-A65B-1E2FF8CFAA4D@exmandato.se> <20130131001553.GC67562@cicely7.cicely.de> <9E78813F3BF946A4A2FCEA2C363A847E@ad.peach.ne.jp> <016DDBBF-D502-4C76-96B5-BEE2D46FC6CC@exmandato.se> <28AF530A-E06F-480A-8A4D-242FB0019136@exmandato.se> <858C493F-151D-4811-8696-AE5932919413@exmandato.se> <010BA15C-C907-43C4-8886-2DE84CE62689@exmandato.se> Content-Type: text/plain; charset="us-ascii" Date: Sat, 23 Feb 2013 10:00:06 -0700 Message-ID: <1361638806.1185.101.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org, ticso@cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Feb 2013 17:00:37 -0000 On Sat, 2013-02-23 at 15:45 +0100, Mats Mellstrand wrote: > Hi > > I made a cut-and-paste error in my previous mail > The log file from the client side should be: > > debug1: Sending command: scp -v -f -- tess.txt > debug2: channel 0: request exec confirm 1 > debug2: callback done > debug2: channel 0: open confirm rwindow 0 rmax 32768 > debug2: channel 0: rcvd adjust 65536 > debug2: channel_input_status_confirm: type 99 id 0 > debug2: exec request accepted on channel 0 > debug2: channel 0: rcvd ext data 39 > Sending file modes: C0755 868 tess.txt > debug2: channel 0: written 39 to efd 8 > Sink: C0755 868 tess.txt > C0755 868 tess.txt > debug2: channel 0: read<=0 rfd 6 len 0 > debug2: channel 0: read failed > debug2: channel 0: close_read > debug2: channel 0: input open -> drain > debug2: channel 0: ibuf empty > debug2: channel 0: send eof > debug2: channel 0: input drain -> closed > [client] ~/Desktop% debug2: channel 0: rcvd eof <--- here the client receives an eof from the RPi, closes the connectionand return. The output from the session continues... > debug2: channel 0: output open -> drain > debug2: channel 0: obuf empty > debug2: channel 0: close_write > debug2: channel 0: output drain -> closed > debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 > debug2: channel 0: rcvd close > debug3: channel 0: will not send data after close > debug2: channel 0: almost dead > debug2: channel 0: gc: notify user > debug2: channel 0: gc: user detached > debug2: channel 0: send close > debug2: channel 0: is dead > debug2: channel 0: garbage collecting > debug1: channel 0: free: client-session, nchannels 1 > debug3: channel 0: status: The following connections are open: > #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1) > > debug1: fd 0 clearing O_NONBLOCK > debug1: fd 1 clearing O_NONBLOCK > Transferred: sent 2656, received 2488 bytes, in 0.4 seconds > Bytes per second: sent 7543.1, received 7066.0 > debug1: Exit status 1 Is there any chance you've got a logon script (.cshrc or whatever) that's echoing output when you log on, even in the case of a non-interactive session? I've had that kind of thing cause ssh and scp problems in the past. -- Ian