public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Sommrey <jo@sommrey.de>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: FUSE unmount breaks serial terminal line
Date: Tue, 22 Aug 2006 20:24:41 +0200	[thread overview]
Message-ID: <20060822182441.GB6293@sommrey.de> (raw)
In-Reply-To: <20060822175411.GB31064@flint.arm.linux.org.uk>

On Tue, Aug 22, 2006 at 06:54:11PM +0100, Russell King wrote:
> 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/).
> 

Sure I did check this.  No ttyS? there.
Thanks anyway!

-jo

-- 
-rw-r--r-- 1 jo users 62 2006-08-22 19:05 /home/jo/.signature

      reply	other threads:[~2006-08-22 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-20 18:05 PROBLEM: FUSE unmount breaks serial terminal line Joerg Sommrey
2006-08-20 20:57 ` Miklos Szeredi
2006-08-20 21:28   ` Joerg Sommrey
2006-08-22  8:57     ` Miklos Szeredi
2006-08-22 15:59       ` Joerg Sommrey
2006-08-22 16:07         ` Miklos Szeredi
2006-08-22 17:43           ` Joerg Sommrey
2006-08-22 17:54             ` Russell King
2006-08-22 18:24               ` Joerg Sommrey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060822182441.GB6293@sommrey.de \
    --to=jo@sommrey.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox