Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S271333AbTHMCB4 (ORCPT ); Tue, 12 Aug 2003 22:01:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S271329AbTHMCBz (ORCPT ); Tue, 12 Aug 2003 22:01:55 -0400 Received: from pl734.nas911.n-yokohama.nttpc.ne.jp ([210.139.39.222]:18631 "EHLO standard.erephon") by vger.kernel.org with ESMTP id S271324AbTHMCBw (ORCPT ); Tue, 12 Aug 2003 22:01:52 -0400 Message-ID: <3F399C8E.7070109@yk.rim.or.jp> Date: Wed, 13 Aug 2003 11:03:58 +0900 From: Chiaki User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: ja, en-us, en MIME-Version: 1.0 To: Chiaki CC: Paul Blazejowski , wb , "Justin T. Gibbs" , Patrick Mansfield , Andrew Morton , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org Subject: Re: Badness in device_release at drivers/base/core.c:84 References: <20030801182207.GA3759@blazebox.homeip.net> <20030801144455.450d8e52.akpm@osdl.org> <20030803015510.GB4696@blazebox.homeip.net> <20030802190737.3c41d4d8.akpm@osdl.org> <20030803214755.GA1010@blazebox.homeip.net> <20030803145211.29eb5e7c.akpm@osdl.org> <20030803222313.GA1090@blazebox.homeip.net> <20030803223115.GA1132@blazebox.homeip.net> <20030804093035.A24860@beaverton.ibm.com> <1060021614.889.6.camel@blaze.homeip.net> <1352160000.1060025773@aslan.btc.adaptec.com> <5793.199.181.174.146.1060050091.squirrel@www.blazebox.homeip.net> <3F2F84D2.8000202@nospam.com> <3F2FD6ED.1005BB2C@yk.rim.or.jp> <1060189107.887.7.camel@blaze.homeip.net> <3F3138C7.2040404@yk.rim.or.jp> In-Reply-To: <3F3138C7.2040404@yk.rim.or.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1942 Lines: 60 Chiaki wrote: >> Kermit was very helpful but due to my inexperience i was not able to get >> the log due to Linux's box resetting of /dev/ttyS0 when booting, i would >> get disconnect... >> > > Oh, I forgot some details. You might be able to > circumvent the problem by > issueing > set carrier-watch off > > I use the direct-wire connetion with > a device from a Linux PC's tty port using ckermit and > so let me check the setup again tomorrow at the office. Sorry for the delay. Below is the copy of kermit startup file that I use for talking to a device that does not echo back characters. I also power-on/off the device while connecting kermit to it, and I don't think I got kicked off. : so set carrier-watch off (abbreviated below as set carrier off) should get you going talking to a linux box via serial line during booting. (However, I believe you already captured the necessary log using uucp suite of tools.) set line /dev/ttyS0 set speed 38400 set carrier off <- This is key to the disconnect problem. set terminal echo local <--- lines below here are for local echo back set terminal newline on set terminal cr-display crlf >> Thanks a lot for suggesting ckermit. You are very welcome. From a happy Kermit user. If you need to ask elaborate ckermit questions, comp.protocols.kermit.misc is where the original developers of Kermit hang around. Happy Hacking, Ishikawa, Chiaki -- int main(void){int j=2003;/*(c)2003 cishikawa. */ char t[] =" @abcdefghijklmnopqrstuvwxyz.,\n\""; char *i ="g>qtCIuqivb,gCwe\np@.ietCIuqi\"tqkvv is>dnamz"; while(*i)((j+=strchr(t,*i++)-(int)t),(j%=sizeof t-1), (putchar(t[j])));return 0;}/* under GPL */ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/