Re: Potential problem with reading data from usb devices with ugen(4)

Hello. I've been making progress on this issue and have now run into another issue which folks may be able to shed some light on. First, where I am. I've modified the ugen(4) driver to read from devices asynchronously using a callout, allowing me to issue non-blocking read

Re: Potential problem with reading data from usb devices with ugen(4)

On Nov 5, 9:07pm, Nick Hudson wrote: } Subject: Re: Potential problem with reading data from usb devices with uge } On 05/11/2015 18:53, Brian Buhrow wrote: } > Hello. I've been making progress on this issue and have now run into } > another issue which folks may be able to shed some light

Re: NFS related panics and hangs

On 05 Nov 2015, at 21:48, Rhialto wrote: > Looking into this: > > the occurrences of nfs_reqq are as follows: > > fs/nfs/client/nfs_clvnops.c: * nfs_reqq_mtx : Global lock, protects the > nfs_reqq list. > > Since there is no other mention of nfs_reqq_mtx in the whole syssrc

Re: NFS related panics and hangs

On Thu 05 Nov 2015 at 22:30:51 +0100, J. Hannken-Illjes wrote: > This file (fs/nfs/client/nfs_clvnops.c) is part of a second (dead) nfs > implementation from FreeBSD. It is not part of any kernel. > > Our nfs lives in sys/nfs. Ok, why is it included in syssrc.tgz then? I'd say it should not be

Re: NFS related panics and hangs

[ Adding tech-kern. The relevant earlier mails start at http://mail-index.netbsd.org/current-users/2015/10/19/msg028233.html This is about a default-installed amd64 GENERIC 7.0 kernel. Replies are better in tech-kern, I think, so I set Reply-To accordingly. ] On Fri 23 Oct 2015 at

Re: NFS related panics and hangs

On Thu, Nov 05, 2015 at 10:46:17PM +0100, Rhialto wrote: > > This file (fs/nfs/client/nfs_clvnops.c) is part of a second (dead) nfs > > implementation from FreeBSD. It is not part of any kernel. > > > > Our nfs lives in sys/nfs. > > Ok, why is it included in syssrc.tgz then? > I'd say it