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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
