Return-Path: <linux-kernel-owner+willy=40w.ods.org-S1751425AbWHVRyV@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751425AbWHVRyV (ORCPT <rfc822;willy@w.ods.org>);
	Tue, 22 Aug 2006 13:54:21 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751426AbWHVRyV
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 22 Aug 2006 13:54:21 -0400
Received: from caramon.arm.linux.org.uk ([217.147.92.249]:4873 "EHLO
	caramon.arm.linux.org.uk") by vger.kernel.org with ESMTP
	id S1751425AbWHVRyV (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 22 Aug 2006 13:54:21 -0400
Date: Tue, 22 Aug 2006 18:54:11 +0100
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Joerg Sommrey <jo@sommrey.de>, Miklos Szeredi <miklos@szeredi.hu>,
       linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: FUSE unmount breaks serial terminal line
Message-ID: <20060822175411.GB31064@flint.arm.linux.org.uk>
Mail-Followup-To: Joerg Sommrey <jo@sommrey.de>,
	Miklos Szeredi <miklos@szeredi.hu>, linux-kernel@vger.kernel.org
References: <20060820180505.GA18283@sommrey.de> <E1GEuMZ-0004uq-00@dorka.pomaz.szeredi.hu> <20060820212840.GA29855@sommrey.de> <E1GFS4R-0007wJ-00@dorka.pomaz.szeredi.hu> <20060822155949.GA4268@sommrey.de> <E1GFYmi-0000Ct-00@dorka.pomaz.szeredi.hu> <20060822174329.GA6293@sommrey.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060822174329.GA6293@sommrey.de>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1381
Lines: 34

On Tue, Aug 22, 2006 at 07:43:29PM +0200, Joerg Sommrey wrote:
> On Tue, Aug 22, 2006 at 06:07:24PM +0200, Miklos Szeredi wrote:
> > > Tested both gphoto2 and gtkam without any problems. There is no impact
> > > on the serial lines.
> > > 
> > > NB: The *real* trouble I have is with ntpd and a reference clock
> > > attached to /dev/ttyS1.  ntpd enters a busy loop reading ttyS1, stops
> > > working and eats up 100% CPU.  
> > > 
> > > Thanks for your investigations.  Any other idea?
> > 
> > Try 'killall -9 gphotofs' and then the 'fusermount -u'.
> > 
> > Does that have the same effect?  If so, after which does the serial
> > line die?
> 
> Here are the results and another insight:  only the first serial device
> open for reading is affected.  I.e. if ttyS0 is open for reading,
> ttyS1 doesn't break.  If ttyS0 is not open, then ttyS1 breaks.  This
> happens when gphotofs gets killed (or with fusermount -u without
> killing).

Have you checked to see what files gphotofs has open?  (Check in
/proc/<pid>/fd/).

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
-
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/